The first impression, checked everywhere at once.
The first thing anyone sees of your work is usually a link preview: a card in a chat, a post in a feed, a line in search results. Every platform renders the same tags differently, dark mode doubles the surface, and the favicon is easy to forget. Preview A Link shows all of it on one screen, then tells you exactly what to fix.
Questions
Are these real screenshots?
No — every preview is a simulation, rebuilt in HTML and CSS from the tags your page serves and the rules each platform follows (which tags it reads, when it switches between a large image and a thumbnail, where it cuts text). The rules come from platform docs and, where possible, the apps' own source code. Apps change their designs often, so treat a preview as a very good estimate and confirm launch-critical links in the real app.
What do you fetch?
Only the URL you submit. We request it once with our own user agent, then once with each platform's published crawler user agent to spot sites that serve bots something different. We read the <head>, then download the og:image and the icons it declares. We don't follow links, crawl other pages, run JavaScript or log in anywhere.
Do you respect robots.txt?
robots.txt governs automated crawling. We fetch a single page because a person asked us to, the same way Slack, iMessage or WhatsApp fetch a link the moment someone pastes it — and those platforms don't consult robots.txt for previews either. If your preview is broken for a platform, we'd rather show you than hide it.
What do you store?
Each check is saved as a snapshot — the tags we found plus copies of the preview image and icons — so its permalink keeps rendering even after the site changes. Snapshots live at unguessable, unlisted URLs, are never indexed, and are deleted after 90 days. The browser that ran a check can delete its snapshot immediately. Your list of recent checks never leaves your browser.
My site blocks you. Now what?
Some bot-protection services block unfamiliar crawlers (sometimes including smaller platforms' real ones — worth knowing). Use “Paste HTML”: paste your page's <head> and we'll render every preview without fetching the page itself. It also works for localhost and staging sites behind a login.
I fixed my tags but the real app still shows the old preview.
Platforms cache previews — Slack and Discord for about 30 minutes, X for about a week, Facebook and LinkedIn until you ask them to re-scrape. Each tile has a ↻ refresh note with the platform's tool or workaround (usually: share the URL with a new query string like ?v=2).
Is this affiliated with any of these platforms?
No. Platform names are used only to say which app a preview simulates. We don't use their logos.
User agents we send
| facebookexternalhit | facebookexternalhit/1.1 (+http://www.facebook.com/externalhit_uatext.php) | Server |
| Twitterbot | Twitterbot/1.0 | Server |
| Slackbot | Slackbot-LinkExpanding 1.0 (+https://api.slack.com/robots) | Server |
| Discordbot | Mozilla/5.0 (compatible; Discordbot/2.0; +https://discordapp.com) | Server |
| LinkedInBot | LinkedInBot/1.0 (compatible; Mozilla/5.0; Apache-HttpClient +http://www.linkedin.com) | Server |
| WhatsApp/2.25.20.0 A | Device | |
| TelegramBot | TelegramBot (like TwitterBot) | Server |
| iMessage (Apple) | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/601.2.4 (KHTML, like Gecko) Version/9.0.1 Safari/601.2.4 facebookexternalhit/1.1 Facebot Twitterbot/1.0 | Device |
| Signal | WhatsApp/2 | Device |
| Teams (SkypeUriPreview) | Mozilla/5.0 (Windows NT 6.1; WOW64) SkypeUriPreview Preview/0.5 skype-url-preview@microsoft.com | Server |
| Bluesky Cardyb | Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Bluesky Cardyb/1.1; +mailto:support@bsky.app) Chrome/131.0.0.0 Safari/537.36 | Server |
| redditbot | Mozilla/5.0 (compatible; redditbot/1.0; +http://www.reddit.com/feedback) | Server |
| Googlebot | Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) | Server |
“Device” means the real app fetches the preview from the sender's phone or computer; “Server” means the platform's servers do.