Zen Browser

Zen Browser is a privacy-focused, open-source web browser built on Firefox 152.0.1, engineered to help users stay productive by reducing digital clutter and streamlining workflow. It targets professionals, students, and content creators who need a clean, distraction-free browsing experience without sacrificing full Firefox extension compatibility or web standards compliance.

Built directly atop Mozilla’s Gecko engine, Zen extends Firefox with native Workspaces, Split View, Compact Mode, Glance previews, Live Folders, and a Boosts system that lets users inject custom CSS per-site — without needing a userscript manager. The browser ships on Windows, macOS, and Linux under the MPL-2.0 license, with weekly stable releases and an opt-in Twilight channel for early adopters.

Zen’s architecture is a direct fork of Firefox, patched via its own build toolchain called Surfer. All new features are implemented as Mozilla-compatible JSWindowActor modules and C++-backed XPCOM components that hook into Firefox’s existing CustomizableUI, UrlbarUtils, and nsStyleSheetService APIs. This approach gives Zen access to the full depth of Firefox internals while preserving upstream update compatibility.

With over 42,000 GitHub stars and 180 contributors since its 2024 launch, Zen Browser has established itself as one of the fastest-growing Firefox-based productivity browsers. It maintains an active release cadence of roughly one release per week and incorporates upstream Firefox security advisories promptly.

What You Get

• Workspaces - Organise tabs into named, bookmark-backed groups so each project or context gets its own isolated tab set, switchable with a click or keyboard shortcut.
• Split View - Pin two tabs side-by-side in the same window for direct comparison, code review, or dual-reference research without a second window.
• Glance - Open any link as a floating overlay atop your current page — inspect content, copy a snippet, then dismiss without touching your history or back-stack.
• Compact Mode - Auto-hides the sidebar when the browser is not in focus, recovering horizontal space for content-heavy work like writing or reading.
• Live Folders - Subscribe to GitHub Issues, Pull Requests, or RSS feeds that auto-populate a bookmark folder, turning the sidebar into a live dashboard.
• Boosts - Inject custom CSS or JavaScript into any site on a per-domain basis via a built-in editor, replacing the need for Stylus or Tampermonkey for simple tweaks.
• Firefox 152.0.1 base - Full compatibility with every Firefox extension on AMO, all DevTools features, and every web standard Firefox supports.
• Open source and privacy-first - MPL-2.0 licensed, no built-in telemetry, no bundled accounts, and no data collection beyond what stock Firefox includes.

Common Use Cases

• Parallel research workflows - An academic uses Workspaces to keep literature review tabs, citation tools, and a writing app separated so switching topics is a one-click context switch.
• Code and documentation side-by-side - A developer uses Split View to keep the API docs pinned on the left while writing implementation code in the right pane, without toggling windows.
• Live PR review queue - An engineering team lead adds a GitHub Live Folder pointing at their repo’s open pull requests so the sidebar always shows the current queue without opening GitHub.
• Distraction-free writing sessions - A content creator enables Compact Mode to hide the sidebar and reduce chrome noise while drafting in Notion or Google Docs.
• Quick-check links without losing context - A journalist uses Glance to preview sources linked in an article draft without navigating away or accumulating open tabs.
• Site-specific UI customisation - A power user applies a Boost to remove cookie banners and hide the sidebar on a news site, keeping the tweak persistent across sessions.

Under The Hood

Architecture Zen Browser is structured as a curated patch set applied to Firefox’s upstream source tree via a purpose-built CLI called Surfer. Rather than wrapping Firefox as a dependency, Zen modifies it in-place: Surfer downloads the Gecko source, applies patches from the src/ directory, and compiles a full browser binary. Each Zen feature is implemented as a standalone module — ZenSpaceManager, ZenGlanceManager, ZenViewSplitter, ZenLiveFoldersManager — registered through Firefox’s existing component manifests and initialised via the JSWindowActor parent-child pattern for cross-process isolation. Global state is managed through module-level singletons prefixed with gZen*, tightly coupled to Firefox’s own Services, ChromeUtils, and XUL DOM APIs. The architecture offers deep integration at the cost of tight coupling to Firefox internals, making upstream rebasing the central maintenance challenge.

Tech Stack The browser’s custom features are written in ESM JavaScript targeting Gecko’s privileged chrome context, with Mozilla’s Fluent (FTL) format for all localisation strings. Performance-critical subsystems — the Boosts style-sheet cache and accent-colour cache — are implemented in C++ and exposed to JS via XPCOM interfaces. The build and release pipeline runs on Surfer backed by Python scripts for Firefox version synchronisation, AppImage metadata injection, and automated test running. TypeScript covers tooling and configuration but not browser chrome code directly. CI runs on GitHub Actions with Blacksmith runners; releases are distributed as signed binaries in MAR (Mozilla Archive) format for differential updates via Zen’s own update server.

Code Quality Zen ships an extensive test suite that integrates directly with Firefox’s mochitest and browser-chrome test frameworks, covering Workspaces, Compact Mode, Glance, Live Folders, Split View, URL-bar actions, and tab management in separate browser test directories. C++ components are covered by GoogleTest unit tests (for example, the Boosts accent-cache and colour-filter logic). Code quality tooling includes ESLint with mozilla-specific rule sets, Prettier via a shared @zen-browser/prettier package, and lint-staged with Husky pre-commit hooks. Error handling is explicit and asynchronous throughout, using Promise.withResolvers() and structured try-catch rather than silent fallbacks. Naming conventions follow Mozilla’s established patterns, which improves readability for contributors already familiar with Firefox development.

What Makes It Unique Zen’s most technically distinctive choice is implementing Workspaces as bookmark-backed storage rather than a purely in-memory tab-grouping abstraction — each workspace is a bookmark folder, giving persistence and sync without a separate database. Glance is implemented as an arc-animated floating overlay with configurable keyframe physics (ARC_STEPS, MAX_ARC_HEIGHT, ARC_HEIGHT_RATIO) rather than a simple iframe, preserving the original tab’s rendering context. The Boosts system layers a C++-backed XPCOM stylesheet service atop Firefox’s nsStyleSheetService, enabling per-domain injection without requiring users to install a userscript extension. Live Folders introduce a provider abstraction — RSS and GitHub providers ship out of the box, with a registry pattern that allows community-built providers — turning the bookmark sidebar into a real-time content hub.

Self-Hosting

Zen Browser is released under the Mozilla Public License 2.0, a weak copyleft licence that requires modifications to MPL-covered files to be shared under the same licence, but does not require the entire application to become open source if combined with proprietary code. For individuals and organisations, this means Zen can be used commercially and internally without restriction; only direct modifications to Zen’s own source files need to be disclosed under MPL-2.0. There are no CLAs, no commercial licences, and no proprietary tiers.

Running Zen Browser in a managed environment is closer to deploying a custom Firefox build than installing a self-hosted web service. There is no server component — Zen is a desktop application distributed as binaries for Windows, macOS, and Linux. Organisations that want to manage it at scale should use standard OS-level software deployment tools (Intune, Jamf, Ansible) and can configure preferences via a user.js or policies.json file in the same way they would manage Firefox in enterprise settings. Updates are delivered via Zen’s own MAR-based update server at updates.zen-browser.app, which organisations with strict change-control requirements may want to mirror or disable in favour of manual package distribution.

Zen has no official managed or cloud tier, no SLA, no enterprise support contract, and no paid offering of any kind as of its current release. Support is entirely community-driven through GitHub Issues and Discussions. Organisations that depend on browser stability for regulated or high-availability workflows should weigh this against the rapid release cadence (roughly weekly) and the project’s relative youth — it was founded in early 2024. The upside is that Zen tracks Firefox security advisories closely and ships security fixes within days of Mozilla’s own releases, which reduces the CVE exposure risk compared to slower-moving Firefox forks.