Telegram In-App Browser vs Your Own Browser

menu_open What it is, and what the setting controls

The in-app browser is a web view that lives inside Telegram. It has a back control, an address it will show you if you ask, and on current versions it can be minimised to a bar so several pages stay open behind your chats.

A single switch in the settings decides whether links open there or in whatever browser your device uses by default. Turning it off sends every link out to that browser instead.

One thing is not covered by the switch, and it is worth separating now: mini apps are not web links. Something launched from a bot or an attachment menu runs in its own container regardless of this setting, and Step 088 is where that subject belongs. The setting here governs ordinary links to ordinary websites.

password The warning you stop receiving

This is the strongest argument in the step and it has nothing to do with encryption.

A password manager offers to fill in your details only on the exact site it saved them for. That behaviour is usually described as convenience, and it is quietly something else: when the manager stays silent, it is telling you that this is not the site you think it is. A convincing copy at a lookalike address gets no offer to autofill, and a great many people have been saved by noticing that nothing appeared.

Inside an in-app browser you generally do not get that signal. Extensions are not there, and integration with a manager is limited or absent depending on the platform. So the page looks right, nothing offers to fill in the password, and you type it manually — which is exactly the behaviour the silence was supposed to prevent.

None of that makes the in-app browser malicious. It makes it a browser without your equipment in it, which is a different and perfectly ordinary problem. The remedy is to move, not to worry.

devices The second browser nobody audits

Because pages persist, sessions persist. Sign into something in the in-app browser and that login stays there, in a place you never open deliberately and would not think to check.

That produces two habits worth adopting, neither of which takes long.

Close tabs you have finished with. The minimise bar makes leaving things open the default, and a dozen forgotten pages is both clutter and a set of live sessions.

Clear its data occasionally. There is an option to clear cookies and browsing data for the in-app browser in the settings beside the toggle. Doing it once in a while signs out anything lingering there, and costs you nothing you will miss.

This is the same reasoning as Step 028's device list, one level down. The account audit you do every few months covers Telegram sessions; the browser inside Telegram is not on that list, and nothing else is watching it.

touch_app Try it now — five minutes

Four steps, and the second one is a discovery for most people.

1. Find the in-app browser setting In the chat settings, beside the other link options. Whether you turn it off is your choice; knowing the switch exists is the point.
2. Look at how many pages you have minimised Open the bar and count. Most people who use recent versions have several they forgot about, including one they signed into.
3. Clear the in-app browser data once Next to the same toggle. It signs out the strays and costs nothing.
4. Adopt one rule for logins When a page asks who you are, open it in your real browser instead. That single rule captures nearly all of the value in this step.

library_books The third destination nobody mentions

Links do not open in only two places. Some pages have a reader version — a stripped-down rendering of the article itself, opened instantly, with the banners, consent dialogues, autoplaying video and tracking scripts absent.

When it is available you are offered it, and it is a genuinely good way to read something linked from a channel. It loads immediately even on a poor connection, it is legible on a phone without pinching, and it removes the modern experience of fighting a page for thirty seconds before reaching a paragraph.

It is also a reconstruction, and that is the part to know. The reader version contains what the parser could identify as the article, which means tables, charts, footnotes, embedded media and anything added to the page afterwards — including a correction published later — may simply not be there. Nothing tells you what is missing.

So the honest rule is the same shape as everything else in this step: read it here, and open the real page before you rely on it. For following a story, the reader version is better than the website. For quoting it, forwarding it as fact, acting on a number in it, or checking whether it has been updated, open the original.

help Common questions at this stage