New Update Ungoogled Chromium

[7Oz-64]

What features makes this browser appealing?

Almost no Google services connections (as i don't need them)
Really good flags (some differ from Chromium)
Nice switch avalaible
Privacy, no Telemetry
If you want you can install extensions (loaded locally, url, extension by NeverDecaf)
MV2 still supported
Guess no AI
Fast Update with Eloston one
Clean Interface

 

[simmerskool]

What features makes this browser appealing?

no google telemetry

 

[HarborFront]

What features makes this browser appealing?

Read my post #94 here on comparison between UG vs Helium vs Brave

H

Battle Post in thread 'Firefox vs. Brave vs. Vivaldi'

May 16, 2026

In order not to start another browser comparison thread I'm adding Ungoogled Chromium vs Helium vs Brave browsers. If mod/TS finds it needs another thread can move this


Below is my comparison. Nothing really new as the pointers are available on the net. They are not mainstream browsers so expect some sites might not work properly.

Summary

If you want an aggressive, minimal de-Googled Chromium with lower RAM use and no crypto or telemetry baggage, Helium currently looks the most user-friendly option; if you want out-of-the-box privacy tooling plus convenience features (Tor...

• HarborFront

• 
• 
• 

 

[HarborFront]

Almost no Google services connections (as i don't need them)
Really good flags (some differ from Chromium)
Nice switch avalaible
Privacy, no Telemetry
If you want you can install extensions (loaded locally, url, extension by NeverDecaf)
MV2 still supported
Guess no AI
Fast Update with Eloston one
Clean Interface

Too bad I tried installing uBO but it won't install. Only uBO Lite accepted

 

[7Oz-64]

@HarborFront
Really, no problem here, but maybe you're using it on Windows or other distro like mine, i even don't modify the V2 avalaibility flag for makes UBO working

 

[HarborFront]

@HarborFront
Really, no problem here, but maybe you're using it on Windows or other distro like mine, i even don't modify the V2 avalaibility flag for makes UBO working

Yup, using on Windows

 

[7Oz-64]

Yup, using on Windows

I've just attached screenshot to my previous post

 

[HarborFront]

I've just attached screenshot to my previous post

Did you drop directly or use a crx file? I can't find the crx file in the uBO zip file from github

EDIT

OK, done it now. I went to Chrome Web Store and downloaded the crx file (with Chromium Web Store app) which allows me to install. I thought that it wasn't available on Chrome Web Store and went to github to download the zip file instaed

 

[HarborFront]

v148.0.7778.178-1 released

Downloads for ungoogled-chromium

 

[HarborFront]

v148.0.7778.215-1 released

Downloads for ungoogled-chromium

 

[nicolaasjan]

Starting with version 150, MV2 will be completely disabled.
PSA: Google Chrome 149 will be the last version fully supporting MV2 and Blocking WebRequest on regular extension installs · Issue #1000 · w3c/webextensions
However, Chromium can still be built with support for MV2 by changing one line in the source code .
That is Line 41 here:
https://source.chromium.org/chromiu...rowser/manifest_v2_experiment_manager.cc;l=41
Set to:

bool g_allow_mv2_for_testing = true;

If you maintain a Chromium fork or build Chromium from source, you can restore MV2 support by changing a single line: just change g_allow_mv2_for_testing to true.
Setting g_allow_mv2_for_testing to true unconditionally restores MV2 functionality without any flags. This boolean is used to run Chromium tests, so it will exist for as long as Chromium needs to run MV2 extension tests (most tests are still MV2 for historical reasons, even if they test behaviors identical across manifest versions).
I tested this approach at the very beginning of Chromium MV2 deprecation years ago and at least one Chromium fork uses it (source). This patch even re-enables MV2 support in Chrome Web Store developer private API, permitting user to install MV2 extensions from Chrome Web Store. As of writing Chrome Web Store hides MV2 extensions from search, but it still serves them if user opens a direct link and delivers updates for MV2 extensions. Of course, Chrome Web Store should be expected to gradually remove MV2 extensions altogether.

Proof from that one Chromium fork that applied the patch: