Digitools .ca

OpenGraph Previewer

Preview how a URL's OpenGraph and Twitter Card tags render on social media. Supports URL or pasted HTML.

URL lookups route through a third-party CORS proxy. Paste-HTML mode is fully client-side.

Heads up: Browser-based URL fetching needs a third-party CORS proxy because browsers can't fetch cross-origin pages directly. This tool currently uses api.allorigins.win. Public proxies rate-limit, occasionally go down, and sometimes change their terms. If URL fetching fails, use "Paste HTML" instead — that mode runs entirely in your browser and never depends on any third party.

About this tool

Previews how a webpage's OpenGraph and Twitter Card tags will render when the link is shared on social media. Useful when you've just updated your meta tags and want to confirm they parse correctly before posting.

What the tool reads

  • og:title, og:description, og:image, og:url, og:site_name, og:type
  • twitter:title, twitter:description, twitter:image, twitter:card
  • Falls back to <title> and standard <meta name="description"> when OG tags are missing

Two ways to use it

  • From URL: easier when the page is public. The request goes through a public CORS proxy because browsers can't fetch cross-origin pages directly. The proxy sees your URL.
  • Paste HTML: works for any page, including authenticated ones or local development. Open the page in your browser, View Source, copy, paste here. Nothing leaves your device.

Privacy note

The URL mode routes through a third-party CORS proxy (currently api.allorigins.win). The proxy sees the URL you're looking up but doesn't see anything from us — calls go directly from your browser. If you'd rather not involve any third party, use the "Paste HTML" tab.

Public CORS proxies tend to be unstable over time (rate limits, terms changes, full shutdowns). When this tool's URL mode breaks, you'll see a clear error message and can fall back to Paste HTML. The paste-HTML path is the durable one.

Frequently asked questions

The URL fetch fails — what now?
Two common reasons: (1) the CORS proxy is being rate-limited or blocking your region; (2) the target site is blocking proxy requests (Facebook, Instagram, LinkedIn often do this). In either case, switch to the "Paste HTML" tab — open the page in your browser, View Source (Ctrl+U or Cmd+Option+U), copy, paste. Same result, no proxy needed, always works.
Why does my preview not match what Facebook actually shows?
Facebook and Twitter cache aggressively and apply their own rendering quirks. To force a refresh on Facebook, use their Sharing Debugger. On Twitter/X, use the Card Validator (when available).
What size should my og:image be?
Facebook recommends 1200×630 pixels, ratio 1.91:1. Twitter prefers the same. Smaller images get downscaled and may look fuzzy; very different ratios get cropped unpredictably.
Is the URL I look up logged anywhere by Digitools?
No. The request goes from your browser to the CORS proxy directly — Digitools doesn't see it. The proxy itself may log requests; check their terms if it matters for your use case. The "Paste HTML" tab avoids any third party entirely.

Related tools

Last updated: May 17, 2026