OG Tag Previewer
Preview how your Open Graph tags appear on social platforms.
Related Tools
Meta Tag Generator
Generate meta tags, Open Graph tags, and Twitter Card markup for any page. Real-time preview with copy and download.
Use tool →Twitter Card Validator
Preview and validate Twitter Card meta tags from any URL or HTML.
Use tool →UTM Link Builder
Build campaign URLs with UTM parameters for Google Analytics tracking.
Use tool →Schema.org Generator
Generate JSON-LD structured data for LocalBusiness, Product, FAQ, Article, and 12+ schema types.
Use tool →How to Preview Your Open Graph Tags
View Source on your page (Ctrl+U on Windows, Cmd+Option+U on Mac), copy the entire HTML, and paste it above. The tool extracts every Open Graph and Twitter Card meta tag, then shows you exactly how Facebook, Twitter/X, and LinkedIn will render your link when someone shares it. No guessing, no posting a test link to see what happens.
The extracted tags panel shows you what's set, what's missing, and what might cause problems. If your og:description is 400 characters long, you'll see a warning because Facebook is going to chop it at 155. If your og:image is a relative URL, social platforms won't be able to find it. Better to know now than after your post goes live.
What Are Open Graph Tags?
Open Graph is a protocol Facebook created in 2010 to control how URLs appear when shared on social media. You add <meta property="og:..."> tags to your page's <head>, and every major platform reads them to build the link preview card — the image, title, and description people see before they click.
The three tags that matter most: og:title, og:description, and og:image. Without them, platforms pull whatever they can find from your page — usually the wrong thing. Your carefully written headline gets replaced by your site's tagline, and your hero image gets replaced by a random thumbnail. Set the tags, control the narrative.
Facebook vs Twitter vs LinkedIn: How They Differ
All three platforms read og: tags, but they don't render them identically. Facebook truncates descriptions around 155 characters. Twitter has its own twitter: meta tags that override the OG equivalents, plus two card layouts: a small thumbnail ("summary") and a large banner ("summary_large_image"). LinkedIn is the most aggressive truncator — descriptions get cut around 100 characters.
Image requirements differ too. Facebook wants 1200×630 pixels (1.91:1 ratio). Twitter's large card uses 2:1 ratio; its summary card uses a 1:1 square. LinkedIn uses the same 1.91:1 as Facebook. If you only set one image size, go with 1200×630 — it works acceptably everywhere.
Recommended Image Sizes
Facebook and LinkedIn: 1200×630 pixels, 1.91:1 aspect ratio. Twitter summary_large_image: 1200×600 pixels, 2:1 ratio. Twitter summary (small card): 144×144 pixels minimum, 1:1 square. Facebook requires at least 200×200 to display an image at all. Keep file size under 5 MB for Facebook and 8 MB for all others. Use JPG or PNG — SVG won't render in social cards.
What size should my og:image be? +
Why does my preview look different on Facebook vs Twitter? +
twitter:title, twitter:description, etc.) that override the OG equivalents. Twitter also has two card layouts — "summary" with a small thumbnail, and "summary_large_image" with a banner — controlled by the twitter:card tag. Facebook always uses the same layout. If you set different values for og:title and twitter:title, each platform shows different text.
Do I need both og: and twitter: tags? +
og: tags when twitter: tags aren't set, so you can get away with just OG tags. But you need twitter:card to control the card layout — without it, Twitter defaults to the small "summary" card. Best practice: set the core OG tags, add twitter:card, and only add other twitter: tags if you want platform-specific titles or descriptions.
Why isn't my og:image showing? +
https:// URL), the image is too small (Facebook requires at least 200×200 pixels), the image is behind authentication or a CDN that blocks crawlers, or the server is returning the wrong content type. Also check that the URL actually works — paste it into a browser tab to verify.