Approximate device RAM
RAM in gigabytes, rounded down to a power of two and capped at 8.
In one line
Can see roughly how much RAM you have, rounded and capped at 8 GB
RAM in gigabytes, rounded down to a power of two and capped at 8.
Lets a site serve a light page to low-memory phones. Rounded to 0.25, 0.5, 1, 2, 4 or 8 GB, so a 32 GB workstation and an 8 GB laptop look identical.
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, 0.5, 1, 2, 4, or 8 GB
- Send a lighter page to low memory phones
- Use the number as one hardware clue
It cannot
- See your exact RAM; a 32 GB machine looks like 8
- Work in Firefox, Safari, or on iPhone
- See how much memory is free right now
- Work on pages that are not HTTPS
How it differs between platforms: Chrome, Edge, and Samsung Internet share it. Firefox and Safari share nothing.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 63 | 2017-12-06 | Secure contexts only |
| Edge | Supported | 79 | 2020-01-15 | None |
| Firefox | Not supported | Not available | Not listed | None |
| Safari | Not supported | Not available | Not listed | None |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Supported | 63 | 2017-12-05 | None |
| Samsung Internet | Supported | 8.0 | 2018-07-18 | None |
How a site asks for it
| API | navigator.deviceMemory; Sec-CH-Device-Memory, Device-Memory headers |
| Browser compat keys | api.Navigator.deviceMemory |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | read fresh on every page load; nothing stored |
| How to take it back | none needed (no grant) |
| 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: object
How often: static per session
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
deviceMemory | float | GB | 0.25, 0.5, 1, 2, 4, 8 | rounded down to power of two, max 8 |
Technical limits
- Capped at 8 GB, floor 0.25 GB
- Not in Firefox or Safari
- Header needs Accept-CH opt-in
The story
What it is
Tells a page roughly how much memory your device has, capped at 8 GB.
For you
You never see it asked. If your phone has little memory, a site may quietly give you a lighter version so it does not crash. If you have a big machine, you get the full version.
For makers
Sites use it to serve light pages to low-memory phones and heavy pages to strong machines. It is capped and rounded, so a 32 GB workstation looks like 8 GB. It still adds a clue to a fingerprint.
Where you see it
| Type | Example | Apps |
|---|---|---|
| shopping | A shop serves smaller images and fewer scripts to a phone that reports 2 GB, so the page loads fast. | None named |
| games | A browser game turns down textures and crowd count on devices that report 2 GB or less. | None named |
| video | A video site loads fewer thumbnails ahead of time on a low-memory phone. | YouTube |
| creative | A browser editor warns that a large file may crash on a device with little memory. | Figma, Photopea |
| news | A news site drops heavy interactive graphics for low-memory visitors. | None named |
| ads | An ad network picks lighter ad formats for low-memory phones to avoid freezing the page. | None named |
| security | A fraud tool treats an impossible combination of memory and device model as a sign of a fake. | None named |
Risks
- Fingerprint clue
- Treats low-end phones differently
What the platform says
- MDN: Navigator.deviceMemory. Documents a rough, rounded memory figure that lets pages adapt to low-end devices.
Good uses and abuse
Legitimate uses
- Adaptive loading on cheap phones
Known abuse
- Device-tier inference
- Fingerprint component
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 1 | Rough identifying entropy, when known |
A real example: LinkedIn
Collector key(s): deviceMemory. BleepingComputer confirms memory is collected.
History
- 2017-12, Chrome 63: Shipped with the 8 GB cap
- 2021-01, Chrome: Restricted to secure contexts per spec
Related capabilities
Related
- CPU logical core count. Can see how many processor threads your device has
Sources
- W3C Device Memory
- MDN deviceMemory
- fingerprintjs source: device_memory
- BleepingComputer: LinkedIn scans for 6,000+ Chrome extensions
- mdp/linkedin-extension-fingerprinting (LinkedIn script snapshot and ID list)
How well checked: Checked against real behavior.