Mullvad Browser launched in April 2023, the result of a collaboration between Mullvad VPN and the Tor Project. The pitch was specific. Take the Tor Browser’s privacy and fingerprinting protections, strip out the Tor network routing (you supply your own VPN, or none), and ship a browser configured for daily use rather than for anonymous research. After about two years, the product has matured. This is what it is like to actually use it.
What Mullvad Browser is, technically
The browser is built on Firefox ESR, hardened with the same configurations and patches that the Tor Project uses for Tor Browser. The key components:
- Default privacy settings tuned aggressively (no telemetry, no studies, no Pocket, no Firefox Account integration, no autofill of search suggestions)
- Fingerprinting resistance via the same letterboxing, font rationalization, and resolution clamping that Tor Browser uses
- Default search set to DuckDuckGo (no Google integration)
- No Mullvad-specific spyware or telemetry built in (the browser does not phone home to Mullvad, despite the brand association)
- uBlock Origin and NoScript pre-installed and configured
- Default behavior of clearing cookies, cache, and site data on shutdown
The browser does not include Tor Network routing. When you use Mullvad Browser, your traffic goes through your normal internet connection (or your VPN if you have one running separately). For Tor functionality, you still want Tor Browser, which is the slower-but-anonymous variant.
The product is free, open source, and updates through its own channel (not Firefox’s). The release cadence has been roughly every 4 to 6 weeks, tracking Firefox ESR upgrades.
What I expected versus what I got
I expected a privacy-focused browser that would feel like a slightly slower, slightly more constrained Firefox. The fingerprinting resistance, in particular, makes some sites behave oddly, and I assumed the daily-driver experience would have noticeable friction.
The reality has been less dramatic than that. For roughly 90 percent of web browsing (reading articles, doing searches, watching videos, posting on forums, doing email), Mullvad Browser feels essentially identical to Firefox. The fingerprinting protections do their work in the background; the visible difference is nearly nothing.
The 10 percent where it falls short is concentrated in specific categories of sites:
- Some interactive web apps (collaborative documents, complex SaaS dashboards) occasionally behave differently because they fingerprint your browser to apply specific optimizations. Most still work, just with reduced features.
- Sites that track returning visitors (news sites with paywalls, e-commerce sites with browse history) lose track of you between sessions. This is by design and usually a feature, but if you specifically want to be remembered (your favorite sites with logged-in personalization), you have to actively allow that.
- Video conferencing in browser tabs (Google Meet, Zoom web) sometimes has performance issues that do not occur in regular Firefox. The fingerprinting resistance interacts oddly with WebRTC.
These constraints are knowable upfront if you read the project’s documentation. For me they have been minor inconveniences rather than blockers.
What it does that Firefox out of the box does not
The privacy default values are all set correctly without configuration. With regular Firefox, you have to spend an hour tweaking about:config, installing privacy add-ons, and configuring the various settings. With Mullvad Browser, all of that is done for you.
Letterboxing (the technique of constraining the browser viewport to standard sizes to prevent screen-resolution fingerprinting) is enabled by default. This means your window has a slight black border around the content area. After a week you stop noticing it.
The user agent is the same as every other Mullvad Browser user. This is one of the biggest fingerprinting wins. Standard Firefox sends a unique combination of OS, browser version, screen resolution, and other parameters that, in combination, identify you. Mullvad Browser deliberately makes this non-unique.
WebRTC IP leaks are blocked by default. WebGL fingerprinting is constrained. Canvas fingerprinting is randomized.
The cookie behavior is more aggressive. Cookies, localStorage, and various other tracking mechanisms are cleared at the end of each session by default. You can pin specific sites to retain their cookies if you have a logged-in service you actually want to stay logged into.
Where it sits versus alternatives
Mullvad Browser is in a small category. The closest alternatives:
LibreWolf is similarly hardened Firefox-fork, similar privacy defaults, longer-running project (it predates Mullvad Browser by a few years). LibreWolf’s user community is more developer-focused and the project is volunteer-run. The fingerprinting resistance in LibreWolf is solid but does not include the specific letterboxing and resolution clamping that Tor Browser uses.
Tor Browser itself is the original. It includes everything Mullvad Browser has, plus the Tor network routing. Tor routing is slow (network of volunteer relays, not optimized for speed) and not necessary for daily browsing. Tor Browser’s daily-driver friction comes mostly from the network performance, not the browser itself.
Brave is in the privacy-browser category but with a different philosophy. It is fast, has built-in ad blocking, but increasingly bundles cryptocurrency features and an opinionated set of additional services. We have written about why this caused us to stop recommending Brave, separately.
Firefox with Arkenfox user.js is the DIY version of what Mullvad Browser does out of the box. If you are willing to maintain your own configuration, the result can be very close to Mullvad Browser. The trade-off is the maintenance burden.
Standard Firefox with privacy add-ons (uBlock Origin, Privacy Badger, Multi-Account Containers) is the most common choice and is meaningfully better than Chrome out of the box. It is not as hardened as Mullvad Browser by default.
The case for switching
You should switch to Mullvad Browser if any of these apply:
You currently use standard Firefox without privacy customization and want hardened defaults without the configuration work.
You have configured Firefox with Arkenfox-style hardening and you are tired of maintaining that configuration as Firefox versions change. Mullvad Browser handles the maintenance for you.
You currently use Brave and the increasing crypto-feature pile is starting to feel like noise. Mullvad Browser is the closest to what Brave was a few years ago.
You want a browser whose corporate alignment with privacy is structurally maintained, not just claimed. Mullvad and the Tor Project have track records that justify trust.
The case against switching
The fingerprinting protections do break some sites, and the breakage is not always graceful. If your livelihood depends on web apps that need extensive browser introspection, you may find Mullvad Browser too constrained.
If you are extremely deep in the Firefox add-on ecosystem and rely on specific extensions, double-check compatibility before switching.
If you want to use the browser for video conferencing or streaming services, the experience is sometimes worse than standard Firefox. WebRTC tweaks affect both.
If you are a person who customizes everything (your shell, your editor, your browser themes), the more locked-down nature of Mullvad Browser will feel constraining. The browser is opinionated by design.
Practical day-to-day notes
After a year of use:
The performance is comparable to Firefox. Web pages load at the same speed. Memory usage is similar.
The update process is automatic and silent. You do not have to think about it.
The Linux experience is solid. Packages exist for most major distributions, plus a generic Linux build.
The macOS experience has been improving. Early releases had some signing and notarization issues that have since been resolved.
The Windows experience is identical to other Firefox-based browsers on Windows.
Mobile is the gap. There is no Mullvad Browser mobile app. For mobile privacy, the closest equivalents are Onion Browser (iOS), Tor Browser (Android), or DuckDuckGo Browser. None are perfect substitutes.
How it makes money
Mullvad Browser does not generate revenue for Mullvad. It is given away free, with no telemetry that returns to the company. Mullvad’s stated rationale is that the browser is an extension of their broader privacy mission and contributes to a healthier privacy-tools ecosystem. The Tor Project benefits from Mullvad’s funding contribution to their ongoing work.
This funding model is unusual in the browser space. Chrome is funded by Google’s advertising business. Firefox is largely funded by Google’s search-deal revenue. Brave is funded by their advertising and crypto products. Edge is Microsoft’s. Safari is Apple’s.
Mullvad Browser exists because two organizations with privacy missions decided to fund it. This funding is sustainable as long as both organizations continue to operate. It is not guaranteed in the long term.
Should you switch
For privacy-focused readers of this site: yes, probably. The friction is small, the protection is meaningful, and the alternatives are either more work (Arkenfox) or have product-direction issues (Brave).
For users who care about privacy but do not want to think about it: Mullvad Browser is the easiest path to good defaults that I know of in 2026.
For users who do not care about privacy and just want their browser to work: stay with whatever you are using. The marginal benefit of switching is small if you are not actively trying to maximize privacy.
For me: I have not switched my primary browser to Mullvad Browser. I have switched my secondary browser (the one I use for sites I do not want to retain cookies for, for research, for one-off tasks) to it, and that has been the right call.
Mullvad Browser (free, open source, no affiliate)
Related: I recommended Brave for years, I’m not anymore, Hardening Firefox with Arkenfox