Open Graph Meta Generator
Generate Open Graph and Twitter Card meta tags with live social media card previews for Facebook, Twitter/X, LinkedIn, Discord, and WhatsApp. 100% client-side.
How to Use
Generate pixel-perfect Open Graph and Twitter Card meta tags with live social media previews showing exactly how your links appear when shared on Facebook, Twitter/X, LinkedIn, Discord, and WhatsApp.
How to use this tool
- Enter OG Details: Fill in your page title (max 60 characters for Facebook), description (max 200 characters), page URL, and image URL. The character counters show real-time feedback on optimal lengths.
- Set Image URL: Provide a direct URL to your OG image. The ideal size is 1200x630 pixels (1.91:1 ratio). This image appears in social card previews across all platforms.
- Configure Platform Settings: Select the OG type (
website,article, orproduct), choose your Twitter card style (summary_large_imagefor hero images orsummaryfor compact cards), and add your Twitter handle. - Preview on Each Platform: Switch between the Facebook, Twitter/X, LinkedIn, Discord, and WhatsApp tabs to see pixel-accurate mock previews of your social card.
- Copy & Deploy: Copy the generated HTML meta tags and paste them into the
<head>section of your web page. Use platform debuggers to verify after deployment.
About This Tool
Open Graph Protocol
The Open Graph protocol, originally created by Facebook in 2010, transforms ordinary web pages into rich objects within social graphs. When you share a URL on Facebook, LinkedIn, Discord, or WhatsApp, the platform's crawler reads your og:title, og:description, og:image, and og:url meta tags to construct a visual card preview. Without these tags, platforms generate card content by scraping your page content, often producing poor-quality previews with missing images or truncated text.
Twitter Cards vs Open Graph
Twitter/X implements its own card system using twitter:card, twitter:title, twitter:description, and twitter:image meta tags. Twitter falls back to Open Graph tags when its own tags are absent, but there are key differences: Twitter supports two card types (summary for small square images, summary_large_image for hero images), enforces different character limits (70 characters for title, 200 for description), and uses its own image aspect ratios. Our generator outputs both tag sets simultaneously so each platform gets optimized content.
Platform-Specific Rendering
Each social platform renders shared links differently. Facebook displays a 1.91:1 aspect ratio image with title and description below. LinkedIn uses the same ratio but truncates more aggressively. Discord shows an embedded card with a colored left-border accent, the site name above the title, and a large inline image. WhatsApp renders a compact card within a chat bubble, requiring images under 300KB for reliable unfurling. This tool previews all five rendering modes so you can optimize for each audience.
Image Best Practices
Use a 1200x630px image at 1.91:1 aspect ratio for maximum compatibility. Keep file size under 300KB for WhatsApp and under 5MB for Facebook. Always use HTTPS URLs; some platforms (especially Twitter/X) silently reject HTTP image URLs. Center-crop your key content because platforms may crop to different ratios. If using text overlays, keep text within the inner 80% safe zone to avoid cropping.
Why Use This Tool
Why Open Graph Tags Matter
Pages with properly configured Open Graph tags see up to 2.5x higher click-through rates when shared on social media, according to multiple marketing studies. A well-crafted social card with a compelling image, concise title, and engaging description can be the difference between a scroll-past and a click. For content marketing and SEO strategies, social sharing amplification is a significant traffic driver that starts with correct meta tag implementation.
Privacy-First Generation
This generator runs entirely in your browser. Your page metadata, URLs, and content strategy details are never transmitted to any server. Unlike online OG validators that fetch your page, our tool generates tags locally, making it safe for use with pre-launch pages, internal tools, and confidential projects.