Content

Open Graph Image Generator

A share preview that actually renders

In build

Fill in a headline, a site name and a logo and get a 1200 by 630 PNG, plus the og:image, og:image:width, og:image:height and twitter:card tags to paste in the head, with the file kept under the size each network accepts.

Get early access

What it returns

A 1200 by 630 PNG with your headline, site name and logo composed on it, ready to upload and reference.
The tags that make it render: og:image, og:image:width, og:image:height, og:image:alt, og:title, og:description and twitter:card, as one block for the head.
The rendered file size next to the ceiling each network enforces, because an image that is too heavy is dropped rather than resized.
The same image previewed at the aspect ratios the major platforms crop to, so a headline that survives in one feed is not cut in half in another.

When this matters

You ship a launch post, paste the link into Slack, and get a grey box with the URL in it. Nothing is broken on the page: either the og:image is a relative path, or the file is heavier than the crawler will fetch, or there is no tag at all and the platform picked the first image in the body, which happened to be an author avatar. The fix takes a minute, and the irritating part is that it was visible before publishing.

How to answer this today

Site audit finds this across a whole site rather than on one page: the crawl records the Open Graph and Twitter tags on every URL and reports the pages where they are missing, copied across unrelated posts, or pointing at an image that does not resolve. What it will not do is draw an image for a post that is still a draft, which is the job here.

Site audit

Why this is harder than it looks

Every network crops differently

One file has to work at close to 1.91:1 in a link preview, square in some feeds, and tightly cropped in others. Text near an edge survives in one place and is cut in another, so the safe area matters far more than the canvas size.

Text that will not fit

A headline long enough to need three lines at a size that reads on a phone has to shrink, wrap or truncate, and non-Latin scripts and long compound words break the measurement that worked for English. Putting text in an image is a typesetting problem, not a template fill.

Caches are long and stubborn

Social platforms keep what they fetched the first time, so replacing the file at the same URL often changes nothing visible for days. A new filename, or a revalidation through the platform's own debugger, is the only reliable fix.

The crawler is not a browser

Preview bots do not run JavaScript, frequently ignore redirects, and need an absolute URL on a publicly reachable host. A tag that looks correct in your browser can still return nothing to the crawler that decides what the share looks like.