You paste a link into a Google Chat message, hit send — and the card that comes back shows the page title and description but no image, just a gray block where the thumbnail should be. Or the preview is missing entirely and your message is nothing but a raw URL. Google Chat is where a huge share of work conversations actually happen now — millions of teams run project updates, approvals, and daily standups in Spaces — yet link previews in Chat fail in their own specific ways, and there's no official debugger to tell you why.
Google Chat builds previews with Google's link unfurl service: when you paste a URL, Google fetches the page, reads the Open Graph meta tags, and renders a card with a title, a description, and a thumbnail. If the og:image tag is missing, unreachable, or too small, Chat silently drops the thumbnail and shows a text-only card — and because Google aggressively caches previews, the fix you deploy today may not show up until the cache clears.
In this guide, I'll cover why Google Chat previews lose their images, the exact specs Google's crawler expects, and the step-by-step fix I use — verified with ogimgen's free OG checker.
Why Your Google Chat Link Preview Shows No Image
Google's unfurl service behaves like any other social crawler: fetch the page once, read the meta tags, cache the result against the URL. When the image is missing from the card, the cause is almost always one of these:
- No og:image tag at all. Google Chat renders the card from whatever it finds — title and description only, or the site's favicon as a placeholder.
- An image that's too small. Like most platforms, Google's crawler rejects tiny images. Below roughly 200×200 pixels, the thumbnail is dropped and the card renders without an image.
- An image URL the crawler can't reach. HTTP URLs, redirect-heavy links, hotlink protection, and signed or expiring URLs all make the fetcher give up silently.
- An oversized, slow image. A 5 MB PNG can exceed the crawler's patience, and the preview times out with no thumbnail.
- The crawler is blocked at the edge. robots.txt rules, Cloudflare bot protection, or WAF rules that block Google's crawler prevent the fetch entirely.
- A stale cached preview. Google caches previews against the URL. Update the image and the old one can stick around for days.
- The link was pasted into a thread. Google Chat often skips previews for links pasted as replies inside a thread — the unfurl service prioritizes top-level messages.
The two that matter most for most sites: a missing or too-small og:image, and a stale cached preview that refuses to refresh.
The OG Image Specs Google Chat Actually Needs
Google Chat reads the same standard Open Graph tags as every other platform — og:title, og:description, and og:image — and falls back to <title> and <meta name="description"> when they're missing. If your OG setup already works on WhatsApp or Telegram, it will almost certainly work on Google Chat:
| Setting | Google Chat Requirement | Why It Matters |
|---|---|---|
| Minimum size | 200×200 px | Below this, the image is rejected entirely |
| Recommended size | 1200×630 px | Crisp in both compact cards and expanded previews |
| Display crop | Thumbnail, center-weighted | Keep key text in the center of the canvas |
| File size | Under 1 MB | Heavy images delay or fail the preview |
| Format | PNG or JPG | Both work; PNG for text-heavy cards |
| HTTPS | Required | HTTP images are silently dropped |
| Crawler access | Google's fetcher allowed | Blocked crawler = no preview data at all |
The required meta tag set looks exactly like this — the same six tags that work on Facebook, LinkedIn, and WhatsApp:
<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 Google Chat-specific detail: Chat renders the thumbnail in a compact card in the message stream, but if the same link is the first item in a conversation, it can expand into a larger preview. A 1200×630 image with your headline centered survives both crops cleanly — the same advice that holds for WhatsApp and Telegram.
How to Fix a Missing or Stale Google Chat Preview (Step by Step)
Google Chat has no public debugger like Facebook's Sharing Debugger or Twitter's Card Validator, so you have to verify and bust the cache yourself. This is the sequence I use — it catches the vast majority of Google Chat preview 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, Google Chat 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 Google's crawler isn't blocked. If you use bot-management services (Cloudflare Bot Fight Mode, DataDome, etc.), whitelist Google's fetcher or the fetch gets challenged.
- Bust the cache with a query parameter. Google caches previews against the URL. Appending
?v=2(or any unique string) to the og:image URL makes the crawler treat it as a brand-new image. Update the tag, save, and re-verify with the checker. - Delete the message and re-paste the link. In the Chat conversation, delete the message containing the link and paste it again. This forces a fresh unfurl against the current URL instead of the cached one.
- Paste the link at the top level. If you originally pasted it inside a thread reply, paste it as a new top-level message instead — Chat is more likely to unfurl links in fresh top-level messages.
Google Chat vs. WhatsApp vs. Telegram: Preview Behavior Compared
Google Chat, WhatsApp, and Telegram are the three messaging apps where your links get shared most often. They all read the same OG tags, but the card treatment and the failure modes differ:
| Aspect | Google Chat | Telegram | |
|---|---|---|---|
| Card style | Compact card in message stream | Small 1:1 thumbnail + text block | Wide card below the message text |
| Public debugger | None | None | None |
| Cache refresh | Query param, delete and re-paste | Query param, re-send | Query param |
| Thread behavior | May skip previews in replies | Previews in any chat | Previews in any chat |
| Recommended image | 1200×630 | 1200×630 | 1200×630 |
The practical takeaway: because all three platforms consume the same six OG tags, one well-built 1200×630 image covers Google Chat, WhatsApp, and Telegram at the same time — which is exactly the setup I recommend in the Telegram link preview guide too.
Summary
Google Chat link previews lose their images for five main reasons: missing or too-small og:image tags, an image URL Google's crawler can't reach, an oversized file that times out, edge rules that block the fetcher, and aggressive caching that keeps old cards alive. The fix is the same sequence every time — generate a 1200×630 image with your headline centered, set the standard OG tags, unblock Google's crawler, append a query parameter to bust the cache, and delete-and-re-paste the link in a top-level message.
Google Chat previews are how your product looks inside the tool millions of teams use to make decisions every day, and a branded card beats a gray rectangle every time. Generate your OG image with ogimgen in about 30 seconds, verify the tags with the OG checker, re-paste the link — and check what it looks like in WhatsApp as well, since the same tags drive both.