Give every blog post and page its own Open Graph image
Stop sharing every link with the same generic preview. Each page gets an OG image with its own title, in bulk for old pages and automatically for new ones.
50 free credits. No credit card required.
When
Your CMS
Page list or new post

Templated
Render PNG
1200 × 630 OG image
Then
Your CMS
og:image tag
At a glance
When a site uses one default og:image, every shared link looks the same on LinkedIn, Slack and X, and none of them says what the page is about.
Fix the pages you already have in one batch: list them in a spreadsheet and render an image per row. Then cover new posts from now on, either by calling the API when you publish or by sending your CMS's publish webhook to Templated.
- Trigger
- Your CMS: Page list or new post
- Output
- PNG, 1200 × 630 OG image
- Delivered to
- Your CMS: og:image tag
- Run it with
- Spreadsheet generation, REST API, Inbound webhooks
- Cost
- 1 credit per image (each page of a multi-page template counts as one)
- Free plan
- 50 credits, no credit card required
How it works
Three steps, from the event to the finished file.
- 1
List the pages, or catch new ones
A spreadsheet of titles for the backlog. Your build script or CMS webhook for new posts.
- 2
Templated renders 1200 × 630
Title, category and author fill your OG template.
- 3
Set the og:image
Put the render URL in the page's
og:imageandtwitter:imagetags or the CMS's social image field.
Map your data to the template
Each dynamic layer in your template gets its value from one field. Name your layers like this, or map whatever names you use.
| Template layer | Comes from | Example |
|---|---|---|
| title | Page title | Pricing that scales with your team |
| category | Section or category | Guides |
| url | Path or domain | yoursite.com/pricing |
Text layers take text, image layers take image_url. You can also change colors, hide layers or swap fonts per render. See every layer property .
Templates for this workflow
Start from one of these and make it yours in the editor, import a Canva design, or describe one to the AI template generator.
When to use it
- Sites still sharing one default preview image.
- Docs, changelogs and blogs with many pages.
- Programmatic SEO pages that need unique previews at scale.
Tips
- Render once per page and store the URL. Render URLs don't expire, so there is no need to render on every request.
- Keep titles under about 60 characters on the image, or turn on auto-fit for the title layer.
- After you deploy, check the preview with LinkedIn Post Inspector, since networks cache old images.
How to run it
Pick the tool you already use. The first one is the quickest way to set this up.
Spreadsheet generation
In the dashboard, no code
- Export your page titles and URLs to CSV (from your sitemap, CMS or SEO tool).
- Upload the file in Spreadsheet generation, map the title column and render the batch.
- Download the ZIP and add the images to your site, one per page.
REST API
From your own code
- In your build or publish step, call
POST /v1/renderwith the post title. - Save the returned URL with the post (front matter, CMS field or database).
- Output it in the
og:imagemeta tag.
curl -X POST https://api.templated.io/v1/render \
-H "Authorization: Bearer $TEMPLATED_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"template": "YOUR_TEMPLATE_ID",
"format": "png",
"layers": {
"title": {
"text": "Pricing that scales with your team"
},
"category": {
"text": "Guides"
},
"url": {
"text": "yoursite.com/pricing"
}
}
}'Inbound webhooks
A URL any app can call
- Create a Templated inbound webhook on your OG template and map the title path from your CMS's publish payload.
- Add the webhook URL to the CMS's publish webhooks, and a callback URL to receive the render and save it to the post.
Step-by-step guides
Related workflows
Share every new blog post with its own branded image
Publish the article and you are done: the RSS feed triggers a branded share image with the title, and the post goes out on your channels.
Run with: Zapier, Make, n8n n8n template
Announce every GitHub release with a branded card
Tag the release and the announcement is done: a card with the version and the highlights goes to your community channels.
Run with: REST API, n8n, Zapier
Personalize email images for every contact
An image with the reader's own name in it: one render per contact, its URL saved to a contact field, dropped into the email with a merge tag.
Run with: Make, Zapier, n8n, REST API
Set up your first workflow today
Create a template, connect your tool and render your first image in minutes.
50 free credits. No credit card required.