Chrome lands on arm64
In this article
Chrome now has official arm64 Linux builds. Shipped by the Chrome team on 30 July 2026.
I filed the original issue requesting arm64 for Chrome back in October 2024, and also put an industry call out for people share & star the issue on Bluesky, Mastodon, and a Chrome for Testing GitHub issue.
It was widely supported, and Google responded that they were working on it. The first arm64 builds shipped at the end of July 2026, and the Chrome team has committed to maintaining them going forward.
Chrome arm64 is a great outcome for anyone wanting to run Chrome on more efficient hardware, and we’re one of them.
Why arm64 Chrome matters#
Calibre runs synthetic monitoring on top of Chrome. Our Test Agents run a recent version of Chrome, on a schedule, for every page our customers monitor. Our autoscaling fleet runs up to thousands of concurrent Chrome instances at any given time, and we’re always looking for ways to make that fleet more efficient.
That makes the machine that runs Chrome one of our biggest factors for energy consumption, and the emissions that come with it. Here’s how I put it in the original request:
Alongside the rise of Chrome headless, arm64 based architecture has taken several steps forward in terms of efficiency and availability among cloud vendors. In a nutshell, Arm64 CPUs: require less power, produce less heat, less carbon emissions and do so at a lower operational cost.
AWS says its Graviton3 instances use up to 60% less energy for the same performance than comparable EC2 instances, and that Graviton costs up to 20% less than comparable x86. At scale, that’s a big deal. We run thousands of Chrome instances at any given time, and we’re happy to move them to more cooler, cheaper and slightly faster hardware.
If you run automated Chrome for CI/CD, testing or monitoring, then arm64 builds are good news for you too. You can run the same tests, and save money while you’re at it.
Where to get it#
Head to the Chrome download page and pick the arm64 .deb or .rpm.
The direct download link appeared as well:
https://dl.google.com/linux/direct/google-chrome-stable_current_arm64.debGoogle’s apt and RPM repositories carry arm64 across every channel, so once it’s installed it updates like anything else.
Chrome for Testing has arm64 too#
The build I was most looking forward to is Chrome for Testing, which became our chosen solution for managing chrome versions. It landed on 11 August 2026, supported from 153.0.8001.0, with chromedriver and chrome-headless-shell alongside it.
Chrome for Testing is where a lot of browser automation gets its Chrome. Puppeteer downloads from the Chrome for Testing bucket, and Selenium Manager resolves Chrome and chromedriver through it.
@puppeteer/browsers is fetched almost 100 million times a month.
By moving your automation work to arm64, you may be able to save energy and money without changing a line of code.
When this was published in August 2026, arm64 builds were Canary only. As of September 2026, Chrome for Testing publishes linux-arm64 on Stable, Beta, Dev and Canary.
arm64 is already running in our pre-release Test Agent fleet. Once we’ve observed it long enough to right-size for the new architecture, it’ll join our production fleet alongside others.
Chrome arm64 will enable Chrome automation to run on more efficient hardware, a net-win for energy usage, and the budget that pays for it.
To the Chrome engineers who built the arm64 release, and who’ll keep it maintained from here: thank you. And to the 176 of you who starred the issue, thank you too. Your support helped get the wheels turning.