Chrome 152 beta

Published: July 30, 2026

Unless otherwise noted, the following changes apply to the newest Chrome beta channel release for Android, ChromeOS, Linux, macOS, and Windows. Learn more about these features by using the provided links or by visiting ChromeStatus.com. Chrome 152 is in beta as of this release. You can download the latest beta version from Google.com for desktop or from Google Play Store on Android.

CSS and UI

CSSPseudoElement support for ::backdrop, ::scroll-marker, and ::view-transition

Support for CSSPseudoElement, previously defined for ::after, ::before, and ::marker, extends to include several new pseudo-elements:

  • ::backdrop: Helps close a dialog when the backdrop is clicked without interfering with clicks inside the dialog content, eliminating the need for complex intersection logic.
  • ::scroll-marker: Used to collect click statistics.
  • ::view-transition: Supports geometry-aware view transitions and intercepting a view transition mid-flight to start a new one, using the coordinates of the currently animating element to avoid visual jumps.

Expose the autocorrect global HTML attribute

The HTML autocorrect attribute lets web authors control whether autocorrection should be applied to user input in editable elements including <input>, <textarea>, and contenteditable hosts. This feature exposes the autocorrect global HTML attribute to web developers.

Media element pseudo-classes

The :playing, :paused, :seeking, :buffering, :stalled, :muted, and :volume-locked CSS pseudo-classes match <audio> and <video> elements based on their current state. These pseudo-classes are one of the focus areas for Interop 2026.

Relative alpha colors (CSS Color 5 alpha() function)

Relative alpha colors reference an origin color and modify only the alpha channel, letting developers set transparency relative to an existing color value.

window-drag CSS property

The window-drag CSS property lets web content designate regions of an installed desktop web app UI that should behave as draggable window titlebar areas. When applied, user pointer interactions such as click-and-drag on that region move the top-level application window rather than triggering normal page interaction.

This feature standardizes and renames the existing app-region CSS property, changes its value names to move and none, and adds explicit inheritance behavior.

Web APIs

CPU Performance API

Starting in Chrome 152, Chrome introduces the CPU Performance API, which lets web applications determine the CPU performance tier of a user's device. Web applications can use this information to provide an improved user experience, optionally in combination with the Compute Pressure API to react to changes in CPU pressure.

Users can override the reported performance in Chrome's Performance settings. Administrators can also control this behavior using the CpuPerformanceTierOverride enterprise policy.

For more details, see the CPU Performance API Explainer.

Connection Allowlists

Connection Allowlists provides explicit control over external endpoints by restricting connections initiated through the Fetch API or other web platform APIs from a document or worker.

Servers distribute an authorized endpoint list through an HTTP response header. Prior to establishing any connection, Chrome evaluates the destination against this allowlist; connections to verified endpoints are permitted, while those failing to match are blocked.

For more details, see the Connection Allowlists proposal.

Notification attribution for PWAs on macOS

Chrome is rolling out notification attribution for installed Progressive Web Apps (PWAs) on macOS. When a PWA is installed on macOS, its notifications are natively attributed to the PWA itself, using its own name and icon in Notification Center, rather than Google Chrome.

This update aligns PWA notifications with native macOS applications:

  • Chrome no longer supports the requireInteraction field for PWA notifications on macOS because notification persistence is controlled per-app by macOS settings.
  • The Badging API requires notification permissions for the app badge to display.

Administrators pre-granting permissions through policies should note that along with NotificationsAllowedForUrls, a macOS MDM configuration profile is needed to pre-grant permissions for the PWA's specific bundle ID.

OpaqueRange

OpaqueRange represents a live span of text within a form control's value, such as a <textarea> or text-based <input>, so developers can work with value text using range-like APIs.

It supports operations such as getBoundingClientRect(), getClientRects(), and integration with the CSS Custom Highlight API for inline suggestions, highlights, and anchored popovers. It preserves encapsulation by exposing only value offsets while returning null for startContainer and endContainer.

Isolated Web Apps (IWA) Sub apps

Sub apps let developers create multiple apps under a single Isolated Web App (IWA) installation. Each sub app has its own distinct name, icons, and OS integrations.

Sub apps appear on the desktop shelf with a distinct identity from the parent IWA, offering separate OS capabilities such as file type association. Administrators can control this feature using enterprise policies including DefaultSubAppsWithoutPromptsSetting, SubAppsWithoutPromptsAllowedForOrigins, and SubAppsWithoutPromptsBlockedForOrigins.

Unframed display mode for Isolated Web Apps

Unframed display mode lets Isolated Web Apps occupy the entire browser window by removing standard window borders and title bars, supporting custom branding and menu hierarchies.

Administrators can manage this feature using policies including DefaultWindowManagementSetting, WindowManagementAllowedForUrls, and WindowManagementBlockedForUrls.

WebGPU: Subgroup Size Control

Adds the optional GPU feature "subgroup-size-control" that lets developers explicitly set the subgroup size in a compute shader. This optimizes compute shader performance using subgroup operations with specific subgroup sizes on targeted hardware platforms, particularly for AI workloads.

Window Shape API

The Window Shape API lets Isolated Web Apps on ChromeOS set a customized, non-rectangular window shape through window.chromeos.isolatedWebApp.setShape. This requires the window to be in unframed display mode and requires window management permission.

Media

MediaCapabilities encryptionScheme

Adds the encryptionScheme attribute to the KeySystemTrackConfiguration dictionary used in navigator.mediaCapabilities.decodingInfo(). This lets web applications query whether a specific encryption scheme such as 'cenc' or 'cbcs' is supported.

audioPreferred capture in getDisplayMedia API

Adds an audioPreference attribute to the DisplayMediaStreamOptions dictionary used in navigator.mediaDevices.getDisplayMedia(). This hint lets web applications signal to the browser that audio sharing is preferred along with video capture.

New origin trials

In Chrome 152, you can opt into the following new origin trials.

Speculation Rules: moderate viewport heuristics controls

This origin trial provides experimental controls for speculation rules viewport heuristics, letting developers test whether alternative heuristics parameters deliver better prefetching and prerendering performance for their sites.

Deprecation trial for client-side XSLT

Chrome has deprecated client-side XSLT, and is getting close to removing it from the browser, in Chrome 158. A deprecation (origin) trial has been set up to allow sites to extend the migration time away from XSLT by about nine months, to Chrome 175. This trial is available now, before the removal, so that it can be tested early.

Deprecations and removals

In Chrome 152, the following deprecations and removals take place. Visit ChromeStatus.com for lists of planned deprecations, current deprecations, and previous removals.

Remove Private Aggregation API

Following Chrome's announcement that the current approach to third-party cookies will be maintained, we are now planning to deprecate and remove the Private Aggregation API (along with certain other Privacy Sandbox APIs). This API is only exposed through the Shared Storage and Protected Audience APIs, which are also planned to be deprecated and removed.