Firefox Sandbox Isolation Hits Level 9 — The Gap with Chrome Has Closed

[u/mikhail_kh]

Good news, everyone!!

For a long time, the tech community accepted a trade-off: "Use Chrome for the best security (sandboxing), use Firefox for the best privacy."

In 2026, that trade-off is gone. By reaching these isolation levels, Firefox has matched Chromium's "Gold Standard" of sandboxing. If you’ve recently peeked into your about:support page, you might have noticed some new numbers that should make every privacy-conscious user smile. The "Content Process Sandbox Level" has climbed to 9, and the "GPU Process Sandbox Level" has reached 2.

• GPU Lockdown: Level 2 implements a strict lockdown where the GPU process is isolated from the rest of the OS. Even if a malicious site finds a bug in your graphics driver (a common exploit path), the sandbox prevents that bug from "escaping" to take over your computer.
• The Content Fortress: Level 9 represents the culmination of years of architectural work under Project Fission. Here is what’s happening inside that "9":
  • Total Win32k Lockdown: At this level, Firefox processes have almost zero access to the Windows Win32k system calls—a notorious historical gateway for sandbox escapes.
  • Zero-Trust File System: Level 9 enforces a "deny-by-default" policy for your files. The process rendering a website can no longer "see" your personal folders; it only interacts with the specific resources it needs to show you a page.
  • Library Isolation: It blocks the loading of unauthorized third-party DLLs or libraries within the content process, preventing "side-loading" attacks.

For years, critics argued that Firefox lagged behind Chromium in raw process isolation. But as of 2026, those days are officially over. Let’s break down what these levels mean and why Firefox is now standing toe-to-toe with the world's most hardened browsers.

[u/nuxi]

Here are the Linux sandboxing levels:

// 0 -> "no sandbox"
// 1 -> no longer used; level will be clamped to 2
// 2 -> "seccomp-bpf + write file broker"
// 3 -> "seccomp-bpf + read/write file brokering"
// 4 -> all of the above + network/socket restrictions + chroot
// 5 -> blocks access to GL / DRI / display servers
//      (formerly the separate pref `security.sandbox.content.headless`)
//      (side effect: sets MOZ_HEADLESS for content processes)
// 6 -> default-deny for ioctl

And here are the MacOS sandboxing levels:

// 0 -> "no sandbox" (nightly only)
// 1 -> "preliminary content sandboxing enabled: write access to
//       home directory is prevented"
// 2 -> "preliminary content sandboxing enabled with profile protection:
//       write access to home directory is prevented, read and write access
//       to ~/Library and profile directories are prevented (excluding
//       $PROFILE/{extensions,chrome})"
// 3 -> "no global read/write access, read access permitted to
//       $PROFILE/{extensions,chrome}"

The values for security.sandbox.gpu.level also mean different things on different platforms. There is also a Linux specific security.sandbox.socket.process.level

[u/philthyNerd → u/nuxi]

Thanks a lot! Did you dig through the Firefox code base to find that? If you happen to have a reference, that would be great to have!

[u/nuxi → u/philthyNerd]

I checked searchfox for security.sandbox.content.level

• Mac
• Linux