Chrome 152 Beta Lets Any Website Ask Your Phone How Powerful It Is

Google pushed Chrome 152 into beta on July 28, 2026, and buried inside it is a new API that lets a site check whether a visitor's device is a workhorse or a budget phone, then quietly adjust what it serves. Here's what it means before the stable release lands around August 25.

What's Actually in the Chrome 152 Beta

Chrome 152 moved into its beta channel on July 28, 2026, which is Google's usual few week testing runway before a version goes stable for everyone. Based on the release calendar, stable should land around August 25. That date matters for one specific reason: it's the last release on Chrome's long standing four week cycle. Starting with Chrome 153 in September, Google is switching to a two week cadence, meaning updates start arriving roughly twice as often.

For a business owner, the practical effect of that cadence shift is close to zero. Chrome updates itself in the background for the overwhelming majority of visitors, so a faster release train mostly means the browser world moves a bit quicker under the hood. The more interesting part of Chrome 152 is a single new API that gives websites a genuinely new capability, one that touches how a site can behave depending on who's viewing it.

The CPU Performance API: A Site Can Now Ask 'How Strong Is This Device?'

Chrome 152 introduces navigator.cpuPerformance, a read only number from 1 to 4 that reports how powerful a visitor's device is, with 0 meaning the browser can't tell. A rating of 1 points to weaker, older or budget hardware, while a 4 signals a fast, modern machine. It's designed to be paired with the existing Compute Pressure API, which reports when a device is actively straining under load, so a site can react both to what a device is capable of and to what it's dealing with right now.

The use case is straightforward once you see it. A site with a heavy animated hero section, an interactive 3D product viewer, or an autoplaying background video can check that number first and quietly serve a lighter version, a static image instead of a video, simpler transitions instead of full animation, to anyone on tier 1 or 2 hardware. Nobody sees a warning or a popup. The page just adapts, and a visitor on an older phone gets a version that actually loads and scrolls smoothly instead of one that stutters.

There are guardrails built in from day one. Visitors can override what their device reports in Chrome's own performance settings, and IT administrators managing company fleets get a matching CpuPerformanceTierOverride policy. In other words, this isn't a fingerprinting shortcut, it's closer to the existing 'prefers reduced motion' setting, just aimed at raw device capability instead of a stated preference.

The Smaller Interface Changes Worth Knowing About

A handful of other additions round out the beta. Chrome now supports native pseudo classes like :playing, :paused, :muted and :buffering directly on video and audio elements, which means a developer can style a custom play button or loading spinner using plain CSS instead of writing JavaScript to track player state. There's also a new window-drag CSS property, aimed at installed, app-like websites, that lets part of the page act as a draggable titlebar, the kind of detail that matters for a booking tool or dashboard a client installs and uses like a real app rather than a browser tab.

Chrome 152 also formally closes the door on Manifest V2 browser extensions, the older extension format Google has been phasing out for several release cycles. That's mostly a note for anyone still relying on an old, unmaintained browser extension for site management or analytics, worth a quick check that nothing mission critical still depends on it.

• navigator.cpuPerformance: a 1-4 device power rating a site can read and react to
• Pairs with the Compute Pressure API to catch real time CPU strain, not just device class
• Native :playing, :paused, :muted pseudo classes replace custom JavaScript for player styling
• window-drag CSS property for installed, app-style web tools
• Manifest V2 extensions are fully retired as of this release

What This Means If You Run a Small Business Site

For the overwhelming majority of small business sites, brochure pages, service listings, a booking form, this changes nothing today. There's no setting to flip and no visible difference for a visitor. The CPU Performance API only becomes useful once a site is complex enough to have genuinely heavy elements worth scaling back, things like animated product configurators, embedded 3D views, or video-forward homepages.

The bigger signal is directional, and it's one worth filing away rather than acting on immediately. Browsers are increasingly willing to hand sites more information about the device on the other end, and the sites that use it well will feel noticeably faster to visitors on older phones, which in Las Vegas, where plenty of local searches still happen on a budget device in a parking lot between errands, is not a small slice of traffic. If a site leans on heavier interactive elements, this is a reasonable thing to raise with whoever built it: is there a plan to serve a lighter version to slower devices, or does everyone get the same experience regardless of what they're holding.

6 Things Chrome 152 Changes Under the Hood

Most of this beta is invisible to a typical visitor, but here's what it actually adds for anyone building or maintaining a site.

1. CPU Performance API: Reports a visitor's device on a 1 to 4 power scale so a site can lighten heavy elements automatically.
2. Compute Pressure pairing: Combines device class with real time CPU load for a fuller read on what a device can currently handle.
3. Native media pseudo classes: :playing, :paused, :muted and similar states can now be styled in plain CSS instead of tracked with script.
4. window-drag CSS property: Gives installed, app-like web tools a draggable titlebar region, useful for booking tools or dashboards.
5. CpuPerformanceTierOverride policy: Lets IT admins and visitors themselves override the reported device tier rather than have it forced on them.
6. Manifest V2 sunset: The older browser extension format is fully retired as of this release.
7. Two week release cadence ahead: Chrome 152 is the last four week cycle release before Chrome 153 shifts to updates every two weeks in September.

← More from the CyTek Studios blog