Open Graph Preview and Checker
Paste your page's HTML and see the card your link will produce, plus every reason a platform might refuse to show the image.
Unlike every other tool here, this one sends the address to our server, because a browser isn't allowed to read another site's HTML. Only the URL is sent, only public pages can be read, and nothing is stored.
What the Open Graph Checker does
- Fetches any public page and reads every Open Graph, Twitter Card and canonical tag out of it.
- Loads the real og:image in your browser and measures it, so it can tell you when the declared width and height don't match the file, or when the image is too small for a large card.
- Renders both layouts a platform can choose between, so you can see whether you'll get the wide card or the small square thumbnail.
- Explains each problem in terms of what it costs you, not just which tag is absent.
What it doesn't do
- This is the one tool here that isn't purely local. Reading another site's HTML is something a browser is forbidden to do, so the address you enter is sent to our server, which fetches the page on your behalf. Only the URL is sent, only public pages can be read, and nothing about the request is stored.
- It can't reach anything private. Addresses inside a home or company network, and the internal addresses used by cloud hosts, are refused — so this can't be used to probe machines that aren't on the public internet.
- It can't measure the image's file size, only its dimensions. A browser can display a cross-origin image but not read its bytes. WhatsApp's practical ceiling is around 600 KB.
- It can't clear a platform's cache. Previews are cached per URL for days, so a fix won't show on a link you've already shared until the platform re-scrapes it.
- Some sites refuse automated requests. If a page loads in your browser but not here, it's blocking non-browser traffic — which also means Facebook and WhatsApp may be getting the same refusal.
Frequently asked questions
Why does WhatsApp show a small square thumbnail instead of a big card?
WhatsApp decides per scrape, and it falls back to the small layout whenever it can't confirm the image quickly. The usual causes are a missing og:image:width and og:image:height, a missing og:image:type, or an image that's slow to serve. Declaring all three removes the round trip it would otherwise need. Also check on your phone — WhatsApp Desktop shows the compact layout far more often than the mobile app does.
I fixed my tags but the preview hasn't changed. Why?
Every platform caches previews per URL, typically for several days, and re-sending the same link shows the cached copy. Facebook's Sharing Debugger has a "Scrape Again" button that clears it, and because WhatsApp uses the same crawler, that also fixes WhatsApp. Otherwise, test with a URL the platform hasn't seen — adding ?v=2 is enough.
What size should the image be?
1200×630. That's 1.91:1, which is what Facebook, LinkedIn, X and Slack all crop toward, and 1200px keeps it sharp on high-density screens. Anything under 200px on a side is rejected outright, and a square image gets cropped top and bottom.
Do I need Twitter tags if I already have Open Graph ones?
Mostly no — X falls back to og:title, og:description and og:image. The one tag that matters is twitter:card, because without it X shows the small square layout even when a perfectly good image is available. Set it to summary_large_image.
Why does the image have to be an absolute URL?
The scraper fetches it from its own servers, not from your page, so it has no idea what "/og.png" is relative to. This is the most common reason a card appears with no picture, and it's easy to miss because the same path works fine in your browser.