Open Graph checker: See your link before you share it
This free Open Graph checker shows how your link looks on Facebook, X, LinkedIn, Slack, Discord, iMessage, WhatsApp and Telegram, checks your share image the way each one reads it, and gives you the tags to paste for every fix.
How your link looks
Fix these
The tags to paste
Your share image
What each crawler got
Every tag on the page
Get new free tools by email
One email when we add a new tool, and one on the 1st of each month before Google deletes a month of your Search Console data. Nothing else.
You confirm by email first. We keep only your address, and every email has a link that stops them and deletes it.
Turn these results into fixes
Get ready-to-paste prompts for ChatGPT or Claude, built from what this check found and from the pages Google and AI answers cite for your topic.
How the Open Graph checker works
The Open Graph checker works the way a chat app or a social network does when you paste a link: it fetches the page, reads its tags, fetches the image they name, and builds the preview.
- Read the page. Our server asks for the page as a browser, follows any redirects to the final address, and reads every Open Graph and X tag, the title, the description and the canonical link.
- Measure the image. It downloads the share image and reads its real width, height, format and file size from the file itself, not from the tags, so a wrong og:image:width shows up.
- Ask as each crawler. It checks robots.txt and asks for the page again under the names of eight link preview crawlers, so you see when a firewall turns one away.
- Draw each preview, then list the fixes. Each preview follows that platform's own rules for which tag it reads first, how it crops the image and where it cuts the title. Each fix comes with the exact tag to paste.
Open Graph tags every page needs
Open Graph tags every page needs come down to five: og:title, og:description, og:image, og:url and og:type, plus twitter:card for X and the image's size and alt text.
og:title
The title in bold. Write it for the page alone, without your site name, which og:site_name carries. X cuts titles at 70 characters, so put the words that matter first.
og:description
One or two sentences under the title. Facebook shows about one line of it and WhatsApp two, and WhatsApp suggests about 80 characters.
og:image
The picture, at its full https address: 1200 x 630 px, a JPEG or PNG under 600 KB so it shows on WhatsApp too. Add og:image:width, og:image:height and og:image:alt with it, so Facebook can show it on the first share.
og:url and og:type
og:url is the page's one clean address, the same as its canonical link, with no tracking codes: Facebook counts shares under it. og:type is website for most pages and article for posts.
twitter:card
Set it to summary_large_image. X has no Open Graph fallback for the card type, and Slack and Discord read it to show the large picture. For the title, description and picture, X falls back to the og: tags, so you need no other twitter: tags.
A template to copy
<meta property="og:type" content="website"> <meta property="og:url" content="https://yoursite.com/page"> <meta property="og:title" content="Your page title"> <meta property="og:description" content="One or two sentences about the page."> <meta property="og:site_name" content="Your site name"> <meta property="og:image" content="https://yoursite.com/images/share.jpg"> <meta property="og:image:width" content="1200"> <meta property="og:image:height" content="630"> <meta property="og:image:alt" content="What the picture shows"> <meta name="twitter:card" content="summary_large_image">
OG image size for every platform
The OG image size for every platform is 1200 x 630 pixels at 1.91:1, saved as a JPEG or PNG under 600 KB: big enough for every large card, and under WhatsApp's file limit, the strictest one.
| Platform | Best size | Smallest it shows | Largest file | Shape | Formats |
|---|---|---|---|---|---|
| Best size: 1200 x 630 | Smallest it shows: 200 x 200; under 600 x 315 shows as a small square | Largest file: 8 MB | Shape: 1.91:1 | Formats: JPEG, PNG, GIF; WebP works but is not documented | |
| X | Best size: 1200 x 600 (not documented) | Smallest it shows: 300 x 157 for the large card, 144 x 144 for summary | Largest file: 5 MB, at most 4096 x 4096 | Shape: 2:1 large, 1:1 summary | Formats: JPEG, PNG, WebP, GIF (first frame only); no SVG |
| Best size: 1200 x 627 | Smallest it shows: Under 401 px wide shows as a thumbnail | Largest file: 5 MB | Shape: 1.91:1 | Formats: Not documented | |
| Best size: At least 300 px wide | Smallest it shows: 300 px wide; no wider than 4:1 | Largest file: 600 KB | Shape: Not documented | Formats: Not documented | |
| iMessage | Best size: At least 900 px wide | Smallest it shows: Under 150 px wide may be ignored or shown as an icon | Largest file: 10 MB for every image and icon on the page | Shape: Not documented | Formats: Not documented |
| Discord | Best size: 1200 x 630 (its own example) | Smallest it shows: Not documented | Largest file: Not documented | Shape: Large only with summary_large_image | Formats: JPEG, PNG, GIF, WebP, AVIF |
| Slack | Best size: Not documented | Smallest it shows: Not documented | Largest file: Not documented | Shape: Large only with summary_large_image | Formats: Not documented |
| Telegram | Best size: Not documented | Smallest it shows: Not documented | Largest file: Not documented | Shape: Not documented | Formats: Not documented |
These are each platform's own published numbers, read in October 2026. X took its card documentation offline in 2026, so its numbers come from the last published copy. Where a platform publishes nothing, the checker draws what is commonly seen and never calls the preview broken over it.
Twitter card validator
A Twitter card validator still matters now that X has none of its own: its Card Validator's address opens X's login page, and X took its card documentation offline in 2026. This checker draws the X card from the same rules.
What it tests for X
It reads twitter:card and checks it is summary, summary_large_image, app or player. It follows X's fallback from twitter:title, twitter:description and twitter:image to the og: tags, checks the picture against X's limits (300 x 157 at least for the large card, under 5 MB, at most 4096 x 4096, no SVG) and asks for the page as Twitterbot.
robots.txt and Twitterbot
X's crawler follows robots.txt. A rule that keeps Twitterbot out of the page means no card, and one that keeps it out of the picture's folder means a card with no picture.
How long X keeps a card
X keeps a card for about seven days and has no refresh tool. To see a change sooner, share the address with a new query string on the end, like ?v=2, which X reads as a new page.
The card X draws today
Since 2023, X's large card shows the picture with your domain on it and little or no text under it. The preview here draws it that way and says where X's look is unsure.
Old link previews after a fix
Old link previews after a fix come from each platform's copy of your page: they read a link once and keep what they found for a while, so a new image can take days to show unless you ask them to read it again.
Facebook keeps what it read and updates it on its own after a while: its own pages say both 24 hours and 30 days. To update it now, run the link through Facebook's Sharing Debugger and scrape it again. Pictures are kept by address, so a new picture needs a new file name.
LinkedIn's Post Inspector reads the page again, but only new posts get the new preview. Posts already up keep the old one.
X
X keeps cards for about seven days and has no refresh tool. Share the address with ?v=2 on the end to get a fresh card.
Slack and Discord
Slack and Discord keep a preview for about 30 minutes. Discord's Embed Debugger, in its developer portal, shows which tags it picked.
WhatsApp and iMessage
WhatsApp and iMessage build the preview on the sender's phone when the message is written, so a sent message never changes. New messages pick up the fix.
Open Graph checker questions
These Open Graph checker questions come up most: what Open Graph is, why a preview shows the wrong image, and what the checker keeps.
What is Open Graph?
Open Graph is a set of meta tags, first made by Facebook, that tells apps how to show a link: its title, description, picture and address. X, LinkedIn, Slack, Discord, WhatsApp, iMessage and Telegram all read it.
Why does my link show the wrong image?
Usually one of four things: the page has no og:image, so the platform guesses; the picture is too small, too heavy or an SVG; a firewall turns the platform's crawler away; or the platform still shows the copy it read before your fix. The checker tells you which one it is.
What size should an OG image be?
1200 x 630 pixels, at 1.91:1, as a JPEG or PNG under 600 KB. That gives the large card on Facebook, LinkedIn and X, and stays under WhatsApp's 600 KB limit.
Do I need separate Twitter tags?
Only twitter:card. X falls back to og:title, og:description and og:image when twitter:title, twitter:description and twitter:image are missing, but it has no fallback for the card type.
Do link previews run JavaScript?
Discord and Apple say outright that theirs don't: they read the HTML your server sends. Tags a script adds after the page loads often never show in a preview, so the checker reads the page the same way, with no JavaScript.
Does Open Graph help SEO?
Open Graph doesn't move rankings by itself. It decides how your link looks wherever it is shared, and that decides whether people click it. Google Discover can also use og:image as a page's picture when it is at least 1200 px wide.
Is the Open Graph checker free?
Yes: 50 checks a day with no sign-up, and 150 when you sign in with Google. Nothing is kept, no copy of the page or the picture, so a page you just fixed shows the change on the next check.