Snapchat Link Preview Checker

Q: 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.

Q: 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.

Q: 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.

Q: 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.

Q: 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.

Q: Do you store the pages I check?

No. We fetch the page once to read its , 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.

Snap's URL Preview Service builds a title, a subtitle, and a thumbnail when a link is shared in chat. Paste a URL to check the Open Graph tags that card is allowed to use. The cards below are the other platforms that read the same tags — Peekly does not draw a Snap.

How Snapchat builds the chat preview

The tags Snap names. Snap's robots page at developers.snap.com/robots says the URL Preview Service scans a site's HTML so a link shared in chat can show a card with a title, a subtitle, and a thumbnail. It prioritizes Open Graph tags, and the two it names are og:title and og:image. It will use X card tags when those are missing, and the names it prints are twitter:title and twitter:img:src. X's card docs name twitter:image, not twitter:img:src. Set og:title and an absolute https og:image, which is the pair Snap says it reads first. Also set og:description. The card has a subtitle, and Snap does not name the tag that fills it. Set twitter:title and twitter:image for X. Do not drop og:image in favor of either Twitter tag. Snap does not mention Stories or Spotlight on that page. The documented surface is chat.
```
<meta property="og:title" content="Page title">
<meta property="og:description" content="One or two sentences.">
<meta property="og:image" content="https://example.com/og.png">
<meta property="og:url" content="https://example.com/page">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Page title">
<meta name="twitter:image" content="https://example.com/og.png">
```
The user agent and the cache. The same page says the service requests with the user agent Snap URL Preview Service; bot; snapchat; https://developers.snap.com/robots, and that it caches the response for a URL for 30 minutes so it does not keep hitting one address. If the card is wrong, Snap's own steps are to allow-list that user agent and to put the metadata tags in the HTML header. Snap does not say the fetcher runs JavaScript, does not say whether it reads robots.txt, and does not publish a pixel size, a file-size cap, or a format list. Tags that exist only after the page hydrates are invisible to a fetcher that reads the HTML it was sent. This checker does not send Snap's user agent. It shows the tags your server returns to the fetch it does make.
The image. Snap does not publish a pixel size. Ship the 1200×630 JPEG or PNG the Facebook image guide asks for, which is the large-card size this checker measures. og:image has to be an absolute https URL. A path with no host, an http:// file, or a login wall leaves the thumbnail empty. SVG is a miss where a platform publishes a format list, and Snap publishes no list, so a JPEG or PNG is the file that also works everywhere else. The Open Graph Image Size page has the sizes other platforms do publish.
After you change the tags. Snap does not publish a debugger. The cache it does publish is 30 minutes for that URL. Wait that out, or share a URL Snap has not cached. A query string such as ?v=2 is a different URL, not a refresh of the original one. Snap does not say whether a chat that already showed a card rewrites itself. This checker shows the tags your server sends. It does not clear Snap's cache.

Tags covered: og:title · og:description · og:image · og:url · twitter:title · twitter:image · twitter:card

More checkers

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.

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.

Get the fix report — $9