Framer can automatically assign an Open Graph image to every CMS page, but its documented native workflow does not create new artwork from an item’s text. Store an image in a CMS Image field, map that field to the page’s Social preview setting, and validate the published metadata. If you need a newly rendered, template-driven image for each item, add a custom integration or image-generation service and test the result with the actual social crawlers that matter to you.
What “auto-generate” means in Framer
There are two different jobs that are often called auto-generation:
- Automatic assignment: Framer selects the correct, already-uploaded image for each CMS item. This is the native workflow documented for CMS pages.
- Artwork generation: A system renders a new image from fields such as a title, author, price, or category. Framer’s CMS instructions do not describe creating that artwork automatically.
Framer’s CMS product material describes automatic SEO fields, including dynamic titles, descriptions, schema, and Open Graph tags. That does not mean an image file is generated. For the image itself, the detailed workflow still requires an image in the CMS.
Use Framer’s native CMS workflow
-
Create an image field
Open the relevant CMS collection and add an Image field, for example Cover image. Upload or select an image for every item that can be shared. An item without a value in this field has nothing for Framer to use as its social image.
Free tools Windows power users keep installed
One-click scans. No signup required.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Map the field to Social preview
Open the CMS detail page and its Page Settings. Under Page images, find Social preview, choose CMS Variables, and select the image field you created.
-
Prepare the image canvas
Framer recommends a 1200 × 630 pixel aspect ratio for social previews. Keep logos, headlines, and other essential content near the center because services can crop or resize the image differently.
-
Preview and publish
Use Framer’s Link Preview tool to inspect how the title, description, and image may appear on services such as Google, X, LinkedIn, and Slack. Publish the site, then open the live URL and inspect it as a recipient would. A preview inside the editor is not a substitute for checking the published page.
How the metadata works
Open Graph places the image in page metadata as a URL; it is not an image embedded in the post itself. The protocol defines four required properties for every page: og:title, og:type, og:image, and og:url. The specification recommends og:image:alt when an image is supplied.
For a CMS page, the effective chain is:
- The item stores an image in the CMS Image field.
- Framer’s Social preview variable reads that field.
- The published page emits an Open Graph image URL and the other page metadata.
- A sharing service fetches the URL and builds its card.
Inspect the final HTML or metadata response for the published URL. Confirm that og:image points to the intended asset, that the URL is reachable without an editor session, and that the page’s canonical URL and title describe the same item.
When you need newly generated artwork
If every card must contain a dynamically composed background, title, badge, or data value, treat that as a separate rendering pipeline. Framer documents custom code and plugins as extension points for JavaScript, structured data, meta tags, automation, content generation, and integrations. Those options do not prove that a browser-side script will change metadata for every social crawler: many crawlers do not execute client-side JavaScript the way a browser does.
Use a rendering service or API
Bannerbear documents template-driven images, APIs, signed or simple URLs, and an instant-URL use case for Open Graph images generated when a page is viewed. That makes it a plausible external option when you truly need generated artwork. The available documentation does not establish a native Framer integration, a specific Framer configuration, or crawler compatibility for your implementation. Treat the service as an external dependency, generate a stable URL, place that URL in the published page metadata, and verify it on the live page before adopting it.
Decide where generation occurs
- At content publish time: Generate one image per CMS item and store its URL. This gives you a stable asset and predictable cache behavior.
- At request time: Use a signed or parameterized image URL. This can reduce editorial steps, but a changed title or template may produce a new URL and trigger cache issues.
- In a build or automation job: Generate images when a CMS record changes, then update the item’s image field. This keeps Framer’s native mapping while moving artwork creation outside Framer.
Validate changes and handle caching
Social platforms may cache an earlier image after you publish a change. Framer specifically cautions that a cached preview can make a correct CMS mapping look broken. Check the live page first, then allow the target service to refresh its cache. Test the exact URL you intend to share rather than relying only on an old message or an editor preview.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallValidation checklist
- The CMS item has a non-empty image field.
- The Social preview variable points to that field, not to a static fallback.
- The image is approximately 1200 × 630 and keeps important content centered.
- The published HTML contains
og:title,og:type,og:image, andog:url. og:imageresolves publicly and returns the expected image format.og:image:altdescribes the image when your implementation supplies it.- Framer Link Preview and the target social service show the current URL after cache refresh.
Common failure modes
The preview shows no image
Usually the CMS field is empty, the wrong field is selected, or the page has not been republished. Populate the item, recheck Page Settings → Page images → Social preview → CMS Variables, publish, and inspect the live metadata.
The old image still appears
First verify the live page’s og:image. If it is correct, the sharing platform is likely serving a cached card. Use its URL-preview or debugger workflow where available and allow time for refresh; changing the CMS mapping repeatedly will not necessarily invalidate an external cache.
The image is cropped badly
Re-export at the recommended 1200 × 630 ratio and move critical text toward the center. Avoid putting essential information at the extreme edges, where a service’s card layout may crop it.
A custom script works in a browser but not in social cards
Do not assume a crawler executes the script. Put the final image URL in server-delivered metadata, publish, and inspect the HTML returned to an unauthenticated request. If you need generated artwork, generate it before the crawler requests the page.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The generated URL fails intermittently
Check whether it requires authentication, expires too quickly, blocks crawler user agents, or depends on client-side rendering. Prefer a stable publicly reachable URL, log generation failures, and test from an external network before launch.
Rank #4
Performance, reliability, and maintenance
Native CMS assignment is the smallest moving system: editors manage one image field and Framer emits the mapping. External generation adds a template, an API or URL contract, credentials, failure handling, and another cache. Decide who owns template updates and what happens when generation fails. Keep a fallback image available for items whose generated asset is unavailable, and monitor the published URL rather than only the generation job.
For large collections, define naming and versioning rules for generated assets. A content change should either update the image URL or intentionally preserve the previous artwork. Document the target sharing services and their refresh behavior so editors know why a newly published image may not appear immediately.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If your immediate need is to capture a published Framer page for QA, documentation, or an automation pipeline, ScreenshotNeo provides a website screenshot API and MCP server. It is not an Open Graph artwork generator; it captures the rendered page after you publish it.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteA single request returns PNG, JPEG, WebP, or PDF. Cookie and consent banners, newsletter popups, and chat widgets are removed before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers identify the page verdict and billing result. Its MCP tools—take_screenshot, get_page_info, and capture_pdf—let Claude, Cursor, or another MCP client request captures.
cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);See the ScreenshotNeo documentation for options such as full-page capture, CSS-selector targeting, device presets, custom headers, cookies, waits, blocking rules, PDFs, caching, signed links, asynchronous jobs, bulk capture, and the usage API. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Create a free ScreenshotNeo account to test a published Framer page.
Best Value
FAQ
Does Framer create a unique image from each CMS title?
Not in the documented native Social preview workflow. It assigns an image already stored in the item’s CMS Image field.
Can I use a different image for each CMS page?
Yes. Give each item its own image value and map the collection’s Social preview setting to that field.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Is 1200 × 630 mandatory?
No. It is Framer’s recommended ratio for social previews. Other dimensions may work, but they increase the chance of unwanted cropping.
Why does Link Preview differ from a platform card?
Services can cache metadata and apply different crop, size, and refresh rules. Validate the published HTML and the target platform separately.
The Bottom Line
Use Framer’s CMS Image field and Social preview variable when you need automatic per-item assignment. Use a pre-generation pipeline or external renderer only when the requirement is new artwork from data, and verify the final published metadata before relying on it.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
