Chromium-Based Browsers Ungoogled

What is Ungoogled Chromium?
Ungoogled Chromium is an open-source project that takes the core Chromium source code (the basis for Google Chrome and many other browsers) and strips it of all its Google-specific integrations. The goal is to provide a browser that offers the compatibility and performance of Chromium without the privacy concerns associated with Google’s ecosystem.
Its key principles are:
Remove Google Services: Disable and remove code for Google-hosted services like tracking, safe browsing, crash reporting, Google-hosted search engines, etc.
Increase Transparency and Control: Deploy functionality that gives users more control over their experience.
Maintain Compatibility: Remain as close as possible to the vanilla Chromium codebase, so it works with all websites and extensions.
The Full History of the Ungoogled Chromium Project
Phase 1: Inception and Early Development (2015)
The Creator: The project was started in 2015 by a developer known as Eloston.
Motivation: The primary motivation was privacy. While Chromium is open-source, it still includes numerous proprietary components from Google that communicate with Google’s servers. Eloston saw a need for a version of Chromium that retained its excellent web compatibility but respected user privacy by default.
Initial Approach: The project began as a set of patches and scripts that would systematically de-Google the Chromium source code. This made it reproducible and transparent, allowing others to verify the process.
Phase 2: Growth and Community Adoption (2016 - 2019)
During this period, the project gained significant traction among privacy-conscious users, Linux enthusiasts, and developers who were wary of Google’s data collection practices.
Key developments included:
Expanding Platform Support: Initially focused on Linux, the project quickly expanded to provide builds for Windows and macOS.
Packaging for Distributions: It became popular enough to be included in the official repositories of several Linux distributions (e.g., Arch Linux’s AUR, Debian repositories), making it easy to install and update.
Refinement of Techniques: The de-googling process became more sophisticated. Beyond just disabling services, the project learned to:
Remove Binary Blobs: Strip out proprietary codecs and binaries that were included in the standard Chromium build.
Block Internal Requests: Use domain substitution to block requests to Google servers at the source code level.
Enhance Build Configuration: Change default build flags to further enhance privacy and control.
Phase 3: Mainstream Recognition and Ecosystem Expansion (2020 - Present)
As online privacy became a mainstream concern, Ungoogled Chromium moved from a niche tool to a well-known name in the privacy community.
Key characteristics of this phase:
Influence on Other Browsers: The principles and techniques of Ungoogled Chromium influenced other privacy-focused browsers. Some projects use its patches as a starting point for their own builds.
Wide Availability: Pre-built binaries became readily available via the project’s GitHub releases page, making it accessible to non-technical users.
Active Maintenance: The project remains actively maintained by Eloston and a growing community of contributors. They work tirelessly to keep the patches updated with every new release of Chromium, which is a significant challenge given Chromium’s rapid update cycle.
Not a “Browser” in the Traditional Sense: The project’s core deliverable is the source code and patches. The pre-compiled binaries are a convenience. This differs from a company like Google or Mozilla that develops and distributes a finished browser product.
Key Features (What “Ungoogling” Actually Does)
Removal of Google Services: All features that rely on Google services, such as Google Safe Browsing and Google account synchronization, are disabled or removed.
Custom Patches: The browser includes patches that replace Google-specific domains with non-existent ones and remove proprietary binaries, enhancing privacy and control
Manual Configuration: Users have the option to enable or disable various features through flags, providing granular control over the browser’s behavior
The project’s modifications are extensive, but major ones include:
Disables and Removes:
Google Host Search (the omnibox search suggestion).
Google Safe Browsing (replaced with a user-controlled option).
Google Cloud Messaging (GCM).
Google URL Tracker.
Background crashes reporting and tracking.
Pre-included Google APIs and services.
Adds/Enables Privacy Enhancements:
Forces extensions to be installed from the source (not just the Chrome Web Store), though this can be re-enabled for security.
Removes code that obfuscates the source code (the “source” in open-source).
Uses the system’s certificate store for enhanced transparency.
Challenges and Criticisms
Lack of Convenience Features: By removing Google integration, you lose seamless sync with your Google account, automatic translation, and some safe browsing protections.
Manual Updates: On Windows and macOS, users often have to manually download and install new versions, as there is no auto-update mechanism (by design, to avoid a Google service).
Not for Everyone: It is primarily aimed at users who understand the trade-offs between ultimate privacy and convenience.
Summary Timeline
Period—>Event
2015—>Project created by Eloston to de-Google the Chromium browser.
2016-2019—>Gains popularity in the Linux and privacy communities. Expands to Windows and macOS.
2020-Present—>Becomes a well-known reference in the privacy space. Continues to be actively maintained, keeping pace with Chromium releases.
🛠️ Origins and Development
Founded in 2015: The project was initiated by a developer known by the pseudonym Eloston. It began as a personal project to create a Chromium-based browser without Google integration, primarily targeting Linux users
Early Releases: Eloston released initial builds for Linux, which were well-received by privacy-conscious users. Over time, the project expanded to support other operating systems, including Windows and macOS
Shift in Maintenance: Around 2019, Eloston reduced his involvement in the project. Consequently, the maintenance and development were taken over by the community, with other contributors providing updates and support
🧭 Project Evolution
GitHub Repository: The project’s source code is hosted on GitHub under the repository name This platform allows for community contributions, issue tracking, and discussions.
Community Contributions: Over the years, numerous contributors have added features, fixed bugs, and maintained the browser, ensuring its relevance and functionality.
Transition to Ungoogled Software: In 2022, the GitHub repository was transferred from Eloston’s personal account to a new organization called ungoogled-software, signifying a more community-driven approach to development
📈 Reception and Usage
Privacy Advocacy: The browser has been praised by privacy advocates for its commitment to removing Google dependencies and providing users with greater control over their browsing experience.
Adoption: While it doesn’t have the widespread user base of mainstream browsers, Ungoogled Chromium has garnered a dedicated following among users who prioritize privacy and open-source software.
🔄 Current Status
Active Development: The project continues to receive updates and contributions from the community, ensuring compatibility with the latest web standards and operating systems.
Alternative Builds: Various distributions and package managers, such as Homebrew for macOS and Linux distributions like Debian, offer precompiled binaries of Ungoogled Chromium for easier installation.
Conclusion
Ungoogled Chromium is not a browser with a corporate history but a continuous, community-driven software project. Its history is one of relentless effort to reclaim user privacy from within one of the world’s most dominant software platforms. It serves as a critical tool for privacy advocates and a testament to the power of open-source to empower users. It is the browser to choose when you want the Chromium engine but want to sever all ties to Google by default.