How to Preview Open Graph Tags on LinkedIn, WhatsApp & Discord Before Sharing

LinkedIn, WhatsApp, and Discord all read Open Graph tags differently — and each has its own image size preferences and caching quirks. Here is how to preview exactly what your link will look like on each platform before you share it.

You have just published a blog post. The og:title is set, the og:image looks great in your CMS preview. You share it on LinkedIn — and the image is cropped weirdly, showing half your logo and half of someone's face. You paste it into your Discord server — and the wrong description appears. You send it in a WhatsApp group — and there is no image preview at all. Same URL, same OG tags, three completely different results.

This happens because each platform interprets OG tags with its own rendering logic, caching rules, and fallback behavior. Here is exactly what each platform does and how to get consistent, professional previews everywhere.

How Each Platform Reads OG Tags

Platform	Reads og:title	Reads og:description	og:image Size Recommended	Has Own Debugger	Caching Behavior	Fallback When Tags Missing
Facebook	✓ Yes	✓ Yes	1200x630px	✓ Sharing Debugger	~Aggressive (days-weeks)	Scrapes page title + first image
Twitter/X	✓ Fallback from twitter:title	✓ Fallback from twitter:description	800x418px (summary_large_image)	✗ Deprecated 2022	~7 days typical	Uses title tag + no image
LinkedIn	✓ Yes	✓ Yes	1200x627px	✓ Post Inspector	~24 hours typical	Pulls page title + first image found
WhatsApp	✓ Yes	✓ Yes	1200x630px (compressed)	✗ No debugger	~Very aggressive (days)	Shows URL only, no preview card
Discord	✓ Yes	✓ Yes	1200x630px (displays large)	✗ No debugger	~Minutes to hours	Shows URL text only
Slack	✓ Yes	✓ Yes	1200x630px	✗ No debugger	~Hours	Shows URL with minimal preview

LinkedIn Post Inspector

LinkedIn is one of the more predictable platforms for OG previews, and they provide a testing tool. Here is how to use it:

1. Go to linkedin.com/post-inspector/
2. Paste your URL and click Inspect
3. LinkedIn shows the cached preview — og:title, og:description, og:image
4. If the data is outdated, click the refresh button to force a re-fetch
5. LinkedIn usually updates the cached data within minutes

LinkedIn quirks to know:

• LinkedIn crops images more aggressively than Facebook. Keep important content in the center 80% of your image.
• LinkedIn is strict about image quality. Blurry, low-resolution images (under 200px wide) may not display in the preview at all.
• If og:image is missing, LinkedIn scans the page for any image tag and uses whatever it finds first. This could be a tiny icon, a tracking pixel, or a sidebar ad. Always set og:image explicitly.
• LinkedIn truncates og:description at approximately 150 characters. Write your description with that limit in mind.

WhatsApp Link Preview Quirks

WhatsApp is the most unpredictable platform for OG previews. Here is what you need to know:

• No testing tool exists. WhatsApp has no equivalent of Facebook's debugger or LinkedIn's Post Inspector. The only way to test is to send the link to yourself in a WhatsApp chat.
• Image compression is heavy. WhatsApp compresses og:image aggressively to save bandwidth on mobile. High-detail images with text overlays become blurry. Use bold, high-contrast images with large text if the image contains words.
• Caching is aggressive and unpredictable. WhatsApp can cache a link preview for hours or days. There is no way to force a cache clear. If you update your OG tags and the old preview still appears, you have to wait.
• Preview generation happens on the sender's device. When you paste a link into a WhatsApp message, your phone fetches the OG data and generates the preview locally. If the fetch fails (slow server, large image, timeout), no preview appears at all.
• HTTPS is required. WhatsApp will not generate link previews for HTTP-only URLs. Your site must have an SSL certificate.

Best practices for WhatsApp previews:

1. Use a small, optimized og:image (under 300KB for fastest loading on mobile)
2. Keep og:title under 40 characters — WhatsApp truncates aggressively
3. Keep og:description under 100 characters
4. Use high-contrast images that survive heavy compression
5. Test by sending the link to yourself before sharing publicly

Discord Embed Previews

Discord is one of the best platforms for OG tag support. It renders rich, visually appealing embeds for shared links with features other platforms do not offer:

• og:video support — Discord can embed inline video players from og:video tags. If your page has a video preview, Discord will play it directly in the chat.
• Colored sidebar — Discord reads the <meta name="theme-color" content="#hex"> tag and uses it as the embed sidebar color. This is a subtle but effective branding opportunity.
• og:site_name is prominent — Discord shows your site name above the title in the embed header. Make sure og:site_name is set to your brand name.
• Large image display — Discord shows og:image in a large format by default. Images look great in Discord if they are the right size (1200x630px).
• Fast cache updates — Discord refreshes cached link data more frequently than most platforms (minutes to hours, not days). Updated OG tags appear quickly.

Discord-specific tips:

• Add a theme-color meta tag to brand your embeds: <meta name="theme-color" content="#58a6ff">
• Set og:site_name to your brand name — it appears above the title in Discord embeds
• If you have video content, add og:video for inline playback in Discord
• Discord supports multiple og:image tags — it will display the first one

Slack Link Previews

Slack unfurls links in channels and direct messages using OG tags. The preview is compact compared to Discord but still effective:

• Slack reads og:title, og:description, og:image, and og:site_name
• It also reads twitter:card tags as a secondary source if OG tags are incomplete
• Slack link previews update within a few hours when you change OG tags — faster than Facebook but slower than Discord
• Image display: Slack shows a thumbnail on the right side of the text preview (compact mode) or a larger image below (depending on the workspace settings and card type)
• Slack respects robots.txt — if your page blocks the Slackbot user-agent, no unfurl will appear

The One OG Setup That Works Everywhere

You do not need platform-specific tags for every platform. This single set of tags works across Facebook, Twitter/X, LinkedIn, WhatsApp, Discord, and Slack:

<!-- Universal OG tags -->
<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="A compelling summary under 150 characters">
<meta property="og:image" content="https://yoursite.com/image-1200x630.jpg">
<meta property="og:url" content="https://yoursite.com/page/">
<meta property="og:type" content="article">
<meta property="og:site_name" content="Your Brand Name">

<!-- Twitter-specific (only one tag needed) -->
<meta name="twitter:card" content="summary_large_image">

<!-- Discord branding (optional but recommended) -->
<meta name="theme-color" content="#yourcolor">

That is 8 tags total. This setup covers every major platform. Twitter falls back to OG tags for everything except the card type. Discord picks up the theme-color for sidebar branding. LinkedIn, WhatsApp, Slack, and Facebook all read the same core OG tags.

Platform-Specific Meta Tags Beyond OG

Some platforms support additional meta tags beyond the Open Graph standard:

Tag	Platform	Purpose	Example
twitter:card	Twitter/X	Sets card type (summary, summary_large_image)	summary_large_image
twitter:site	Twitter/X	Your Twitter handle for attribution	@yourhandle
theme-color	Discord, Chrome mobile	Accent color for embeds and browser chrome	#58a6ff
og:video	Discord, Facebook	URL for inline video playback in embeds	https://yoursite.com/video.mp4
og:image:width	Facebook, LinkedIn	Image dimensions (speeds up rendering)	1200
og:image:height	Facebook, LinkedIn	Image dimensions (speeds up rendering)	630
og:locale	Facebook	Language and region for the content	en_US
article:published_time	Facebook, LinkedIn	Publication date for articles	2026-04-02T00:00:00Z

Debugging Cross-Platform Preview Issues

When the same URL shows different previews on different platforms, here is the systematic way to debug:

1. Check OG tags first. Use our Open Graph Checker to see exactly what tags are present and whether any are malformed or missing.
2. Verify the image is accessible. Open the og:image URL directly in a browser. If it 404s, redirects, or takes more than 3 seconds to load, some platforms will skip it.
3. Check for platform-specific overrides. Some CMS platforms add twitter:image or other tags that override og:image for specific platforms. Look for conflicting tag values.
4. Clear platform caches individually. Facebook: Sharing Debugger scrape. LinkedIn: Post Inspector refresh. Twitter: wait 7 days or use query parameter trick. Discord: usually updates within minutes. WhatsApp: wait or test with a query parameter appended.
5. Test with the actual platform. After validating tags, share the URL on each platform. Use private accounts or test channels for LinkedIn, Discord, and Slack. Send to yourself on WhatsApp.

Tools for Cross-Platform OG Testing

• Open Graph Checker — validate all OG tags and preview how they will render across platforms
• Meta Tag Generator — generate the universal tag set that works on every platform
• Image Compressor — optimize og:image under 300KB for fastest WhatsApp previews
• Image Resizer — resize to the universal 1200x630px standard
• Image Cropper — crop to 1.91:1 aspect ratio for consistent display
• Social Media Resizer — resize images for platform-specific dimensions
• Robots.txt Generator — ensure social platform crawlers are not blocked
• Headline Analyzer — craft og:title headlines that drive clicks from social previews