Key takeaways
- Chromium is the open-source browser project Google leads; Chrome is Google’s own build of it with H.264 and AAC codecs, Widevine DRM, an automatic updater and Google account sync added.
- Both use the same Blink rendering engine and V8 JavaScript engine, so the same version renders and runs a page the same way.
- For automated testing, use Chrome for Testing: Google’s versioned Chrome build with no auto-update. Selenium Manager, Puppeteer and Playwright (since 1.57) download it for you.
Chromium is the open-source browser project that anyone can download, build or fork; Google Chrome is Google’s branded build of that same code with proprietary parts added. Chrome adds the H.264 video and AAC audio codecs, the Widevine DRM module that streaming services need, a background updater, Google account sync and opt-in crash reporting. Under the hood both run the same engines, so for most people the choice comes down to updates, media playback and how much Google integration they want.
Chromium vs Chrome at a glance
| Chromium | Google Chrome | |
|---|---|---|
| Who builds it | The Chromium project, a Linux distribution, or you | |
| License | Open source (BSD-style license) | Proprietary, free to use, built from Chromium code |
| Engines | Blink and V8 | Blink and V8 |
| Video codecs | AV1, VP8, VP9 (no H.264) | AV1, VP8, VP9 and H.264 |
| Audio codecs | Opus, Vorbis, MP3, FLAC, WAV (no AAC) | The same plus AAC |
| Widevine DRM (Netflix, Disney+) | Not bundled | Bundled |
| Automatic updates | No for snapshot builds; Linux packages update through the package manager | Yes, in the background |
| Google account sign-in and sync | Not available to third-party builds since March 2021 | Yes |
| Crash reports and usage statistics | Never sent | Sent only if you turn them on |
| Logo | Blue | Multicolored |
Codec support in a Chromium package depends on who built it: some Linux distributions compile their Chromium with extra codecs turned on. The table describes the default build settings in the Chromium source and Google’s own comparison for Linux.
What is Chromium?
Chromium is the open-source project behind Chrome. Its source code is published under a BSD-style license, which means anyone can read it, change it and ship their own browser from it. Google started the project and its engineers do most of the work, but the code is public and other companies contribute too.
That openness is why so many browsers are built on it: Microsoft Edge, Brave, Opera, Vivaldi and Samsung Internet all start from Chromium and add their own features, updater and branding.
You can get Chromium in two ways. On Linux, most distributions package it, and the package manager keeps it updated. On any platform you can also download raw snapshot builds from the Chromium project, but those are built from arbitrary revisions that do not map to a Chrome release, they never update themselves, and the project warns against third-party “portable” Chromium binaries for security reasons.
What is Google Chrome?
Chrome is Google’s build of Chromium, tested by Google before release and shipped with everything the open-source build leaves out:
- Proprietary media support. H.264 video and AAC audio, plus the Widevine content decryption module that DRM-protected streaming relies on.
- An updater. Chrome updates itself in the background. Since Chrome 153 (8 September 2026) Google ships a new stable version every two weeks instead of every four; Chrome 156 began rolling out to the Stable channel in October 2026. An Extended Stable channel exists for organizations that cannot keep up with that pace.
- Google services. Sign-in and sync for bookmarks, passwords and history, plus features that call Google APIs such as Safe Browsing and geolocation. Chrome ships with Google’s API keys; a Chromium build only has them if whoever built it added their own.
- Opt-in reporting. Chrome sends crash reports and usage statistics only if you allow it. Chromium never sends them.
Key differences between Chromium and Chrome
Media codecs and DRM
This is the difference people notice first. A default Chromium build plays AV1, VP8 and VP9 video but not H.264, and it has no AAC audio. Many MP4 files and some video calls depend on exactly those codecs, so a clip that plays in Chrome can fail in Chromium. Widevine is a separate gap: without it, Netflix and similar services refuse to play.
Automatic updates
Chrome patches itself. A snapshot Chromium build stays on the version you downloaded until you replace it, and a distribution package is only as fresh as its maintainers keep it. With Chrome now releasing every two weeks, an un-updated Chromium falls behind quickly.
Google account sync
In January 2021 Google announced that third-party Chromium builds would lose access to Chrome sync and other private Google APIs from 15 March 2021. If you rely on bookmarks and passwords following you between devices through a Google account, that only works in Chrome (or another browser’s own sync service).
Privacy
Chromium never reports crashes or usage metrics to Google, and it has no Google sign-in by default. Chrome lets you turn reporting off, but it is built around a Google account. If keeping Google out of the picture matters to you, Chromium from your distribution, or a privacy-focused Chromium-based browser, is the cleaner start.
Security
The security code is the same: the sandbox, site isolation and the rest of the engine come from the same source. Google’s Linux comparison notes that Chrome always has the sandbox on, while in Chromium it depends on how the distribution built it. In practice the bigger risk is update lag. A Chromium build that is a few versions behind is missing security fixes that Chrome users already have.
Is Chromium faster or lighter than Chrome?
For the same version, page rendering and JavaScript speed are the same, because both run Blink and V8. Chrome does run a few extra background services, such as the updater and sync. When one feels faster than the other, the cause is usually a version gap, extensions or a long-lived profile full of cached data, not the branding. If memory use matters, compare the two on your own machine with the same tabs open, using each browser’s built-in task manager.
Chromium vs Chrome for automated testing
For test automation the question has a different answer than for everyday browsing. You want a browser version you can pin, one that matches what users run, and one that never updates in the middle of a CI job.
Google built Chrome for Testing for exactly that in 2023. It is a dedicated Chrome flavor with no auto-update, published for every Chrome release, so a version number maps directly to a public Chrome version. It is built with the same proprietary codecs and Widevine as Chrome, which raw Chromium snapshots lack. Google’s own reasons for not using Chromium snapshots in tests are that they are not reliably available on every platform, their versions do not map to Chrome releases, and Chromium is different from Chrome.
The major automation tools now default to it:
- Selenium: since Selenium 4.11, Selenium Manager downloads and caches the current stable Chrome for Testing if Chrome is not installed, along with the matching driver.
- Puppeteer downloads a recent Chrome for Testing and a
chrome-headless-shellbinary when you install it. - Playwright: from version 1.57, Playwright runs Chrome for Testing instead of its own Chromium builds (headless runs use
chrome-headless-shell); on Arm64 Linux it still uses Chromium. The Playwright tutorial shows the API, which is unchanged.
Headless mode changed too. Chrome 132 removed the old headless mode from the main Chrome binary; it lives on as the separate chrome-headless-shell, while --headless in Chrome itself now runs the full browser. Older guides such as taking screenshots with Puppeteer and headless Chrome still show the right idea, but expect small rendering differences between the two headless modes.
A practical setup: pin a Chrome for Testing version in CI so results are reproducible, and run the same suite against current stable Chrome on a schedule, since users now move to a new version every two weeks. If your product plays video, include at least one test in a browser with H.264 and AAC. To check other engines (Firefox’s Gecko, Safari’s WebKit), see our roundup of cross-browser compatibility testing tools.
Which should you use?
Everyday users
Chrome, or another Chromium-based browser with its own updater. You get automatic security fixes, working video on every site and sync between devices without any setup.
Privacy-conscious users
Chromium from your Linux distribution’s package manager, which updates with the rest of your system and sends nothing to Google by default. Avoid manually downloaded snapshot builds for daily browsing, because they never update.
Developers and QA engineers
Chrome for Testing for automated tests, regular Chrome for checking what users see, and Chromium when you need to build or patch the browser itself.
Businesses and agencies
Chrome, managed through Google’s enterprise policies, is the easier fleet to keep patched. Teams that cannot absorb a new version every two weeks can use the Extended Stable channel. Agencies should test client sites in Chrome first, because that is the build most of their visitors run.
Testing page speed in Chrome with LoadFocus
Page speed numbers depend on the browser that measures them, so measure in the one your visitors use. The free LoadFocus website speed test runs Google Lighthouse in Chrome against any public URL, with no account, and shows the scores, the Core Web Vitals and what slows the page down. To keep watching a page after a release, page speed monitoring runs scheduled Lighthouse audits from 25 cloud regions, alerts you when a page slows down and shows real-user Core Web Vitals from the Chrome UX Report next to the lab results.
Frequently Asked Questions
Which is better, Chromium or Chrome?
For most people, Chrome: it updates itself, plays every video format and syncs across devices. Chromium is better if you want a fully open-source browser with no Google sign-in or reporting, and you get it from a source that keeps it updated, such as your Linux distribution.
Do I need Chromium if I have Chrome?
No. Chrome contains everything Chromium does plus codecs, DRM and Google services. Developers sometimes install Chromium or Chrome for Testing alongside Chrome to test against a fixed version.
Is Chromium owned by Chrome?
No. Chromium is an open-source project that Google started and leads, and its code is under a BSD-style license. Chrome is Google’s proprietary product built from that code, so the relationship runs the other way: Chrome is made from Chromium.
Is Chromium a good or bad browser?
It is a good browser with the same engine as Chrome. Its weak points are practical: no H.264 or AAC by default, no Widevine for streaming services, no Google sync, and no automatic updates unless a package manager handles them.
Why is Chromium so popular?
Because it is the open-source base of most browsers in use today. Chrome, Microsoft Edge, Brave, Opera, Vivaldi and Samsung Internet are all built on Chromium.
Is Chromium safe?
Yes, as long as it stays up to date. It has the same security architecture as Chrome. The risk comes from old builds: Chrome now ships a new version every two weeks, so a Chromium that is not updated falls behind on security fixes quickly.
What browser uses the least RAM?
There is no fixed answer, because memory use depends mostly on the pages and extensions you have open. Chromium and Chrome running the same version with the same tabs use similar amounts. Measure on your own machine with the browser’s built-in task manager rather than relying on general rankings.
Which browser is the fastest?
Chromium and Chrome render pages at the same speed when they are on the same version, since they share Blink and V8. Differences between browsers built on other engines depend on the site and the benchmark, so test the pages you care about.
Is Firefox based on Chromium?
No. Firefox uses Mozilla’s own Gecko engine, and Safari uses WebKit. Testing in Chromium-based browsers alone does not cover them.
Is Chromium less secure than Chrome?
Not by design: the security code is the same. It becomes less secure in practice when it lags behind Chrome’s releases, which happens with manually downloaded builds that never update.
Can I watch Netflix on Chromium?
Usually not. Netflix needs the Widevine DRM module, which Chrome bundles and default Chromium builds do not. Some Chromium-based browsers add Widevine themselves.
Can I switch between Chromium and Chrome easily?
Yes. Both can export and import bookmarks as an HTML file. Passwords and extensions need to be moved separately, and Google sync will not carry them into a third-party Chromium build.
How do I keep Chromium up to date?
Install it from your Linux distribution’s package manager, which updates it with the rest of the system. A snapshot build downloaded from the Chromium project never updates itself; you have to download a new one.
What is Chrome for Testing?
A Chrome build from Google made for test automation. It does not auto-update, it exists for every Chrome release, and it includes Chrome’s codecs. Selenium Manager, Puppeteer and Playwright download it automatically.
Sources
- Chromium Browser vs Google Chrome, Chromium docs (checked October 2026)
- Chromium build settings for proprietary codecs and Widevine (October 2026)
- Download Chromium and API keys, chromium.org (October 2026)
- Limiting Private API availability in Chromium, Chromium Blog, 15 January 2021
- The two-week release cycle is here, Chrome for Developers, 8 September 2026
- Chrome for Testing: reliable downloads for browser automation, Chrome for Developers
- Removing the old headless mode from Chrome, Chrome for Developers, 23 October 2024
- Selenium Manager, selenium.dev; Puppeteer installation, pptr.dev; Playwright release notes, v1.57 (October 2026)
