JSON API
Static JSON, no key, no rate limit, CORS-open. Regenerated on the same schedule as the site, so an updater script can poll it directly.
Checked automatically Aug 29, 2026. Latest Chromium stable is 152.0.7977.64.
Endpoints
| Endpoint | Returns |
|---|---|
/api/v1/builds.json | Every tracked build with all downloads, checksums and metadata. |
/api/v1/latest.json | One flat row per build with the preferred download URL. The best endpoint for an updater. |
/api/v1/upstream.json | Current upstream Chromium stable, beta, dev and canary versions with revisions. |
/api/v1/windows.json | Windows builds only. |
/api/v1/macos.json | macOS builds only. |
/api/v1/linux.json | Linux builds only. |
/api/v1/android.json | Android builds only. |
/api/v1/distros.json | Chromium version currently packaged by each Linux distribution. |
Example
# newest Windows x64 build that is level with upstream stable
curl -s https://chromiumbuilds.org/api/v1/windows.json \
| jq -r '.builds[] | select(.arch[0]=="x64" and .freshness=="current")
| "\(.name) \(.version) \(.downloads[0].url)"'
Field notes
freshnessis derived by comparing the build's milestone against upstream stable:current,behind(one milestone),outdated(two or more), orabandoned(nothing published in a year).sha256comes from the release host itself, not computed here.googleis one ofsync,nosync,ungoogledorraw.- Download URLs point at the maintainer's release host. Nothing is proxied through this site.
Using it
Please poll no more than hourly; the data only changes when a maintainer publishes. If you are
replacing a dead update endpoint in an existing tool, latest.json is the closest shape.
The generator is open source, so you can also just run it yourself.