Open Graph & Twitter Card Preview
Preview how your links appear on Facebook, X (Twitter), LinkedIn, Discord, Slack, WhatsApp & iMessage. Live image upload, auto-generated meta tags, image-size validation, presets & templates โ 100% client-side.
๐ผ Image (1200ร630 recommended)
๐ Twitter-specific
๐ Quick templates
How to Use the Open Graph & Twitter Card Preview
- Pick a platform โ Facebook, X/Twitter, LinkedIn, Discord, Slack, WhatsApp, iMessage, or "All at once" for side-by-side.
- Enter your image URL (or upload) โ 1200ร630 px is best for all platforms.
- Add title, description, URL, site name, pick a content type.
- Configure X-specific options โ card type, site & creator handles.
- Pick a template for a fast start, or use Fetch from URL to pull existing OG tags from any live page.
- Copy the generated meta tags and paste into your <head>.
What are Open Graph & Twitter Cards?
Open Graph (OG) is a meta-tag protocol Facebook introduced in 2010 controlling how your page looks when shared on social media. Twitter Cards is X's parallel protocol. Together they govern the title, description, image, and metadata in link previews on every major platform.
Without OG tags, social platforms guess โ often wrong. They may grab a random thumbnail, a meaningless snippet, or just the URL. The right OG image alone can double or triple click-through rates.
All major platforms โ Facebook, X, LinkedIn, Pinterest, Discord, Slack, WhatsApp, iMessage, Telegram, Microsoft Teams โ read OG tags. X additionally reads its own twitter:* tags (and falls back to OG if those aren't present). This tool generates both so your link looks perfect everywhere.
Common Use Cases
Why Choose Our OG Preview?
Frequently Asked Questions
What's the ideal OG image size?
1200ร630 px (1.91:1) works on all platforms. FB recommends 1200ร630, X needs at least 300ร157 (1200ร675 ideal), LinkedIn 1200ร627. Keep under 5 MB. JPG for photos, PNG for graphics.
What if I don't add OG tags?
Platforms guess. Random image, favicon, generic placeholder, or nothing. The page title + meta description become the preview text. Result: ugly previews, lower CTR.
Do I need both OG and Twitter tags?
You only NEED OG โ X falls back to OG. But explicit Twitter tags let you customize for X. Best practice: add both.
Why doesn't my new OG image show on Facebook/LinkedIn?
They cache aggressively. Use Facebook's Sharing Debugger and LinkedIn's Post Inspector to force re-fetch.
summary vs summary_large_image?
summary = small thumbnail beside text (article-focused). summary_large_image = big edge-to-edge image (higher engagement, recommended).
Different images per platform?
Yes โ set og:image for FB/LinkedIn, separate twitter:image for X. WhatsApp uses og:image at smaller dimensions. For Pinterest, use vertical 2:3 (1000ร1500).
Should OG title match my page title tag?
Not necessarily. <title> is for SERPs (keyword-optimized), og:title is for social (can be more emotional/click-worthy).
Is my data uploaded?
No โ all preview is local. Optional "Fetch from URL" uses a public CORS proxy.
