🇬🇧 English🇪🇸 Español🇫🇷 Français🇩🇪 Deutsch🇸🇦 العربية🇧🇷 Português
🚀 Explore All Tools
🚀 Explore All Tools

OpenGraph Previewer

Preview social share cards and extract meta from any page, free, private, 100% in-browser.

Enter a URL to fetch (may be blocked by CORS). Parsing is local.
📋

How to use this tool

1
⌨️
1. Enter your input
Type, paste or drop your file above.
2
🔒
2. Run in browser
Your files never leave your device.
3
💾
3. Download result
Save or copy instantly, no sign-up.

Preview how your link looks when shared

Free OpenGraph Previewer reads the Open Graph and Twitter Card tags of any URL and renders the preview that Facebook, X, LinkedIn, WhatsApp and Slack would show. Paste a link to see the title, description and image exactly as they will appear.

What to check before publishing

  • Title, clear, unique and under about 60 characters
  • Description, compelling and under about 155 characters
  • Image, at least 1200×630 for large cards
  • Missing or duplicated og: tags

The tool also lists the raw tags it found, so you can spot typos, relative image paths or pages that fall back to a bare link preview. Free, no sign-up, and nothing is stored.

How the preview is built

The page HTML is fetched and its Open Graph and Twitter Card tags are parsed: og:title, og:description, og:image (with its declared dimensions), og:url, og:type, plus the twitter: equivalents. The result is rendered as it would appear in a shared link card, and the raw tag list reveals the usual culprits, truncated titles, missing og:image, relative image URLs that break when crawled from outside, or tags duplicated by a plugin. Absolute image URLs with the correct size are what platforms actually need.

Processing details and limits

PropertyOpenGraph previewer behavior
InputAny public URL
Parsesog:title, og:description, og:image, og:url, og:type, twitter:*
ShowsVisual preview card plus the raw tag list
CatchesMissing tags, relative image paths, title/description truncation
Stored by 0AppzNothing
CostFree, no account, no extension

Privacy: fetched from your browser

The fetch happens on your connection, so the target site sees your request as a normal visit. 0Appz does not proxy the page or store the tags; there is no history of the URLs you preview.

Fixing common preview problems

  • Use absolute https URLs for og:image, relative paths fail outside the site.
  • Provide 1200×630 images for large cards; smaller ones become thumbnails.
  • Keep titles under about 60 characters and descriptions near 150-200.
  • Set both Open Graph and Twitter Card tags for consistent previews.
  • After changing tags, re-scrape in the platform debugger, caches are sticky.

Related: browse the developer tools for meta tags, headers and SSL checks.

Which tags actually control the preview

Platforms read a small set of tags when they build a share card, and the rest are ignored. og:title sets the headline; if it is missing, the crawler falls back to the HTML title, which often carries a site suffix you did not intend. og:description controls the two or three lines under the headline, and og:url tells the platform which canonical address the card belongs to, a mismatch here is a common cause of cards pointing at the wrong page. The image is the part most often wrong: og:image must be an absolute https URL, ideally 1200×630 pixels for a 1.91:1 ratio, and under about 5 MB so the crawler does not time out. og:image:width and og:image:height let the platform reserve layout space before the image loads. For X, twitter:card selects the layout, summary_large_image is what most sites want, and twitter:title, twitter:description and twitter:image can override the OpenGraph values when the two networks need different copy. Two practical checks save time: confirm that the previewed URL returns 200 without a redirect chain, and remember that platforms cache cards aggressively, so use each network's own debugger to force a refresh after changing tags.

Frequently asked questions

Why does direct fetch fail for some sites? +

Browsers block cross-site reads (CORS). This tool fetches the page directly in your browser.

What tags are extracted? +

og:title, og:description and og:image (with twitter: fallbacks and document title). Relative image URLs are resolved against the page URL.

Are the URLs I preview stored anywhere? +

Yes. The page is fetched straight from your browser to the target site; nothing passes through 0Appz servers.

🔒 100% browser-based. Your files never leave your device