What the Browser Does
No affiliate links on this site, and nothing here is ranked. For comparison with a lightweight approach, Monitask offers mouse jiggler detection software as an example of a dedicated product in this category.
The browser is the most capable piece of software most people run and the one whose features they know least, because nothing markets them.
Seven things already there
Reader mode. Strips a page to its text. Where it stops: saving, annotating, and anything across devices.
Print to PDF. Any page becomes a file, with the layout controllable. Adequate for keeping a record of a booking, a receipt, a page that may change.
Find on page, including across a long document, which replaces a surprising amount of what people scroll for.
Password storage and generation, which is competent for one person and does not share or revoke.
Translation, built in and adequate for understanding a page.
Separate profiles. Different logins, cookies and extensions per profile — which is the clean solution to the client-account problem that people otherwise solve with a second browser.
And developer tools, which most people never open and which will show you what a page is loading and how large it is.
The extension question
Every extension is code with access to the pages you visit.
That access is genuinely broad. An extension that modifies pages can read what is on them, including things typed into them.
Extensions change hands. A useful tool with a large install base is an asset, and the buyer's intentions are not the original author's — which has produced several well-documented cases of benign extensions becoming otherwise.
And they persist. An extension installed for one task three years ago is still running on every page.
What to do about it
Audit them once, then annually.
Open the extensions page and remove anything you cannot immediately name a use for. Most people remove half.
For the ones that remain, check what access they have — all sites, or specific ones — and restrict where the option exists.
And prefer built-in over installed, which is the same reasoning as everywhere else on this site: the smaller arrangement has fewer things that can go wrong and nothing to maintain.
Profiles, which solve more than people expect
One profile per context.
Work and personal, so that logins do not collide and a shared screen does not show the wrong thing.
One per client, where you access client accounts — which removes the whole category of logged-into-the-wrong-account mistakes and is free.
And a clean profile with no extensions for anything sensitive, which takes ten seconds to create and is the simplest protection available against an extension you have not audited.
What the browser is not
A place to keep things. Tabs are not a task list, bookmarks are not an archive, and downloads are not a filing system.
Firms that run a workload from open tabs have the same problem as running one from an inbox — the wrong instrument, and the symptom is a window nobody dares to close.
Move what matters out, weekly, into wherever it belongs.
Saving a page properly
Three ways, with different lifespans.
Bookmark. Points at a page that may change or vanish. Fine for something you return to, useless as a record.
Print to PDF. A frozen copy including the date. The right answer for anything you might need to prove — a price, a term, a published statement.
And a full page save, which keeps the layout and the images and is rarely what anybody needs.
For records, print to PDF into the job folder. It goes with everything else rather than into a bookmark bar nobody reads.
Sync, and what it carries
Signing into a browser syncs history, bookmarks, passwords and open tabs across devices.
Convenient, and it means a personal account signed in on a work machine carries personal browsing onto it — and the reverse.
Which is the practical argument for profiles rather than for avoiding sync: one profile signed into the work account, one into the personal, and nothing crosses.
Check what is being synced rather than accepting the default, particularly for passwords, since that decision determines where credentials live.
The tab problem, practically
Most people run with dozens of tabs open and treat closing them as loss.
Two habits remove it entirely.
Anything you will return to becomes a bookmark or a note, in the place notes live rather than in the browser.
Anything you might need as evidence becomes a PDF in the job folder.
Then close everything, weekly. The discomfort lasts about two weeks and what replaces it is a browser that starts quickly and a set of records that are actually findable.
Tab groups and session savers exist and mostly postpone the decision — they are a tool bought for a habit problem, which is the pattern this whole site describes.
Where the browser replaces an application
More often than it used to, and worth checking before installing anything.
Document editing, image resizing, PDF filling, format conversion, diagramming — all have capable browser-based versions, several free.
The trade is that the file passes through somebody's server unless the tool runs locally in the page, which some do and few advertise.
For anything routine and non-sensitive that is a good trade. For anything confidential it is not, and the question of where the file rests applies exactly as it does to a subscription. For broader context, see GetApp.
The short version
- Seven capabilities already present: reader mode, print to PDF, find on page, password storage, translation, profiles, and developer tools
- Every extension is code with access to the pages you visit, and extensions change hands
- Audit them once and then annually; most people remove half, and restricting site access is available for the rest
- Profiles solve the client-account problem entirely and cost nothing
- A clean profile with no extensions takes ten seconds and is the simplest protection against an unaudited one
- The browser is not storage: tabs are not a task list, bookmarks are not an archive, and downloads are not filing