
Google Chrome now runs natively on ARM64 Linux. That’s good news for anyone using a Raspberry Pi 5, an ARM-based laptop or a compact Linux workstation. There’s just one catch. Google hasn’t made the new version especially easy to find. The software is available, the update system works and the packages are ready, but the regular Chrome download page may still point Linux users towards the standard AMD64 version. So yes, Chrome for ARM64 Linux has arrived. You might simply have to look a little harder for it.
Chrome now runs without emulation
Until now, ARM Linux users usually relied on Chromium. It uses the same basic browser engine as Chrome, and for everyday browsing it works perfectly well. But the two browsers aren’t identical. Chrome includes Google’s account syncing, its own media components and Google-managed software packages. That matters when you want your bookmarks, passwords, browser history, extensions and settings to appear automatically across several computers.
The new ARM64 release brings that full Chrome setup to 64-bit ARM machines. It also runs directly on the processor. There’s no need to translate software built for Intel or AMD chips, and there’s no x86 compatibility layer sitting in the middle. That should reduce installation headaches and avoid some of the performance issues that come with emulation. It’s simply a cleaner setup.
Raspberry Pi users get a proper Chrome build
The Raspberry Pi is probably the most obvious winner here. Newer Pi models have enough power and memory to work as everyday desktop computers. People use them for web browsing, office work, development, media playback and lightweight server tasks. Browser support, however, hasn’t always kept pace with the hardware.
Chromium has filled the gap for years, but some people need Chrome itself. They may depend on Google account syncing, specific extensions or websites that behave differently when they detect Chromium. Now they have an official option.
Users running a 64-bit Raspberry Pi operating system can install the ARM64 version of Chrome using a normal Linux package. Debian-based systems get a DEB file, while distributions built around RPM packages receive an AArch64 RPM version. That’s far better than relying on repackaged files or unofficial fixes.
Widevine support makes streaming easier
One of the biggest improvements sits behind the scenes. Chrome for ARM64 Linux includes native support for Widevine, Google’s system for playing protected video. Many paid streaming platforms and online media services use it to control access to films, series and other licensed content.
Widevine has often been awkward on ARM Linux. Users have had to copy files from other devices, install unofficial packages or follow long guides that could stop working after an update. The new Chrome package includes an ARM64-compatible Widevine component. That should make protected video playback much easier to set up. Don’t expect every streaming service to offer 4K, though.
On Linux, Widevine usually runs with software-based security rather than the stronger hardware protection found on some TVs, phones and streaming boxes. Because of that, certain services may limit playback to 720p or 1080p. Still, the main problem was getting reliable playback at all. Chrome’s native support should help with that.
Updates work through the normal Linux system
This isn’t just a browser file you’ll need to replace manually every few weeks. When you install the official package, Chrome adds Google’s software repository to the system. Future versions can then arrive through the Linux package manager, alongside other system updates. That’s essential for a browser.
Chrome receives frequent security fixes, and nobody wants to keep checking a download page for every new release. Automatic updates mean ARM64 users should get patches in much the same way as people running Chrome on a standard Intel or AMD Linux computer.
Google has also released ARM64 versions across several Chrome channels, including stable, beta, developer and Canary builds. That suggests this isn’t a small experiment. ARM64 Linux now appears to be part of Chrome’s regular release process.
The launch still feels a little unfinished
The browser may be ready, but the rollout isn’t especially polished. Google previously said Chrome would come to ARM64 Linux during the second quarter of 2026. The actual packages appeared later, and they arrived without the kind of clear public launch you’d expect from such a widely used browser. The biggest issue is the download page.
It doesn’t always detect ARM64 Linux correctly, so users may still see the wrong installer. Unless you already know which package you need, it’s easy to assume Chrome isn’t available for your machine.
That should improve as Google updates its download tools and documentation. For now, users should double-check the processor architecture before installing anything. It’s also sensible to keep Chromium or another browser installed as a backup, especially on a machine used for work.
A small release with a big practical impact
Chrome on ARM64 Linux won’t change how the browser looks or feels. It doesn’t introduce a new interface, and it won’t suddenly make every Raspberry Pi twice as fast. What it does is remove friction.
ARM Linux users now have an official Chrome build, native Widevine support, automatic updates and access to Google’s full browser ecosystem. They no longer need to rely on emulation or unofficial packages just to get the standard Chrome experience. The technology is ready. Now Google just needs to make the download button easier to find.














