Template · 5 min read
Changelog OG image template
A free changelog OG image template for release notes and product updates. Add the version, date, and summary, then export at 1200 x 630.
Updated
The short answer
Use a 1200 x 630 card with the version number as the largest element, the release date as a small label, and a one-sentence summary a customer would understand. Keep the layout identical across releases so the series is recognizable. Export a PNG or JPG under 1 MB.
- Canvas
- 1200 x 630
- Safe area
- 64 px inset
- Headline
- 6-10 words
- File size
- Under 1 MB
- Cost
- Free, no account
- Editable
- In the browser
A changelog card is part of a series, so consistency matters more than novelty. The version number is the recognizable element; the summary is the reason to click. Keep both in the same place every release and the archive starts to look like a publication instead of a pile of announcements.
Why this layout works
ogimg.in
- Addedbulk generation from CSV and JSON input
- Improvedtemplate gallery renders at 2x
- Fixedcrop warning when the canvas ratio does not match
The version number is doing the work of a series mark. It should be large enough to read at thumbnail size and always in the same position. The date is secondary. The summary should pass the "would a customer say this?" test; internal commit language fails it immediately.
What to put on the card
- Version:
v2.4,2026.10, or the release name. Keep the format consistent. - Date: a short label such as
October 2026or27 Oct 2026. - Summary: one sentence in customer language.
Brand kits now apply in one clickbeatsRefactored brand kit application. - Brand mark: the product name or domain, in the same place as the rest of the series.
- Visual: optional. A before/after crop or a single UI detail. Do not show the whole app.
ogimg cardsIf the release is about a number, use the metrics layout: one figure, one label, one source. A card with three numbers has no number. If the release is about a flow, show the before/after in two small panels rather than one dense screenshot.
Size and export
| Setting | Value | Why |
|---|---|---|
| Canvas | 1200 x 630 | The common link card |
| Version | 96-140 px | The series mark; it has to read at thumbnail size |
| Summary | 36-44 px | Secondary, but still legible |
| Format | PNG | Flat colour and crisp type |
| File size | Under 1 MB | Fast loading in a feed |
How to make it yours
- 01Open the changelog template.
- 02Set the version and date.
- 03Write the summary in customer language.
- 04Add a visual only if it proves the change.
- 05Keep the layout identical to the previous release.
- 06Export and add the card to the release page.
Common mistakes
- Using internal commit language in the summary.
- Changing the layout every release, so the series loses recognition.
- Making the date larger than the version.
- Showing a full app screenshot for a one-line change.
Frequently asked questions
What size is a changelog OG image?
1200 x 630 pixels with a 1.91:1 ratio. Use the same size for every release so the archive has a consistent rhythm.
What should a changelog card say?
The version, the date, and one sentence a customer would understand. Put the version in the largest type and the summary underneath. Avoid internal language and commit messages.
Should every changelog entry have its own image?
Yes, if you share the entries individually. Use the same layout and change the version, date, and summary. A series should be recognizable at a glance.
Can I use a screenshot for a changelog card?
Only if the screenshot proves the change. Crop to the before/after or the single panel that matters. A full app window is too dense for a card.
Do I need a changelog card for an internal release?
No. Make cards for releases customers can see. Internal refactors do not need a public card unless they change something a customer would notice.
Sources and further reading
Written and maintained by GxAditya
The person who builds ogimg.in. Last updated . 5 min read.
Free, no account
Make the image, then copy the tags
Start from a template or a blank canvas. Export a 1200 x 630 PNG, JPEG, or WebP, and copy the Open Graph tags from the preview panel.