Why Your Chromium-Based Browser Shows a Different Version Than Chromium Drift

Your browser's version number and the Chromium version on Chromium Drift can legitimately differ, and it usually isn't a sign that anything is wrong. Three things explain most mismatches: updates roll out gradually, Chrome's dashboard entry reflects the newest pinnable release rather than every build in flight, and some browsers use their own versioning scheme that doesn't map cleanly onto Chromium's numbers. To see what Chromium version your own browser is actually running, check it at chromiumchecker.com rather than comparing version strings by eye.

Gradual rollouts mean "stable" isn't the same as "on your machine"

When a browser publishes a new stable release, it doesn't reach everyone at once. The vendor designates a version as stable, then serves it to users over a period of time. Chromium Drift shows the version officially designated as stable, so for a day or two after a release, the dashboard can be ahead of what your browser reports.

This is expected behavior, not a detection error. If the dashboard says a newer major version than your browser shows, waiting a day or two is often all that's needed.

For Chrome, the dashboard shows what administrators can pin

Chrome gets a narrower definition on Chromium Drift than other browsers. The dashboard lists the newest release that system administrators can pin. That deliberately excludes:

• Partial rollouts that haven't reached full availability
• A/B test builds served to subsets of users

So if you're on a Chrome build that came from a partial rollout or an experiment, your version can differ from the dashboard even though both are "current" in their own sense.

Different browsers, different version numbers

Not every Chromium-based browser uses Chromium's version numbers. Some vendors run their own versioning scheme, which is exactly what makes it hard to tell which Chromium release they're based on just by reading the number. A browser reporting "version 120" tells you nothing about its Chromium base unless the vendor documents the mapping.

This is also why Chromium Drift has to detect versions in different ways. Some browsers are fetched live from public APIs on each page load; others are detected daily through CI by extracting version information from their binaries. The two methods can produce slightly different freshness, but neither one is reading your local install.

What the colors on the dashboard mean

The color coding is relative to Chrome Stable, not to an absolute security judgment:

A browser can show blue even if it's on a newer Chromium major than Chrome Stable, because Google rolls out each Chrome Stable release gradually. If another Chromium browser has already picked up that newer major, it isn't behind, so it stays blue.

Being a major version behind doesn't automatically mean insecure

This is the most common misreading of the dashboard. A yellow or red color means the version number trails Chrome Stable — it does not by itself mean the browser is missing security patches.

Some browsers intentionally track Chromium's Extended Stable channel and backport security fixes from newer releases. In that case the major version number stays behind while the security fixes don't. The dashboard is a version-tracking tool, not a vulnerability scanner, so treat the colors as a prompt to look closer rather than a verdict.

Why the dashboard lags matter at all

When a browser does ship an older Chromium version without backported fixes, two things follow: users may be exposed to known vulnerabilities that have already been patched elsewhere, and they don't get the latest Web APIs and features, which shows up as website compatibility problems. That's the real reason to care about drift — not the number itself, but whether patches and platform features have actually landed.

If your browser isn't listed

Chromium Drift covers major Chromium-based desktop browsers. If yours is missing, the site points to the GitHub repo, where you can open an issue to request it. Mobile browsers and smaller forks generally fall outside the dashboard's scope.

Quick way to resolve a mismatch

1. Check your actual Chromium version at chromiumchecker.com.
2. Compare it to the dashboard, remembering that the dashboard may be a day or two ahead during a rollout.
3. If you're on Chrome, consider whether you might be on a partial rollout or an A/B build.
4. If the gap is a major version or more, check whether your browser's vendor backports security fixes before assuming you're unpatched.

Most reported mismatches resolve at step 2 or 3. Only a persistent gap combined with no backporting policy is worth acting on.