How far subtraction can go in a browser

The Chromium engine earned its reputation on speed and on following standards, and it also ships with a set of background connections that leave anyone who cares about where data goes feeling uneasy. Ungoogled Chromium takes the structural route rather than the settings route: it is an open source fork started in 2015 and maintained by the community since, and it patches the source at build time. Company domains are replaced with invalid ones, internal requests are blocked systematically, and the provenance of every binary is documented. Install it and the engine feels entirely familiar while the background goes quiet.

The point worth grasping is that nothing here is a runtime trick. A patch applied while compiling cannot be undone by a policy pushed from a server, which is exactly the failure mode people worry about with extension based fixes. What the fork removes stays removed, and what it keeps behaves like the browser everybody already knows.

The trade is priced in plain sight

Its rule is transparency over convenience. Every change sits in a public patch list that anyone can audit, and the build adds several dozen behaviour switches that expose low level settings which were previously not configurable at all. That is the offer: a browser that explains itself instead of one that asks for trust.

The cost is equally plain. Account sync is gone, along with some capabilities that depend on the company services, and adding extensions from the store requires a helper extension supplied by the community. The project follows upstream closely, so version 153.0.8010.36 arrived in 2026-09, the licence is BSD-3, and community builds exist for Windows, macOS, Linux and Android.

Who it suits, and who should stay away

It suits the person who cares where the background traffic goes and is willing to spend ten minutes setting switches to taste. It suits the person who dislikes a bundle that assumes an account and simply wants a quiet engine. It does not suit anyone whose day depends on sync across devices or who expects everything to work without a single decision, because automatic sync is precisely what was taken away on purpose.

Extension compatibility is where the balance sits. The common extensions, once installed, behave almost exactly as they do in the original, which is the reason this fork remains usable as a daily browser rather than a demonstration. A browser is open for a dozen hours a day, and whether its background is quiet deserves to be taken seriously.

A concrete example of what the patches change: a build that phones home on first launch to measure a new profile, or prefetches a page it thinks you will want, is doing work nobody asked for. Removing that is not a performance feature, it is an answer to a question about consent, and the answer is written in text a person can read rather than explained in a blog post.

Reading the patch list is itself an education. Most people discover for the first time how many connections a browser opens before a single page loads, and that knowledge changes how they read every other product. Even someone who never installs this build comes away knowing more about the browser they already use.

The value of Ungoogled Chromium is not that it is faster or that it has more features, but that it hands the choice back: every background connection that was removed is written in a patch in plain text. For a tool that stays open twelve hours a day, that is the kind of claim worth making and worth checking.