Skip to content

X · Aug 3, 2026

Why your OG image doesn't show on Twitter/X

You set og:image. The Facebook debugger looks fine. On X the Twitter/X link preview is a sad thumbnail — or nothing. X does not treat Open Graph as gospel. If twitter:card is not set, you often get a small summary instead of your Twitter card image.

The card you want for a 1200×630 file is:

<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Your title">
<meta name="twitter:description" content="Your description">
<meta name="twitter:image" content="https://example.com/og.png">

twitter:image can fall back to og:image, but setting both avoids a surprise small card. The OG image checker fails when twitter:card is missing and warns when twitter:image is absent.

Size

A Twitter card image works at 1200×630. If you only ship X, 2:1 (e.g. 1600×900) is also documented. OGForge’s preset=x is 1600×900; preset=og is 1200×630. For a site-wide og:image, stay on 1200×630 and let X letterbox slightly rather than shipping a second file you will forget to update.

Why the preview stays broken after you “fixed it”

Usual stack:

  • No twitter:card (or it is still summary)
  • Image is HTTP or a relative path
  • Image is a WebP that this crawler skipped (try PNG)
  • You changed the pixels but not the URL, so the old card is cached

Unlike Facebook, X does not give you a public “scrape again” button with the same UX. Changing the image URL is the reliable hammer. Then wait.

HTTPS, relative URLs, and cache live in why your OG image is not showing. Tag limits: which Open Graph tags still matter.

Use the OG image generator, save the image, and put the /u/… URL in both og:image and twitter:image. PNG is free. If X has been picky about WebP, stay on PNG — or use JPEG on Pro. Confirm the page in the OG image checker before you tweet it.

Need the actual image?

Open the OG image generator — PNG export is free. Pro is $19.99/mo for JPEG/WebP, CDN URLs, and an API key. Or paste a live URL into the checker first.