Skip to Content
Platform.Ontology

Compute Pressure API

Reports the device CPU load as nominal, fair, serious or critical.

Gets silentlySpeed and timingDeviceWeb browsersWhile you use it

In one line

Can see how busy your device's processor is, in four coarse levels

Reports the device CPU load as nominal, fair, serious or critical.

A PressureObserver reports coarse CPU state and thermal throttling (four levels), limited to secure contexts and top level or permission policy frames. Replaces CPU benchmarking for adaptive apps, but exposes load state.

What it can and can't do

What the user does: Nothing. It happens when the page asks, on a secure page

It can

  • Learn if CPU load is nominal, fair, serious or critical
  • Learn when the device slows down from heat
  • Lower its own work when your device is stressed

It cannot

  • See which apps are running
  • See exact CPU numbers
  • Work in Firefox or Safari
  • Work inside embedded frames unless allowed

How it differs between platforms: Works in Chrome, Edge and Samsung Internet. Firefox and Safari do not support it.

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported1252024-05-14None
EdgeSupported1252024-05-17None
FirefoxNot supportedNot availableNot listedNone
SafariNot supportedNot availableNot listedNone
Safari on iPhoneNot supportedNot availableNot listedNone
Chrome on AndroidSupported1252024-05-14BCD lists no support; agent research says otherwise
Samsung InternetSupported27.02024-11-06BCD lists no support; agent research says otherwise

How a site asks for it

APInew PressureObserver(cb).observe('cpu',{sampleInterval})
Browser compat keysapi.PressureObserver
How access is grantednone
What the user seesNot listed
Needs a secure context (HTTPS)Yes
Needs a user gestureNo
How long it lastsNot listed
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Create PressureObserver
  2. Observe cpu
  3. Receive state changes at 1 Hz at most

Data you get

What comes back: state: nominal, fair, serious, critical
Shape: event

FieldTypeUnitRangePrecision
statestringNonenominal, fair, serious, critical4 levels

Technical limits

  • Only when the page is visible and focused (or permitted)
  • Rate limited and levels deliberately coarse

The story

What it is

A page learns how busy your processor is, shown as nominal, fair, serious or critical.

For you

You will not see a prompt. A video call or game may quietly turn off a fancy effect when your computer is overloaded, so the sound and picture stay smooth.

For makers

Real time apps need to know when the processor is struggling. They can then reduce quality before the app lags. The same level is a small hint about your device load.

Where you see it

TypeExampleApps
videoA video call turns off background blur and drops video size when the laptop gets hot and busy.Google Meet, Zoom web client
gamesA browser game lowers physics detail and effects when the processor is under heavy load.None named
gamesA cloud gaming page like Xbox Cloud Gaming lowers decoding work when the device gets too hot.Xbox Cloud Gaming, GeForce NOW
liveA live streaming studio in the browser lowers encode quality when the processor hits critical.Restream, StreamYard
creativeA web video editor pauses previews or lowers detail when the computer is struggling.Clipchamp
musicA browser music studio lowers the number of live effects when the processor is overloaded to avoid crackles.Soundtrap
securityA fraud tool may use odd load patterns as a signal for a server farm of fake browsers.None named

Risks

  • Reveals what else you run
  • Only in Chromium

What the platform says

Good uses and abuse

Legitimate uses

  • Video conferencing quality adaptation

Known abuse

  • Load side channel and device inference

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits2Rough identifying entropy, when known

History

  • 2024-05, Chrome 125: Compute Pressure ships (CPU only)

Sources

How well checked: Based on official documentation.

On this page