Store-first workflow
Start with product-share templates for stores, then reuse the same system for blog posts, articles, and website pages.
Public documentation
Store-first Open Graph images from beautiful templates and automate them with URL parameters.
OGDynamic gives you a template-driven workflow for social previews. Start with product pages for stores, customize the important fields, then pass dynamic values from your app, CMS, ecommerce backend, or publishing pipeline. The same approach also works for blog posts, articles, and standalone website pages.
Field-level customization
Update product names, prices, descriptions, badges, image URLs, and structured attribute rows to match the content you publish.
GET and POST delivery
Use query parameters for simple GET requests or send the same fields as a JSON body with POST when that integration fits better.
Brand-consistent output
Keep one visual system across product launches, blog posts, articles, changelogs, and landing pages.
Quick start
The simplest workflow is: template first, content second.
For most teams, that means product templates first, then editorial and web-page templates after the store workflow is stable.
01
Choose a store-ready template
Pick the closest starting point from the template library for product pages first, then adapt it for blog posts, articles, or standalone pages.
02
Map your content fields
Set the content you want to control, such as product title, price, description, badge text, logo image, or attribute items.
03
Publish with GET or POST
Use the generated image directly in your metadata flow with GET parameters, or send a JSON payload with POST from your store, CMS, or app.
Customization model
Templates expose structured fields you can edit or drive from dynamic input.
The editor supports a small set of reusable content primitives. That keeps templates flexible without turning each image into a one-off design file, whether you are publishing product pages, articles, or website content. Alongside text, image, and attribute fields, templates can also expose `tag` content as an array of strings.
Common content fields
Text
Product names, badges, categories, article titles, author names, price labels
Tags
Array of strings for pills, feature tags, categories, benefit highlights, or quick metadata chips
Image URL
Logos, product shots, hero visuals, author avatars, feature imagery
Attributes
Price/spec rows, feature lists, ingredient highlights, metadata pairs
Dynamic URL pattern
Send published template fields through GET query parameters or a POST JSON body.
GET example
https://cdn.ogdynamic.com/d/template-id?title=Prestige+GMT+Automatic&price=%242400&description=Luxury+watch+for+global+travelers&brand=OGDynamicRecommended mapping
title=PrestigeGMT price=2400 description=LuxuryWatch badge=Accessories brand=OGDynamic image=watch.png tags[]=FreeShipping&tags[]=NewArrival specs[][label]=CaseSize&specs[][value]=42mmPOST JSON example
{ "title": "PrestigeGMT", "price": "2400", "description": "LuxuryWatch", "badge": "Accessories", "brand": "OGDynamic", "image": "watch.png", "tags": ["FreeShipping", "NewArrival"], "specs": [{ "label": "CaseSize", "value": "42mm" }] }Field names should follow the keys exposed by your template. Keep that mapping stable whether you send data through GET query parameters or a POST JSON body, and your integration stays predictable.
Recommended implementation pattern
Start with a reusable template per format: product, blog post, article, or landing page.
Use clear parameter names that mirror the fields your template exposes.
Keep dynamic values content-only and let the design system stay fixed.
For stores, lock layout and styling while changing product-specific fields like title, price, specs, and image.
FAQ
Do all templates use the same query parameter names?
No. Parameters should match the fields exposed by a specific template. A product template, blog template, and website template can each map different field names.
Can I use OGDynamic for fully automated OG images?
Yes. The intended workflow is to create a design once, then pass dynamic values from your store, CMS, product database, or publishing pipeline.
What kind of content can I customize?
Templates can expose text, textarea, color, image URL, and attribute-based content, which covers most product, editorial, and website preview use cases.
Is OGDynamic only for stores?
No. Stores are the main target, but the same workflow works for blog posts, articles, landing pages, changelog pages, and standalone websites.
Next step
Start with a template, then turn it into a reusable OG image endpoint.
If you need help shaping a template system for your store, blog, article, or CMS workflow, use the builder or reach out for support.