OG image generator
Make the link preview look intentional before a blog post, launch note, or landing page gets shared.
Theme
Ship your next launch with a stronger social preview
Create an OG card that makes release notes, blog posts, and landing pages look more polished when shared.
The preview scales down to fit the page. The downloaded file uses 1200x630.
About Open Graph images
Best-practice size: 1200x630
The 1.91:1 landscape ratio is widely used for Open Graph previews. It gives enough room for a headline, product context, and brand mark without relying on tiny text.
Why it matters
A link preview is often the first visual impression of a launch, post, or tool. A deliberate card makes the page look maintained instead of auto-generated.
Readable at small sizes
Social cards are frequently shown as thumbnails. Keep type large, avoid dense paragraphs, and leave important content away from the edges.
Platform sizing guide
Facebook / LinkedIn
The standard landscape format. Keep important text centered so it survives platform crops.
Twitter Summary Large
Twitter also works well with a slightly shorter 2:1 card, although 1200x630 remains broadly compatible.
WhatsApp / WeChat
Square previews often crop from the center, so central composition matters when sharing across messaging apps.
Frequently asked questions
Do I own the generated image?
Yes. The image is created locally in your browser and is not uploaded to a server during generation.
How do I wire the image into metadata?
Add an og:image meta tag pointing to the final image URL, and pair it with twitter:card set to summary_large_image when needed.
Can I use non-Latin text?
Yes. The browser-based renderer supports non-Latin text as long as the required fonts are available in the rendering environment.
Why does a platform show an old preview image?
Social platforms cache link previews. After changing the image URL or metadata, use the platform's sharing debugger or card validator to force a refresh.
Should every page use the same OG image?
A default image is fine for utility pages, but important launches, blog posts, and landing pages usually perform better with a page-specific card.