Why the Chromium Team Sunset Lacros on ChromeOS

This article explores the reasons behind the Chromium engineering team's decision to cancel the Lacros project on ChromeOS. Originally designed to decouple the Chrome web browser from the underlying operating system to extend device longevity and speed up browser updates, Lacros was ultimately sunset after years of development. The cancellation stemmed from the introduction of a 10-year automatic update policy that solved the longevity problem differently, the high engineering cost and bugginess of maintaining a split system, and a major strategic shift toward integrating the Android technology stack into ChromeOS.

What Was the Lacros Initiative?

Historically, the Chrome browser and the ChromeOS system interface were combined into a single executable binary. Updating the browser meant updating the entire operating system. Furthermore, once a Chromebook reached its End of Life (now called Automatic Update Expiration), it stopped receiving both OS and browser updates, rendering the device insecure for web browsing.

Lacros—short for Linux and ChromeOS—was an initiative to separate the two. It turned the Chrome browser into an independent Linux application running on top of the ChromeOS system UI. While the concept was sound, several practical and strategic factors led the Chromium team to abandon the project in late 2024.

The 10-Year Update Policy Made Lacros Redundant

The primary motivation for Lacros was to provide indefinitely updated browsers to aging Chromebooks whose hardware could no longer support full OS updates. However, in late 2023, Google announced that it would extend automatic full-system updates for Chromebooks to 10 years.

By committing to update the entire operating system for a full decade—longer than the physical lifespan of most laptops—Google solved the core problem Lacros was meant to fix. Because the OS and browser could continue updating together for 10 years, the urgent need to separate them vanished.

High Engineering Complexity and Technical Debt

Untangling years of deeply integrated code proved to be a massive engineering hurdle. Because ChromeOS was built under the assumption that the browser and the window manager were the same entity, splitting them broke hundreds of basic system functions.

To make Lacros work, the Chromium team had to build complex bridges using the Wayland display protocol. This introduced persistent bugs and regressions in everyday features, including:

  • Screen sharing and video capture.
  • Password manager integration and biometric authentication.
  • Accessibility tools like screen readers.
  • File system access and drag-and-drop functionality.

Maintaining two separate architectures (the legacy combined system and the new Lacros system) required double the testing and slowed down the development of new ChromeOS features.

Performance Overhead on Low-End Hardware

A vast majority of Chromebooks, particularly in the education sector, run on budget processors with limited RAM (often 4GB). Under the traditional ChromeOS model, the system UI and the browser shared the same underlying processes and memory footprint.

With Lacros, the Chromebook had to run one instance of Chromium to power the desktop environment and a second, separate instance of Chromium to run the web browser. This duplication increased RAM consumption and CPU overhead, degrading performance on the entry-level devices that needed optimization the most.

The Pivot to the Android Tech Stack

The final nail in the coffin for Lacros was a major shift in Google's long-term operating system strategy. In June 2024, Google announced that ChromeOS would soon begin adopting large portions of the Android OS stack, specifically the Android Linux kernel and Android system frameworks, to power its foundation.

This initiative, aimed at unifying Google's hardware ecosystems and accelerating AI integration, required a massive reallocation of engineering resources. Continuing to pour time and money into Lacros—a Linux-specific Wayland implementation—no longer aligned with a future where ChromeOS was moving closer to Android's architecture.

By officially ending the Lacros project, the Chromium team eliminated years of accumulating technical debt, restored system performance on low-end devices, and freed up developers to focus on the transition to an Android-backed ChromeOS.