Website Systems

Why Your Website Link Shows No Image on WhatsApp, Facebook or LinkedIn

When a link to your site arrives as bare text, the platform visited your page and could not find a picture it was able to use. The cause is almost always one of six things. Here is how to find which, and how to make the fix show.

Open GraphLink previewsSocial sharingWhatsAppLinkedIn

Paste a link to your website into WhatsApp, LinkedIn or Facebook and you expect a card: a picture, a title and a line of description. When it arrives as a bare link, or with a title and no picture, the platform has read your page and not found what it needed. Nothing looks wrong to visitors, which is why this can run for months while every share of the site looks unfinished.

Every platform builds that card the same way, from a few tags in the page's head. This guide covers what those tags are, the six usual reasons the picture is missing, what each platform actually requires, and how to make a platform drop the old preview once you have fixed it.

01

How it works

The card comes from tags in your page, not from the page itself.

When a link is shared, the platform requests the page and reads the Open Graph tags in its head. Four of them make the card: og:title, og:description, og:image and og:url. Meta's sharing guide for webmasters lists those four as the basic tags, and LinkedIn's help page says the same four must exist.

og:image is the tag that decides whether a picture appears. It holds the address of one image file. The platform does not look through the photos on your page and choose one, so when the tag is missing the card usually has no picture at all.

X also reads a tag of its own, twitter:card. The value summary_large_image asks for the card with the wide picture; with no twitter:card tag, a link on X can appear as a small card or as plain text.

02

The causes

Six reasons the picture does not appear.

There is no og:image tag. This is common on hand-built sites and on themes where the share settings were never filled in. Check for the tag first; most cases end here.

The image address is broken. The tag points at a file that was renamed, moved or deleted in a redesign. Copy the address out of the tag into a new browser tab. If the image does not open there, the platform cannot open it either.

The image is too small. Meta does not accept an image smaller than 200 x 200 pixels, and LinkedIn shows an image narrower than 401 pixels as a small thumbnail beside the text rather than as a full-width picture.

The file is an SVG, or not an image at all. Logos are often SVG files, and Meta's documentation lists JPEG, GIF and PNG as the image types. An SVG, or an address that answers with a web page instead of a picture, leaves the card empty.

The platform is turned away. The image sits behind a login, a firewall rule or bot protection that lets browsers in and refuses automated requests. LinkedIn's help page names a site blocking it from fetching the image as one of the causes.

The old preview is cached. You have fixed the tag, but the platform still shows the card it built the first time. This is the one that makes a correct fix look as if it did not work. It is covered in the last section.

03

The requirements

What each platform asks for, and where it says nothing.

Meta and LinkedIn both publish their image rules, and they agree on the shape: a wide picture close to a 1.91:1 ratio, about 1,200 pixels across. An image of 1200 x 630 pixels meets both.

WhatsApp publishes no size or file-size rule for link previews in its help pages. It reads the same og:image tag. Forum threads often blame large files for missing WhatsApp previews; that is advice from users, not a stated limit, but a JPEG well under a megabyte is quick to fetch on every platform, so it costs nothing to follow.

From Meta's sharing documentation for webmasters and LinkedIn Help, both read on 20 November 2026.
PlatformImage sizeFile size
Facebook and Messenger (Meta)At least 1200 x 630 recommended; 600 x 315 for the large card; 200 x 200 is the smallest acceptedUp to 8 MB
LinkedInAt least 1200 x 627, ratio 1.91:1; under 401 pixels wide shows as a thumbnailUp to 5 MB
WhatsAppNo published figureNo published figure
04

Checking it

Check the tags and the image in one pass.

The free Social Presence Checker on this site reads a page's share tags and then fetches the og:image file the way a platform would. It reports whether the tag is there, whether the address opens, whether the file is a real JPEG, PNG, WebP or GIF rather than an SVG or a web page, its size in pixels, whether a side is under 200 pixels or the image is smaller than 600 x 315, whether the file is over 5 MB, and whether it is served over plain http.

The same report checks og:title, og:description, og:url, og:type, og:site_name and twitter:card, and finds the links from your site to its Facebook, LinkedIn, Instagram, X and Threads profiles.

It does not contact WhatsApp, Facebook, LinkedIn or X, so it cannot tell you what a platform has already cached. That is what the platforms' own tools are for.

05

After the fix

Make the platform forget the old preview.

Facebook and Messenger. Meta caches a share image by its address, so a changed picture saved under the same file name may never be fetched again. Enter the link in Meta's Sharing Debugger, at developers.facebook.com/tools/debug, and it reads the page again and shows the card it now builds.

LinkedIn. LinkedIn's Post Inspector, at linkedin.com/post-inspector, reads the page fresh and shows the preview it will use.

WhatsApp. There is no refresh tool. Messages that were already sent keep the card they were sent with, so test the fix by sending the link again in a new message.

From note to action

Continue through the system.

Keep reading

Related practical notes.

Apply the note

Working on a similar problem?

Bring the current system, failure point or desired outcome. We can scope the architecture, implementation and verification path.

Start a Project Try the Related Tool