Chromium is the open-source project; Chrome is Google's branded build on top. See what Google adds — and why kernel checks report 'Chromium', not 'Chrome'.
"Chromium" and "Chrome" get used almost interchangeably, but they aren't the same thing. Chromium is the open-source browser project that Google publishes; Chrome is Google's own branded product, built on top of Chromium with a set of closed-source additions layered in. If you've ever run BrowserInsight's kernel check and seen it report "Chromium 124" instead of "Chrome," this is why — and it's not a bug. Here's exactly what separates the two, and what that gap means for privacy.
Key Takeaways
- Chromium is Google's open-source project — the raw browser, built from the Blink rendering engine and V8 JavaScript engine, free for anyone to build and ship.
- Chrome is Chromium plus Google's proprietary layer: branding, auto-update, a Google API key bundle, account sync, proprietary media codecs, Widevine DRM, and crash/usage reporting.
- Dozens of browsers — Edge, Brave, Opera, Vivaldi, Samsung Internet, Yandex — are built on Chromium too, which is why they all share the same underlying rendering behavior.
- Engine-detection tools report "Chromium
<version>" rather than "Chrome" because they detect the shared engine via feature behavior, not the branded product sitting on top of it. - The privacy-relevant deltas are almost entirely in Google's added layer — the open-source Chromium core itself doesn't include Google's account sync or telemetry hooks.
What Chromium actually is
Chromium is the open-source browser project Google started in 2008 and continues to fund and maintain. It bundles two components: the Blink rendering engine (which lays out HTML and CSS) and the V8 JavaScript engine (which executes scripts). Anyone can download the Chromium source, compile it, and ship a browser — no license fee, no Google approval required. That's exactly what Microsoft, Brave, Vivaldi, and a long list of others do.
Because it's a bare open-source build, plain Chromium ships without most of the conveniences people associate with Chrome: no licensed proprietary media codecs, no automatic background updates, and no Google account integration. Distributions like the ones in Linux package repositories are essentially Chromium with none of Google's branding attached.
What Google adds to make Chrome
Chrome starts from the same Chromium source but adds a closed-source layer on top before Google ships it as a product:
- Branding and UI polish — the Chrome name, icon, and some interface details that never make it into the open-source tree.
- Automatic background updates — Chromium doesn't self-update; Chrome ships an updater service that keeps it current silently.
- A private Google API key bundle — used for services like spell-check, safe browsing lookups, and geolocation, which Chromium builds either lack or must supply their own keys for.
- Google account sync — bookmarks, passwords, history, and extensions synced across your signed-in devices.
- Proprietary media codecs — licensed codecs such as AAC and H.264 for video/audio playback that Chromium omits for licensing reasons.
- Widevine DRM — required for streaming services like Netflix and Disney+ to play protected content; Chromium doesn't include it by default.
- Crash reporting and usage statistics — opt-out telemetry that reports crashes and feature usage back to Google.
None of this changes how pages render — Blink is Blink either way — but it does change what leaves your machine and what Google can see about your browsing.
Chromium vs Chrome — comparison
| Chromium | Chrome | |
|---|---|---|
| License | Open source (BSD-style) | Proprietary, free to use |
| Rendering engine | Blink | Blink (identical) |
| Auto-update | No, manual | Yes, background service |
| Google account sync | No | Yes |
| Proprietary codecs (AAC/H.264) | No | Yes |
| Widevine DRM | No | Yes |
| Crash/usage reporting | No | Yes, opt-out |
| Who ships it | Anyone who compiles the source |
Chromium is a family, not just Chrome
Chrome is only the most famous member of a much larger family. Microsoft Edge, Brave, Opera, Vivaldi, Samsung Internet, and Yandex Browser are all built on the Chromium codebase, each adding its own layer on top the same way Chrome does — Brave adds tracker blocking and its own privacy defaults, Edge adds Microsoft account integration and its own telemetry, and so on. Google publishes engine milestones on the Chrome feature roadmap, and because these browsers all track the same underlying Chromium release cadence, a new engine milestone tends to reach Chrome, Edge, and Brave within a similar window.
That shared foundation is also why compatibility testing against "Chrome" effectively tests most of the browser market at once — a page that renders correctly in one Chromium browser will almost always render the same way in the others, since the rendering layer underneath is identical.
Why kernel-check reports "Chromium," not "Chrome"
BrowserInsight's kernel check doesn't read your browser's name off its user-agent string or its "About" page — it reverse-engineers the actual rendering engine version from feature-detection behavior: which APIs exist, how specific edge cases are implemented, and other signals that are far harder to fake than a text label. Chrome, Edge, Brave, Opera, and every other Chromium-based browser report the same engine milestone for the same underlying build, because they are running the same Blink engine version underneath their separate branding.
That's the practical reason the tool's verdict says "Chromium 124" instead of "Chrome 124": the check is measuring the shared open-source core, not the proprietary product wrapped around it. If you want the deeper background on why engine detection works this way at all — including what happens when Blink, Gecko, and WebKit disagree — see Browser Engines Explained. And because the traditional user-agent string can simply be edited to claim any browser name, understanding the Chrome developer platform's approach to structured identity signals like User-Agent Client Hints explains what's replacing that string as the more trustworthy channel.
Frequently Asked Questions
Is Chromium safe to use instead of Chrome?
It's the same rendering engine, so page compatibility is equivalent. The trade-offs are practical: plain Chromium builds typically lack automatic updates (so you're responsible for staying current with security patches) and lack Widevine DRM (so some streaming services won't play protected video). Security-conscious users who value not having Google's proprietary telemetry layer sometimes prefer it for exactly that reason, provided they have another way to keep it updated.
Does Chrome collect more data than Chromium?
Chrome's proprietary layer includes opt-out crash reporting and usage statistics that plain Chromium doesn't ship with. Signing into a Google account in Chrome also enables sync, which by design shares bookmarks, history, and passwords with Google's servers. Chromium itself, run without any Google account, doesn't have that sync channel to begin with.
Are Edge and Brave "Chrome" under the hood?
No — they're Chromium under the hood, not Chrome. Edge and Brave build on the same open-source Chromium project Google does, but each adds its own separate closed-source layer (Microsoft's for Edge, Brave's tracker-blocking and privacy defaults for Brave) rather than Google's. They share Chrome's rendering engine, not its proprietary additions.
Why does my browser say "Chrome" but the kernel check says "Chromium"?
Because they're answering different questions. Your browser's own UI reports its product name (Chrome, Edge, Brave, whichever you installed). The kernel check reports the rendering engine detected through feature behavior — and since Chrome's rendering engine is Chromium's Blink engine, unmodified, that's the accurate technical answer regardless of which branded product you're running.
Conclusion
Chromium is the open-source engine project; Chrome is Google's branded product built on top of it, with auto-update, account sync, proprietary codecs, DRM, and telemetry layered in. The rendering behavior underneath is identical, which is exactly why dozens of browsers — Chrome included — all share the same Chromium foundation, and why engine-detection tools correctly identify that shared core as "Chromium" rather than any one product's name.
Recommended Reading:
