What Is Chromium? – Definition and How It Works

Learn what Chromium is, how it relates to Chrome and other browsers, what its components do, and why it matters for automation.

Chromium is the open-source browser project that Chrome and many other browsers are built from. It supplies the engine, the networking stack, and the developer-facing protocol that most browser automation depends on.

1. Chromium and Chrome

Chrome is Chromium plus proprietary additions.

For automation the important consequence is that codec differences can affect media playback, while the automation surface itself is identical.

2. What It Contains

• Blink — the rendering engine that turns markup and styles into a layout tree.
• V8 — the JavaScript engine, also used outside browsers.
• Network stack — connection handling, TLS, caching, cookies.
• Multi-process architecture — separate processes per tab and per component, for isolation and stability.

That architecture is why a crashed page does not take down the browser, and why memory use per session is substantial.

3. The Chrome DevTools Protocol

CDP is the interface for instrumenting and controlling a Chromium browser. It exposes domains for navigation, DOM inspection, network interception, performance tracing, and input.

Nearly all Chromium-based automation speaks CDP, directly or through a library, which is why so many tools share the same capabilities and the same limits.

4. Why Other Browsers Use It

Building a browser engine is an enormous undertaking, so many vendors ship Chromium with their own interface and services layered on. The practical effect is that a page rendering correctly in one Chromium-based browser usually renders identically in the others.

Firefox and Safari maintain separate engines, which is why cross-browser testing remains meaningful despite Chromium's ubiquity.

5. Chromium in Automation

Automation libraries either bundle a specific Chromium build or connect to an installed one. Bundling makes behaviour reproducible, at the cost of a large download per version.

Version matters: rendering, protocol details, and default flags change between builds, so pinning the browser version is as important as pinning the library.

6. Headless Mode

Chromium can run without a visible window. Modern headless mode uses the same rendering path as headed mode, so differences are far smaller than they once were — though timing and some GPU-dependent behaviour can still differ.

Automated instances are also observable through characteristics of their default configuration, which is a separate matter from whether a window is drawn.

7. Resource Characteristics

Each browser context consumes substantial memory, and each page more. Practical measures for running many sessions: reuse one browser process with several isolated contexts, block unnecessary resource types, and close pages promptly rather than relying on garbage collection.

8. Summary

Chromium is the open-source project underlying Chrome and many other browsers, providing Blink, V8, the network stack, and the DevTools Protocol that automation relies on.

Chrome adds proprietary pieces on top, but the automation surface is the same — so the decisions that matter in practice are version pinning, context reuse, and resource control.

Potential Related Glossary

• Headless Browser
• Browser Fingerprints
• Parsing
• Web Crawling