You paste a link into WhatsApp and get bare text, or a small square where a big image should be. WhatsApp is stricter than Facebook or LinkedIn about one thing — file size — and it is the cause we see most. WhatsApp's own developer page, Link Previews, lists every rule; this page goes through them, what we reproduced, and how to get a new preview once you have fixed the page.
What we did and did not test. On 2026-11-21 we served test pages from a local Node.js server, fetched them with curl 8 as WhatsApp/2.22.20.72 A (an example user agent from WhatsApp's page), cut the HTML at WhatsApp's 300 KB limit and ran it through the parser of our OG checker, and checked test images made with ImageMagick against WhatsApp's limits. We did not send the test pages in WhatsApp — they were not public — so what WhatsApp displays comes from its documentation.
WhatsApp's rules
From WhatsApp's page, word for word where it matters:
| Rule | WhatsApp's wording |
|---|---|
| Where the tags go | "The <head> containing the HTML mark-ups must appear within the first 300KB of the HTML." |
| Which tags | og:title, og:description and og:url "must be inside the <head> tag. They should not be empty." |
| The image URL | og:image "is an absolute URL for an image used as the thumbnail" |
| File size | "This image should be under 600KB in size." |
| Width and shape | "Image should be 300px or more in width with 4:1 width/height or less aspect ratio." |
| Fallback | WhatsApp may relax requirements and revert "to small link previews. However, this should not be relied on." |
| The crawler | an HTTP GET with `User-Agent: WhatsApp/2.x.x.x A |
The page names no image formats. Its own example tag points at an .svg file, but WhatsApp does not say SVG is supported, and we did not test it; JPEG is the safe choice (the formats page compares every platform).
What we measured
| Test | Result |
|---|---|
| 1200×630 JPEG, random noise at quality 97 | 743 KB — our checker: over WhatsApp's 600 KB |
| 1200×627 PNG, detailed fractal pattern | 3.1 MB — over 600 KB, though within LinkedIn's 5 MB |
| 1200×630 JPEG, flat gradient | 16 KB — within every limit |
| 2000×400 PNG (5:1) | our checker: too wide for WhatsApp's 4:1 |
Page with a 400 KB inline script before the og: tags, cut at 300 KB |
our parser found no og:image, og:title or og:description |
| The same page, whole (410 KB) | all tags found |
| Page behind a rule that returns 403 to user agents containing "bot" | 200 for WhatsApp — its user agent has no "bot" in it |
It is not rare: in our census of the top 10,000 sites (2026-11-17), 5.9% of the homepage og:images we could measure were over WhatsApp's 600 KB.
Two lessons. First, an image that is fine everywhere else can still break WhatsApp: Facebook allows 8 MB (Meta) and LinkedIn 5 MB (LinkedIn), WhatsApp 600 KB. Second, the 300 KB limit is about position, not page size: our 410 KB page had its tags after a 400 KB block of inlined data, which is how server-rendered apps that embed their state in the <head> end up with no preview.
The causes and the fixes
1. The image is over 600 KB
Export the social image as JPEG at quality 80–85, or as a PNG with few colours for flat graphics, and check the size the crawler gets:
curl -s -A "WhatsApp/2.22.20.72 A" -o /dev/null \
-w "%{http_code} %{content_type} %{size_download}\n" https://example.com/og/post.jpg
You want 200, image/jpeg or image/png, and a size under 614,400 bytes. One image under 600 KB at 1200×630 works for Facebook, LinkedIn and X too, so there is no need for a WhatsApp-only file.
2. The tags are too far down the page
Put the og: tags near the top of <head>, before large inline scripts, styles or JSON. To see where they are, count the bytes before the first og: tag:
curl -s -A "WhatsApp/2.22.20.72 A" https://example.com/post | grep -bo 'og:image' | head -1
The number before the colon must be well under 307,200 (300 KB).
3. A tag is missing, empty or relative
og:title, og:description and og:url must be present and non-empty, and og:image absolute: https://example.com/og/post.jpg, not /og/post.jpg. Tags added by JavaScript after load are not in the HTML WhatsApp reads. Our WhatsApp link preview checker reports each of these and checks the image against WhatsApp's size, width and ratio limits.
4. The image is too narrow or too wide
At least 300 pixels wide; no wider than four times its height. A 1200×630 image is 1.9:1, well inside.
5. The crawler is blocked
A bot rule that matches "bot" does not catch WhatsApp, as we measured, but a firewall that blocks unknown user agents, a country block, a login or hotlink protection can. Fetch the page with WhatsApp's user agent and look for anything other than 200.
Check before you send
WhatsApp's own test: "Start with composing a message with the link to test (not tap to send yet)." If no preview appears above the composer after 10 seconds, a requirement is not met; if it appears small, the image requirements are not met.
Getting a new preview after a fix
WhatsApp documents no refresh tool and no cache duration. What works without one: share a URL it has not seen (https://example.com/post?v=2) and give a changed image a new file name (post-v2.jpg). Messages already sent keep the preview they were sent with. Every other platform's refresh steps are on refresh a link preview.
Images that fit WhatsApp by default
Shareglint renders a page's social image from an HTML template as a 1200×630 JPEG — the social images of our own guide pages, made with the built-in blog template, weighed 36–64 KB each on 2026-11-21, far under WhatsApp's 600 KB — at an absolute HTTPS URL, through the API or a signed image URL in the og:image tag. The free plan covers 100 images a month.