Skip to content

In-app browsers

Logged out when you open a link from Instagram or TikTok? Here's why

Signed in on your phone's browser but logged out after a tap in Instagram or TikTok? Why in-app browsers don't share your session, and what fans and creators can do.

By Tim Geithner8 min read

If you're logged out when opening a link from Instagram or TikTok, even though you're signed in to Patreon, Fansly, a shop or a newsletter in Safari or Chrome, the page has usually opened in the app's own browser. That browser can keep its own cookies, separate from Safari or Chrome, so the session saved in your usual browser doesn't come along. Open the page in Safari or Chrome to use the sign-in you already have, or sign in once inside the app.

Why your session doesn't come along

When you sign in to a site, your browser usually stores a cookie that lets the site recognise you next time. That cookie lives in the browser you signed in with. An app's built-in browser can keep its own store instead, and then the site sees a visitor it hasn't met.

Android's comparison of in-app browsing options puts it plainly: a WebView is sandboxed and doesn't share cookies or logins with the user's main browser. Android's CookieManager reference describes those as the cookies used by an application's WebView instances. Custom Tabs are the exception: they use the default browser's session, including cookies and saved passwords, so you don't have to sign in again to sites you've already visited.

On iPhone, an app's own web view keeps cookies and other site data in a data store that the app sets up: a persistent one by default, or a non-persistent one meant for private browsing. Apple's ready-made in-app Safari view, SFSafariViewController, supports Safari features such as AutoFill, but Apple points apps that want to share data with Safari to a separate sign-in API instead. Apple doesn't document either view as using your Safari sign-ins.

Instagram and TikTok don't document which of these they use, and it can differ by platform and app version.
Where the page is openUses your usual browser's sign-ins?
Safari, Chrome or your default browserYes, that's where they are stored
Android Custom TabYes, per Android's documentation, including saved passwords
Android WebViewNo, per Android's documentation
An iPhone app's own web view (WKWebView)Not documented as shared; the app sets up its own data store
SFSafariViewController on iPhoneSupports AutoFill; Apple doesn't document it as sharing Safari's data
Instagram and TikTok don't document which of these they use, and it can differ by platform and app version.

Which one do Instagram and TikTok use?

Neither app says. In 2022, developer Felix Krause reported that Instagram's and Facebook's iOS in-app browsers ran the apps' own JavaScript inside web pages, and later found TikTok's doing the same. Apple's in-app Safari view doesn't let apps interact with page content, and Apple tells developers who need that to use WKWebView, which points to app-controlled web views, at least at the time. Apps can change this; the in-app browser checker shows which browser you're in today.

  • You're signed out. Any site where your session lives in Safari or Chrome can show its login screen: Patreon, Fansly, a shop, a forum, a newsletter's account page.
  • You're asked to verify again. Many sites remember a trusted device with a cookie. Google's help on trusted computers, for example, says its don't-ask-again choice depends on cookies and has to be set in each browser. A browser that has never seen you looks new, so a code or an email check is normal there.
  • Saved passwords may not be offered. Android's documentation says Custom Tabs share saved passwords and WebViews don't share logins with the browser. Whether your password manager offers to fill inside an app's web view depends on the app, the phone and the manager.
  • Passkeys may not be available. The community-maintained passkeys.dev reference explains that embedded web views run in the context of the calling app, so only passkeys for that app's own linked domain can be used. Android's WebView passkey guide likewise requires the app to be associated with a website it owns. A passkey you made for a membership site or shop is unlikely to be offered inside a social app's web view.
  • Sign in with Google may fail. Google refuses its sign-in in embedded web views; see Error 403: disallowed_useragent.
  • Carts and wallets stay behind too. A cart started in Safari isn't in the app's browser, and payment buttons can differ; see why Apple Pay may not show in an in-app browser.

If you're the fan: what to do

  1. 1

    Open the link in your usual browser

    Look for Open in browser in the page menu, or copy the link and paste it into Safari or Chrome. The guides for Instagram and TikTok cover missing menus and blocked copying. If you're signed in there, that session is used.

  2. 2

    Sign in there once if you need to

    If you weren't signed in in your browser either, sign in there. The next time you open the site in that browser, it can recognise you.

  3. 3

    If you sign in inside the app, expect extra checks

    A code or a confirmation email is normal for a browser the site hasn't seen. Patreon's login help, for example, says it may ask you to confirm a login by email. That email's link opens wherever your mail app opens links, not inside Instagram or TikTok. If the login waiting in the app doesn't continue, sign in from your usual browser instead.

  4. 4

    Skip Sign in with Google inside the app

    If a site offers it, open the page in your browser first. Google refuses that sign-in in embedded web views.

  5. 5

    On a shared phone, sign out where you signed in

    Depending on how the app stores web data, a sign-in inside its browser may still be there next time. Sign out on the site before you hand the phone to someone else.

If you're the creator: what to do

  1. 1Test it signed in. Sign in to your membership site, shop or newsletter in Safari and Chrome, then tap your own link from Instagram and TikTok on an iPhone and an Android phone. Note whether you land signed out, and record app and operating-system versions.
  2. 2Link to the exact page. Send fans to the post, tier or product rather than the home page, so the address they carry into their browser is the right one. Keep any campaign parameters in the link.
  3. 3Say it in plain words. A short line near the link, such as Members: open this in Safari or Chrome to use your existing login, sets expectations. Don't promise that it opens automatically.
  4. 4If you run the site, offer a sign-in that works in the app. Email and password, or a one-time code typed into the page, can work inside an embedded view; Google sign-in can't.
  5. 5Offer the browser before the login screen. A link page with browser guidance can suggest Safari or Chrome before fans reach your site.
  6. 6Count sign-ins and renewals, not taps. Compare completed actions by source and device. A browser switch adds a step of its own.

OpenOut's breakout engine is that kind of step. It is part of the Pro and Agency plans and has to be switched on. On iPhone the default is a guided copy flow, with no automatic attempt to open Safari; on Android, OpenOut makes an opening attempt when the visitor taps. Nothing guarantees that the external browser opens, so copying the link and manual instructions always remain available. It can't sign anyone in: once the page is open in the browser, the fan's existing session there does the rest, if they have one. Plans are on the pricing page.

Frequently asked questions

Why am I logged out when I open a link from Instagram?

Instagram usually opens links in its own browser, which can keep its own cookies separate from Safari or Chrome. Your session is stored in your usual browser and doesn't come along. Open the page in that browser, or sign in once inside Instagram.

Why am I not logged in in TikTok's browser?

For the same reason: TikTok shows websites in its own browser view, which may not have the sign-ins saved in your usual browser. Use the page menu's browser option, or copy the link into Safari or Chrome.

Why do I have to enter a verification code again?

Many sites remember a trusted device with a cookie. An in-app browser that doesn't share your usual browser's cookies looks like a new device, so the site asks again. Signing in from your usual browser avoids repeating it.

Why don't my saved passwords or passkeys show up in the app's browser?

Android documents that WebViews don't share logins with the main browser, and passkeys in embedded web views are limited to the app's own linked sites. Whether a password manager offers to fill depends on the app and the phone. Your usual browser is the dependable place to use them.

How do I stay logged in to Patreon or Fansly when opening links from Instagram?

Open the link in Safari or Chrome, where you're already signed in, through the page menu or by copying it. A sign-in made inside the app's browser applies to that browser only, not to Safari or Chrome.

Go deeper

One link that gets people to the real web

Build a link-in-bio page with a breakout flow that guides visitors out of restricted in-app browsers. Free to start, no credit card.

Claim your handle