Twitter Card Image Not Showing: 7 Causes and Fixes

Your tweet with a link shows no image — just a plain URL. Here are the 7 most common causes and exactly how to fix each one.

The 7 Causes of Missing Twitter Card Images

When a URL shared on X (formerly Twitter) doesn't show a card image, it's almost always one of these seven issues. Let's go through each one.

1. Missing or Incorrect twitter:card Tag

X requires an explicit twitter:card tag. Without it, X won't render a card at all — even if your OG tags are perfect.

<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="Your Title" />
<meta name="twitter:description" content="Your description" />
<meta name="twitter:image" content="https://yoursite.com/image.jpg" />

There are two card types: summary (small thumbnail) and summary_large_image (full card). Use summary_large_image for the best visual impact.

2. Image Too Small

X has minimum image size requirements:

• summary_large_image: minimum 800×418 pixels
• summary: minimum 400×150 pixels
• Recommended: 1200×628 (works across all platforms)

If your image is smaller than the minimum, X silently drops the card. There's no error message — the link just appears as plain text.

3. Image URL Not Publicly Accessible

X's crawler must be able to fetch your image without authentication. Common blockers:

• Image behind a login wall or authentication
• Blocked by robots.txt
• Cloudflare or CDN returning 403/429 errors to crawlers
• CORS restrictions preventing cross-origin fetch

4. Twitter's Cache Hasn't Refreshed

Like all platforms, X caches card data. After you update your tags, X won't pick up changes until the cache expires or you force a refresh.

<meta property="og:image" content="https://yoursite.com/new-image.jpg" />

Use the Twitter Card Validator to enter your URL and trigger a cache refresh. The validator shows you exactly what X sees.

5. Wrong MIME Type or Corrupt Image

If your image server returns the wrong MIME type (e.g., serving a PNG with image/jpeg content-type), X may reject it. Similarly, a corrupt or partially loaded image will be dropped.

6. Page Returns an Error to Twitter's Crawler

If your page returns a 4xx or 5xx error when Twitter's bot fetches it, no card will be generated. This can happen with:

• SPA apps that require JavaScript to render (Twitter's crawler doesn't execute JS)
• Geo-blocking that blocks US-based crawlers
• Cloudflare turnstiles or CAPTCHAs

7. Using Only OG Tags Without Twitter Card Tags

While X can fall back to OG tags, it prefers twitter:card tags. If you only set og:image and not twitter:image, X may not render the card correctly. Always set both.

<!-- Open Graph (for LinkedIn, Discord, Slack, WhatsApp) -->
<meta property="og:image" content="https://yoursite.com/image.jpg" />

<!-- Twitter/X specific (for X/Twitter) -->
<meta name="twitter:image" content="https://yoursite.com/image.jpg" />

Quick Fix Checklist

Frequently Asked Questions