Download Fluorite

Plain versioned artifacts, straight from the promotion gate. Every bundle below was built from a pinned upstream stable tag, passed its gates, and landed in the dist tree unchanged.

Next scheduled cycle release

—

42-day cadence from last promotion · security respins land any time they're needed

Release 154.0.8021.1 cycle release

Built from Chromium upstream tag 154.0.8021.1: official release configuration, current patch layer applied, promoted after passing the build gate.

File	What it is
SHA256SUMS	Checksums for everything in this directory - fetch this first
fluorite-154.0.8021.1.tar.xz.00.part	Bundle part 1 of N (24MB chunks)
All parts: `.00.part .01.part .02.part …` - grab every one, then rejoin with a single command (see verify section)

Inside the bundle: the chrome binary plus its runtime files (icudtl.dat, resources.pak, both chrome_100/200_percent.pak, v8_context_snapshot.bin) under fluorite-<version>/.

Browse all files Install guide

Verify & unpack

Download every part for your version into one directory, then:

$ sha256sum -c SHA256SUMS
$ cat fluorite-154.0.8021.1.tar.xz.*.part > fluorite-154.0.8021.1.tar.xz
$ mkdir -p ~/apps/fluorite
$ tar xf fluorite-154.0.8021.1.tar.xz -C ~/apps/fluorite

A checksum you didn't check is decoration, not verification.

Release channels

Cycle releases

A fresh tree at the newest upstream stable tag, every 42 days. The mainline you probably want.

~8–9 per year · scheduled

Security respins

Unscheduled rebuilds when the weekly watcher catches an upstream fix for the pinned milestone. Same version family, patched base.

as needed · exit code 10

Both channel types land here under their exact upstream tag. Announcements go out on the main site's status page.

First run

Keep your profile far away from the extracted tree:

$ mkdir -p ~/.local/share/fluorite/profile
$ ~/apps/fluorite/154.0.8021.1/chrome \
    --user-data-dir=$HOME/.local/share/fluorite/profile

Full walkthrough, including upgrades and desktop launchers, lives in the install guide.

Older versions

Promoted artifacts are kept per version at /releases/<tag>/. The directory name is always exactly the upstream tag it was built from - no decoding required.