Free Open Graph + X/Twitter + Facebook + LinkedIn Preview Tool

An Open Graph preview tool is a free debugger that fetches a webpage's HTML and extracts its Open Graph meta tags (og:title, og:description, og:image, og:url) and Twitter Card tags (twitter:card, twitter:title, twitter:image) to show you exactly how the page will appear when shared on social media. The tool makes an HTTP request to the URL you provide, parses the HTML head section for meta tags with 'og:' and 'twitter:' prefixes, and renders visual previews matching the card layouts used by Facebook, X/Twitter, and LinkedIn. This lets you verify your social sharing appearance before publishing or sharing links. Without previewing, you risk broken images, missing titles, truncated descriptions, or the wrong content appearing in share cards, all of which reduce click-through rates and engagement on social platforms.

The recommended Open Graph image size is 1200 x 630 pixels with a 1.91:1 aspect ratio. This size displays optimally across Facebook, LinkedIn, WhatsApp, Slack, and most platforms that support Open Graph. For Twitter Cards using the 'summary_large_image' card type, the recommended size is 1200 x 628 pixels, which is nearly identical to the OG standard. For Twitter's smaller 'summary' card type, use 144 x 144 pixels minimum (up to 4096 x 4096). The image file should be under 8 MB for Facebook and under 5 MB for Twitter. Use JPEG or PNG format for best compatibility. Always include the full absolute URL in your og:image tag (starting with https://), not a relative path. If your image is smaller than 600 x 315 pixels, Facebook will display it as a small thumbnail instead of a large preview card, significantly reducing engagement.

Open Graph (OG) tags were created by Facebook in 2010 and have become the universal standard for social media link previews. They use the property attribute with 'og:' prefix in HTML meta tags. Twitter Cards are Twitter's proprietary system that uses the name attribute with 'twitter:' prefix. The key practical difference is fallback behavior: if Twitter Card tags are not present, Twitter will fall back to reading Open Graph tags instead. Facebook and LinkedIn only read OG tags and ignore Twitter Card tags. This means you should always implement Open Graph tags as your baseline, then optionally add Twitter Card tags for Twitter-specific customization. The most common Twitter-only tag is twitter:card, which controls the card layout (summary, summary_large_image, player, or app). For most websites, implementing OG tags plus twitter:card is sufficient for optimal display across all platforms.

Missing OG images are one of the most common social sharing problems and can have several causes. First, check that your og:image tag uses an absolute URL starting with https:// — relative paths like /images/og.jpg won't work. Second, verify the image URL is publicly accessible and not behind authentication or a CDN that blocks crawlers. Third, ensure the image meets minimum size requirements: Facebook requires at least 200 x 200 pixels, but images under 600 x 315 display as small thumbnails. Fourth, check that your server returns the correct Content-Type header for the image (image/jpeg or image/png). Fifth, social platforms cache OG data aggressively — if you recently added or changed your og:image, use Facebook's Sharing Debugger or Twitter's Card Validator to force a cache refresh. Finally, some platforms block images served from localhost or private networks during development.

Social media platforms cache Open Graph and Twitter Card data to reduce server load, which means changes to your meta tags won't appear immediately when resharing. To force Facebook to refresh, use the Facebook Sharing Debugger (developers.facebook.com/tools/debug) — paste your URL and click 'Scrape Again.' This clears Facebook's cache and fetches fresh OG data. For Twitter/X, use the Card Validator (cards-dev.twitter.com/validator) to preview and refresh your Twitter Card. LinkedIn has its own Post Inspector (linkedin.com/post-inspector) for refreshing cached data. For WhatsApp and Telegram, there is no official tool — WhatsApp caches OG data for approximately 7 days and refreshes automatically. As a best practice, always test your OG tags with these platform debuggers before launching a campaign or sharing important content, especially after making changes to titles, descriptions, or images.

In most cases, you only need Open Graph tags plus one Twitter-specific tag (twitter:card) to cover all major platforms. Facebook, LinkedIn, WhatsApp, Slack, Discord, Telegram, and iMessage all read Open Graph tags. Twitter reads Twitter Card tags first but falls back to OG tags if they are missing. The one tag you should always add specifically for Twitter is twitter:card with the value 'summary_large_image' (for large preview images) or 'summary' (for smaller cards), because this controls the card layout and has no OG equivalent. You may optionally add twitter:title and twitter:description if you want different copy on Twitter versus other platforms — for example, shorter text optimized for Twitter's character limits. Pinterest reads OG tags but also supports its own pin description meta tag. For most websites, implementing the four core OG tags plus twitter:card provides complete coverage.