Chromium OS on Raspberry Pi is a board overlay, not an operating system

What is in the repository: four overlay directories and a document

The top-level entries include baseboard-rpi3/, chipset-bcm2837/, overlay-rpi4/ and overlay-rpi5-vanilla/, plus project-cros-pi/. Alongside them sit README.md, LICENSE, CHANGELOG.md and.github/.

This is the shape of a Chromium OS board port. Chromium OS separates the generic operating system from the hardware description, and a port supplies the latter: a baseboard file naming the board, a chipset directory for the SoC, and an overlay holding the device tree, firmware blobs and configuration. Because the operating system itself comes from upstream Chromium, none of that code lives here.

The chipset directory is named for bcm2837, which is the Broadcom chip in the Pi 3 and Pi 4 era. The presence of an rpi5-vanilla overlay alongside it shows the port has been extended to the Pi 5 without renaming the older chipset directory, and the word vanilla in that name suggests a minimal variant rather than a fully tuned one.

The primary language of the repository is Shell, which fits: the deliverable is a set of build and setup steps plus configuration, not a large codebase. The README describes how to get the Chromium OS source code, set up the Raspberry Pi overlay, set up local Chromium source, build, and boot from the image, and that sequence is the whole workflow.

The three products with similar names, and which one this is

The README opens with a FAQ because the naming is genuinely confusing, and the confusion is not the author's fault. It identifies four distinct things.

Chromium OS is the open-source project, used primarily by developers, with code anyone can check out, modify and build. Google Chrome OS is the Google product OEMs ship on Chromebooks for consumers. openFyde is a downstream fork of Chromium OS with modifications and enhancements from Fyde Innovations, under a similar series of relaxed licences to the upstream. FydeOS is the commercial-grade product from the same company, built on openFyde and Chromium OS.

This project is only the first of those. The README states it aims to ship only vanilla Chromium OS developed by Google and the Chromium Authors, ported to the Raspberry Pi, and explicitly not FydeOS for You for the Pi 400 and not openFyde.

Even the naming convention differs: Chrome OS has a green, yellow and red logo, Chromium OS a blue one, openFyde a circular mark and FydeOS a wordmark. So if you find a Raspberry Pi Chromium OS image and the branding is not blue, it is not from here.

What you give up by building from source, stated as a list

The README enumerates the differences that follow from the firmware gap, and they are worth reading as a feature matrix against the commercial products.

Google Chrome OS has additional firmware features, including verified boot and easy recovery, which require corresponding hardware changes and therefore do not work out of the box in Chromium OS builds. That is a hardware statement, not a software one, and no amount of building will fix it on a Raspberry Pi.

Chrome OS and FydeOS run on specially optimised hardware for enhanced performance and security. The Raspberry Pi is not that hardware.

Chromium OS and openFyde images do not auto-update by default, so that changes you have made are not blown away, whereas Chrome OS and FydeOS update seamlessly. The reason given is protective, but the practical consequence is that you own the update path entirely.

Chrome OS and FydeOS include proprietary, commercial or licensed packages which are not in the Chromium OS project. As a direct consequence, Chrome OS and FydeOS support the Android subsystem while Chromium OS and openFyde do not.

That last one is the dealbreaker for many buyers. If the goal is Android apps on a cheap board, this project cannot deliver them, by design rather than by omission.

Hardware support, and why the Pi 3 was dropped

The supported hardware is named in the introduction: Raspberry Pi 4B, the Pi 400 personal computer kit and the latest Raspberry Pi 5. Earlier models such as the Pi 3B and 3B+ were supported in earlier releases and were dropped because of hardware performance limitations. The README states it will not work on an earlier version of the Raspberry Pi line-up.

That drop is the clearest signal about what this port is and is not. Chromium OS assumes a machine with fast storage, adequate memory bandwidth and a display pipeline comparable to a Chromebook. A Pi 3 does not have it, and the port team concluded that shipping a build which technically runs but is unusable helps nobody.

The overlays and document were tested against the Pi 3B, 3B+, 4B and Pi 400 by the FydeOS team, which is the historical range of what has been verified rather than what is currently supported.

Note the difference between building an image and writing a new overlay. Supporting the Pi 5 required a new overlay directory, not a change to the operating system, which is the clearest illustration of why board ports are separate repositories at all.

Where to actually get an image, and where to report what

There is no install command in this repository, and the reason is that the artefact is a disk image rather than a package.

For a pre-built image, the README directs you to the releases tab of the repository, where all historical releases are listed along with release notes, and it asks twice, once in the FAQ and once inline, that you read the release notes. That emphasis is a warning in practice: the releases are Chromium milestone images, and what you get depends entirely on which milestone the tag names.

For FydeOS for You on the Pi 400, the download page is on the FydeOS official site, which is a different product.

The support routing is spelled out just as precisely. An issue opened here will be taken seriously if you have read the developer guide and the build demonstration video and still hit a problem building, or if you believe your copy of Chromium OS for Raspberry Pi is not functioning correctly.

Issues will likely be closed if you are asking about FydeOS for You, which belongs on the FydeOS community forum or their Telegram group, if you are reporting a generic Chromium OS or Chrome OS bug, which belongs in the chromium-os-dev Google group or on CRBUGS, or if you are asking about a third-party app, a non-standard peripheral or a one-off setup.

Release cadence and what a stale milestone means

Here is the maintenance picture, and it is the thing to weigh most carefully.

The repository is not archived and the last push was on 2026-04-21. The recent releases, however, are r114-r1 on 2024-01-24, r114 on 2023-12-21 and r108 on 2023-02-08. The naming is a Chromium milestone number, so the newest published image is built from Chromium 114.

That gap between a recent commit and an old tag is normal for this kind of project: the board overlay and build scripts can be maintained, upstreamed, or adjusted for newer toolchains, without a new image being cut and published. It also means the newest downloadable build is from a Chromium version that is now well behind current upstream, and the browser on it will carry whatever security posture that milestone had.

CHANGELOG.md exists at the root, so the history of changes is recorded even where the release tags are old.

Licence is BSD-2-Clause with LICENSE at the root, which is the usual licence for board overlay files copied out of the Chromium tree and is permissive enough for commercial hardware work without copyleft.

Where an official Linux distro or FydeOS fits better

The alternatives divide cleanly by what you are optimising for.

If you want a usable browser-based appliance on a Raspberry Pi, a mainstream Linux distribution with a kiosk browser is the honest answer. You get current browsers, an update path that works, and no build. You lose the Chrome OS interface, the overlay approach and any ability to contribute board support upstream. For a digital signage screen or a kitchen dashboard, that trade is usually correct.

If you want a FydeOS image instead, use FydeOS. It is the commercial product from the same team, built on openFyde and Chromium OS, and per the README it auto-updates, includes the licensed packages, runs on optimised hardware and supports the Android subsystem. None of those hold for a Raspberry Pi build from this repository, which is exactly why the two are separate downloads.

If you want to contribute board support to Chromium OS itself, this is the only route described here. openFyde is the fork to build if you want modifications and enhancements layered on top, with its own project website.

The boundary is simple: build this if you need to read or change Chromium OS on ARM, and use anything else if you need a device that works.

Editorial conclusion

The project fits a developer who wants to read, patch and rebuild Chromium OS against ARM hardware and ship their own board support, and who is prepared to handle a build that takes hours and an image that does not update itself. It does not fit someone who wants a working Chromebook, because verified boot, easy recovery and the Android subsystem are absent by construction. Before downloading a pre-built image, read the release notes as the README insists, check that the tag you are getting corresponds to a Chromium milestone your browser expectations match, and confirm your board is a 4B, Pi 400 or Pi 5 since earlier models were dropped.

Frequently asked questions

Official sources

1. FydeOS/chromium_os-raspberry_pi on GitHub
2. License: BSD-2-Clause
3. Project website
4. README
5. Releases