简体中文
EnglishWebsite review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Chromium Drift?
Chromium Drift is a dashboard that tracks which Chromium version each major desktop browser is currently shipping. It answers a narrow but practical question: is the browser you're using based on the same Chromium major version as Chrome Stable, one major behind, or two or more behind?
The page encodes that gap as a traffic-light system. Blue means the browser matches Chrome Stable's Chromium major or is ahead of it. Yellow means one major version behind. Red means two or more major versions behind. The stated reason this matters is twofold: an older Chromium base can leave users exposed to known vulnerabilities that have already been patched upstream, and it can miss newer Web APIs and features, which shows up as website compatibility problems.
How to read it without over-reading it
The dashboard is a signal, not a verdict. Its own FAQ makes the key caveat explicit: being a major version behind Chrome Stable does not automatically mean a browser is insecure. Some browsers deliberately track Chromium's Extended Stable channel and backport security fixes from newer releases, so the version number alone can understate how current their patches are.
Two other nuances are worth keeping in mind:
- Rollout lag. Chrome Stable ships gradually, so the version shown here can briefly trail the newest Chromium major even after that major has shipped. A rival browser that has already picked up the newer major isn't "ahead" in any meaningful sense; it's shown as up to date.
- Versioning schemes. Some browsers use their own numbering that doesn't line up directly with Chromium's, which is part of what makes their true Chromium base hard to pin down.
Who it's useful for
- Web developers deciding whether a feature or API is safe to rely on across the major desktop browsers.
- IT and security staff who want a quick read on which browsers in a fleet are trailing the current Chromium major.
- Curious users who want to know how their browser's engine compares to Chrome's.
A useful next step
If you want to know where your own browser sits, check its Chromium version and compare it against the dashboard's current Chrome Stable figure. The page points to Chromium Checker for that lookup. If your browser shows yellow or red, the sensible follow-up isn't panic but a check of whether that vendor publishes its own security patch notes — a one-major gap with active backporting is a very different situation from a two-major gap with no updates at all.
How can I check which Chromium version my own browser is running?
Open your browser's own About or version page first; that is the fastest check and needs no third-party tool.
Check your browser directly
- Chrome: open the three-dot menu → Help → About Google Chrome. The version number appears there, and the page also triggers an update check.
- Edge: three-dot menu → Help and feedback → About Microsoft Edge.
- Brave, Opera, Vivaldi and similar: look for About in the main menu; most Chromium-based browsers put the full version string there.
- Any browser: type
chrome://versionin the address bar. This works in most Chromium-based browsers and shows both the browser version and the underlying Chromium version.
The number you want is the Chromium version, not just the brand version. Some browsers use their own numbering scheme, which can make it hard to tell which Chromium release they are based on. On chrome://version, the Chromium line gives you the direct answer.
Chromium Drift tracks which Chromium version each major desktop browser is currently shipping, so you can compare your result against the current stable baseline. It also flags how far behind a browser is: blue means the same major version as Chrome Stable or ahead, yellow means one major version behind, and red means two or more behind.
Reading the result sensibly
A gap is a prompt to investigate, not proof of a problem. Browsers roll out updates gradually, so your installed version can lag the dashboard by a day or two even when an update is already rolling out. Some browsers also deliberately track Chromium's Extended Stable channel and backport security fixes, so being a major version behind on the number does not automatically mean missing patches.
If your browser is a major version or more behind, open its About page and let it update, then restart. If it still will not move, check whether your operating system or your organisation's device management is holding updates back.
Why does my browser show a different Chromium version than the Chromium Drift dashboard?
Version mismatches are usually expected, not a sign that the dashboard is wrong or that your browser is unsafe. Chromium Drift tracks the version officially designated as stable, while your own browser may be mid-rollout, pinned to an older release, or using its own version numbering scheme.
Common reasons for the difference
- Gradual rollouts. Browsers push updates to users over a day or two. The dashboard may show a newer stable version than the one your browser has actually received.
- Admin pinning (Chrome especially). Chromium Drift shows the newest release system administrators can pin, which deliberately excludes partial rollouts and A/B test builds.
- Different versioning schemes. Some Chromium-based browsers number their releases independently, so their version string doesn't line up with Chromium's major version at all.
- Update timing. Live-fetched browsers refresh on every page load, but other browsers are detected once daily, so a very recent release may not appear yet.
What to do next
Check your own browser's Chromium version directly, then compare it with what the dashboard lists. If they differ by a major version or more, look at the browser's release notes before assuming anything is wrong — the gap may be intentional.
Reading the gap correctly
A one- or two-major-version lag is not automatically a security problem. Some browsers intentionally follow Chromium's Extended Stable channel and backport security fixes rather than jumping to each new major. The dashboard's color coding reflects version distance, not patch status:
| Color | Meaning |
|---|---|
| Blue | Same major version as Chrome Stable, or ahead |
| Yellow | One major version behind |
| Red | Two or more major versions behind |
So a yellow or red entry is a prompt to investigate, not a verdict. For a practical example: if you manage a fleet of work machines and the dashboard shows your browser two majors behind, confirm whether your vendor backports fixes before escalating. If you're an individual user and your browser is one major behind, waiting a day or two for the rollout to reach you is usually the simplest step.
Does being a major Chromium version behind Chrome Stable mean my browser is insecure?
No — a major version gap alone doesn't prove your browser is insecure. It's a warning sign worth investigating, not a verdict.
What the gap actually tells you
A browser one Chromium major behind Chrome Stable is missing the newest upstream code. Whether that matters depends on how the vendor handles security fixes. Some browsers deliberately track Chromium's Extended Stable channel and backport security patches from newer releases onto an older base. In that setup, the version number stays behind while the known vulnerabilities still get fixed. Chromium Drift makes this distinction explicitly: being a major version behind "does not always mean missing security patches."
So the version number answers "how current is the engine base?" — not "are my patches current?"
How to tell the difference
| Signal | Reassuring | Concerning |
|---|---|---|
| Vendor's update notes | Cite backported security fixes | Only mention features or UI |
| Patch cadence | Frequent small releases | Long gaps, no security entries |
| Extended Stable support | Stated openly | Not mentioned at all |
| Gap size | One major version | Two or more, and growing |
A browser two or more majors behind is harder to defend, because backporting becomes more work and vendors rarely keep it up indefinitely.
A practical check
Open your browser's about page, note the version, then compare it against the dashboard. If it sits one major behind, look at the vendor's release notes for the last month and search for security-related entries. If you find backported fixes, the lag is likely a deliberate trade-off for stability. If you find nothing, treat the browser as unpatched and switch to a browser that tracks Chromium closely — Chrome or Edge — until the vendor ships an update.
To read your own engine version directly, use Chromium Checker, referenced by Chromium Drift for exactly this purpose. Vendors with their own versioning schemes (common among regional and privacy-focused browsers) can be hard to map to Chromium numbers, so check the vendor's own release notes when the dashboard leaves you guessing.
How often does Chromium Drift update its version data?
Live-fetched browsers update on every page load, while CI-detected browsers update once daily via GitHub Actions. That split is the short answer from the site itself.
What that means in practice
- Live-fetched browsers reflect whatever their public API reports at the moment you open the page. If a vendor publishes a new stable version mid-day, the dashboard can show it almost immediately.
- CI-detected browsers are checked once a day by extracting version info from their binaries. A fresh release may not appear until the next scheduled run.
- The dashboard shows the version officially designated as stable, not every partial rollout. Chrome Stable in particular is listed as the newest release system administrators can pin, excluding partial rollouts and A/B test builds.
A quick decision rule
- If you are checking whether a just-announced update has landed, treat a daily-updated row as potentially one day stale and verify in the browser itself.
- If you are comparing long-term drift across browsers, the daily cadence is more than enough; the meaningful signal is major-version lag, not same-day timing.
- If a browser shows a different version than the dashboard, that is usually gradual rollout, not an error.
For a hands-on check of your own browser, the site points to a separate version checker; otherwise, the fastest next step is to reload the dashboard and compare the color coding: blue for same major as Chrome Stable or ahead, yellow for one major behind, red for two or more behind.
How can I request that a browser be added to the Chromium Drift dashboard?
The dashboard points you to its GitHub repository: open an issue there requesting the browser you want covered. That is the route the site itself names in its "Why isn't my browser listed?" FAQ, which says the dashboard covers major Chromium-based desktop browsers and invites issue requests for additions.
What to put in the request
Make it easy for the maintainer to act on:
- Browser name and vendor, plus a link to its official site.
- Desktop platforms it ships on (Windows, macOS, Linux), since the dashboard is scoped to desktop browsers.
- Where version information is publicly available — a release-notes page, an API endpoint, or a public build/download listing. The dashboard detects versions either by fetching public APIs on each page load or by extracting version data from binaries in daily CI runs, so a machine-readable source is the most useful thing you can supply.
- The Chromium base version, if the vendor publishes it. Some browsers use their own versioning scheme that doesn't line up with Chromium's numbers, which the site notes is what makes their Chromium base hard to determine.
- Why it belongs on the list — for example, a meaningful desktop user base or a history of lagging behind Chromium stable.
A practical scenario
Suppose you use a smaller Chromium-based desktop browser at work and want to know whether it's one or two majors behind Chrome Stable. Before filing, spend five minutes checking whether the vendor publishes a version page or a public release API. If it does, say so explicitly in the issue and include the URL; that single detail often decides whether a request is feasible. If the vendor only ships opaque auto-updates with no public version data, mention that too — it may explain why the browser isn't tracked yet, and the maintainer can tell you whether binary extraction is realistic.
For context on how the dashboard handles this once a browser is added, see Chromium Drift, and for checking your own browser's Chromium version, the site points to chromiumchecker.com.
Cloudflare
User reviews (0)