Tor Browser
A circuit diagram in the toolbar showing the three relays your traffic hops.
Tor Browser's interface is anti-personalization by design. Built on Firefox, its standout UI is the circuit display: click the site info and it draws the chain of relays, guard, middle, exit, your traffic is routing through, with a one-click button to build a fresh circuit for the site. Privacy posture becomes a visible diagram instead of an abstraction. The security-level slider trades convenience for hardening in plain terms. Crucially, the chrome is engineered to make everyone look identical, fixed window dimensions, blocked fingerprinting surfaces, so the browser actively resists the customization others celebrate, because uniqueness is the threat. The friction is deliberate: pages load slowly, some break, and warnings interrupt. That friction is the feature, an interface honest about the cost of anonymity.
Tor Browser opens on a connection step that most browsers never show. Before the first page loads, a dedicated screen offers to connect directly or to configure bridges for networks where Tor is blocked, and newer releases can detect censorship and suggest a bridge automatically. That screen sets the tone: the browser explains how it reaches the internet before it lets you use it.
Once connected, the start page leads with a search box backed by DuckDuckGo and a short statement of what the browser protects. Many of the choices a mainstream browser exposes are missing on purpose. Extensions are discouraged, saved logins and history are cleared when the window closes, and the New Identity command closes every tab and resets the session in one action, which is the closest thing the interface has to a panic button.
The design cost is that the protections are easiest to undo by accident. Resizing the window to full screen, installing a favourite add-on or logging into a personal account all chip away at the uniform profile the browser works to present, and the interface can only warn so much. Letterboxing, the grey margins that keep the page at a common size, is the visible trace of that trade-off: a slightly odd layout accepted so that many users look alike.
Flows
Flows for Tor Browser are being captured
We haven't taken Tor Browser apart screen by screen yet. Explore the UX patterns it's known for, or request an audit of your own product.
Request a UX auditNotable UX patterns
How does your product compare to Tor Browser?
Get a free UX Snapshot of your page — a quick read on what works and what to fix.
Teardowns
Teardowns of Tor Browser are coming
We haven't published a written teardown of Tor Browser yet. Explore related topics, or request an audit.
Request a UX auditFree course
WCAG 2.2 Fundamentals: Audit a Screen for Accessibility
6 lessons · ~25 min
Start lesson 1 →