Webflow Integration - Dynamic CMS Images
Generate an OG image for every Webflow CMS item through Zapier or Make. Map collection fields to a template, write the URL back to the item. Free tier included.

imejis renders an image for every Webflow CMS item and writes the URL back into the collection. You design the template once, map collection fields onto it, and each published item gets its own link-preview image, thumbnail or product shot without anyone opening a design tool.
There is no first-party Webflow connector. The link runs through Zapier or Make, both of which have native Webflow CMS triggers and an Update Item action for the write-back.
What you can automate
- An OG image per blog post: title, category and author straight from the collection, so shared links stop looking generic.
- Thumbnails that stay in sync: rename an item and the image follows.
- Product shots from a collection: price and badge pulled per item.
How to connect
-
In Zapier or Make, trigger on a Webflow Collection Item Created or Updated event.
-
Add an HTTP action pointing at your design's render endpoint, with
?delivery=hostedso you get a stored URL rather than raw bytes:https://render.imejis.io/v1/<designId>?delivery=hosted -
Send the
dma-api-keyheader and POST the collection's fields as overrides. -
Finish with Webflow's Update Item action, writing the returned URL into the item's image field. Publish the site, and the CMS serves it as the
og:image.
The write-back is the step people skip. Without it the image exists but Webflow never points at it.
A worked example
A 1200x630 design, the Open Graph size, with four dynamic fields: title,
category, author and read_time.
{
"title": { "text": "Why we moved our CMS image pipeline off headless browsers" },
"category": { "text": "INFRASTRUCTURE" },
"author": { "text": "Priya Raman" },
"read_time": { "text": "11 min read" }
}Long titles are the thing that breaks OG images
A CMS title is whatever the author typed. The usual result is text running off the canvas or clipping mid-word, which only shows up once the link is shared.
Set minFontSize and maxFontSize on the title layer and the renderer shrinks
the text to fit instead of overflowing. On this design the title sits at 68px
and is allowed down to 40px. An 85-character headline wraps to three lines and
drops a size; a six-word one stays large. Same template, no per-post babysitting.
Field mapping
| Webflow CMS field | imejis field | Override key |
|---|---|---|
| Name (plain text) | Title | title.text |
| Category (reference) | Category | category.text |
| Author (reference) | Author | author.text |
| Read time (number) | Read time | read_time.text |
| Main image (image) | not overridden | write the render URL back here |
What it costs
One render per item, charged once, because ?delivery=hosted stores the result
and Webflow then serves that stored URL. Only a re-publish of the item spends
another render. A 300-post blog costs 300 renders to backfill, and the free tier
is 100 renders a month (as of October 2026). See the pricing page.
Going further
- The longer walkthrough is in Webflow + image API: auto-generate CMS images.
- Check how a URL will actually unfurl with the free OG image tester.
- To call the endpoint from code instead of an automation tool, see the API reference.