In-app browsers
Why do links open in the app instead of my browser?
It is not a setting you got wrong. Almost every large app now renders links in a browser it controls — here is why, what actually changes, and how to leave.
You tap a link in Instagram, TikTok, Facebook or LinkedIn, and a page opens — but not in Safari or Chrome. Your bookmarks aren't there, you're logged out of a site you were definitely logged into, and the back arrow returns you to the feed rather than to a browser tab.
Nothing is misconfigured. This is what the app is designed to do, and the short answer to "why" is that leaving is bad for the app.
The mechanism: a browser inside the app
Every mobile operating system lets an app embed a webview — a browser engine rendering inside the app's own window. It uses the same engine as the system browser (WebKit on iOS, the Android System WebView component on Android), so pages generally look correct.
What it does not inherit is everything around the engine. The webview gets its own cookie storage, no access to your extensions, and a reduced set of the browser capabilities a site might reach for. It is a browser in the same sense that a hotel room kettle is a kitchen.
Why apps do it anyway
- Retention. Handing you to Safari is an app switch, and a meaningful share of people don't come back in that session. A webview keeps you one back-tap from the feed.
- Speed of return. From the app's perspective, an in-app page genuinely is a faster round trip than a cold app switch — this part is a real user benefit, not only a business one.
- Measurement. Traffic that stays inside the app remains inside a surface the app can observe.
- Control of the experience. The app decides the chrome, the share sheet, the menu and what happens on back.
None of those reasons are going away, which is why this has become more common over the past several years rather than less. Treat it as the default condition of mobile social traffic, not as a temporary annoyance.
What actually changes for you
| What you expect | What happens in a webview |
|---|---|
| You're already signed in | Separate cookie storage — you arrive signed out |
| Your password manager fills the form | Extensions don't run; no autofill from 1Password or Bitwarden |
| Apple Pay / Google Pay button | Frequently unavailable — manual card entry instead |
| Download the PDF or ticket | Often fails silently; the tap does nothing |
| The page opens in a tab you can return to | Closing the view usually discards it |
How to get out of it
- 1
Look for the menu in a corner
Usually three dots, top-right. Some Android builds put it bottom-right.
- 2
Choose the browser entry
"Open in browser", "Open in Safari", "Open in Chrome" — the wording differs by app and version, and apps move it around between releases.
- 3
If there's no such entry, copy the link
Use "Copy link" from the same menu, open Safari or Chrome yourself, long-press the address bar and choose Paste and Go. Slower, but it never depends on the app offering the right button.
The copy-and-paste route is worth knowing precisely because it has no dependencies. Every other method relies on the app exposing something it is under no obligation to keep exposing.
Can you turn it off permanently?
Partly, and only on some apps. Several Android builds — Facebook's among them — expose a preference that sends links to your default browser. Where it exists, it works and it is a one-time fix. iOS offers no system-wide equivalent, so on an iPhone this stays a per-link action.
Setting your default browser in iOS Settings changes which browser opens when an app does hand a link over. It does not stop apps from using a webview in the first place — those are different decisions, and only the second one is yours.
If you're the one sharing the link
Then this stops being a nuisance and becomes a conversion problem, because you cannot ask an audience to learn a workaround. Everything above requires your visitor to notice something is wrong, find a menu and complete a task — most won't, and the ones who don't never tell you why.
What you can control is what your page does in the seconds before they give up: detect the context, attempt whatever hand-off the platform actually supports, and make the manual route one tap rather than a puzzle. The full list of apps this applies to is on the supported in-app browsers page.
One thing worth being suspicious of while you shop for a fix: nobody can guarantee Safari opens. iOS provides no supported mechanism for a webview to push a URL into the system browser, and Android's works often rather than always. Any tool promising otherwise is describing a capability the platform doesn't expose.
Frequently asked questions
Why do links open in the app instead of my browser?
Because the app embeds its own browser engine (a webview) and renders links inside it. Apps do this to keep you from switching away — an app switch is a real risk of losing you for the session. It is a deliberate design decision, not a fault on your device.
How do I force a link to open in Safari or Chrome?
Open the menu inside the in-app browser — usually three dots in a corner — and pick the "Open in browser" entry. If there isn't one, use "Copy link", switch to your browser yourself and paste it into the address bar. The copy route always works because it depends on nothing the app controls.
Why am I logged out of sites in the in-app browser?
The webview has its own cookie storage, separate from your normal browser. Your session lives in Safari or Chrome, so the webview genuinely does not know who you are — and without extensions, your password manager can't sign you back in either.
Can I stop apps from using their in-app browser?
Only in some apps, and mostly on Android, where a few expose an "open links externally" preference. iOS has no system-wide setting for this. Choosing a default browser in iOS Settings only decides which browser opens when an app hands a link over — it does not stop the app from using a webview instead.
Is an in-app browser dangerous?
Not inherently, but it is worth being deliberate about what you type into one. The host app controls the surrounding interface, and you cannot inspect it the way you can a normal browser tab. For anything involving a password or a payment, moving to your own browser first is the sensible habit.