Device memory exposure after changing your user-agent

You changed your browser’s user-agent, but you want to know whether websites can still guess how much memory your device has. The user-agent and device-memory information are separate browser details, so changing one does not necessarily change the other.

Use Browser Info to check which browser and engine you are testing, then compare the device-memory hint before and after the change. A browser can expose only a rounded estimate, not your exact installed RAM.

Check device memory exposure

1. Open Browser Info in the browser and profile where you changed the user-agent. Note the browser and engine information in its report, along with any relevant privacy or supported-feature details.
2. Look for a device-memory value in the report, if one is shown. Browser Info reports information the browser makes available, but it may not display a device-memory value in every browser.
3. For a direct check in a supported browser, open the browser’s developer tools, select the Console, and type navigator.deviceMemory. Press Enter. If the browser supports this property, it may return a number in GiB, such as 4. If it returns undefined or an error, that browser may not expose the property.
4. Reload the page after changing the user-agent, then repeat the check. Compare the results using the same browser, profile, device, and network. Change only the user-agent setting between checks.

The console check is optional. If you are not comfortable opening developer tools, use Browser Info to confirm the browser and engine, then treat any device-memory result provided by your browser or test page as an estimate.

What the result means

The memory value stays the same

This is common. A user-agent override changes the browser’s reported identity, but the device-memory estimate can be supplied separately. A website may receive a different browser or operating-system label while still seeing the same coarse memory hint.

The value changes

The browser, an emulation setting, or an extension may be changing more than the user-agent string. Check that you are using the same browser profile and that the only changed setting is the user-agent. A changed hint does not mean the computer’s physical RAM changed.

No value appears

The browser may not support the device-memory property, or it may limit access to it. An absent value does not prove that every website is unable to infer anything about your device. Browsers can expose other clues, and privacy protections differ by browser.

The reported amount looks too low or too high

Device memory is a rough hint, not a hardware inventory. Browsers that expose it return a rounded, limited value, often in power-of-two buckets such as 0.5, 1, 2, 4, or 8 GiB. The result may be capped or adjusted for privacy. It does not confirm the exact amount of installed RAM, available memory, or memory currently in use. For more on the limit, see why a browser can’t tell you how much RAM you have.

How to investigate a mismatch

1. Reload after each change. A page can keep the browser details it received when it first loaded. Reload Browser Info and any page you use for the comparison after changing the user-agent.
2. Check which override is active. If you changed the user-agent with a browser extension, review that extension’s settings and confirm it is not also enabling device emulation or other overrides. If you used developer tools, check the Network conditions panel and turn off device emulation when you do not need it.
3. Test without the extension. Temporarily disable the user-agent extension, reload the page, and compare the result. If the value returns to its earlier state, the extension or its configuration is likely involved.
4. Compare in a clean browser profile. Use a separate profile with no user-agent extensions or custom emulation. Keep the browser version and device the same where possible. A private window is not always a clean comparison because privacy settings and extensions may behave differently there.
5. Check another browser engine. Open Browser Info in another browser on the same device. Different engines can support different features and apply different privacy limits, so a missing or changed value does not by itself indicate a hardware problem.

There is no universal Windows 11 or macOS setting that shows or controls a website’s exact view of your RAM. Browser controls for user-agent changes vary by browser and by extension. Avoid changing system memory settings to explain a value returned by a web page.

What a user-agent change can and can’t hide

A user-agent string is a label that a browser sends to websites to describe itself. Changing it can alter that label, but it does not turn the browser into the operating system or browser named in the new string. Other browser features may still reveal differences.

Likewise, a device-memory hint is not the same as exact RAM access. Websites do not receive a complete list of your hardware from this value. The browser may round it, limit it, or omit it. For a broader explanation of what browser-based checks can establish, read why a browser cannot measure exact RAM capacity.

Use the same browser profile and change one setting at a time when you compare results. That makes it easier to tell a user-agent change from a difference in browser support or privacy controls.