CPU temperature, fan and power
No API reads CPU heat; only coarse pressure buckets exist.
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
| Browser | Status | First version | Note |
|---|---|---|---|
| Chrome | Not supported | Not available | None |
| Edge | Not supported | Not available | None |
| Firefox | Not supported | Not available | None |
| Safari | Not supported | Not available | None |
| Safari on iPhone | Not supported | Not available | None |
| Chrome on Android | Not supported | Not available | None |
| Samsung Internet | Not supported | Not available | None |
How a site asks for it
| API | PressureObserver('cpu') (secure context, Permissions-Policy compute-pressure) |
| How access is granted | not-exposed |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | read fresh on every page load; nothing stored |
| How to take it back | not applicable |
| Inside an iframe | Readable from cross-origin iframes too (same values) |
Typical flow
- Page script reads the value
- No prompt is shown
Data you get
Shape: none
How often: static per session
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
proxy: Compute Pressure states | string | None | nominal, fair, serious, critical (4 buckets) | Not listed |
proxy: rate limit | string | None | default sample interval 1000 ms, min 1 s | Not listed |
proxy: performance timing jitter | string | None | indirect load signal only | Not 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
| Type | Example | Apps |
|---|---|---|
| video | A video call app wanted real temperature to avoid overheating and uses the busy level. | Google Meet |
| games | A browser game wanted fan speed to lower graphics and uses frame rate drops as a hint. | None named |
| games | A cloud gaming tab wanted heat readings and watches decoder stalls instead. | Xbox Cloud Gaming |
| creative | A browser editor wanted to throttle exports based on heat and reads the busy level. | Clipchamp |
| security | A tracker wanted temperature as a device clue and cannot get it. | None named |
| enterprise | An IT portal wanted to monitor laptop health and needs a managed agent instead. | None named |
| utilities | A browser hardware monitor site can show only coarse pressure, not true temperatures. | None named |
Risks
- Coarse level still leaks activity
What the platform says
- Google: Compute Pressure API. Chrome describes a coarse busy signal instead of raw temperature readings.
Good uses and abuse
Legitimate uses
- None: the browser deliberately withholds it
Known abuse
- Sites attempt proxies to recover it
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 3 of 5 | How much the user has to do |
| Fingerprint bits | 0 | Rough identifying entropy, when known |
Sources
How well checked: Based on official documentation.