Google puts ChromeOS updates through 2034 in writing for admins preparing for Googlebook hardware

A school IT admin planning a refresh has a spreadsheet of serial numbers and two columns to fill. One is the date each Chromebook stops getting ChromeOS updates. The page says those updates continue through 2034 ^[1]. The other column asks whether the device can move to Googlebook OS, and the page's answer is "many of our newest Chromebook devices" ^[2].

Chrome Unboxed wrote that the 2034 figure caught some readers by surprise ^[5]. A team that writes 2034 at the top of the spreadsheet is using the newest hardware's date for the whole fleet. That year applies to Chromebooks built on 2024 development boards ^[9]. Under the same 2023 promise, a model launched in 2021 gets updates to about 2031 ^[13]. A fleet bought between 2021 and 2024 therefore has cutoffs spread over roughly three years ^[14].

Google's own wording ties support to each device. In a May statement to Chrome Unboxed, a Google ChromeOS executive said that "all Chromebooks will continue to receive support through their device's existing date commitment, and many Chromebooks will be eligible to transition to the new experience. We'll share more details closer to launch." ^[10] The site's text credits the statement to Charles Lee, while the line beneath the quote names Bryan Lee, VP of ChromeOS Enterprise Go-to-Market ^[15]. Chrome Unboxed says the new enterprise page repeats the statement almost word for word ^[11].

Chrome Unboxed describes the pitch as "a software bridge for capable existing hardware" ^[7]. So far, what Google has actually shipped is a support page whose eligibility language, as the site quotes it, is one sentence ^[2]. In January, Google's VP of ChromeOS John Maletis told Chrome Unboxed an upgrade path for capable hardware was in development, and that Google wanted to allow migrations wherever possible with "product truth," the site reported ^[12].

I'd plan refreshes on each device's own update date and leave Googlebook OS out of the budget until Google publishes a model list. The cost is that some units retired on schedule may later turn out to have qualified. To sort a fleet, place each model on two lines. The first is whether its ChromeOS update date falls before or after the next planned refresh. The second is whether it appears on a published eligibility list, and for now every model is on the unlisted side ^[3].

A model that is unlisted and ends before the refresh gets replaced on schedule. An unlisted model that ends after the refresh stays on ChromeOS, and the migration question waits for the list. A listed model that ends after the refresh is the right place to pilot a migration. A listed model that ends before it can be tested on Googlebook OS. Its replacement still belongs in the budget, because Google ties support to each device's existing date commitment ^[10].