Why your og:image is not showing

Last updated October 30, 2026 · Reviewed by Sumera Yaqoob

When a shared link shows no picture, a tiny thumbnail, or an outdated image, the cause is almost always in a short list of places. Work the steps in order. Each step rules out a whole class of failures so you usually find the issue quickly.

Quick diagnosis

What you see Most likely cause Go to
No image anywhere Tag missing, relative URL, or JS-only tags Steps 1–2
Works on Facebook, not WhatsApp Heavy file or different cache Step 3 + WhatsApp guide
Old image still appears Cached scrape Step 6
Small thumbnail, no large card Image too small or wrong aspect Step 3
Works for you, fails for bots Login, firewall, or robots rules Step 4

Step 1: Check the raw HTML

Crawlers read the HTML your server (or static host) returns. They do not behave like a fully interactive browser. Open the live URL, choose View Source, and search for og:image.

You want exactly one line similar to:

<meta property="og:image" content="https://example.com/images/cover.png" />

Watch for:

  • Nothing found. Tags missing, or only set after JavaScript. Output tags at build time or on the server.
  • More than one og:image. Theme + SEO plugin + social plugin. Keep one source.
  • name instead of property. Open Graph uses property="og:image".

Paste the URL into the Link Preview Checker. Compare against a clean snippet from the Meta Tag Generator or the OG tags cheat sheet.

Step 2: Check the image URL

The content value must be a full, public address.

  • Absolute https:// URL (not /cover.png).
  • Opens in a private window with no login or special cookies.
  • Returns an image (not HTML, not an endless redirect chain).
  • Points at the file itself, not a gallery page that displays it.

Step 3: Size, shape, and format

  • Dimensions. 1200×630 (~1.91:1) is the safe default. Facebook’s absolute minimum is 200×200; large cards need about 600×315.
  • File size. Facebook allows multi‑MB files; X and LinkedIn are typically a few MB. WhatsApp is far stricter—aim 200–400 KB, practical ceiling ~600 KB.
  • Format. PNG or JPG for the tagged file. Avoid relying on WebP or animated formats.

Resize with the Image Resizer, design with the OG Image Generator, and validate with the Social Image Checker. See OG image size for the platform table. Compare weak vs strong cards on OG image examples.

Step 4: Make sure crawlers can reach the page and image

Platforms send distinct user agents (facebookexternalhit, LinkedInBot, Twitterbot, WhatsApp, and others). Any of these can be blocked by:

  • firewall / bot-protection defaults
  • login, age, or cookie walls
  • maintenance mode
  • robots.txt Disallow on the page or media path
  • hotlink protection on the image host

If the site works in your browser but previews fail, check logs for those agents on both the HTML and the image. Our checker identifies as SocialImageKitBot when you test with SocialImageKit.

Step 5: Check og:url and redirects

og:url should match the canonical page you share. A mismatched og:url can make a platform scrape a different document. Collapse http/https and www/apex to one canonical host, and avoid long redirect chains between the shared URL and the final HTML.

Step 6: Refresh caches

Platforms store the first preview they build.

Existing posts often keep their old card. Re-share after the refresh if the historical post matters.

Platform quirks

Platform Notes
Facebook Forgiving on size; strict on cache. Use Sharing Debugger.
LinkedIn Cache often cited ~7 days. Post Inspector refreshes. Prefer ~1200×627.
X Set twitter:card to summary_large_image for a large image.
WhatsApp File weight matters most. See Facebook works, WhatsApp does not and WhatsApp sizes.
Slack / Discord Cache by URL; new file name or query usually helps.

On WordPress, tags usually come from an SEO plugin—see How to set an OG image in WordPress.

A practical order that saves time

People often jump straight to debugger tools. That wastes time when the HTML is wrong. Stay disciplined:

  1. View Source and the Link Preview Checker until the tags are correct.
  2. Open the image URL logged out and confirm format and weight.
  3. Only then open Facebook or LinkedIn official tools.
  4. Only then try URL variants for networks without a clear tool.

If you manage many URLs, keep a short internal note of which plugin owns Open Graph on each site. The next incident will go faster when you already know whether to open Yoast, Rank Math, or a custom head template. Templates and layouts in the OG image templates gallery can also reduce last-minute design mistakes that lead to unreadable crops. When you ship a fix, retest on at least two networks so a Facebook-only success does not hide a WhatsApp file-size failure.

Final checklist

  • One og:image in View Source with an absolute https:// URL
  • Image opens logged out; about 1200 by 630 pixels; PNG or JPG
  • File well under 1 MB; 200 to 400 KB when WhatsApp matters
  • Crawlers allowed; robots.txt not blocking the page or image
  • og:url matches the canonical share URL
  • Re-scraped or tested with a new URL variant after the HTML is fixed

Frequently asked questions

Short answers from this guide.

Why is my og:image not showing on any platform?

If it fails everywhere, the tag is probably missing, relative, duplicated, or only injected by client-side JavaScript. Inspect View Source (raw HTML), not the Elements panel.

What is the best og:image size?

Use 1200×630 as a safe default, PNG or JPG, with an absolute https URL. Keep the file small—especially for WhatsApp (aim 200–400 KB).

Does WebP work for og:image?

Support is inconsistent across crawlers. Prefer PNG or JPG for the tagged file even if your site serves WebP to browsers.

How do I clear the cache for an og:image?

Fix the page first. Then re-scrape in Facebook Sharing Debugger or LinkedIn Post Inspector. If the picture is stuck, change the image file name. X and WhatsApp have no public cache-clear tool—use a URL variant such as ?v=2.

Do I need og:image:width and og:image:height?

They are optional, but they help some crawlers choose a large card on the first fetch. Add 1200 and 630 when your file matches those dimensions.

Can SPA frameworks break og:image?

Yes, if meta tags are only set in the browser after JavaScript runs. Crawlers need the tags in the initial HTML from the server or static build.

Related pages