Helium browser: a Chromium fork with unbiased ad-blocking

What Helium is, and who it is actually for

Helium describes itself as "the Chromium-based web browser made for people, with love", with privacy first and unbiased ad-blocking. The repository is a C++ codebase with patches, build configuration and packaging tooling, not an application you compile in an afternoon. The README credits ungoogled-chromium as the base and says this repo is "heavily modified for Helium".

The audience is narrow and specific. If you want Chrome's rendering engine and extension compatibility without Chrome's account integration, this is aimed at you. If you want a browser that installs in one command and never surprises you, it is not. The README states plainly that Helium is currently in beta and that unexpected issues may occur, with a request to report them if they have not already been reported. That sentence is the honest part of the pitch, and it should shape how you plan to use it.

How the fork is put together: patches, pruning and domain substitution

The top-level layout tells you more about the architecture than the README does. There is a patches directory, sorted by vendor according to the README, holding changes from ungoogled-chromium, the Inox patchset, Debian, Bromite, Iridium Browser and Brave. There is a pruning.list and a domain_substitution.list, which are the mechanisms ungoogled-chromium uses to strip components and rewrite hardcoded Google domains at build time. flags.gn holds the GN build arguments. deps.ini and downloads.ini pin the sources that get fetched.

So the data flow is: upstream Chromium at a pinned revision (revision.txt, chromium_version.txt), plus a stack of patches, minus pruned components, with domains substituted, built through GN. Helium is not a wrapper around Chromium. It is a build system that produces a different binary from the same source tree.

The ad-blocking is handled separately. The README lists a Helium fork of uBlock Origin as its own repository, so the blocker ships as a maintained fork rather than an unmodified upstream extension. That matters for filter list updates and for how quickly a breakage gets fixed, and it also means the blocker's behaviour is Helium's responsibility, not a third party's.

Installing Helium on Linux, macOS or Windows

The README says the easiest way to download Helium is helium.computer, and that the site will pick a compatible binary for your platform automatically. If you would rather go straight to a release, the README points to per-platform repositories: helium-macos, helium-linux and helium-windows, each with its own releases page. There is no single install command documented in this repository, because this repository is the build and patch tree, not the packaging.

On Linux, the packaging repository is the one to read. The README notes that Linux packaging includes a development script similar to the macOS one, and that the same guide can be applied there. For a normal install, take the package from the helium-linux releases rather than building. The build path is documented for contributors, not for users:

# from the macOS repo's building docs, referenced by this README
# https://github.com/imputnet/helium-macos/blob/main/docs/building.md

A first real use looks like any browser launch: start Helium, confirm the version shown in the about page matches the release you downloaded, then open the extension settings and check that the uBlock Origin fork is present and enabled. If it is not, the build you installed is not the one the README describes. After that, load a page with heavy third-party scripts and watch the blocker's counter. That is the fastest way to confirm the fork is doing anything at all.

The beta status is a real constraint, not a disclaimer

The README's note is unambiguous: Helium is currently in beta, so unexpected issues may occur. Treat that as a functional limitation. A browser sits between you and every credential, payment and document you touch, and beta software in that position means you accept a nonzero chance of a rendering bug, a crash on a site you need, or a profile that does not survive an update.

The release cadence visible in the repository is fast, with 0.17.0, 0.17.1 and 0.17.2 all landing within about a week. Fast point releases after a minor version usually mean fixes for something that broke, which is normal for a project at this stage and also a reason not to treat any single release as settled.

The other gap is documentation. The README does not document rollback, profile migration from another browser, or what happens to your data on upgrade. Those are the questions a cautious adopter asks first, and this repository does not answer them. If you need those answers before you switch, you are looking at the wrong artifact: check the platform repositories and the onboarding repository, which the README lists but does not describe.

How Helium differs from ungoogled-chromium and from Brave

ungoogled-chromium is the closest relative and the clearest alternative. The README says this repo is based on it but heavily modified. The difference in approach is that ungoogled-chromium is a patchset you apply and build yourself, with no first-party binary distribution and no bundled content blocker. Helium ships prebuilt binaries through per-platform repositories, maintains its own uBlock Origin fork, and adds patches from Brave, Bromite, Iridium and Debian on top. If you want the minimal upstream-derived patchset and you are comfortable building Chromium, ungoogled-chromium is the more conservative choice. If you want the result without a multi-hour build, Helium is the packaged version of that idea.

Brave is the other obvious comparison, and the README itself acknowledges that Helium includes patches from Brave. The difference is in what ships by default. Brave bundles its own ad-blocking engine and its own optional rewards and wallet features. Helium's README positions the project as "no bloat and no noise" with a forked uBlock Origin instead of a homegrown blocker. That is a genuine architectural difference: uBlock Origin's filter list ecosystem is external and inspectable, while a built-in engine's rules are whatever the vendor ships. If you already trust uBlock Origin's lists, Helium's approach is easier to reason about. If you want an ad blocker maintained as part of the browser's own release cycle, Brave's model is the one you want.

Licence, maintenance and what an upgrade costs you

Helium's own code, patches and unique content are GPL-3.0. Content imported from other projects keeps its original licence, and the README gives the example that unmodified code from ungoogled-chromium remains under their BSD 3-Clause licence, with the text in LICENSE.ungoogled_chromium. For anyone redistributing a modified build, that split matters: the GPL-3.0 obligations attach to Helium's contributions, and the BSD terms attach to the imported portions. This is a description of what the repository states, not legal advice; if you plan to redistribute, read both files and get your own counsel.

Maintenance looks current. The last push was on 2026-09-17, and the repository is not archived. That is a recent commit relative to the release history, and the version file and chromium_version.txt give you a way to see which upstream Chromium revision a given Helium release tracks.

The upgrade cost is the part people underestimate. Because Helium pins a Chromium revision and carries patches from five other projects, a rebase is not a version bump. Every upstream Chromium change can conflict with the patch stack, and the domain substitution and pruning lists have to stay in sync with whatever Chromium renamed or moved. That work happens on the maintainers' side, but it determines how quickly a security fix in Chromium reaches your machine. The relevant thing to watch is not the Helium version number alone; it is which Chromium revision that version is built against.

Editorial conclusion

Helium suits people who want a Chromium engine without Google's defaults and are willing to run beta software. It is the wrong choice for anyone who needs enterprise policy support or a stable release channel, and for anyone unwilling to read release notes before upgrading. Before adopting it, verify that the platform repository for your OS has a current release, that the uBlock fork handles the filter lists you depend on, and that your sync or password manager choice survives the move, since the README does not document migration from another browser.

Frequently asked questions

Official sources

1. imputnet/helium on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases