Mozilla began shipping Firefox 141 on 13 October 2026 for every platform via mozilla.org, and the release centres on the most substantial rework of the browser’s privacy stack in two years. The headline change is a deep revision of Total Cookie Protection (TCP), which now stretches cookie isolation beyond classic third-party requests into service workers, Fetch API caches and persistent authentication tokens — storage layers that earlier builds left reachable.
- Deeper isolation: TCP now enforces per-origin partitioning for service worker storage, cached Fetch responses and long-lived session tokens, closing cross-site tracking vectors open in Firefox 140.
- Passkeys go stable: the built-in passkey manager leaves beta, storing, syncing through Firefox Sync and autofilling WebAuthn credentials without an external password vault.
- Containers ship by default: enhanced tab containers, previously an add-on only, are now part of the base installation.
- Graphics gains: the WebGPU renderer posts a 23% improvement in web 3D benchmarks over Firefox 140 on macOS with Apple Silicon.
What the deeper isolation actually covers
TCP arrived in Firefox 86 back in 2021 with a simple premise: every website gets its own cookie jar, so cookies set on site A cannot be read by site B even when the same person visits both. That worked well against conventional third-party tracking, but tracking systems migrated to storage layers the model did not police — most notably the scripts that keep running in the background after a tab closes.
Firefox 141 answers with per-origin isolation for service worker storage, alongside protection for cached Fetch responses and the persistent tokens that keep sessions alive between visits. The practical effect is that an embedded tracker has far fewer places to park state and re-identify a visitor later in the browsing session or on a subsequent return.
Passkeys exit beta, containers arrive by default
For non-technical users, the visible differences are threefold. The protections panel in the address bar now separates three categories of blocking — third-party trackers, fingerprinters and cross-site tracking scripts — each with its own counter. That replaces a single aggregate number that told users almost nothing about what was being stopped.
Second, the bundled passkey manager has graduated from beta to stable production. Firefox can store, synchronise through Firefox Sync and autofill passkeys under the WebAuthn standard, with no third-party password manager in the loop. That turns the browser into a credible alternative to the credential vault baked into the operating system, especially for people who work across platforms and want one consistent sign-in flow everywhere.
Third, enhanced container tabs are now part of the base install rather than an optional extension. Users can segment their activity into themed containers for work, personal life or shopping, and Firefox will not share cookies or sessions between them even inside a single profile.
A small share with outsized leverage
Firefox’s desktop share keeps sliding and now sits at roughly 3.5% worldwide, according to StatCounter’s October 2026 figures. Mozilla’s own numbers, by contrast, put more than 225 million monthly users across its product line, and its audience is less a mass market than a committed one. The company is also structurally unusual: the Mozilla Corporation is wholly owned by the non-profit Mozilla Foundation, so it answers to a mission rather than to shareholders.
That independence still carries a price. Mozilla’s finances lean heavily on its search agreement with Google, renewed in 2025 at $500 million per year through 2028, leaving a permanent tension between the independence it markets and the revenue it depends on.
Where Firefox punches above its weight is standards work. When Mozilla ships a privacy primitive, European regulatory pressure and W3C momentum tend to drag Chrome and Safari along within two to four years — the exact trajectory TCP followed after 2021. Native passkey support looks set to repeat the pattern, with rival browsers expected to replicate the capability on a roughly 18-month horizon as compliance requirements tighten.
Developer gains and the on-device AI layer
Version 141 also improves the WebGPU renderer, delivering a 23% gain in web 3D rendering benchmarks against Firefox 140 on macOS running Apple Silicon. Most people will never notice, but developers building visually heavy web applications will, since the blend of inspection tooling, privacy controls and graphics performance makes Firefox a defensible default development browser regardless of its consumer share.
The longer arc is Mozilla’s 2025 private AI initiative, which envisions an assistant running locally inside the browser rather than shipping queries to remote servers. TCP isolates cookies, passkeys remove shared secrets, and an on-device model would close the loop by keeping prompts on the machine — layered privacy architecture built without the media noise of its competitors.
Firefox 141 will not move the market-share needle, and Mozilla is not pretending otherwise. What it does is extend the browser’s role as the industry’s privacy testbed: a feature set that regulators, standards bodies and eventually rival vendors treat as a preview of where the web is heading. Organisations operating under strict security and phishing-resistance requirements get stronger primitives today; everyone else gets the version of browser privacy they will be running in a couple of years.
Sources & References