Preview how your web page looks when shared on Facebook, Twitter/X, LinkedIn, and WhatsApp. Audit OG tags, get a score out of 100, and generate optimized meta tags — free and instant.
Google Search
Page Title
https://example.com
Your description will appear here...
Facebook / LinkedIn
EXAMPLE.COM
Page Title
Your description here...
Twitter / X
Page Title
Your description...
example.com
Page Title
Your description here...
example.com
Open Graph Preview is a free tool that lets you see exactly how your web page will look when shared on Facebook, LinkedIn, Twitter/X, and WhatsApp — before you publish. Open Graph (OG) tags are HTML meta tags that control the title, description, and image that appear in social media link previews. Without proper OG tags, social platforms will guess what to show — often displaying the wrong image, a truncated title, or no description at all. This tool also parses existing HTML to audit your current tags, scores your implementation, and provides actionable recommendations to maximize your social media click-through rate.
Use a 1200x630 pixel image for og:image (the optimal size for Facebook and LinkedIn). Keep your title under 60 characters and description between 120-160 characters. Always include twitter:card (use "summary_large_image" for the most impactful previews). Set og:type to "article" for blog posts and "website" for homepages. Test your URLs after publishing using Facebook's Sharing Debugger and Twitter's Card Validator to clear any cached previews.
Essential terms and definitions related to Open Graph Preview.
A protocol originally created by Facebook in 2010 that enables any web page to become a rich object in a social graph. Open Graph uses meta tags in the HTML <head> to define the title, description, image, URL, and type of a page. When a URL is shared on social media, the platform reads these tags to generate a rich link preview. The four required OG properties are og:title, og:type, og:image, and og:url.
Twitter's proprietary meta tag system for controlling link previews on Twitter/X. There are four card types: "summary" (small image + text), "summary_large_image" (large banner image + text), "app" (app download card), and "player" (inline video/audio). Twitter falls back to Open Graph tags if Twitter-specific tags are not present, but the twitter:card tag must be explicitly set to choose the preview format.
The preferred URL for a page when it is accessible at multiple URLs. The canonical URL is specified with <link rel="canonical" href="..." /> and tells search engines which URL to index and display in search results. It is also used by social platforms to associate all shares of the same content, regardless of URL parameters or tracking codes, with a single canonical link.
A map of connections between entities (people, pages, content) on a social platform. When you share a URL with Open Graph tags, the platform creates a "node" for that URL in its social graph, linking it to your profile and to anyone who interacts with the share. Rich metadata (title, image, description) makes this node more engaging and clickable, which increases reach through the platform's algorithm.
Open Graph (OG) tags are HTML meta tags that control how your page appears when shared on social media platforms like Facebook, LinkedIn, Twitter/X, and WhatsApp. Without OG tags, these platforms guess what to display — often showing the wrong image, a truncated title, or no description. Properly configured OG tags can increase click-through rates by 2-3x on social shares by ensuring your content looks professional and engaging in every link preview.
The optimal og:image size is 1200x630 pixels (1.91:1 aspect ratio). This size displays correctly across all major platforms: Facebook uses 1200x630 for link previews, LinkedIn uses the same ratio, and Twitter's "summary_large_image" card displays it well. For Twitter's smaller "summary" card, a 600x600 square image works better. Always use HTTPS URLs for images and keep file sizes under 5MB.
Social platforms cache link previews aggressively. Facebook caches previews for about 30 days, Twitter for about 7 days. To force a refresh: use Facebook's Sharing Debugger (developers.facebook.com/tools/debug/) to scrape new data, use Twitter's Card Validator (cards-dev.twitter.com/validator) to refresh the cache, and for LinkedIn, use the Post Inspector (linkedin.com/post-inspector/). Always clear the cache after updating OG tags.
Twitter/X supports Open Graph tags as a fallback, but for optimal control, include both. Twitter-specific tags (twitter:card, twitter:title, twitter:description, twitter:image) take priority over OG tags on Twitter. The most important Twitter-specific tag is twitter:card, which determines the preview format: "summary" shows a small image, while "summary_large_image" shows a large banner image. If you only implement one set, use Open Graph — it has the broadest platform support.
Parse HTML mode lets you paste the <head> section of any HTML page, and the tool will extract all Open Graph tags, Twitter Card tags, standard meta tags, canonical URLs, and favicons. It then scores your implementation out of 100, shows warnings for potential issues (like titles that are too long), and provides specific recommendations for missing tags. This is useful for auditing existing pages before publishing.
No. This tool does not fetch external URLs — it works entirely with data you provide (either manual input or pasted HTML). This means no network requests are made and your data stays private. To test a live URL, view the page source in your browser (Ctrl+U), copy the <head> content, and paste it into the Parse HTML tab.
Common errors developers encounter and how to resolve them.
Facebook shows wrong image despite correct og:image tag Facebook aggressively caches link previews. Use the Facebook Sharing Debugger (developers.facebook.com/tools/debug/) to force a re-scrape. Also verify that your og:image URL is absolute (starts with https://), the image is accessible publicly (not behind authentication), and the image file is under 5MB. Facebook requires images to be at least 200x200 pixels.
Twitter preview shows "summary" instead of large image Make sure you have the tag <meta name="twitter:card" content="summary_large_image" /> in your page head. The default Twitter card type is "summary" (small image). Also ensure your og:image or twitter:image is at least 300x157 pixels for the large image format to display.
Parse HTML mode does not detect my tags The parser looks for standard meta tag formats. Make sure your tags use proper syntax: <meta property="og:title" content="..." /> or <meta name="twitter:card" content="..." />. Tags with non-standard attribute order or single quotes may not be detected. Also ensure you are pasting the complete <head> section, not just individual tags.