Skip to Content
Platform.Ontology

CPU temperature, fan and power

No API reads CPU heat; only coarse pressure buckets exist.

Blocked for appsDevice detailsSensorsWeb browsersWhen the page loadsWhile you use it

In one line

Can't see your CPU heat, fan speed, or power use

No API reads CPU heat; only coarse pressure buckets exist.

Compute Pressure API (Chrome 125, secure context) returns nominal, fair, serious or critical, throttled to at most 1 update per second and capped per origin. Exact degrees, fan speed and wattage are not exposed. Battery level is separate.

What it can and can't do

What the user does: Nothing. Pages have no way to ask for this

It can

  • Check four coarse busy levels in Chrome and Edge (nominal to critical)
  • Get an update at most once a second
  • Slow down heavy work when the level gets high

It cannot

  • See degrees, fan speed, or watts
  • Check busy levels in Firefox, Safari, or on iPhone
  • Check it from a hidden tab or a page that is not HTTPS
  • Check it if the site or iframe is blocked by Permissions Policy

How it differs between platforms: Only Chrome and Edge offer the coarse levels. Firefox and Safari offer none.

Browser support

BrowserStatusFirst versionNote
ChromeNot supportedNot availableNone
EdgeNot supportedNot availableNone
FirefoxNot supportedNot availableNone
SafariNot supportedNot availableNone
Safari on iPhoneNot supportedNot availableNone
Chrome on AndroidNot supportedNot availableNone
Samsung InternetNot supportedNot availableNone

How a site asks for it

APIPressureObserver('cpu') (secure context, Permissions-Policy compute-pressure)
How access is grantednot-exposed
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsread fresh on every page load; nothing stored
How to take it backnot applicable
Inside an iframeReadable from cross-origin iframes too (same values)

Typical flow

  1. Page script reads the value
  2. No prompt is shown

Data you get

Shape: none
How often: static per session

FieldTypeUnitRangePrecision
proxy: Compute Pressure statesstringNonenominal, fair, serious, critical (4 buckets)Not listed
proxy: rate limitstringNonedefault sample interval 1000 ms, min 1 sNot listed
proxy: performance timing jitterstringNoneindirect load signal onlyNot listed

Technical limits

  • Thermal side channels

The story

What it is

No tool lets a page read how hot your processor is. Only coarse busy levels exist.

For you

A site cannot see your laptop's temperature or fan speed. The nearest thing is a basic busy level, so a video call can lower quality before your laptop overheats.

For makers

Heat and fan data would reveal exactly what is running on a device. The web gives only four rough levels, updated slowly. Apps use those to avoid pushing a laptop too hard.

Where you see it

TypeExampleApps
videoA video call app wanted real temperature to avoid overheating and uses the busy level.Google Meet
gamesA browser game wanted fan speed to lower graphics and uses frame rate drops as a hint.None named
gamesA cloud gaming tab wanted heat readings and watches decoder stalls instead.Xbox Cloud Gaming
creativeA browser editor wanted to throttle exports based on heat and reads the busy level.Clipchamp
securityA tracker wanted temperature as a device clue and cannot get it.None named
enterpriseAn IT portal wanted to monitor laptop health and needs a managed agent instead.None named
utilitiesA browser hardware monitor site can show only coarse pressure, not true temperatures.None named

Risks

  • Coarse level still leaks activity

What the platform says

Good uses and abuse

Legitimate uses

  • None: the browser deliberately withholds it

Known abuse

  • Sites attempt proxies to recover it

Scores

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

Sources

How well checked: Based on official documentation.

On this page