Open Graph Image Size
Design the image at 1200×630. That is Facebook's high-resolution size, and it is a 1.91:1 ratio. The notes below are the sizes each platform actually publishes. Paste a URL and this checker measures the og:image you shipped.
Documented image sizes
- 1200×630 is the baseline. The Open Graph protocol defines og:image as a URL. It does not set a pixel size. Facebook's image guide is where 1200×630 comes from: use at least that size for high-resolution devices, and keep the ratio close to 1.91:1 (1200÷630). This checker fails an image under 200×200, warns under 1200×630, and warns when the ratio is more than about 10% off 1.91:1.
- Facebook and X. Facebook's minimum is 200×200. Use at least 600×315 for the larger link image, and 1200×630 when you can. The file must not exceed 8 MB. Documented og:image:type values are JPEG, GIF, and PNG. X's published card docs specify summary_large_image as a 2:1 image, at least 300×157, at most 4096×4096, under 5 MB. JPG, PNG, WEBP, and GIF are supported; SVG is not. summary is 1:1, at least 144×144, also under 5 MB, and is cropped to a square. A 1200×630 image is 1.91:1, so it is a little taller than that 2:1 ratio.
- LinkedIn and Messages. LinkedIn's sharing module asks for a minimum of 1200×627, a maximum of 5 MB, and a recommended ratio of 1.91:1. The same help page says an image under 401 pixels wide displays as a thumbnail. Required tags there are og:title, og:image, og:description, and og:url. Apple's Messages guidance asks for an image at least 900 pixels wide. Under 150 pixels wide, it may be ignored or shown as an icon. The HTML page is limited to 1 MB, and the icon, image, and video together are limited to 10 MB.
- Slack, Discord, and WhatsApp. Slack's unfurl documentation does not publish a pixel size or a file-size cap. Discord's link-preview guide uses 1200×630 in its example and allows png, gif, jpg, jpeg, webp, and avif. Its limits table has no minimum dimensions. WhatsApp's public help does not state a pixel size or a file-size cap for link previews. The warning in this checker above 600 KB, with a note to aim under 300 KB, is our threshold. It is not a number WhatsApp publishes.
Tags covered: og:image · og:image:width · og:image:height · og:image:type · twitter:image · twitter:card
More checkers
Twitter Card ValidatorOpen Graph CheckerLinkedIn Link Preview CheckerDiscord Embed PreviewWhatsApp Link Preview CheckerSlack Link Preview CheckeriMessage Link Preview CheckerFacebook Link Preview CheckerAll platforms
What each platform reads
- X / Twittertwitter:card, twitter:* → og:* fallback1200×630 (min 300×157), < 5 MB
- Facebookog:title, og:description, og:image1200×630, 1.91:1
- LinkedInog:title, og:image (og: only)1200×627, 1.91:1
- Discordog:site_name, og:*, theme-color, twitter:cardLarge image needs summary_large_image
- Slackog:site_name, og:title, og:description, og:image1200×630
- WhatsAppog:title, og:description, og:imageKeep < 300 KB
Guidance based on each platform's public documentation and observed behavior. Platforms change their rules without notice.
FAQ
+Is Peekly free?
Yes. Checking a single URL is free forever — no signup and no limit on one-off checks. Batch watching and monitoring may arrive later as a paid Pro plan; the free single-URL tool stays.
+Why does my link show no image when I share it?
Usually one of four things: there's no og:image tag, the image URL is relative instead of absolute, the image is behind a login, firewall or bot block, or the file is too big or in an unsupported format like SVG. Peekly checks all four and tells you which one it is.
+What size should my og:image be?
1200×630 pixels (a 1.91:1 ratio) as a PNG or JPG under about 300 KB. That size works for large cards on X, Facebook, LinkedIn, Discord, Slack and WhatsApp.
+Do I need twitter: tags if I already have Open Graph tags?
X reads og:title, og:description and og:image as fallbacks, but you still need twitter:card set to summary_large_image if you want the big image card. Without it, X shows a small thumbnail.
+I fixed my tags but the old preview still shows. Why?
Platforms cache link previews, sometimes for days. Facebook and LinkedIn let you force a refresh with their own debugging tools. On X, Slack and Discord the cache usually expires on its own, or you can add a query string such as ?v=2 to the URL.
+Do you store the pages I check?
No. We fetch the page once to read its <head>, show you the result, and don't save the page or the result. We only fetch public http(s) URLs, and private or internal addresses are blocked.
+Are the previews pixel-perfect?
They're close approximations of each platform's current card layout, built from the same tags the platforms read. Platforms change their designs from time to time, so treat them as a very good guide rather than a screenshot.
$9
One time
A written fix for the batch.
Up to 25 URLs. We check og:image, Twitter cards, size, redirects, and cache, then send copy-paste meta tags within 48 hours. The free single-URL check stays free.