What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Set the thumbnail WhatsApp uses for a page by adding Open Graph tags to that page’s HTML <head>, especially og:image with an absolute image URL. Keep the metadata in the first 300 KB of the response, use an image under 600 KB that is at least 300 pixels wide with a width-to-height ratio no greater than 4:1, then paste the URL into a WhatsApp composer and wait up to 10 seconds for the preview.
The metadata WhatsApp reads
WhatsApp’s crawler requests the page with an HTTP GET and looks for Open Graph-style metadata. The WhatsApp developer documentation’s basic pattern is:
<head>
<meta property="og:title" content="Page title" />
<meta property="og:description" content="A short description of the page." />
<meta property="og:url" content="https://example.com/page" />
<meta property="og:image" content="https://example.com/images/share-image.jpg" />
</head>Place these tags in the actual document head, not in visible page content. The official-attributed WhatsApp developer documentation, updated November 5, 2025, says the head containing the markup must occur within the first 300 KB of HTML; the entire document does not have to be smaller than 300 KB.
What each required value does
og:title: the title shown in the card. It must not be empty.og:description: the supporting text. WhatsApp says 80 characters will suffice, and the display is normally one or two lines.og:url: the canonical page address. Use the real URL without session IDs, tracking counters or identifying query parameters.og:image: the thumbnail address. It must be an absolute, publicly reachable URL such ashttps://example.com/images/share-image.jpg, not a relative path like/images/share-image.jpg.
The broader Open Graph protocol also defines og:type, optional image dimensions, MIME type, secure URL and alternative text. Those fields can supplement your markup, but the WhatsApp setup documented above prioritizes the four tags shown in the example.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →#1 Best Overall
Prepare an image that meets WhatsApp’s limits
Use a purpose-made social-sharing image rather than relying on an arbitrary page image. Before uploading it, check all three documented limits:
| Requirement | WhatsApp guidance | Why it matters |
|---|---|---|
| File size | Under 600 KB | Larger files may be reduced to a small preview or not selected. |
| Width | At least 300 px | Narrow images may fail to produce a useful thumbnail. |
| Width-to-height ratio | 4:1 or less | Very wide banners can be downgraded to a small link preview. |
Keep important text and logos away from the edges because the card’s exact crop can vary. Serve the image over HTTPS, make sure it is not protected by a login, and ensure the URL in og:image points to the final file rather than a temporary upload address.
Add the tags in a website builder or CMS
The exact controls differ by platform, so look for page-level fields named Open Graph, Social sharing, Facebook image or Social preview. Set a title, description, canonical URL and image for the specific page. A site-wide default is useful as a fallback, but an article or product page should override it with its own image and URL.
Verify what the server actually sends
A visual browser inspector can be misleading when JavaScript inserts metadata after the initial response. View the page source or fetch the raw HTML and confirm that the four tags are present in the head near the beginning of the response. The crawler must be able to make an unauthenticated GET request and retrieve the image URL.
Free tools Windows power users keep installed
One-click scans. No signup required.
Direct HTML implementation
If you control templates, put the tags in the shared head template and substitute values from the current page. Escape quotes and ampersands correctly, and do not emit empty tags. For a page at https://example.com/guides/whatsapp, a complete head fragment could be:
<meta property="og:title" content="How to Set a WhatsApp Link Thumbnail" />
<meta property="og:description" content="Add Open Graph metadata and test your WhatsApp preview." />
<meta property="og:url" content="https://example.com/guides/whatsapp" />
<meta property="og:image" content="https://example.com/images/whatsapp-thumbnail.jpg" />Keep the canonical value undecorated. If analytics require campaign parameters for ordinary visitors, do not copy those parameters into og:url; the WhatsApp documentation specifically advises omitting session variables, identifying parameters and counters.
Test the thumbnail in WhatsApp
- Publish the page and confirm it is reachable without signing in.
- Open WhatsApp and start a message to yourself or a test contact.
- Paste the complete page URL into the composer, but do not send it yet.
- Wait for the preview above the composer. The documented check allows up to 10 seconds.
- Inspect the title, description, URL and image. Send the message only after the card is correct.
Preview generation is best effort. WhatsApp says it may relax requirements, inspect other HTML markup or fall back to a small link preview, and its documentation warns that previews are not guaranteed to work or continue working. Treat the composer test as a practical check, not a contract that every recipient and future fetch will see the same card.
Optional independent diagnostic
WhaTools’ WhatsApp link preview debugger can inspect public Open Graph tags and show a preview-like card. It is an independent third-party checker, not an official Meta tool, and it cannot guarantee the exact card WhatsApp will display. Use it to catch an omitted tag before performing the real composer test.
Troubleshoot a missing or stale preview
Check these causes in order so that a formatting problem is not confused with caching or best-effort behavior.
1. The tags are missing from the crawler’s HTML
Fetch the raw response, not only the DOM after scripts run. Confirm the tags are inside <head> and that the head appears within the first 300 KB. Server-side rendering or a template-level change is usually needed when a client-side script adds the tags too late.
2. A value is empty or malformed
Ensure og:title, og:description and og:url contain nonempty values. Check for unescaped quotation marks that terminate an attribute early. Confirm that og:image is an absolute URL and that it resolves directly to the intended file.
3. The image violates a documented limit
Measure the downloaded file, not the source design. Reduce it below 600 KB, make it at least 300 px wide and keep its width-to-height ratio at 4:1 or narrower. If WhatsApp shows only a tiny image, this is the first condition to revisit.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitches4. The crawler cannot retrieve the page or image
Check HTTPS certificates, redirects, robots or firewall rules, authentication, hotlink protection and rate limits. A browser session that is already logged in can succeed while WhatsApp’s unauthenticated GET fails. Test the exact public URL from an ordinary network.
5. You are seeing an older card
The consulted WhatsApp documentation does not specify a cache duration or provide a cache-reset control. Re-paste the URL after confirming the current HTML. A third-party guide suggests changing the URL, for example by adding a query parameter, to prompt another fetch; treat that as an unofficial workaround, not a guaranteed cache purge. Keep the canonical og:url clean even if you temporarily vary the pasted address.
6. The preview never appears after 10 seconds
Recheck the preceding items, then test a simple page with a small, public image. If that works, compare the failing page’s response size, redirects and access controls. If neither page produces a card, the behavior may be WhatsApp’s best-effort fallback rather than a markup error.
Compare implementation routes before you publish
| Route | Page-level Open Graph controls | Early server response | Image URL control |
|---|---|---|---|
| CMS or site builder | Depends on the platform and template; look for social-preview fields. | Verify by viewing raw source; client-side insertion may be too late. | Usually controlled through an upload or media field; confirm the generated URL is public and absolute. |
| Direct HTML or server template | Fully controlled in the page head. | Can be emitted in the initial response before the 300 KB point. | Fully controlled, including the final HTTPS image address. |
The requirements come from the metadata and crawler behavior, not from a particular CMS brand. Choose the route that lets you verify the response sent to an unauthenticated crawler.
Recommended Free Tools
Best Value
Or skip the browser setup
ScreenshotNeo can capture the rendered page while you check that your published template looks right, without building your own browser automation. It is a website screenshot API and MCP server; it does not replace the Open Graph tags or guarantee a WhatsApp card, so still perform the composer test above.
One GET request returns a PNG, JPEG, WebP or PDF. The same call can be made with cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/guides/whatsapp -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com/guides/whatsapp"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com/guides/whatsapp' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);See the ScreenshotNeo documentation for request parameters. Before capture it can accept cookie or consent banners and remove more than 60 known consent platforms, newsletter popups and chat widgets; each cleanup step can be disabled. Only clean shots are billed: bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits cost nothing, and each response identifies the result with X-Page-Verdict and X-Billed headers. Its MCP server provides take_screenshot, get_page_info and capture_pdf tools to Claude, Cursor and other MCP clients.
You can also use full-page capture with lazy images loaded, CSS-selector element capture, dark mode, device presets, custom viewports and retina scale. Other options include custom CSS or JavaScript, clicks before capture, hidden selectors, waits for a selector, delay or network idle, request and resource blocking, custom headers, cookies, user agents, authorization, timezone and geolocation, transparent backgrounds, resizing, selectable cache TTLs, signed links, asynchronous jobs with signed webhooks, bulk capture for up to 100 URLs per call, a usage API and an OpenAPI specification. Existing parameter names used by other screenshot APIs also work, which can simplify migration.
The Free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 shots; yearly billing gives two months free, and every feature is available on every plan. Create a free ScreenshotNeo account to try it without a card.
Operational checklist
- Every target page has nonempty title, description and canonical URL tags.
- The tags are in the initial HTML head within the first 300 KB.
- The image URL is absolute, public and served over HTTPS.
- The downloaded image is under 600 KB, at least 300 px wide and no wider than a 4:1 ratio.
- The canonical URL has no session, identifying or counter parameters.
- You pasted the exact URL into a WhatsApp composer and waited up to 10 seconds.
- You understand that WhatsApp previews are best effort and can fall back to a small link card.
Frequently Asked Questions
Is og:type required for a WhatsApp thumbnail?
The WhatsApp-specific pattern documents og:title, og:description, og:url and og:image. The Open Graph protocol defines og:type as a basic property, but the consulted WhatsApp guidance does not make it part of the required four-tag setup.
Does an Open Graph checker guarantee the WhatsApp card?
No. A checker such as WhaTools can reveal public metadata, but it is independent and cannot reproduce WhatsApp’s crawler and best-effort preview behavior exactly.
Can I rely on a preview for a critical announcement?
No. WhatsApp’s documentation explicitly says link previews are not guaranteed to work or continue working, so include the important information in the message itself.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
