How much memory does my browser report?
If this says 8, your machine has 8 GB or more, and the API will not say which. The specification caps the answer and rounds it down to a power of two on purpose, so 8 covers everything from a modest laptop to a workstation. An empty card means Firefox or Safari, neither of which implements this at all.
What this number actually means
The figure above is navigator.deviceMemory, and it is not your RAM. It is a bucket. The Device Memory specification rounds the real amount to a power of two and then clamps it between 0.25 and 8 gigabytes, so the only values a browser can ever report are 0.25, 0.5, 1, 2, 4 and 8. A machine with 16, 32 or 128 gigabytes all report the same 8, and a blank reading means your browser does not implement the API at all rather than that you have no memory.
The approximate amount of memory your browser reports is shown above, in gigabytes. Through the Device Memory API, some browsers expose a rough RAM figure so sites can decide how heavy an experience your device can handle. The value is deliberately coarse.
To limit fingerprinting, browsers round this to a small set of values, typically 0.25, 0.5, 1, 2, 4 or 8, and cap it at 8 even if you have far more. So a machine with 32 gigabytes still reports 8. It is a capability bucket, not a spec sheet reading.
Support is limited. Chromium-based browsers implement it; Safari and Firefox do not, so an empty value above just means your browser declines to share it. When present, treat it as a hint about class of device rather than a precise measurement.
How a website reads this
This is the exact call a page makes. Nothing else is involved, and nothing is sent anywhere: the value is read in your browser and displayed to you.
navigator.deviceMemoryReturns your RAM in gigabytes, deliberately rounded down to a power of two and capped, so the only possible answers are 0.25, 0.5, 1, 2, 4 and 8. A machine with 64 GB reports 8. Firefox and Safari do not implement the property at all, so the card is empty there.
- Needs your permission
- No, it is read silently
- Can it be faked
- Partly. Not settable, but a browser can decline to implement it, and two of the four major engines do exactly that.
- Contribution to a fingerprint
- About 1.2 bits, our own estimate. Our estimate. The rounding is the point: capping at 8 and snapping to powers of two was specified precisely to keep this from becoming a precise hardware identifier. How we estimate this.
What each browser does with it
The same call does not give the same answer everywhere. Several browsers withhold, round or cap this value on purpose, so a blank or suspiciously round result is usually a privacy decision rather than a fault.
| Browser | What it reports |
|---|---|
| Chrome, Edge and other Chromium browsers | Implemented. Returns 0.25, 0.5, 1, 2, 4 or 8, never anything else. |
| Firefox | Not implemented. navigator.deviceMemory is undefined. |
| Safari | Not implemented. navigator.deviceMemory is undefined. |
What does each device memory value mean?
There are six possible answers, so the interesting question is which class of device yours landed in rather than the exact figure.
| Reported value | Real RAM it can represent | What sites do with it |
|---|---|---|
| 0.25 or 0.5 GB | Very low memory hardware, typically old or entry level phones | Serve the lightest possible page: smaller images, no autoplay, minimal JavaScript. |
| 1 GB | Roughly 0.75 to 1.5 GB | Treat as constrained. Avoid large in-memory caches and heavy client-side rendering. |
| 2 GB | Roughly 1.5 to 3 GB | Budget phone or old laptop territory. Most sites still serve a full experience but trim extras. |
| 4 GB | Roughly 3 to 6 GB | The middle of the market. No special handling from most sites. |
| 8 GB | 6 GB, 8 GB, 16 GB, 32 GB, 128 GB and everything above | Treated as unconstrained. This is the ceiling, so it tells a site nothing about how far above 8 you actually are. |
| Nothing at all | Any amount | Your browser does not implement the API. Firefox and Safari do not, so the site has to fall back to other signals. |
Because 8 is the ceiling, a high end workstation and a mid range laptop are indistinguishable through this API. That is the intended design, not a bug in the reading.
How do I check how much RAM I really have?
The browser cannot tell you, so use the operating system. On Windows, open Task Manager with Ctrl plus Shift plus Escape, choose Performance and then Memory: the total is printed at the top right, with speed, form factor and slots used underneath. Device Manager, which people often reach for, does not list RAM capacity; Task Manager or System Information (msinfo32) is the right tool.
On macOS, choose Apple menu then About This Mac. The memory line shows the installed amount, and System Information under Hardware then Memory gives the per-slot detail on Macs that have slots.
On Linux, run free -h for a human readable total, or cat /proc/meminfo for the full breakdown including how much is actually available rather than merely free.
Those numbers are your real memory. The value at the top of this page is only what websites are allowed to see, which is a deliberately different and much blunter thing.
Why is my device memory blank or missing?
Because the Device Memory API is not universally implemented. Chromium based browsers, which includes Chrome, Edge, Opera and Brave, support it. Firefox and Safari do not, so on those browsers this page has nothing to show and says so rather than guessing.
That is not a fault to fix. A browser that declines to answer leaks nothing, which from a privacy point of view is the better outcome. If you want the value for a legitimate reason, such as testing how your own site behaves on constrained hardware, Chrome DevTools lets you override the reported memory under the Rendering panel and its network conditions controls.
Sites that need a memory hint and do not get one fall back to other signals, most often the core count and the connection type, which is one reason those two are read so widely.
What can a website learn about me from my device memory?
Less than from almost any other hardware signal, and that is by design. Six possible values means at best you are placed in one of six enormous groups, and in practice nearly everyone on a modern desktop reports 8.
The rounding and the ceiling were written into the specification precisely so the API could exist without handing fingerprinting scripts a precise hardware reading. Compare it with the WebGL renderer string, which can name your exact graphics chip and driver, and the difference in privacy design is obvious.
It still contributes a little. A device reporting 0.5 is unusual enough to narrow a crowd, and the mere presence or absence of the value already tells a script whether you are on a Chromium browser or not. But if you are deciding what to worry about, memory is near the bottom of the list.
What you should know
Why sites collect it
Sites use the memory hint to scale their experience: loading lighter assets, fewer background tasks, or a simpler interface on low-memory devices, and richer experiences where there is headroom. It helps pages stay responsive on modest hardware.
Privacy implications
Because it is rounded and capped, device memory is a low-entropy signal by design. It adds a little to a fingerprint but was deliberately blunted so it cannot pinpoint your exact hardware. An unusual bucket contributes slightly more.
How to change or hide it
There is no user setting to change the reported value directly. Browsers that do not implement the API (Safari, Firefox) reveal nothing, which is the most private outcome. The rounding already limits exposure where it is present.
Frequently asked questions
Why does my browser report only 8 GB when I have more?
The Device Memory API caps the reported value at 8 gigabytes and rounds it, on purpose, to reduce fingerprinting. It is a coarse hint, not your true RAM.
Why is my device memory blank?
Your browser likely does not implement the Device Memory API. Safari and Firefox do not, so they report nothing here.
What values can device memory return?
Only 0.25, 0.5, 1, 2, 4 and 8. The specification rounds real memory to a power of two and clamps it to that range, so those six numbers are the complete set of possible answers.
How do I see my actual RAM?
Use your operating system, not the browser: Task Manager then Performance then Memory on Windows, About This Mac on macOS, or free -h on Linux. Device Manager on Windows does not show RAM capacity.
Sources
Browser behaviour changes and vendors cap these values differently, so the claims above that are not self-evident are checked against the specifications and vendor documentation below.
Last checked on . How these values are measured and estimated is set out on the methodology page.
Something wrong here? Tell us what your browser reports and it gets corrected.