Quick Answer
Check your reported figure with the Device Information tool. The number you see is deliberately capped and rounded down by design - browsers report device memory in specific steps (0.25, 0.5, 1, 2, 4, 8GB and so on) and cap the maximum reported value at 8GB regardless of how much RAM you actually have installed, as a privacy protection measure, not a bug or a sign of a hardware problem.
Why Browsers Deliberately Under-Report Memory
The Device Memory API that websites use to check your RAM was designed with privacy and fingerprinting resistance in mind from the start. An exact RAM figure, combined with other details a website can collect (GPU model, screen resolution, installed fonts, and so on), makes it easier to uniquely identify and track a specific device across visits. To reduce this fingerprinting risk, the specification deliberately rounds the reported value to a small set of coarse buckets and caps it at 8GB, meaning a computer with 16GB, 32GB, or even 64GB of RAM will all report the same capped "8" figure through this particular API.
How This Compares to Other Privacy-Capped Browser APIs
Device memory isn't alone in being deliberately limited this way. Reported CPU core count, certain battery status details, and a handful of other hardware-related browser APIs have similarly been tightened over the years specifically to reduce how uniquely identifiable a device's fingerprint becomes across the web. If you notice one of these figures looking suspiciously round or capped, it's worth assuming that's by design rather than a fault, since this is a broader, deliberate pattern in how modern browsers expose hardware information, not a one-off quirk specific to memory reporting.
Step-by-Step: Checking What's Actually Being Reported
- Open the Device Information tool and note the reported device memory figure.
- Compare it against what you know is actually installed, either from the original purchase specs or by checking your OS's own system information panel (Task Manager on Windows, About This Mac on macOS).
- If your actual RAM is 8GB or less, the browser's figure should closely match reality, since the capping only kicks in above that threshold.
- If your actual RAM is above 8GB, expect the browser to report exactly 8 regardless of whether you have 16GB, 32GB, or more - this is expected behavior, not something to troubleshoot further.
How to Interpret the Results
- Browser reports 8GB and you have 16GB or more installed - completely normal; this is the API's built-in cap working exactly as designed.
- Browser reports a figure that seems oddly low even for a system with 8GB or less - worth double-checking your actual installed RAM through your OS directly, since it's possible some memory is reserved by integrated graphics or otherwise not available to the OS, which can genuinely lower the usable total below the sticker specification.
- Different browsers on the same computer report different numbers - not expected for this particular API, since the rounding buckets are part of a shared web standard; if you see this, it's worth confirming you're comparing like-for-like browser versions.
What This Number Is Actually Useful For
Despite the capping, this figure still serves a real purpose: it lets websites make a rough, coarse decision about whether to load a lighter or heavier version of a page for memory-constrained devices, without needing your exact specs. A site can reasonably tell the difference between "very low memory device" and "reasonably capable device" using these buckets, which is genuinely useful for adapting content for budget phones or older computers, even though it can't tell the difference between an 8GB machine and a 64GB workstation.
FAQ
Does this mean my browser can only use 8GB of my RAM?
No - this is purely a reporting limitation of one specific API used by websites to make coarse decisions.
Your browser and OS can still use all of your actual installed RAM normally for everything else.
Is there a way to see my true RAM amount through the browser?
Not through this particular web API by design, since it's intentionally privacy-limited. Your OS's own system
information tools will always show the accurate figure.
Does this affect performance in any way?
No, it's purely an informational reporting cap and has no effect on how your system or browser actually
allocates or uses memory.
Is this the same on mobile browsers?
Yes, the same capping and rounding behavior applies on mobile browsers that support this API, for the same
privacy reasons.