Exact RAM size
Only a capped RAM figure exists; exact memory is hidden.
In one line
Can't see your exact RAM size; only a rounded number capped at 8 GB
Only a capped RAM figure exists; exact memory is hidden.
deviceMemory returns 0.25 to 8 GB (capped, Chromium, secure context, power of two rounding), so a 64 GB workstation looks like 8. Firefox and Safari expose nothing. Memory pressure is not readable.
What it can and can't do
What the user does: Nothing. It happens when the page loads in Chrome or Edge
It can
- See memory as 0.25 up to 8 GB in Chrome and Edge on HTTPS pages
- Guess your RAM class from the JavaScript memory limit
- Send a lighter page to low memory devices
It cannot
- See more than 8 GB; a 64 GB machine looks like 8
- See memory in Firefox or Safari
- See how much memory is free
- See memory pressure
How it differs between platforms: Chrome and Edge share a capped number. Firefox and Safari share nothing.
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 | navigator.deviceMemory (cap of 8) |
| 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: deviceMemory | string | None | 0.25, 0.5, 1, 2, 4, 8 GB only | Not listed |
proxy: performance.memory.jsHeapSizeLimit | string | None | heap limit, Chromium, hints at RAM class | Not listed |
proxy: measureUserAgentSpecificMemory | string | None | cross-origin isolated only | Not listed |
Technical limits
- Capped to limit fingerprinting
The story
What it is
Sites cannot see your exact memory. They get a capped, rounded number at best.
For you
A 64 GB workstation looks like an 8 GB laptop to a website. Firefox and Safari share nothing at all. Your exact memory stays private.
For makers
Exact memory would be a precise device clue and a wealth signal. The web caps and rounds it, which still lets sites pick a light or heavy page. That is enough for performance but not for precise tracking.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A browser game wanted exact RAM for texture choices and uses the capped hint plus a quick speed test. | None named |
| creative | A browser design tool wanted real memory to warn about huge files and relies on error handling. | Figma |
| video | A video call app wanted exact RAM to plan background blur and watches performance instead. | Zoom |
| ads | An ad vendor wanted exact RAM to guess income and sees only the capped number. | None named |
| security | A fraud tool wanted exact RAM to spot virtual machines and uses other signals. | None named |
| developer | A web app team wanted real memory for crash reports and logs the capped value. | Sentry |
| productivity | A big spreadsheet app wanted exact RAM and instead loads data in chunks. | Google Sheets |
Risks
- Capped number still hints at a device tier
What the platform says
- MDN: Navigator.deviceMemory. Docs explain that the value is rounded and capped, so it only hints at memory.
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 |
Related capabilities
Related
- Approximate device RAM. Can see roughly how much RAM you have, rounded and capped at 8 GB
Sources
How well checked: Based on official documentation.