ChromeOS 132 Release Notes

ChromeOS 132 is the last release with NaCl support for unmanaged/consumer devices, followed by ChromeOS 138 in July 2025 for managed devices⁠.

In 2017, we announced the end of support of Native Client (NaCl)⁠ in favor of WebAssembly⁠. With most developers and users having migrated away from NaCl, we confirm the following NaCl discontinuation dates:

• January 2025: Native Client (NaCl) will be disabled from ChromeOS 132 onwards.
  • For unmanaged and consumer users, ChromeOS 132 will be the last ChromeOS release with support for NaCl.
  • For managed environments (including Kiosk sessions), administrators who manage ChromeOS devices for a business or school, will have the option of extending the ability to use NaCl with a NaCl allow policy (DeviceNativeClientForceAllowed) through the ChromeOS 138 release. This policy will be available in the admin console from late December 2024 to early January 2025 before the release of ChromeOS 132.
• July 2025: ChromeOS 138 will be the last version with NaCl support.
  • For managed environments, ChromeOS 138 is a Long-term Support (LTS)⁠ ChromeOS release available to administrators who manage ChromeOS devices for a business or school.
  • For devices that have been switched to the LTS channel⁠ and have the NaCl allow policy enabled, NaCl will be available until LTS Last Refresh in April 2026.
  • No exceptions will be granted.

For Chrome Apps that use NaCl, migrate to WebAssembly⁠ (WASM). To help you with the transition, we've published the WebAssembly Migration Guide⁠.

For more information about this change or if you need assistance, you can refer to any of the following:

• WebAssembly Migration Guide⁠.
• ChromeOS developer community on Discord.
• ChromeOS release schedule⁠ for release dates and updates.

Please refer to the Chrome Enterprise and Education Help Center to learn more about managing policies for ChromeOS devices⁠.

ChromeOS now features AI-powered face control: you can now use face and gesture tracking to navigate your Chromebook, open apps, and even compose emails – all without a keyboard or mouse. This built-in technology, inspired by Project Gameface⁠, provides greater accessibility for users with motor disabilities and offers a more efficient way for everyone to interact with their devices.

ChromeOS 132 removes the Apps & Games module in the Explore app for devices that have the new App Mall feature.

Chromebook users can now disable their touchpads. This accessibility improvement helps those who rely on screen readers or may experience accidental clicks. To turn it off, go to Settings > Accessibility > Cursor and Touchpad.

The passwordless ChromeOS feature allows users to access their device with PIN or a local password as their primary authentication factor. This means that you will be able to log in to your ChromeOS device with a password you set explicitly for your device, as well as with a PIN no longer tying your gmail password with your device password.

ChromeOS 132 enables biometrics in Password Manager and autofill on Chrome for ChromeOS devices.

There are many different setup items that users may look to change once they've started using their devices, including setting up a printer, connecting Bluetooth devices, changing touchpad direction, etc. This feature consolidates many of these common setup items into a simple task list, with deep linking to where a user can change a particular setting, to simplify the process of completing many of these steps.

As part of a new UI design, ChromeOS now features rounded corners on all app windows on Chromebook Plus devices.

As early as ChromeOS 132, a new Content Transfer tool will guide graduate students or other EDU-managed users who want to migrate their data through the updated Google Takeout Transfer process. This allows them to take their Docs, Sheets, Slides, and Gmail content to a Gmail account of their choice.

This new application allows school administrators to pin an icon to the shelf, notify students and faculty on their Chromebooks, and set dates to trigger these nudges to encourage them to use the existing Takeout Transfer process.

Chrome Remote Desktop (CRD) is a feature that allows for remote control of ChromeOS devices, primarily for troubleshooting purposes, where a device is idle and unused. Admins can now initiate a CRD connection to a ChromeOS device sitting on the login screen. This enables an admin to sign-in to a managed device with their own set of credentials for troubleshooting or testing.

The new DeviceRestrictionSchedule⁠ policy allows ChromeOS administrators to disallow users from logging in to specified Chromebooks during certain hours on specified days of the week. During these hours, kiosk apps are also unavailable.

This feature improves the management disclosure on the device's lock screen. To enhance user understanding before using their device for personal or work, we provide a clear explanation of what managed devices entail. This way, users can make informed decisions regarding their device usage. By providing necessary information, users gain the knowledge needed to make choices that align with their privacy and security concerns and preferences.

For more Chrome browser and ChromeOS updates, check out Chrome Enterprise and Education release notes⁠⁠⁠. To keep up-to-date with the latest ChromeOS.dev news, sign up for the ChromeOS developer newsletter⁠ or join the ChromeOS Discord⁠.