Webflow is the design tool of choice for a lot of studios and marketing-led brands. Visual editor, real CMS collections, hosted reliably. The friction shows up when a collection item needs a unique og:image. Webflow lets you set an OG image per item, but the only practical way to do it is to upload a hand-designed PNG to each item, which means a design queue or a sad reuse of the same default.

A more sustainable pattern is to pair Webflow with WordPress as a quiet image-rendering layer. The WordPress site is private, holds a mirror of the Webflow collection, and exists only to render the share images. A small sync (Make, Zapier, custom REST script) pushes each Webflow CMS item into a WordPress post. SleekPixel renders the PNG, and a tiny Webflow embed or DNS-served URL points the Webflow site's og:image tag at the rendered file.

From the visitor's perspective, the Webflow site is unchanged. From the social platform's perspective, every collection item URL now resolves to a per-item card with title, category, headline detail and brand mark. The design team controls the template; the marketing team adds items in Webflow; the cards just exist.

Webflow is excellent at what it does, but per-item OG image rendering is not in the bag. The platform expects designers to upload a hand-made PNG per item, which is unrealistic across hundreds of case studies or blog posts. The result is one of two patterns: either every Webflow item shares with the same default OG image, or a small handful of flagship items have custom art and the long tail reuses the default anyway.

Both patterns leak conversions on social, especially for studios and agencies whose entire pipeline runs on the visual quality of their portfolio shares. Adding WordPress as a quiet rendering layer is unconventional but it solves the problem cleanly. The WordPress install is invisible to the public, the editor never touches it, and the only thing it produces is a stable URL per PNG that Webflow's og:image tag references.

Marketing teams keep adding items in Webflow, designers keep iterating in Webflow, and the share previews quietly maintain themselves across the whole CMS. The investment is a one-time setup of a sync and a template; the return is professional-grade share previews on every URL the Webflow site will ever publish.