Chromium
By Google and the open-source community
Chromium is an open-source web browser project, initially released by Google, that provides the source code base for a large share of modern browsers, including Google Chrome, Microsoft Edge, Opera, Brave, and Vivaldi. It includes the…
Definition
Chromium is an open-source web browser project, initially released by Google, that provides the source code base for a large share of modern browsers, including Google Chrome, Microsoft Edge, Opera, Brave, and Vivaldi. It includes the Blink rendering engine and V8 JavaScript engine, and organizations build their own branded browsers by compiling and customizing the Chromium codebase. The project is hosted publicly and accepts contributions from Google, other browser vendors, and independent developers.
Overview
Chromium was released by Google in 2008 alongside the first version of Chrome, with Google choosing to open-source the underlying browser engineering rather than keep it entirely proprietary. This decision let other companies build their own browsers on the same technical foundation instead of each maintaining an independent rendering engine, which had previously been a significant, costly undertaking. Mechanically, Chromium bundles several major components: the Blink rendering engine, which Google forked from WebKit in 2013, for parsing HTML and CSS into visual layouts; the V8 JavaScript engine for executing page scripts; and a multi-process architecture that isolates tabs, extensions, and plugins into separate operating-system processes for stability and security sandboxing. Companies that build on Chromium typically strip out Google-specific integrations, such as usage reporting and proprietary codec licensing, then layer their own branding, default settings, and additional features on top before shipping their own browser. Within the browser landscape, Chromium's role is closer to an engine and platform than a consumer product; end users rarely install Chromium itself as their daily browser, since prebuilt Chromium binaries lack automatic updates and some licensed media codecs, but they very likely use one of the many browsers built on it. Its main rendering-engine competitors are Gecko, used exclusively by Firefox, and WebKit, used by Safari, making Chromium, Gecko, and WebKit the three lineages that define nearly the entire browser market. In practice, Chromium is used by Google to develop Chrome, by Microsoft to build Edge, and by numerous other companies and open-source projects to build specialized browsers without starting rendering-engine development from scratch. It is also embedded in non-browser software through frameworks like Electron, which package a Chromium instance to let developers build desktop applications using web technologies. Chromium's dominance raises concerns about the web's engine diversity: because such a large share of browsers share the same rendering core, and Google exerts significant influence over Chromium's direction as its primary corporate steward, some worry that web standards increasingly reflect one company's priorities. Chromium's own trade-off as a project is that its comprehensive multi-process architecture, while robust, is resource-intensive, a characteristic every Chromium-based browser inherits. This concentration has also spurred renewed interest in independent engine efforts intended to preserve rendering diversity outside of Google's influence, though none currently approach Chromium's scale of adoption or resourcing. Governance discussions around Chromium periodically resurface calls for a more formal, multi-stakeholder steering structure, similar to how some other large open-source infrastructure projects are governed, though Google remains its dominant contributor and final decision-maker in practice.
Key Features
- Open-source browser codebase originally released by Google
- Includes the Blink rendering engine and V8 JavaScript engine
- Uses a multi-process architecture for stability and sandboxing
- Serves as the base for Chrome, Edge, Opera, Brave, and Vivaldi
- Lacks some proprietary codec licensing found in downstream browsers
- Embedded in frameworks like Electron for desktop applications
- Maintained through Google-led open-source development
- Provides the reference implementation many web standards are tested against