What is remote browser isolation? A plain-English guide
Remote browser isolation (RBI) is a security technique that runs web pages on a remote server and streams only the visual output to your device. The page loads, scripts execute, and any malicious code runs — but all of it happens somewhere else. Nothing executes on your computer.
That single design choice changes everything about how you think about safe browsing.
Why your browser is the biggest target on your device
Your browser touches more untrusted content than any other application you run. Every link you click, every ad that loads, every embedded script on every page — all of it executes directly in your browser, which runs directly on your operating system.
Attackers know this. The most common threat vectors all flow through the browser:
- Drive-by downloads — visiting a compromised page silently downloads and executes malware without any click from you.
- Malicious scripts — JavaScript can exfiltrate data, fingerprint your system, or redirect you before you notice anything is wrong.
- Zero-day exploits — browser vulnerabilities that haven't been patched yet can be weaponised the moment they're discovered.
- Phishing kits — convincing fake pages designed to harvest your credentials, often hosted on legitimate-looking domains.
Traditional security tools try to detect these threats. Antivirus software scans files. URL reputation services check domain lists. Email filters look for known-bad patterns. They all share the same fundamental assumption: we can identify what's dangerous before it runs.
Remote browser isolation takes a different position entirely. It assumes the page is hostile. It doesn't try to decide. It just contains the execution somewhere that can't hurt you.
How remote browser isolation works, step by step
The mechanics are straightforward once you see them laid out.
- You paste or click a URL. Instead of your local browser making that request, a remote server does.
- The page loads inside a container or virtual machine. Scripts run. Images load. Whatever the page tries to do, it does it there — not on your device.
- Only the visual output reaches you. The remote session streams pixels (or a rendered representation of the page) to your screen. You can see it and interact with it. But the actual page code never crosses onto your machine.
- The container is destroyed when you're done. No cookies saved. No history written. No persistent state of any kind. The environment is wiped completely.
Compare this to detection-based security. An antivirus has to guess: is this file malicious? A URL scanner has to guess: is this domain on a known-bad list? They can be fooled by new malware, by freshly registered domains, by obfuscated scripts. Isolation doesn't guess. It just keeps the execution contained regardless of what the page does.
The threat model is fundamentally different. Detection says "we think this is safe." Isolation says "we don't care — it can't reach you either way."
Types of remote browser isolation
RBI exists at two very different scales.
Enterprise remote browser isolation
Large organisations deploy RBI across their entire workforce. Every web request from every employee is routed through isolated sessions. This is typically built into corporate secure web gateways and security service edge platforms. It offers centralised policy control, detailed logging, and integration with identity systems.
The tradeoff is cost and complexity. Enterprise RBI requires procurement, configuration, and ongoing management. It's designed for IT teams, not individual users.
On-demand remote browser isolation for individuals
This is where things have changed in recent years. You don't need a corporate contract to benefit from browser isolation. On-demand tools let you open a single link in an isolated session whenever you need it — no installation, no setup, no IT department.
You get the core protection — remote execution, nothing on your device — applied precisely to the link you're not sure about.
Remote browser isolation for individuals: what Tempbrowser does
Tempbrowser is built around exactly this use case. You paste a suspicious URL. It opens inside a temporary cloud sandbox — a virtual computer running in the cloud, streamed to your screen. The page executes there. No code ever touches your computer.
When you close the session, the entire environment is wiped. No history. No cookies. No persistent profile.
There's nothing to install. No account required on the free plan.
Free plan: No signup, no card required. Three launches per 24 hours, with 3-minute sessions — enough to check whether a link is legitimate before you decide what to do with it.
Pro plan: $4.99 per month billed yearly. Sixty-minute sessions and unlimited launches, for users who regularly work with untrusted content or need longer sessions to investigate thoroughly.
The URL analyzer is the core tool: paste a link, watch it open in the sandbox, capture screenshots of what you see, and end the session when you're done. No trace left behind.
For a step-by-step walkthrough of checking a suspicious link safely, see the safe link checker guide.
If you want to understand what a disposable browser is and when to use one, the what is a disposable browser guide covers the broader concept.
Limitations worth knowing
Remote browser isolation is a strong protection. It's also not magic. Here's what it doesn't do.
Streaming latency. The page renders on a remote server and sends a visual stream to you. For most content this is seamless. For very interactive pages or slow connections, you may notice a slight lag compared to local browsing.
Sessions are temporary by design. You can't log into accounts and expect the session to persist. The disposable nature is the point — it's not a replacement for your everyday browser, it's a containment environment for links you don't trust.
It protects your device, not your identity. If you open a phishing page in an isolated session and then manually type your password into the fake form, isolation can't help you. It prevents code from executing on your machine — it doesn't prevent you from handing over credentials willingly. See the FAQ below for more on this.
It doesn't make you anonymous everywhere. The remote server makes requests on your behalf. Your network provider can still see traffic to the isolation service. RBI is a security tool, not a privacy or anonymity tool.
FAQ
Is remote browser isolation the same as a sandbox?
They're related but not identical. A sandbox is an isolated execution environment that restricts what a process can do. Remote browser isolation uses a sandbox (or a container, or a VM) as its mechanism, but the defining feature of RBI is that the execution happens on a remote server and only the visual output reaches your device. A local browser sandbox still runs code on your machine — RBI moves execution off your machine entirely.
Does RBI stop phishing?
It stops the technical payload. If a phishing page tries to run malicious JavaScript, drop a file, or exploit a browser vulnerability, isolation prevents any of that from reaching your device. What it can't do is stop you from reading a fake login page and choosing to type your real credentials into it. Isolation handles the code. Credential discipline — pausing before you type a password into any unfamiliar page — is still on you.
Is remote browser isolation free?
Yes, for basic use. Tempbrowser's free plan requires no signup and no payment card. You get three isolated launches per 24 hours with 3-minute sessions — no commitment. The Pro plan ($4.99/month billed yearly) unlocks 60-minute sessions and unlimited launches.
Do I need to install anything?
No. Tempbrowser runs entirely in the cloud. You open the tool in your existing browser, paste a URL, and the isolated session streams to your screen. Nothing is installed on your device, and nothing is left behind when the session ends.
What happens to my session data when I'm done?
The entire remote environment is wiped when your session ends. No browsing history, no cookies, no cached files, no persistent profile of any kind. Each session starts completely fresh.
Try it now
The fastest way to understand remote browser isolation is to use it. Paste a URL you're not sure about into the Tempbrowser analyzer, watch it open in an isolated cloud environment, and see firsthand that the page runs somewhere that isn't your device.
Three free launches per day. No account needed. No installation.