You add your website link to a YouTube video description, and the little link card that should appear below the text is a blank placeholder — no thumbnail, no title, just a gray box. On a platform where the description is one of the only places you can send viewers off-platform, that dead card is a wasted conversion point: every one of those clicks is a potential subscriber, customer, or reader you lose to a preview that never rendered.
YouTube's link previews work differently from every social network you've dealt with. There is no unfurl-on-paste moment like WhatsApp or Slack, no public debugger like Facebook's Sharing Debugger, and no "refresh" button in the mobile app. YouTube reads your Open Graph tags when it builds the link card — usually when the video is processed or the link is first detected — and the result is cached against the exact URL. If the og:image tag is missing, too small, or unreachable at that moment, the card stays blank until YouTube decides to re-fetch it, which can take days.
In this guide, I'll cover how YouTube builds link cards, the exact specs the og:image needs to pass, and a step-by-step fix — verified with ogimgen's free OG checker.
Why Your YouTube Link Preview Shows No Thumbnail
YouTube generates link cards for URLs in video descriptions, channel about sections, and pinned comments. The card pulls three things from your page — title, description, and image — and each one has its own failure mode. The usual causes:
- No og:image tag at all. YouTube falls back to the domain favicon or shows a bare text-only card with no visual.
- An image that's too small. YouTube's card builder skips og:image below roughly 200×200 pixels; the card renders without a thumbnail.
- An image URL the fetcher can't reach. HTTP URLs, redirect-heavy links, hotlink protection, and signed or expiring URLs all make the fetch fail silently.
- A slow, oversized image. A heavy PNG can time out during the fetch, and YouTube records the failure instead of retrying soon.
- The crawler is blocked at the edge. robots.txt rules or CDN bot protection that block YouTube's fetcher prevent the card entirely.
- The URL was cached before you fixed your tags. YouTube caches link cards against the exact URL, so a card built from a bad fetch can stay blank for a long time.
- The link lives in a comment or community post. YouTube renders cards in video descriptions and channel links, but comment links often stay plain text.
The two that matter most: a missing or too-small og:image when YouTube first builds the card, and a cached blank card that needs a cache-busting URL to refresh.
The OG Image Specs YouTube Actually Needs
YouTube reads the same standard Open Graph tags as every other platform — og:title, og:description, and og:image — and falls back to the page <title> and <meta name="description"> when they're missing. The card image is served directly from og:image:
| Setting | YouTube Requirement | Why It Matters |
|---|---|---|
| Minimum size | 200×200 px | Below this, YouTube drops the thumbnail from the card |
| Recommended size | 1200×630 px | Crisp in the card, works across desktop and mobile |
| Display crop | Wide card thumbnail, center-weighted | Keep key text in the center of the canvas |
| File size | Under 1 MB | Heavy images time out during the fetch |
| Format | PNG or JPG | Both work; PNG for text-heavy cards |
| HTTPS | Required | HTTP images are silently dropped |
| Crawler access | YouTube's fetcher allowed | Blocked crawler = no card, no preview |
| Fetch timing | At link detection, cached per URL | Bad fetches persist until a cache refresh |
The required meta tag set looks exactly like this — the same six tags that work on Facebook, X, and LinkedIn:
<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="A short, punchy description">
<meta property="og:image" content="https://yoursite.com/og-image.png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:url" content="https://yoursite.com/page">One YouTube-specific detail: the card in the video description is built from the page as it exists at fetch time, so a 1200×630 image with your headline centered survives both the mobile card and the desktop hover preview — the same advice that holds for Telegram and Slack.
How to Fix a Missing YouTube Link Preview (Step by Step)
YouTube has no public debugger, and it caches cards aggressively — so the fix has two phases: get the tags right, then force a refresh. This is the sequence I use — it catches the vast majority of YouTube link card problems:
- Verify your tags first. Paste your URL into our free OG image checker. It shows exactly what a crawler sees — title, description, image, and dimensions. If the checker reports a missing or broken og:image, YouTube will never render a thumbnail.
- Fix the underlying issue. Add or correct the OG tags on your page, regenerate a proper 1200×630 image if yours is below 200×200, and confirm the checker shows a valid card. Double-check that the image URL is public, HTTPS, and not behind a redirect.
- Check robots.txt and CDN rules. Make sure YouTube's fetcher isn't blocked. If you use bot-management services (Cloudflare Bot Fight Mode, DataDome, etc.), whitelist YouTube's crawler or the fetch gets challenged.
- Use a cache-busting URL. YouTube caches the card against the exact URL. If the card was built from a bad fetch, edit the description to point at a URL variant — append
?utm_source=youtube(or any unique string) so YouTube treats it as a brand-new link and fetches fresh. - Re-add the link in the description. Delete the URL from the video description, save, then paste it back in and save again. This forces YouTube to re-detect the link and rebuild the card.
- Wait it out. If the card is still blank after a fresh fetch, YouTube may hold the old cache. Give it 24–48 hours; most cards update within a day once the underlying tags are valid.
YouTube vs. X vs. Facebook: Preview Behavior Compared
YouTube, X, and Facebook are the three places where link previews drive the most off-platform traffic. They all read the same OG tags, but when and how they render the card differs a lot:
| Aspect | YouTube | X (Twitter) | |
|---|---|---|---|
| Card style | Small card under description text | Large card below the tweet | Large card in feed |
| Inline unfurl in comments | No | Yes | Yes |
| Public debugger | None | X Card Validator | Facebook Sharing Debugger |
| Cache refresh | Re-add link / cache-bust URL | Re-post or re-scrape | Debugger scrape |
| Fetch timing | At link detection, cached per URL | On each share | Cached against URL |
| Recommended image | 1200×630 | 1200×630 | 1200×630 |
The practical takeaway: YouTube is the most cache-heavy of the three — the card is locked in when YouTube first detects the link, so you have to verify before you add it to a description, and use a cache-busting URL if you ever change the image. X and Facebook let you re-scrape on demand. If your OG setup already works on Facebook, it will almost certainly work on YouTube too — see the OG image file size guide to keep the card fast.
Summary
YouTube link previews lose their thumbnails for six main reasons: a missing or too-small og:image, an image URL YouTube's fetcher can't reach, an oversized file that times out, edge rules that block the crawler, a cached blank card from an earlier bad fetch, and links placed where YouTube doesn't render cards. The fix is simple once you understand YouTube's caching — verify with an OG checker, build a 1200×630 image with your headline centered, and re-add the link or use a cache-busting URL to force a fresh fetch.
On YouTube, the link card in your description is one of the few places you can move viewers from watch time to your own site — and it's cached the moment YouTube detects the link. Generate your OG image with ogimgen in about 30 seconds, verify the tags with the OG checker, and add the link with confidence — and check the Reddit guide too, since that platform is even stricter about fetch timing.