What the Colors on the Chromium Drift Dashboard Mean

Updated

The Chromium Drift dashboard uses three colors to show how far each major desktop browser's Chromium version has drifted from Chrome Stable: blue means the browser is on the same Chromium major version as Chrome Stable or ahead of it, yellow means it is one major version behind, and red means it is two or more major versions behind. The colors describe version distance only — they are not a direct security verdict, and a yellow or red browser may still be receiving backported security fixes.

The three statuses

Color Meaning What it tells you
Blue Same Chromium major as Chrome Stable, or ahead The browser is not lagging on major version number
Yellow 1 major version behind A gap worth noting, but not automatically a security problem
Red 2 or more major versions behind The largest version gap the dashboard flags

The reference point is always Chrome Stable, not the newest Chromium major in existence. That distinction matters for how you read the colors.

Why a browser ahead of Chrome Stable still shows blue

Google rolls out each Chrome Stable release gradually, so the version the dashboard reports as stable can briefly lag the newest Chromium major even after that major has shipped. If another Chromium-based browser has already picked up that newer major, it is not behind — so it is shown as up to date (blue) rather than as something ahead of the scale.

In other words, blue is a single bucket for "at parity or ahead," not two separate states.

What the colors do not mean

A yellow or red status does not automatically mean the browser is insecure. Some browsers intentionally track Chromium's Extended Stable channel and backport security fixes from newer releases. Being a major version behind on the version number does not always mean missing security patches.

The dashboard's own framing is that version lag matters because users on an older Chromium version may be exposed to known, already-patched vulnerabilities, and may miss newer Web APIs and features — but that is a general risk statement, not a per-browser guarantee.

Why your own browser may show a different version

If you check your browser and it disagrees with the dashboard, the usual cause is gradual rollout. The dashboard shows the version officially designated as stable, but a new version may not reach all users for a day or two. For Chrome specifically, the dashboard shows the newest release that system administrators can pin, which excludes partial rollouts and A/B test builds.

Two related caveats:

  • Some browsers use their own versioning scheme that does not line up directly with Chromium's version numbers — which is also what makes it hard to know which Chromium version they are based on.
  • You can check your own browser's Chromium version at chromiumchecker.com.

How the data behind the colors is produced

  • Some browsers are fetched live from public APIs on each page load.
  • Others are detected daily via CI by extracting version info from their binaries.
  • Live-fetched browsers therefore update on every page load; CI-detected browsers update once daily via GitHub Actions.

This matters when you see a status that looks stale: a CI-detected browser can be up to a day behind reality.

Practical reading of the dashboard

  1. Treat blue as "no major-version gap to Chrome Stable."
  2. Treat yellow as a one-major gap — check whether that browser backports security fixes before drawing conclusions.
  3. Treat red as the largest gap the dashboard flags, and the strongest prompt to look into that browser's update and backporting policy.
  4. If a status looks wrong for your own browser, recheck after a day or two to account for gradual rollout, then verify locally at chromiumchecker.com.

The dashboard covers major Chromium-based desktop browsers; if one you use is missing, the site points to opening an issue on its GitHub repo.