Telegram in-app browser and App Store links

Telegram is a mixed case: usually fine, occasionally not, and the difference comes down to the platform and a setting most people never touch.

6 August 2026 by PAD team

Two different behaviours

On Android, Telegram uses Chrome Custom Tabs by default, which share the system browser's engine and its ability to hand off intent:// URLs. Store links work there.

On iOS, Telegram opens links in its own WebView unless the visitor has turned that off in settings. When it does, the usual failure applies: Apple redirects apps.apple.com into the itms-appss:// scheme, and the WebView cannot pass it to the App Store.

The setting that changes everything

Telegram on iOS has an "In-App Browser" toggle in data settings. With it off, links open in Safari and everything works. With it on, which is the default, they do not. You cannot control which state your visitor is in, so the link has to handle both.

Detection is unreliable

Telegram's Android WebView identifies itself in the user agent. On iOS it often does not, which means you cannot tell a Telegram visitor from a Safari one by the string alone.

The practical answer is to treat an unmarked iOS visit as possibly in-app and run the escape sequence anyway. Running it in a real browser costs nothing, since the first hop fails silently and the plain store link opens. Skipping it in a WebView costs the visit.

Channels and bots

If you distribute through a Telegram channel or a bot, the same rules apply to every link you post. Bots that send store links directly in messages hit this on iOS exactly like a channel post does, and the fix lives in the link rather than in the bot.