Lens Protocol publications often reference external content. A post on Hey or Orb that links to your essay, product, or release notes surfaces a preview based on the standard og:image and og:title meta tags. WordPress sites that use a static theme image surface the same flat preview on every Lens post, which kills the recognition that Lens clients rely on as you scroll.

SleekPixel renders a per-post PNG and writes the og:image meta tag for every post. When you link from a Lens publication to a WordPress URL, the client pulls the freshly rendered image with the post title, author handle, and any campaign mark you set.

The pipeline is shared with the rest of your OG image system, so each Lens-referenced post is a side effect of saving the post rather than a separate design task.

Lens publications draw a tighter community than open social platforms, and the cost of an unrecognisable preview is higher because the audience tends to be the same people across multiple sessions. A reader who saw your essay preview last week and sees the same flat logo this week may not realise it is a new piece. Per-post previews keep each cross-reference visually distinct and on brand.

Because SleekPixel uses standard OG meta and renders at save time, the previews work in Hey, Orb, and any future Lens client that respects og:image without extra integration. A rebrand re-renders the archive so older cross-references keep matching the current system.