Open Graph Preview
See how your Open Graph meta tags will look when shared on Facebook, Twitter, LinkedIn and other platforms.
Updated July 11, 2026
100% Private & Secure
This tool runs in your browser.
Your data is never uploaded or stored.
Fill in the OG fields and click "Preview" to see how your link will appear...
How to use
- 1
Enter your Open Graph meta tags or HTML.
- 2
See a live preview of how your link appears.
- 3
Adjust tags and preview again.
When to use it
Previewing a blog post before it ships
Paste the OG tags and instantly see how the link renders across Facebook, X (Twitter), LinkedIn, Slack, and Discord — before anyone shares it. This catches missing images and overlong titles that would otherwise go live unnoticed.
Validating an og:image across platforms
A single og:image at 1200×630 px renders cleanly on every major platform. The preview confirms whether your image meets the recommended dimensions and is reachable at the absolute URL you declared.
Checking Twitter Card compatibility
Adding twitter:card set to summary_large_image opts into the large-preview format on X. The preview shows both the Open Graph fallback and the Twitter-specific rendering side by side.
Debugging a broken social preview
When a shared link shows a blank card or a stale image, the cause is usually a missing tag, a relative URL, or a cached preview. The tool surfaces exactly which required tags are absent and which values are malformed.
How it works
The Open Graph protocol, explained
Open Graph is a protocol introduced by Facebook in 2010 and now specified at ogp.me. It turns any URL into a rich object: when a crawler hits a page with OG tags, it renders a card with title, description, image, and link instead of a plain-text URL.
The protocol defines four required properties per page: og:title, og:type (typically website or article), og:image, and og:url. Everything else — og:description, og:site_name, og:locale — is optional but strongly recommended for a polished preview.
-
og:title— the headline; keep under ~60 characters to avoid truncation in cards -
og:image— absolute URL; recommended 1200×630 px, at least 200×200 minimum -
og:url— the canonical URL; used when aggregating shares and engagement -
og:type— affects which additional properties are valid (article has author, published_time, etc.)
The 1200×630 image standard
A single image at 1200 × 630 pixels (a 1.91:1 aspect ratio) renders cleanly across Facebook, X, LinkedIn, Discord, and Slack with minimal cropping. The Meta sharing documentation recommends at least 1200×630 for high-resolution displays, with an 8 MB file-size ceiling.
Twitter's summary_large_image card technically prefers a 2:1 ratio (1200×600), but in practice a 1200×630 OG image displays well there too. Keep important content away from the edges to survive any platform-specific cropping.
<meta property="og:image" content="https://devtidy.com/og/json-formatter.png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="JSON Formatter — DevTidy"> Twitter Cards and the twitter: namespace
X (formerly Twitter) reads Open Graph tags as a fallback but also defines its own twitter:* namespace for finer control. Setting twitter:card to summary_large_image requests the large image card; summary requests the small square thumbnail.
When both OG and Twitter tags are present, Twitter prefers the Twitter-specific values. Most sites get away with OG tags plus a single twitter:card declaration — the rest of the OG set fills in automatically. The X Card documentation lists the minimum image dimensions (300×157) and maximum (4096×4096) for large-image cards.
Common mistakes & edge cases
Social preview shows no image
The og:image URL is missing, relative, or not publicly fetchable. Use an absolute https URL to a 1200×630 image, and confirm it returns HTTP 200 to any user agent — not just logged-in users.
Preview still shows the old image after a change
Social platforms cache OG data aggressively. Use Facebook Sharing Debugger or Twitter Card Validator to force a re-scrape after updating tags — changes do not propagate on their own.
Image renders cropped on one platform but not another
Each platform applies slightly different cropping. Use 1200×630 px (1.91:1) and keep logos and text within the central safe zone, at least 150 px from every edge.
Twitter shows a plain summary instead of a large image
You are missing twitter:card="summary_large_image". Add it explicitly — Twitter will not infer the large-image format from og:image alone.
Frequently Asked Questions
What is Open Graph?
References & further reading
Related reading
Open Graph and Twitter Card preview debugging
Why link previews break, the OG tags and image dimensions that fix them, and the debugging workflow that catches problems before users do.
Canonical tags: solving duplicate content for good
How rel=canonical works, where duplicate URLs come from, and the implementation mistakes that tell Google the wrong page is canonical.
Meta tags that actually matter for SEO
The meta tags worth setting — title, description, robots, viewport, canonical, OG — with copy-paste examples and what each one does.