Barely a week after ChromeOS 150 finished rolling out to most Chromebooks, Google has already pushed the next version into testing. ChromeOS 151 landed on the Beta channel on July 23, 2026, which means people who opted into early builds get the first look, while everyone else keeps running what they already have.
What actually moved this week
Google shuffled a handful of release channels within days of each other. The Chrome browser itself, on Windows, Mac, and Android, is already cycling through early stable builds of version 151. ChromeOS, the operating system running on your Chromebook, is a step behind that: it only reached the Beta channel with this update, carrying platform version 16733.26.0 and browser version 151.0.7922.42.
That gap between Chrome the browser and ChromeOS the platform is normal. Chromebooks bundle the browser with a full operating system, kernel updates, and hardware drivers, so ChromeOS testing tends to run a cycle or so behind the standalone Chrome browser on Windows and Mac. Nothing about that gap is a bug; it’s just a wider net catching more before an update reaches millions of laptops in classrooms and living rooms.
Alongside the Beta bump, Google also pushed a refreshed Long Term Support build, version 150.0.7871.150, out to devices enrolled in that program. That’s a separate track from the LTS-144 anchor most schools and businesses are actually sitting on, and Google has confirmed LTS-144 remains the default enterprise anchor until October 6, 2026.
Why the slow rollout is the point, not a delay
It’s tempting to read a Beta-only release as Google dragging its feet, but the staged rollout is deliberate. Stable channel changes reach the largest number of devices, so any regression there gets amplified fast. Beta and Dev channels exist specifically to catch the kind of bug that only shows up once real people with real workflows start using a build, whether that’s a Wi-Fi driver quirk on a specific chipset or a rendering glitch in an obscure web app.
For IT admins managing school or office fleets, the LTS anchor serves the same purpose at a slower pace. Locking a large deployment to LTS-144 through early October means fewer surprise reboots and fewer help desk tickets during the part of the year, like the run-up to a new school term, when nobody wants unpredictable software.
If you want the fuller breakdown of what separates Stable, Beta, Dev, and LTS on a Chromebook, we cover the mechanics in our guide to ChromeOS update channels.
What Chromebook owners should do
For almost everyone, the answer is nothing. If you’re on the default Stable channel, you’re still running ChromeOS 150 (or possibly 149, depending on when your device last checked in), and 151 will arrive through the normal automatic update process once it clears Beta and, eventually, Stable testing. You can check your current version any time under Settings, About ChromeOS.
If your Chromebook seems stuck on an older version longer than expected, our guide on how to update ChromeOS manually walks through forcing a check and what to do if the download hangs. And if you’re curious enough to try Beta builds yourself, know that you’re trading a small chance of bugs for early access; switching back to Stable later usually means a Powerwash, so it’s worth reading how automatic updates work on Chromebooks before you opt in.
Schools and businesses running managed fleets on LTS-144 don’t need to do anything before October, which was likely the whole point of setting the date that far out. The bigger item on their radar should still be the Kiosk mode Chrome Apps cutoff that arrived with ChromeOS 150, since that deadline lands with the version Google is currently testing in Beta.
LOG 1 report