the Chromium logo

The Chromium Projects

Version Numbers


Chromium version numbers consist of 4 parts: MAJOR.MINOR.BUILD.PATCH.

MAJOR and MINOR track updates to the Google Chrome stable channel. In this sense, they reflect a scheduling or marketing decision rather than anything about the code itself. These numbers are generally only significant for tracking milestones. In the event that we get a significant release vehicle for Chromium code other than Google Chrome, we can revisit the versioning scheme.

The BUILD and PATCH numbers together are the canonical representation of what code is in a given release. The BUILD number is always increasing as the source code trunk advances, so build 180 is always newer code than build 177. The PATCH number is always increasing for a given BUILD. Developers and testers generally refer to an instance of the product (Chromium or Google Chrome) as BUILD.PATCH. It is the shortest unambiguous name for a build.

For example, the 154 branch was originally released as, but now stands at It's the same basic code with a lot of bug fixes applied. The fact that it went from a Beta release to several 1.0 stable releases just reflects the decision to call some version ( 'out of Beta'.

Chromium OS

Starting with the R16 release, we standardized on the following: [Chrome Version.]<TIP_BUILD>.<BRANCH_BUILD>.<BRANCH_BRANCH_BUILD>

An example Chromium OS version string:

Coordinating Versions

Chromium & Chromium OS

All releases of Chromium OS are tagged in the chromiumos/manifest-versions.git repository. You can look up a Chromium version by doing:

Chrome & Chrome OS

You can use the online CrOS-OmahaProxy app engine to see what versions of Chrome shipped in which versions of Chrome OS.

Alternatively, all releases of Chrome are tagged in the chromeos/manifest-versions.git repository. Follow the same steps as above w/Chromium.