SleekPixel for Blocksy Companion sites
Blocksy Companion already exposes a social share filter on the post head. SleekPixel taps into it, reads the post title, excerpt, featured image and author from wp_posts and wp_postmeta, then writes a branded card into the og:image meta on every share.
♾️ Lifetime License available
A Blocksy site deserves its own social card
Blocksy ships with a fast, opinionated typography system and a palette token model that the rest of the theme respects. The Companion plugin adds header and footer builders, content blocks, and a social share module that filters the og:image meta on the post head. The piece that's still missing on most Blocksy sites is the image itself. The Companion will happily emit a meta tag, but only if something else generates the picture.
SleekPixel is the something else. The plugin reads the post title, excerpt, featured image, author and category straight from wp_posts and wp_postmeta, composites them into a template that mirrors your Blocksy palette, and writes a PNG to the uploads directory. On save, the new URL flows through Blocksy Companion's filter and ends up in the og:image meta that the share scraper actually reads.
The work is one-time. Pick fonts that match your Blocksy typography preset, pick an accent that matches your primary palette token, and decide which post fields render. Every post from then on gets its own card on save, no manual export step in the loop.
Workflow
Blocksy install to per-post cards
Install alongside Blocksy Companion
Pick a Blocksy template
Map post fields to slots
post_title, post_excerpt, post_author, featured image and the first category from wp_term_relationships.
Save a post in WordPress
Output
Sample Blocksy blog post card
Rendered from a real Blocksy post using the Companion social share filter, with title, excerpt, author and accent pulled from the post fields.
Comparison
Default Companion share vs SleekPixel for Blocksy
Companion meta, theme logo
- Companion filter emits the meta tag but does not generate per-post images
- Default fallback is the theme logo so every post shares with the same picture
- Excerpt and author never make it into the share preview
- Featured image gets stretched into Open Graph aspect with hard crops
- Brand palette and typography stop at the post page, never reach the share
SleekPixel
-
Hooks the existing
blocksy:social_share:og_imagefilter, no theme edits -
Reads
wp_posts,wp_postmetaand post taxonomy directly - Template uses Blocksy palette tokens for accent, foreground and surface
- Featured image composited with safe-zone padding, no hard crops
- Per-post PNG written to uploads on save, no background polling
Features
What SleekPixel gives you for Blocksy Companion
Matches your palette
The template picks up Blocksy's primary, accent and surface tokens so the share preview looks like an extension of the site, not a generic share card with mismatched colors and typography.
On the Companion filter
SleekPixel registers on the same social share filter Blocksy Companion already uses, so no custom head injection or theme child edits are required to get the og:image meta wired up.
Featured image as art
The featured image stays as art inside the layout, not a stretched background. Posts without a featured image fall back to a typographic card built from the title and excerpt.
Use cases
Where Blocksy sites get the most lift
Editorial Blocksy blogs
Editorial Blocksy sites publish weekly. Each post deserves its own share card with the right author and topic, not a recycled logo image.
Agency portfolio sites
Agencies ship Blocksy starter sites to clients. SleekPixel ships in the same starter and gives the client per-page social previews from day one.
Companion-powered landings
Landing pages built with Blocksy Companion content blocks share into Slack and email more than the blog. Each landing needs its own preview.
The bigger picture
Why Blocksy sites get more out of per-post cards
Blocksy is a fast theme and Blocksy Companion is the typical plugin that ships alongside it, so a Blocksy site already has the surface area to receive per-post social images. The piece that breaks the loop on most installs is that nothing actually generates the image. The Companion's social share module filters a meta tag, but if the filter receives an empty string the scraper falls back to the site icon.
The site icon is the same across every post, so every share looks identical. Readers learn to ignore Blocksy site shares the way they ignore generic logo previews. SleekPixel restores the per-post signal.
Each post emits a card that names the post, shows the featured image, and carries the typography decisions the rest of the site already enforces. The cost is the price of the plugin and a one-time template setup. The benefit is that every share from the Blocksy site looks like it came from the Blocksy site, every time.
Questions
Common questions about SleekPixel for Blocksy Companion
Both. SleekPixel hooks into the social share filter that ships in Blocksy Companion free and is still present in the Pro version. No code differences between the two for the og:image path SleekPixel cares about.
 Only if you set a per-post manual social image inside Blocksy. That manual image wins, by design. Posts without a manual override get the SleekPixel-generated card automatically, with no extra editor work.
 
Yes. The Blocksy preset reads your global palette and applies blocksy_color_1 as the accent and blocksy_color_5 as the foreground by default. You can remap which token feeds which template slot.
The template falls back to a typographic card built from post_title and an accent block. No broken image placeholders show up on the share, and the layout stays readable on every aspect ratio the scrapers crop to.
Yes. The same 1200 by 630 PNG works as og:image for Facebook, LinkedIn and Slack, and as the twitter:image for Twitter and X with the summary_large_image card type, which is what Blocksy Companion emits by default.
Yes. SleekPixel matches templates by category, tag or any taxonomy stored in wp_term_relationships. So a 'Case studies' category can render a different card style than a 'News' category on the same Blocksy site.
On every save_post for a published post, SleekPixel re-renders the card and overwrites the PNG. Companion's filter already references the same URL so the scraper picks up the new image on the next share recrawl.
No. Rendering happens on save, not on the request that loads the post. The frontend just reads the og:image meta Companion already emits. Pagespeed scores stay where they were before SleekPixel was installed.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkoutBrowse more
- Threads profile banners
- Twitch overlay
- Twitch offline banners
- Odnoklassniki banners
- Facebook event covers
- Weibo post images
- Instagram carousel slides
- Patreon cover images
- Twitch panel images
- Lens Protocol posts
- Xiaohongshu cover images
- Telegram bot avatar
- YouTube community images
- Kick channel banners
- Behance banner