Logo

MonoCalc

/

Social Share Preview Simulator

Social Media

The metadata

Both modes fill the same values, so switching between them keeps everything you have already entered. Paste your tags or fill the fields — we can't read another site's HTML from your browser.

What every card leads with. Leave it empty to see the fallback.
Used by the cards that print a site name instead of a host.
Only some of the cards show this at all — the checklist says which.
Only the host is ever displayed, never the path or the query string. Nothing at this address is fetched.
A wide picture above the text. The image is cropped to a landscape strip, so anything near the top or bottom edge is at risk.

Image

Your browser loads this one picture the way any page would. It is never read back pixel by pixel, and it is never uploaded anywhere.
Read out in place of the picture. An empty one is flagged in the checklist.
These are approximations, not screenshots
Each card is drawn from public rendering behaviour and carries no platform logos or branding. Shapes, spacing and which lines appear are close enough to catch a missing image or a clipped title; they are not pixel-exact, and every platform changes its chrome without notice.

Facebook

Wide picture, then a bar carrying the host, the title and a line of description.

Nothing to print — no title and no address.

No image — this is the text-only card, and it is a much smaller target in a feed.

X

The only card the card-type selector changes: a wide picture, or a small square beside the text.

Nothing to print — no title and no address.

No image — this is the text-only card, and it is a much smaller target in a feed.

LinkedIn

Wide picture with the title beneath it, and the host under that. The description is usually left out.

Nothing to print — no title and no address.

No image — this is the text-only card, and it is a much smaller target in a feed.

Slack

Site name above the title, the description in full, and a small square picture beside them.

No image

No site name

Nothing to print — no title and no address.

Discord

A vertical accent bar down the left, text stacked behind it, and the picture underneath.

No site name

Nothing to print — no title and no address.

WhatsApp

A compact block above the message bubble: title, a line of description, then the host.

No image

Nothing to print — no title and no address.

What will go wrong

Check

No image

Each card drops to its text-only shape, which is a much smaller target in a busy feed.

Affects all six cards.

Check

No title

Every card falls back to the host — and with no address typed either, there is nothing left to print.

Affects all six cards.

Note

No description

The cards that print a description leave the line empty. The rest never show one, so they look no different either way.

FacebookSlackDiscordWhatsApp

Note

No usable address

The domain line is blank on every card. Only the host is ever printed — the path and any query string are dropped.

Affects all six cards.

Each row says what will happen rather than scoring your tags. There are no character counts or pixel sizes here on purpose: every platform revises them quietly, and a stale number stated confidently is worse than no number at all.

About This Tool

Social Share Preview Simulator – One Link, Six Cards

When a link is pasted into a feed, a channel or a chat, the app that receives it reads a handful of <meta> tags from the page and draws a preview card from them. The same tags reach every app, but no two apps arrange them the same way. This tool takes one set of metadata — typed into the fields or pasted as tags — and draws approximate cards for Facebook, X, LinkedIn, Slack, Discord and WhatsApp side by side, so the differences are visible before anything is published.

Three shapes, six arrangements

Nearly every card is a variation on one of three shapes. A large-image card puts a wide picture on top and a bar of text underneath. A thumbnail card sets a small square picture beside the text. A left-rule card runs a coloured bar down the side of a text block with the picture below it. What varies on top of that is the ordering: whether the site or domain line sits above the title or beneath it, and whether the description is printed at all. A description written with care can simply never appear on some cards, which is worth knowing before it is written.

What breaks, and where it shows

The failures worth catching are not subtle once you can see them. A missing image collapses a card to its text-only shape, a far smaller target in a scrolling feed. A long title is clipped by the box rather than by any rule you can count in advance, so it matters where the useful words sit. A portrait or square picture is cropped hard by the large-image layouts, and whatever was near the top or bottom edge is the part that disappears. An empty title makes the card fall back to the bare host name. Each of these gets a row in the checklist beside the grid, and each row says what will happen rather than awarding a pass or a fail.

Why clipping here is visual, not counted

No character limit or pixel dimension is asserted anywhere in this tool, and that is deliberate. Platforms revise those numbers quietly, this is a static page, and a confident stale figure is worse than none at all. Titles and descriptions are therefore clipped by the rendered box using CSS line clamping — the same mechanism the real cards use — rather than by slicing the text at some remembered count. The image warning likewise reports the shape of your picture, wider than tall or not, which is an observation about the file rather than a claim about anyone's specification.

Pasting tags, and the precedence behind them

The paste mode accepts a <head> fragment, a whole page, or a loose pile of tags. Both property= and name= are read, because Open Graph specifies one, most twitter: tags specify the other, and plenty of real pages get it backwards. Each field then resolves through the same order: the platform-specific tag first, the Open Graph tag next, and a plain HTML fallback such as <title> or link[rel=canonical] last. An X-specific value is kept apart rather than folded in, which is why the X card can legitimately differ from the other five. A summary lists what was found, what was absent and what was read but meant nothing here, so nothing is silently dropped.

Nothing leaves your browser
Your page is described, never fetched. A browser cannot read another site's HTML — the same-origin policy forbids it — so there is no “paste a link and we will scrape it” mode here, and no proxy standing in for one. An uploaded image is read through a local object URL that is released the moment it is replaced; an image named by address is loaded by your browser the way any page would load it.

Approximate on purpose

These cards are drawn from public rendering behaviour and carry no platform logos or branding. They are close enough in shape to catch a missing picture, a clipped headline or a hard crop, and they are not pixel-exact reproductions of anyone's interface.

An already-shared link keeps its old card
Whoever unfurled your link cached what they scraped, and they decide when to look again. Correcting a tag changes nothing about a post that is already out, and no preview tool can clear someone else's cache. Most platforms run a debugging or card-inspector page that re-scrapes a URL on demand — deploy the change first, then ask each one to re-read the page.

Frequently Asked Questions

Is the Social Share Preview Simulator free?

Yes, Social Share Preview Simulator is totally free :)

Can I use the Social Share Preview Simulator offline?

Yes, you can install the webapp as PWA.

Is it safe to use Social Share Preview Simulator?

Yes, any data related to Social Share Preview Simulator only stored in your browser (if storage required). You can simply clear browser cache to clear all the stored data. We do not store any data on server.

Why can't I just paste a link and have the tool read its tags?

A browser is not allowed to read another site's HTML. The same-origin policy blocks it, and routing the request through a proxy would mean handing your links to a third-party server this tool does not control. So the metadata has to come from you: type it into the fields, or paste the meta tags from your own page's head section. Everything then stays in your browser.

How closely do these cards match the real thing?

They match the shape, not the pixels. Each card is drawn from public rendering behaviour — a wide picture above the text, a small square beside it, a vertical accent bar — and carries no platform logos or branding. Platforms redesign their chrome without notice, so treat the previews as a way to catch missing images, clipped titles and hard crops rather than as a screenshot of the finished post.

What happens when there is no image?

Each card falls back to its text-only shape rather than leaving a gap, which is what the platforms themselves do. That is worth seeing: a link with no picture is a much smaller target in a feed than one with a picture, and the difference between the two is obvious in the grid.

Why is the description missing from some of the cards?

Not every card shows one. Some arrangements print the title and the domain only, so a carefully written description is simply never displayed there. The warnings panel names which cards show the description and which ignore it, so you can see where the effort lands.

I fixed my tags but the link still previews the old way. Why?

Whoever unfurled the link cached what they scraped, often for a long time, and they decide when to look again. Nothing on your page clears someone else's cache, and no preview tool can do it either. Most platforms run a debugging or card-inspector page that re-scrapes a URL on demand — that is the route to a refresh, and an already-published post will usually keep the old card regardless.

Is anything I type or upload sent anywhere?

No. There is no server involved at all: the text is rendered into the cards by your own browser, and an uploaded image is read with a local object URL that is released as soon as you replace it or leave the page. If you point at an image by its address, your browser loads that one picture from wherever it lives, exactly as any web page would.