Skip to Content
Platform.Ontology

Exact RAM size

Only a capped RAM figure exists; exact memory is hidden.

Blocked for appsDevice detailsHardwareWeb browsersWhen the page loadsWhile you use it

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

BrowserStatusFirst versionNote
ChromeNot supportedNot availableNone
EdgeNot supportedNot availableNone
FirefoxNot supportedNot availableNone
SafariNot supportedNot availableNone
Safari on iPhoneNot supportedNot availableNone
Chrome on AndroidNot supportedNot availableNone
Samsung InternetNot supportedNot availableNone

How a site asks for it

APInavigator.deviceMemory (cap of 8)
How access is grantednot-exposed
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsread fresh on every page load; nothing stored
How to take it backnot applicable
Inside an iframeReadable from cross-origin iframes too (same values)

Typical flow

  1. Page script reads the value
  2. No prompt is shown

Data you get

Shape: none
How often: static per session

FieldTypeUnitRangePrecision
proxy: deviceMemorystringNone0.25, 0.5, 1, 2, 4, 8 GB onlyNot listed
proxy: performance.memory.jsHeapSizeLimitstringNoneheap limit, Chromium, hints at RAM classNot listed
proxy: measureUserAgentSpecificMemorystringNonecross-origin isolated onlyNot 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

TypeExampleApps
gamesA browser game wanted exact RAM for texture choices and uses the capped hint plus a quick speed test.None named
creativeA browser design tool wanted real memory to warn about huge files and relies on error handling.Figma
videoA video call app wanted exact RAM to plan background blur and watches performance instead.Zoom
adsAn ad vendor wanted exact RAM to guess income and sees only the capped number.None named
securityA fraud tool wanted exact RAM to spot virtual machines and uses other signals.None named
developerA web app team wanted real memory for crash reports and logs the capped value.Sentry
productivityA 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

Good uses and abuse

Legitimate uses

  • None: the browser deliberately withholds it

Known abuse

  • Sites attempt proxies to recover it

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility2 of 5How useful it is to honest apps
Friction3 of 5How much the user has to do
Fingerprint bits0Rough identifying entropy, when known

Sources

How well checked: Based on official documentation.

On this page