Google Chromium, sans integration with Google
A lightweight approach to removing Google web service dependency
Help is welcome! See the docs/contributing.md document for more information.
In descending order of significance (i.e. most important objective first):
In scenarios where the objectives conflict, the objective of higher significance should take precedence.
Without signing in to a Google Account, Chromium does pretty well in terms of security and privacy. However, Chromium still has some dependency on Google web services and binaries. In addition, Google designed Chromium to be easy and intuitive for users, which means they compromise on transparency and control of internal operations.
ungoogled-chromium addresses these issues in the following ways:
These features are implemented as configuration flags, patches, and custom scripts. For more details, consult the Design Documentation.
This section overviews the features of ungoogled-chromium. For more detailed information, it is best to consult the source code.
Contents of this section:
These are the core features introduced by ungoogled-chromium.
qjz9zk(known as domain substitution; see docs/design.md for details), then modifying Chromium to block its own requests with such domains. In other words, no connections are attempted to the
chrome://flagsentries to configure disabled-by-default features. See docs/flags.md for the exhaustive list.
These are the non-essential features introduced by ungoogled-chromium.
chrome://settings/searchEngines) for customizing search engine suggestions.
http://, hiding certain parameters)
trk:scheme from connecting to the Internet
qjz9zk(as used in domain substitution) from attempting a connection.
--set-ipv6-probe-falseflag above to adjust the behavior instead.
In addition to the features introduced by ungoogled-chromium, ungoogled-chromium selectively borrows many features from the following projects (in approximate order of significance):
Other platforms are discussed and tracked in this repository's Issue Tracker. Learn more about using the Issue Tracker under the section Contributing, Reporting, Contacting.
NOTE: These binaries are provided by anyone who are willing to build and submit them. Because these binaries are not necessarily reproducible, authenticity cannot be guaranteed; In other words, there is always a non-zero probability that these binaries may have been tampered with. In the unlikely event that this has happened to you, please report it in a new issue.
These binaries are known as contributor binaries.
Also, ungoogled-chromium is available in several software repositories:
eloston-chromium. Just run
brew cask fetch eloston-chromiumand
brew cask install eloston-chromium. Chromium will appear in your
This repository only contains the common code for all platforms; it does not contain all the configuration and scripts necessary to build ungoogled-chromium. Most users will want to use platform-specific repos, where all the remaining configuration and scripts are provided for specific platforms:
If you wish to include ungoogled-chromium code in your own build process, consider using the tags in this repo. These tags follow the format
chromium_versionis the version of Chromium used in
revisionis a number indicating the version of ungoogled-chromium for the corresponding Chromium version.
Additionally, most platform-specific repos extend their tag scheme upon this one.
Building the source code: See docs/building.md
List of mirrors:
List of known projects that fork or use changes from ungoogled-chromium:
BSD-3-clause. See LICENSE