og:image Not Showing? How to Fix It
An og:image not showing almost always comes down to one of five causes: the image URL is not public, the image is too large, the platform cached an old version, the tags target the wrong page, or the image format is unsupported. This guide walks each fix with the debugging tools Facebook, X, and LinkedIn provide.
Why is my og:image not displaying?
Most of the time the image URL is not publicly fetchable, the file exceeds the platform's limits, or the platform is showing a cached copy. Social platforms re-scrape on a schedule and cache aggressively, so a fresh image often appears to "not work" until you force a refresh with their debug tools.
The five most common causes (and fixes)
1. The image URL is not public
Platforms must fetch the image without authentication. A URL behind a login, localhost, or an IP address will fail.
Fix: host the image at a public, HTTPS URL and confirm curl -I <image-url> returns 200 OK with an image Content-Type.
2. The image is too large
Most platforms cap OG images at 8 MB (X at ~5 MB). A huge PNG fails silently.
Fix: keep the file under 5 MB; a 1200×630 text card is usually 200–500 KB. On FastOG, PNG output is already sized for this.
3. The platform cached an old version
Facebook, X, LinkedIn, Slack, and Discord all cache aggressively. After changing the image, the old card persists for hours or days.
Fix: force a scrape with the platform's tool (below). For changing images, use a URL that changes with the content (FastOG's signed URLs do this automatically).
4. Wrong URL or wrong page
The og:image tag may be missing, duplicated, or pointing at a page without that tag.
Fix: view the page source and confirm the og:image tag is present, server-rendered, and absolute.
5. Unsupported format
Some platforms reject certain formats or animated images.
Fix: use PNG or JPG; 1200×630 is the supported ratio.
Debugging tools
| Platform | Tool |
|---|---|
| Facebook / WhatsApp | Sharing Debugger — developers.facebook.com/tools/debug |
| X / Twitter | Card Validator — cards-dev.twitter.com/validator |
Post Inspector — linkedin.com/post-inspector |
Paste the URL, then hit "Scrape" / "Refresh" to pull the latest tags.
FastOG specifics
- FastOG renders 1200×630 PNG — the supported size — so size/ratio issues are avoided.
- Signed URLs gate only the first render; cached images stay valid, so a shared card keeps working.
- Change the title → change the URL → one new render. The platform (eventually) picks up the new card when you force a re-scrape.
FAQ
Does FastOG guarantee my og:image appears?
FastOG delivers a valid 1200×630 PNG from a public URL. Whether the platform shows it depends on its cache — re-scrape with the validator after changing an image.
Why does Facebook show an old image even after I updated it?
Facebook caches scrapes. Use Sharing Debugger → "Scrape Again" and wait; multiple consecutive scrapes sometimes clear a sticky cache.
How do I force X to show my new card?
Open the X Card Validator and paste the URL. It re-fetches the latest og:image and twitter:image.
Related
Try it free — no signup required
Preview and test dynamic OG images in seconds.
Open the Free OG Image Tester