Free · reads the real file · nothing stored
OG image checker
Most broken social cards are an image problem, not a tag problem. Paste a URL and we download your actual og:image to check its dimensions, aspect ratio, format and file size — then show it cropped the way each platform will crop it.
The correct og:image size is 1200x630 pixels (a 1.91:1 ratio) as an absolute https URL to a PNG or JPEG. Keep the file under 300 KB if WhatsApp matters — it drops images over roughly 300 KB — and under 5 MB everywhere else. Every platform crops from the center, so keep text and faces inside the middle of the frame.
Showing a sample page — paste your URL above
og:image:alt is missing
ImproveImageAdding alt text describes your card image to people using screen readers on Facebook and X.
<meta property="og:image:alt" content="Describe what the image shows" />
LinkedIn caches your preview for about 7 days
ImprovePlatform gotchasOnce LinkedIn has seen a URL it keeps the old title and image for roughly a week, no matter what you change. After fixing your tags, run the URL through LinkedIn's Post Inspector to force a refresh.
Facebook needs a manual re-scrape after changes
ImprovePlatform gotchasFacebook and Instagram share one cache. Paste the URL into Facebook's Sharing Debugger and press Scrape Again so your new card appears immediately.
LinkedIn ignores your description entirely
ImprovePlatform gotchasLinkedIn shows only the image, title and domain. Make sure the headline works on its own, because the supporting sentence will never be seen there.
og:title is present
GoodCore tagsEvery platform will use "The 8 link preview mistakes costing you clicks" as the headline of your card.
og:description is present
GoodCore tagsFacebook, Slack, WhatsApp and Discord will show this supporting line.
og:image is present
GoodCore tagsYour link will render as a large visual card instead of a plain text row.
og:url is present
GoodCore tagsShares and reactions across platforms will be attributed to one canonical address.
og:type is set to "article"
GoodCore tagsPlatforms know what kind of content this is.
og:site_name is present
GoodCore tagsSlack and Discord show your brand name above the headline.
Title is 46 characters
GoodLengthIt fits without truncation on every platform we check.
Description is 120 characters
GoodLengthIt fits comfortably on every platform that shows a description.
Image is 1200x630
GoodImageThat is the recommended size and renders crisply everywhere.
Aspect ratio is 1.90:1
GoodImageThis matches the 1.91:1 shape every platform crops to, so nothing important gets cut.
X will use the large image card
GoodPlatform gotchastwitter:card is set correctly, so X shows the full-width image.
Image file is 180 KB
GoodImageComfortably under every platform's limit, including WhatsApp's tight one.
The page is served over https
GoodTechnicalSecure pages unfurl normally on every platform.
A canonical URL is declared
GoodTechnicalSearch engines and some unfurlers will treat https://commonpoint.co/insights/social-preview-audit as the one true address.
A favicon was found
GoodTechnicalSlack and iMessage show it next to your site name.
Twitter Card tags are present
GoodTechnicalX has explicit instructions rather than guessing from your Open Graph tags.
The rules that decide this card
- 1200x630 is the target
- That is a 1.91:1 landscape frame and it renders crisply on every platform including high-density screens. Going wider than 1200 adds bytes and nothing else.
- Below 600x315 you lose the big card
- Facebook and X downgrade smaller images to a square thumbnail beside the text, which looks like a mistake even though your tags are valid.
- File size is the silent killer
- WhatsApp skips images much above 600 KB and renders your link with no picture at all. Past roughly 5 MB most crawlers give up. Aim under 300 KB and this never bites you.
- SVG never works
- No major platform renders a vector social image. If your build points og:image at a logo SVG, every card is blank. Export a PNG or JPEG specifically for sharing.
- Relative and http URLs fail
- Crawlers do not resolve relative paths and refuse insecure images inside a secure feed. og:image must be a full https address.
- Declare width and height
- og:image:width and og:image:height let the very first share render at the right size instead of waiting for a crawler to measure the file.
- Everything gets centre-cropped
- Platforms crop to roughly 1.91:1, so text and faces near the top or bottom edge disappear. Keep the important content in the middle third.
- Add alt text
- og:image:alt describes your artwork to people using screen readers on Facebook and X. One sentence is enough.
Quick answers
- What size should an og:image be?
- 1200x630 pixels at a 1.91:1 aspect ratio. It satisfies Facebook, LinkedIn, X, Discord and Slack with a single export.
- Why is my og:image ignored on WhatsApp?
- WhatsApp silently drops images over roughly 300 KB and struggles with images over about 600px tall. Compress the file and it appears.
- Can I use an SVG as an og:image?
- No major platform renders SVG og:images. Export a PNG or JPEG instead — this checker flags SVG as a failure.
- My og:image is set but nothing shows. Why?
- Usually a relative URL, an http (not https) URL, or a redirect. The URL in the tag must be absolute, secure, and load the image directly.
The og:image tags to paste
<meta property="og:image" content="https://example.com/card.png" /> <meta property="og:image:width" content="1200" /> <meta property="og:image:height" content="630" /> <meta property="og:image:type" content="image/png" /> <meta property="og:image:alt" content="Describe what the image shows" /> <meta name="twitter:image" content="https://example.com/card.png" /> <meta name="twitter:card" content="summary_large_image" />