Link Preview Debugger
Reads Open Graph and Twitter card tags from a URL and renders how the link will look when shared.
Reads a page’s og: and twitter: tags the way KakaoTalk, Slack, Facebook and X read them, draws the card they would draw, and fetches the image to check it actually opens. Most broken previews are a tag that is present but unreachable, which only a fetch can tell you.
Our server makes this request for you. Only the URL you typed is sent to it — none of your cookies or login state goes along. The server will only connect to public addresses and refuses private and internal ones.
How to use it
Enter the page you are about to share
The exact URL, including the query string if the page varies by it. A redirect is followed, and the tags read are the destination’s.
Compare the card against what you meant
The card falls back the way the platforms do: og tag, then twitter tag, then <title> and meta description. If your title arrives from the fallback, the og tag is missing rather than wrong.
Check the image row
The image is fetched and its status, type and size reported. A relative URL, an image behind a login, or one served over http from an https page all fail here exactly as they would in the messenger.
Common questions
I fixed the tags and KakaoTalk still shows the old card
Every platform caches the card, and none of them re-read on their own for a long time. Clear it in Kakao Developers’ OG cache reset, Facebook’s sharing debugger, or X’s card validator. This page reads the live tags, which is why it and the messenger disagree.
The image works in my browser but fails here
Then it is not publicly fetchable, and no messenger will get it either. The usual causes are a login, a hotlink protection rule keyed on Referer, or a relative og:image URL that only resolves in the context of the page.
What size should the image be?
1200×630 is the safe answer — 1.91:1, big enough for every platform. KakaoTalk wants at least 800×400 and Facebook at least 200×200 before showing anything at all.
Does this see a page rendered by JavaScript?
No, and neither do the messengers. Only the HTML the server sends is parsed, and only the first megabyte of it. Tags injected by client-side script are invisible to every crawler that draws these cards.
Feed it from
URL Parser & Query Editor
Splits a URL into its parts, shows query parameters as an editable table and rebuilds the result.
Redirect Chain Tracer
Follows a shortened or tracking URL through every redirect and shows the final destination.
robots.txt & Sitemap Checker
Fetches robots.txt and the sitemap, tests whether a URL is crawlable and validates the sitemap format.
Social Card Generator
Composes a 1200×630 share image from a title, subtitle, brand line and optional logo on a chosen template, and writes the meta tags to go with it.
Next
These accept what this tool produces, so the result can go straight in.
HTTP Header Inspector
Fetches a URL and shows the full response headers, redirect chain, timings and compression used.
Social Card Generator
Composes a 1200×630 share image from a title, subtitle, brand line and optional logo on a chosen template, and writes the meta tags to go with it.
robots.txt & Sitemap Checker
Fetches robots.txt and the sitemap, tests whether a URL is crawlable and validates the sitemap format.
URL Parser & Query Editor
Splits a URL into its parts, shows query parameters as an editable table and rebuilds the result.
HTTP Request Builder
Composes and sends a GET/POST/PUT/PATCH/DELETE/HEAD request with custom headers and a body, and shows the status, headers, body and timing — without ever forwarding cookies or Authorization.
QR & Barcode Reader
Reads QR codes and common barcodes from an uploaded image, a screenshot or the camera.