OG Image Not Showing on Mobile: How to Fix Social Previews on iOS and Android

Why OG Images Work on Desktop but Not Mobile

Desktop social platforms (Twitter.com, LinkedIn.com, Facebook.com) fetch link previews server-side. Mobile apps — especially messaging apps — often rely on a different scraper pipeline, or they cache aggressively, or they apply stricter size/HTTPS requirements. A preview that works fine in Chrome on your laptop can completely fail in iOS Messages.

The fix is usually one of five things: image size, HTTPS, cache, accessibility from mobile scrapers, or an app-specific tag requirement. Work through the checklist below.

Quick Diagnostic

First, confirm what you actually have. Paste your URL into OGFixer and review the preview. Check: Does og:image exist? Is it an absolute HTTPS URL? Is it ≥ 300×157px? Is the image accessible without a cookie or login?

Fix 1: Image Too Small or Wrong Aspect Ratio

Mobile previews are tighter. Many messaging apps require a minimum image size to display a thumbnail at all. Use these minimums:

• WhatsApp: At least 300×157px; 1200×630px is ideal (2:1 ratio).
• iOS Messages / iMessage: At least 200×200px for a square thumbnail; 1200×630px for a wide card.
• Telegram: At least 100×100px, but small images may not display as a rich card.
• Instagram DMs: 1080×1080px or 1200×628px — non-square images may be cropped.
• Facebook/Messenger mobile: 600×315px minimum, 1200×630px recommended.

<!-- Correct og:image for mobile compatibility -->
<meta property="og:image" content="https://example.com/images/preview-1200x630.png" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />

Fix 2: HTTP Instead of HTTPS

Mobile apps almost universally block mixed-content. If your og:image URL starts with http://, mobile clients will silently skip it. Make sure your image is served over HTTPS and that the SSL certificate is valid (not expired, not self-signed).

<!-- Wrong: -->
<meta property="og:image" content="http://example.com/image.png" />

<!-- Correct: -->
<meta property="og:image" content="https://example.com/image.png" />

Fix 3: Image Blocked by Auth or Firewall

Mobile app scrapers have different IP ranges and user agents than desktop bots. If your server has rate-limiting, a WAF, Cloudflare challenge pages, or geo-blocks, the mobile scraper may be blocked while desktop scrapers pass through.

Test: try downloading your og:image URL in a fresh incognito window or from a different IP (VPN or curl -A "WhatsApp/2.0" https://yoursite.com/image.png). If you get a 403 or a challenge page, that's your culprit.

Fix: whitelist common scraper user agents in your WAF rules. For WhatsApp: facebookexternalhit. For iMessage: Twitterbot and Apple's own scrapers. For Telegram: TelegramBot.

Fix 4: Stale Cache in Messaging Apps

WhatsApp, Telegram, and iMessage all cache link previews aggressively. If you recently updated your OG tags but the old preview is still showing, the app is serving a cached version.

WhatsApp: Add a query string to the URL (e.g. ?v=2) to bust the cache when sharing. There's no official invalidation API.

Facebook/Messenger: Use the Facebook Sharing Debugger to force a re-scrape.

Telegram: Telegram caches per-URL. Sharing a slightly different URL (add a UTM parameter) will fetch fresh metadata.

iMessage / iOS Messages: No cache invalidation exists. The preview is generated on first share. If the recipient previously saw the old preview, they may see the old version.

Fix 5: Missing or Incorrect MIME Type

Some mobile scrapers check the Content-Type header of your image. If your server returns the wrong MIME type (e.g. application/octet-stream instead of image/jpeg), the app may refuse to display it.

Check with: curl -I https://example.com/og-image.jpg — look for Content-Type: image/jpeg in the response headers.

Fix 6: Image Too Large (File Size)

Messaging apps that preview links over cellular connections may skip large images. Keep your OG image under 300KB. Use JPEG for photos (vs PNG), and compress with tools like Squoosh or ImageOptim.

Platform-Specific Fixes

iMessage / iOS Messages

iOS uses its own link scraper for iMessage previews. It respects both og:image and Apple's own apple-touch-icon as fallbacks. Make sure both exist and are HTTPS.

<meta property="og:image" content="https://example.com/og-1200x630.png" />
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png" />

WhatsApp

WhatsApp uses the facebookexternalhit scraper. If your server blocks this UA, previews will silently fail. See WhatsApp link preview not working for the full fix.

Telegram

Telegram's bot (TelegramBot) scrapes links shared in chats. It prefers square images (1:1) for channel posts but supports wide cards in DMs. See Telegram link preview not working for platform-specific details.

Instagram DMs

Instagram DMs preview links with a simple card (no rich embed). They follow og:image but may crop heavily on mobile. Use a 1:1 fallback image for Instagram DM sharing contexts.

Debug Checklist

• ✅ og:image is an absolute HTTPS URL
• ✅ Image dimensions are ≥ 1200×630px (wide) or ≥ 300×300px (square)
• ✅ Image file size is under 300KB
• ✅ Image MIME type is image/jpeg, image/png, or image/webp
• ✅ Image URL is publicly accessible (no auth, no cookie, no Cloudflare challenge)
• ✅ og:image:width and og:image:height tags present
• ✅ Scraper user agents not blocked by WAF or rate limiter
• ✅ Cache busted if you recently changed tags

Preview Before You Share

The fastest way to catch mobile OG image problems before sharing is to run your URL through a preview tool. OGFixer shows you exactly what Twitter, LinkedIn, Discord, Slack, and WhatsApp will display — including image rendering and metadata scores — so you can fix problems before they go live.