SleekPixel for Otter Blocks
SleekPixel renders a 1200 by 630 OG image on save for any post built with Otter Blocks. Reads title, category, and any custom field. Lives alongside Otter without modifying it.
♾️ Lifetime License available
Otter extends Gutenberg, the share preview needs its own engine
Otter Blocks is a free plus Pro block library from ThemeIsle, often paired with the Neve theme but theme-agnostic in practice. Sites built with Otter cover most marketing sections natively in Gutenberg and inherit a clean front-end. The share preview is the gap, since Otter does not generate per-post OG images and most sites fall back to the SEO plugin's global image.
SleekPixel covers the share layer at the post-meta level. It hooks save_post on any post type, reads native fields plus ACF, Meta Box, and any other custom field, and renders a 1200 by 630 PNG. Otter keeps composing the visible page, SleekPixel writes the og:image meta tag for the document head. The two systems update independently because they do not share code paths.
For sites pairing Otter with the Neve theme, the SleekPixel template can match the same Customizer palette so the share card stays visually aligned with the rest of the site without any extra wiring.
Workflow
From Otter save to share image
Enable post types
Map fields
Save the post
Meta tags update
Output
Sample card for an Otter post
Rendered from the post's title, category, and brand color. Same template, every Otter post.
Comparison
Otter default versus SleekPixel
SEO plugin fallback
- Every Otter post falls back to the SEO plugin's global OG image
- Block-level styles configured in Otter never reach the share preview
- Custom fields surfaced in Otter dynamic content stay invisible to the OG image
- Brand refresh leaves all past share cards in place
- Per-post Canva exports do not scale to a full Otter site
SleekPixel
- Hooks save_post for any post type Otter renders for
- Reads ACF, Meta Box, and native fields used in Otter dynamic content
- Self-hosted render with no per-image fees
- Template export moves between Otter sites
- Bulk regenerate covers a full Otter site after a refresh
Features
What SleekPixel gives you for Otter Blocks
Block agnostic
Runs on save_post regardless of which Otter blocks compose the page. The image renders from post-level data, not the block tree.
Dynamic content aware
Reads the same ACF, Meta Box, and native fields Otter dynamic content uses, available inside the SleekPixel template.
Theme palette match
Pair Otter with Neve and pick the same Customizer hex values in SleekPixel. The share card stays visually aligned with the rest of the site.
Use cases
Where Otter sites benefit most
Otter plus Neve blogs
Per-post share cards on the standard Otter plus Neve stack. Editors keep using the Gutenberg flow.
Marketing landing pages
Otter handles the body, SleekPixel handles the share preview pulled from page title and campaign tag.
Resource libraries
CPT detail pages each get cards using topic name and any field surfaced in the Otter layout.
The bigger picture
Why Otter sites need automated share cards
Otter is the broad block library most often deployed by Neve users and by sites that want richer Gutenberg blocks without leaving WordPress core. The plugin covers feature, hero, pricing, contact form, and most of the standard marketing-page sections, and the design system stays consistent across templates. The share preview is outside that scope.
Otter does not generate per-post OG images, so the share preview falls back to the SEO plugin's global image, which makes every URL on the site share with the same fallback. SleekPixel addresses that with its own template engine sitting at the post-meta layer. Define a card layout once with dynamic fields, render automatically on save, refresh as data changes.
Both layers update independently and do not share code paths, so version updates on either side ship without coordination. For sites pairing Otter with Neve, matching the Customizer palette in SleekPixel keeps the share card visually consistent with the rest of the site.
Questions
Common questions about SleekPixel for Otter Blocks
It runs on save_post, after Gutenberg saves. There is no Otter block to add. The image generates server-side from saved post data.
 Yes. Otter Pro adds extra blocks and dynamic content options. SleekPixel reads from post-level fields, not from the block tree, so Pro features in the body do not change the share card.
 Yes. Otter is theme-agnostic and so is SleekPixel. The Otter plus Neve stack is one common pairing, and the SleekPixel template can match Neve's Customizer palette.
 Yes. ACF, Meta Box, and native custom fields are available in the SleekPixel template picker.
 SleekPixel writes only og:image and twitter:image. Title and description tags stay with the SEO plugin.
 No. The render runs once at save time and stores a static PNG. Nothing additional fires at view time.
 Yes. Bulk regenerate walks every post in enabled post types and re-renders share cards.
 No. SleekPixel reads post meta and writes meta tags, neither of which depends on Otter internals.
 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 checkout