Illustrative Facebook card
May vary card layout, text density and crop by placement, device and ongoing product experiments.
One URL, several rendering systems
Use social preview simulations as a preflight, not a promise
Compare the story carried by image, title, domain and description—then verify the real public page and account for each platform's cache.
What changes between platforms
Illustrative, non-pixel-perfect comparisons
Illustrative LinkedIn card
Uses its own metadata cache and may truncate supporting text differently from consumer social feeds.
X
Illustrative X cardIllustrative X card
Card presentation depends on supported card metadata and current product rules; the visible description can be limited.
Slack and chat apps
Illustrative Slack unfurlIllustrative Slack unfurl
Often build compact unfurls with their own fallback order, density and workspace-level behavior.
What a card simulation can and cannot prove
A simulation is useful for checking hierarchy, likely truncation and whether the image still reads at small size. It cannot reproduce every platform experiment, device width, account setting or crawler decision.
Use the simulation to improve the source material. Use the deployed page, its rendered metadata and each platform's official debugging workflow to verify delivery.
A cache-aware debugging flow
- Inspect the deployed public URL rather than a local or authenticated preview.
- Confirm the final HTML exposes a concise title, description and absolute public image URL.
- Fetch the image URL directly and verify your CDN returns the intended file and media type.
- Use the target platform's official debugger or refresh tool when an old cache persists.
- Share a new test URL only when the platform provides no reliable cache refresh path.
Preview FAQ
Social preview questions
Practical expectations for simulations and real platform caches.
Are the preview cards pixel-perfect?
No. They are labeled simulations for hierarchy and text-density review. Platforms can change layouts and crops without notice.
Why does a corrected page still show the old image?
The platform may have cached the earlier metadata or asset. Verify deployment first, then use its official debugger or refresh workflow.
Should every platform receive different metadata?
Start with one clear, resilient story. Add platform-specific tags only when a real audience or placement requirement justifies the extra maintenance.
Move from simulation to verification
Build a resilient source card
Create the core asset in the full generator, then inspect the deployed metadata before sharing.