ungoogled-chromium

Overview

ungoogled-chromium is a Chromium web browser branch designed for maximum privacy and user control. Fundamentally, it is a standard Google Chromium browser, but its core objective is to completely remove all dependencies on Google's network services, domains, and binary files, without adding new features or altering the default user interface. Think of it as a “clean” or “de-googled” version of Chromium.

This project is not a standalone browser with its own independent vision, but rather a “drop-in replacement” that aims to maintain high consistency with official Chromium’s experience while granting users greater transparency and control.

Core Philosophy and Goals

The project follows these goals, ordered by priority:

1. Primary Goal: Provide a Chromium browser that does not rely on any Google network services.
2. Secondary Goal: Preserve as much of Chromium’s default functionality and experience as possible, making it a “plug-and-play” replacement.
3. Tertiary Goal: Include a set of privacy-enhancing, control-improving, and transparency-increasing tweaks (mostly requiring manual configuration to enable).

In case of conflicts between goals, higher-priority goals take precedence.

Core Features and Characteristics

ungoogled-chromium focuses on “removal” and “disabling” rather than “adding” features. Its main work includes:

• Removal of Network Service Dependencies:

  • Disable background communications: Remove all background connections to Google servers (or other network services) during build and runtime. This includes automatic update checks, Safe Browsing, geolocation queries, crash reporting, usage statistics, QUIC protocol support, etc.
  • Strip Google-specific code: Remove all code and features related to Google-exclusive services (e.g., Google Cloud Messaging, Google Host Detector, Google URLs, Google Safe Browsing).
  • Domain blocking/replacement: Use blacklists and domain replacement techniques to prevent the browser from connecting to Google’s domains.

• Enhanced Privacy and Control (manual activation required):

  • The project includes numerous privacy and security patches that are disabled by default.
  • Users must enable these features manually via command-line flags, extensions, or configuration changes (e.g., enforcing HTTPS-only mode, fine-grained cookie controls).

• Improved Transparency:

  • By removing “black-box” operations (e.g., silent background requests) and telemetry code, the browser’s behavior becomes more transparent and predictable to the user.

Key Differences from Standard Chromium / Chrome

Feature	ungoogled-chromium	Google Chromium	Google Chrome
Google Service Integration	Completely removed	Partially present (e.g., sync, Safe Browsing)	Deeply integrated (account, sync, services, etc.)
Background Communication	Dramatically reduced, almost all telemetry and automatic connections removed	Present (update checks, crash reporting, some service connections)	Extensive background services and data collection
Default Experience	Close to native Chromium, but “cleaner” and more minimal	Original experience with Google service integrations	Full Google ecosystem experience
Binary Files	Replaces proprietary Google binaries (e.g., some codecs, Widevine)	Contains some proprietary Google binary blobs	Contains all proprietary Google components
Build Control	Offers configuration options for further privacy and control enhancements	Standard build options	Unified build controlled by Google

In short: If you trust Google’s products but want more control, use standard Chromium. If you want a browser completely free of any Google elements while retaining Chromium’s performance and compatibility, choose ungoogled-chromium.

Target Audience

• Privacy-focused users: Those who do not want any unnecessary connection between their browsing activity and Google.
• Free software advocates: Users seeking a browser experience as close to fully free/open-source software as possible.
• Advanced users and developers: Individuals who want full control over browser behavior and are willing to manually configure advanced options.
• Users satisfied with the Chromium ecosystem but opposed to Google dependency: Those who enjoy the performance and extension ecosystem of Chrome/Edge/Brave but wish to remove corporate control.

How to Obtain

Since the project itself is a source code repository, ordinary users must download pre-built binaries from third parties.

1. Visit the project’s GitHub Releases page or official download Wiki (usually linked in the README) to find the latest precompiled version for your operating system (macOS, Windows, Linux, etc.).
2. For macOS users, installation via Homebrew Cask is sometimes available: brew install --cask eloston-chromium (this is one of the popular macOS builds).

Important Notes

• No automatic updates: To maintain de-googling, the browser removes automatic update functionality. Users must manually download and install new versions.
• Some features are unavailable: Functions relying on Google services will not work, such as “syncing bookmarks, history, passwords from a Google account” or “native login to the Chrome Web Store” (though CRX extensions can often be installed directly via extension ID).
• Advanced features require manual activation: Its greatest privacy benefits are often hidden within configuration options and command-line parameters; beginners may need to consult documentation to fully utilize them.
• Community-driven: This is an open-source community project; update frequency may lag behind official Chromium.

Conclusion

ungoogled-chromium is a specialized variant of the Chromium browser. Through precise, surgical modifications, it offers a powerful choice for users who value privacy, transparency, and software autonomy. It sacrifices seamless integration with the Google ecosystem and automated convenience for ultimate control over browser behavior. For users seeking to escape data collection by “big tech” companies while still enjoying the performance and extension compatibility of modern web browsers, it is a highly attractive solution.