How to use
- On the page you want to share, press
Ctrl+U(Option+Command+Uon a Mac) to open view-source, copy the<head>or the whole page and paste it into the box. - Read Checks at the top for missing tags and image problems.
- See how the card will look on KakaoTalk, Facebook, X, Slack and in search results.
- To see the real image, turn on Also load the image. It starts off, and the image area shows just the address.
Why the image is not loaded by default
To draw the image, this browser has to send a request straight to the server that hosts it. The HTML you paste is never sent anywhere, but loading the image leaves a visit (a request) on that image server. So the option starts off, and when you turn it on only full addresses starting with https:// are loaded. Relative paths and http:// addresses are never loaded.
Which tags each service reads
| Service | Title | Description | Image |
|---|---|---|---|
| KakaoTalk | og:title, else title |
og:description, else meta description |
og:image |
| Same | Same | og:image |
|
| X | twitter:title, then og:title, then title |
twitter:description, then og:description |
twitter:image, then og:image |
| Slack | og:title, then twitter:title |
og:description, then twitter:description |
og:image |
| Search result | title |
meta description | none |
On X, the twitter:card value picks the card style. summary_large_image draws the large image card; a missing value or summary draws the small square-image card.
How image size is checked
- The tool uses the 1200x630 px (about 1.91:1) that Facebook documents as its recommended size. If you declare
og:image:widthandog:image:height, those values are checked. - Under 600 px wide or 315 px tall raises a warning, and a ratio more than 15% away from the recommended one is flagged as likely to be cropped at the edges.
- A title over 70 characters or a description over 160 is noted. Services cut text at different places, so these are guides, not exact limits.
- Fonts and line counts in the preview can differ from the real apps. For important pages, confirm with each service’s sharing debugger (the Facebook Sharing Debugger, the Kakao sharing debugger).
I fixed the tags but the old card still shows
Sharing services often store a preview once fetched and reuse it for a while. If the old card appears after you fix the tags, ask the debugger above to fetch the address again, and if you swapped the image file, giving it a new file name so the URL itself changes is the surest fix.
Frequently asked questions
Does it show a preview if I just enter a URL?
No. The tool does not fetch pages by address; it reads only the HTML you paste. Copy it from view-source.
Can og:image be a relative path?
Sharing services fetch the image from outside your page, so a full https:// address is the safe choice. This tool also warns about relative paths and does not load them.
My KakaoTalk card looks different from this preview.
The preview is an approximation. KakaoTalk may lay cards out differently depending on the app version and chat type, so check with the Kakao sharing debugger.
What makes a good share image?
Keep the main content near the centre and leave the edges unimportant so a crop does no harm. JPG or PNG is a safe format. File-size limits differ between services, and this tool does not check them.
Where does the pasted source go?
The text you enter is processed only in your browser and never sent to a server. The one exception is the image option: when you turn it on, the browser requests that image directly from the server that hosts it.
Worth a look next: the Meta Tag Generator to write the tags, the Meta Tag Checker for all SEO tags, and the Social Image Size Guide for per-platform sizes.