Browser isolation is the technique of running a web browser in an isolated environment so that any compromise of the browser does not reach the underlying device. Implementations range from local sandboxing (Firefox Multi-Account Containers, Chrome incognito with site isolation, Tor Browser) to remote browser isolation services (Cloudflare Browser Isolation, Menlo Security, Authentic8 Silo) where the browser runs entirely on a remote server and only renders pixel output to the user’s device. The structural defense against browser-based exploitation.
What it means in practice
The local-sandboxing tier is what most users mean by “browser isolation” in casual usage: separate profiles for separate identities, container tabs for separate cookie scopes, full virtualization (Qubes OS qubes for browsing) for the strongest local isolation. The remote-browser-isolation tier moves the browser execution off the user’s device entirely: a malicious website compromises the remote browser instance, which is destroyed at the end of the session, and the user’s device is never touched by the malicious code. The trade-offs: remote browser isolation adds latency, the remote provider sees the user’s browsing (the browser’s exit network identity is the provider’s, not the user’s), and the cost is enterprise-tier rather than consumer-tier. For most users, the local-sandboxing tier (Firefox containers, Tor Browser for sensitive sessions, Qubes for the highest tier) addresses the relevant threats.
Where it shows up
Local-sandboxing tier used by: privacy-conscious users running Firefox Multi-Account Containers to separate identities, journalists and activists running Tor Browser for sensitive sessions, security professionals running Qubes OS qubes for malware research and threat investigation, and (the broadest case) any user who runs incognito or private browsing for a session that should not pollute the persistent browser state. Remote-browser-isolation tier used by: enterprise IT departments protecting employees from web-based malware (the Cloudflare and Menlo deployments dominate this segment), high-target individuals using Authentic8 Silo for the explicitly-isolated browsing tier, and security researchers investigating untrusted material from a sacrificial environment.
What you can change today
Three layers depending on threat model. Layer 1 (everyone): use Firefox Multi-Account Containers (extension installed by default in Firefox) to separate identities into containers (Personal, Work, Banking, Shopping, Social), so cookies and storage do not cross between contexts. Layer 2 (privacy-conscious): keep Tor Browser installed for sessions that need network-and-fingerprint anonymity, use Mullvad Browser for daily sessions that need anti-fingerprinting without Tor latency. Layer 3 (high-target): run Qubes OS for the local-sandboxing top tier, where each browsing context lives in a separate VM and a compromise stays in the qube. Remote browser isolation (Cloudflare, Menlo) is enterprise-tier; consumer access is limited and the use case rarely justifies the operational cost outside specific high-target scenarios.