WhatsApp link not opening

WhatsApp is friendlier than most in-app browsers, which makes the cases where it does fail more confusing.

6 August 2026 by PAD team

WhatsApp is not the worst offender

On both iOS and Android, WhatsApp will usually hand a link to the system browser rather than trapping it. That is why a store link shared in a chat normally works, and why people are surprised when it does not.

In our own traffic, taps arriving from WhatsApp were a small share and none of them needed the manual fallback. It is genuinely a mild case compared with Facebook or TikTok.

When it does fail

Three situations account for most of it.

• The link was opened in WhatsApp's built-in preview browser rather than handed off, which happens on some builds and settings
• The URL is malformed after formatting, usually a trailing character swallowed into the link text
• The recipient is on a work-managed device where the browser hand-off is restricted by policy

The second one is worth checking first because it is invisible. WhatsApp auto-links text, and a URL followed immediately by a bracket or a full stop can end up including that character.

How to send a store link so it survives

Put the URL on its own line, with a space before and after, and avoid wrapping it in brackets. Prefer a short, clean address over a long one with query parameters, because those are the ones that get mangled.

If a chunk of your traffic comes from chat apps and you cannot control how people paste your address, a routing link removes the guesswork: it stays valid regardless of which browser opens it, and it reports where the tap came from.

The underlying mechanism, briefly

Where in-app browsers do trap the tap, the reason is always the same. Apple answers a request for apps.apple.com with a redirect into itms-appss://, and a WebView cannot hand a custom scheme to another app. The full explanation is in the main write-up.