imputnet/helium

Helium is worth a look if you want a Chromium browser with privacy-oriented defaults but don't want to assemble one yourself. It is beta software, so treat it as a daily driver to evaluate, not a settled choice.

The problem

You want to browse with fewer tracking and telemetry defaults, but mainline Chrome pushes you toward Google services and settings you have to harden yourself. Un-Googled builds exist, yet getting one patched, packaged and updated across machines takes effort. Helium changes that step: you install a packaged browser that already carries its own privacy defaults and a custom uBlock Origin fork. The result is a browser you can open and use without a configuration ritual.

What's different

Helium started as a fork of ungoogled-chromium and still sits on Chromium, with patches pulled from several Chromium projects including Bromite, Iridium and Brave. The practical difference is that the privacy work is packaged as a product: platform builds, a first-run setup page at helium://setup, and a Helium-specific uBlock Origin fork with the project's filters and CNAME uncloaking. Its cloud pieces—extension proxy, !bangs, filter lists, updates and crash reports—are self-hostable services, so the project publishes what it actually runs rather than asking you to trust an opaque backend.

The trade-off is that you inherit Chromium's engine and its compatibility profile, plus whatever the Helium patches change. This is not a from-scratch engine or a stripped-down browser; it is a maintained Chromium derivative in beta. The README says unexpected issues may occur and asks users to report them, which is an honest signal about the stage rather than a claim of stability. If you depend on a specific browser extension or enterprise policy, check that behavior against Helium rather than assuming Chrome parity.

Who should try it

A good fit is someone who wants a Chromium-compatible browser with privacy defaults on macOS, Linux or Windows and is comfortable reporting beta bugs. It also suits people who care that the surrounding services are open source and self-hostable, not just the browser binary. A poor fit is anyone who needs a guaranteed-stable browser for regulated or high-stakes workflows, or who depends on Chrome-only integration that Helium's patches may not preserve. Development is centered on macOS and Linux, so contributors on Windows should expect a less-documented path; everyday Windows users still get a packaged release.

Requirements and limitations

Helium is in beta, and that is the main constraint: the README explicitly warns of unexpected issues, so keep a fallback browser available and expect to report problems. Automatic updates are listed for macOS and Windows only; Linux users should check how their package gets updated. Building from source is aimed at macOS and Linux, with the development guide living in the macOS repo; the Linux packaging includes a similar script. Windows is a supported release target but not a primary development platform.

The project's privacy posture depends on services it hosts, and those are self-hostable but not self-hosting by default. If you want to avoid the project's servers entirely, that is additional setup, not a checkbox. Licensing is mixed: Helium-specific code is GPL-3.0, while imported ungoogled-chromium code keeps its BSD 3-Clause license.

HotRepo's take

HotRepo recorded 21,950 stars on 2026-10-24 (+67 that day) and 21,954 on 2026-10-25 (+78), with two days on the daily trending board. That is a snapshot, not a trend line; persistence cannot be judged from two dated observations. Before adopting, verify the update path for your platform and whether the extensions you rely on behave as expected in this beta build.