Setting Safari or Chrome as your phone's default browser feels like the obvious fix. It does nothing here, and the reason is the single most misunderstood part of the whole problem.
Why the default browser setting doesn't apply
A phone's default browser setting only kicks in when one app asks the operating system to open a URL on its behalf, and the OS looks up which app should handle it. That's what happens when you tap a link in a text message, an email, or a PDF. It is not what happens inside Instagram, TikTok, Facebook, LinkedIn, Snapchat, or Pinterest. Each of those apps intercepts the tap itself and renders the page in its own built-in browser, a WebView wrapped in the app's own toolbar, without ever handing the link to the operating system at all. The default browser setting is never consulted, because the request that would trigger it never gets made. This is why changing your default browser fixes links opened from Mail or Messages but does nothing at all for a link tapped inside Instagram.
Why apps do this on purpose
It is not a bug and not an oversight. Keeping a visitor inside the app, rather than handing them off to Safari or Chrome, keeps that visitor inside the app's own session, its own analytics, and its own ad measurement, and it removes the exit point where someone might just close the tab and never come back. It also lets the platform attach its own click identifier and watch what happens right after the tap, something it loses the moment a visitor leaves for a browser it doesn't control. Every major social platform ships an in-app browser for that reason, not because building and maintaining a full browser engine is otherwise appealing to a social app.
This isn't the desktop "default browser" problem
On a computer, links genuinely can open in the wrong browser because of the setting this topic gets confused with: Windows' Default apps setting, or the default web browser choice in macOS System Settings. There, changing the default browser is the actual fix, because a desktop OS handles a link tap the way people assume a phone should too, one app asks the OS to open a URL, the OS checks its default, and hands it off. A rogue installed app hijacking that default is a real, separate desktop problem with a real, separate fix, and it has nothing to do with in-app browsers at all.
The mobile version covered here is a different mechanism entirely, and it's also the more common complaint by volume, since far more link taps happen from inside a social app on a phone each day than from a desktop email client with a hijacked default. Confusing the two is a big part of why generic "change your default browser" advice keeps failing to fix what people actually mean when a link from Instagram or TikTok won't leave the app.
Which platforms do this, and how to escape each one
| App | Default behavior | Way to escape it |
|---|---|---|
| Opens every outbound link in its in-app browser | Settings and privacy > Website permissions > "open links in external browser" toggle, or the per-link "..." menu | |
| Facebook / Messenger | Opens every outbound link in its in-app browser | No app-wide toggle; per-link "..." menu only |
| TikTok | Opens every outbound link in its in-app browser | No app-wide toggle; per-link menu, position varies by app version |
| Opens most outbound links in its in-app browser | Per-link share or "..." menu, where offered | |
| Snapchat | Opens every outbound link in its in-app browser | Per-link "..." menu only |
| Opens every outbound link in its in-app browser | Per-link share icon only |
The Instagram link problem, specifically
Instagram gets singled out here because it is the platform where this shows up most, since almost every outbound link, in a bio, a post, a story, or a DM, opens inside its in-app browser by default. Instagram is also the one major platform that gives you a persistent way out: under Settings and privacy, in Website permissions, a toggle called "open links in external browser" switches every future link over to your phone's real browser, permanently, without needing to find the menu each time. Facebook and TikTok, run by two different companies, have no equivalent app-wide setting; the only option on either is the per-link menu.
How to force a link open in Safari or Chrome
The per-link method works the same general way across most of these apps, even though the exact icon and label vary by app and app version.
- Open the link as normal, letting the in-app browser load it.
- Look for a "..." or share icon, usually in the top-right or bottom-right corner of the in-app browser's toolbar.
- Choose the option along the lines of "open in browser," "open in Safari," or "open in Chrome."
Not every app version, and not every region's version of an app, shows this option in the same place, or at all. TikTok in particular has moved this control around across updates. When it's missing entirely, copying the URL out of the in-app browser's address bar and pasting it into a real browser tab is the fallback that always works, if slower.
What actually breaks when a link stays in the wrong browser
This is not just a preference. A handful of real, specific things fail. Saved logins and passwords don't apply, since a password manager tied to your real browser has nothing to autofill inside a WebView, so checkout and login forms end up filled by hand. Sessions don't carry over either: logging into a site inside Instagram's browser does not log you in the next time you open that site in Safari, and vice versa, because the two keep separate cookie storage. A deep link often can't fire, since an app trying to hand a visitor from a web link straight into its own native app generally needs the tap to reach the operating system's link handler, and an in-app browser frequently intercepts that handoff before it happens (more on that in what a deep link is). And click and conversion tracking gets messier, because every in-app browser session is its own fresh instance with its own cookie jar, which is part of why click tracking built entirely on client-side cookies undercounts return visits coming from social apps.
The fix that doesn't depend on the visitor finding a menu
None of the per-app toggles above are something a marketer, creator, or business sending the link can control from their end. The visitor has to find and use them, and most never do. What a link owner can influence is what happens the moment someone lands, and here the honest options are limited: no link can force iOS or Android to launch an outside browser against the host app's wishes, and any page claiming otherwise is describing a trick that gets patched quickly by whichever platform it targets. The nearest real option is a prompt on the landing page itself, encouraging the visitor to tap the in-app browser's own "open in browser" control, which is the same escape step Raydar's own links include for anyone who lands inside an in-app browser. It's a nudge, not an override, because no link genuinely has the power to override it. Where the URL itself resolves matters here too: a link that lands directly on a checkout form gives no room to show that nudge before the visitor is already mid-task, while one that resolves through a short intermediate page, the kind a link-in-bio or short-link redirect naturally provides, has somewhere to put the reminder without adding real friction to the visit.
For anyone building the link itself rather than just clicking one, checking what a link actually contains before assuming it's the problem is worth doing with a link decoder, and reading what an in-app browser is covers the mechanism behind all of this in more depth than fits here.