Check device memory after enabling browser flags

You enabled a browser flag and want to know whether websites can now see more information about your device memory. A change in a browser report can be a clue, but it does not mean a site can read your exact RAM capacity.

Use TooLab's Browser Info to review the browser details and features it reports. Then compare the same browser with the changed flag and with its default setting.

Recheck what the browser reports

1. Open Browser Info in the same browser where you changed the flag. Review the report's privacy and supported features sections, and note the browser version and engine.
2. If you saved a report from before the change, compare it with the current one. Keep the browser, profile, and other settings the same so the flag is the main difference.
3. Open the browser's flags page in a separate tab. Chrome uses chrome://flags, and Edge uses edge://flags. Find the flag you changed and note its current value.
4. Temporarily set only that flag back to its default value, then relaunch the browser if prompted. Open Browser Info again and compare the reports. Change one flag at a time.

If you did not save a report from before enabling the flag, you can still compare its current state with the default. You cannot reliably reconstruct what the browser reported earlier unless its version and other settings were also the same.

What the result means

A memory-related value or feature appears only with the flag enabled

The flag may have changed a browser feature or the information the browser makes available to pages. That is evidence of a difference in this browser setup, not proof that websites can see the computer's precise RAM size. Check the flag's description before deciding whether to keep it enabled.

The reports look the same

The flag may not affect the information Browser Info reports, or the change may not be visible in this browser version. It does not prove that every site sees identical information. Pages may use different browser features, and privacy protections can vary by browser and settings.

The browser version or engine changed too

You do not have a clean comparison. Browser updates can change supported features and privacy behavior independently of a flag. Record the version shown in each report, and repeat the comparison without updating between runs if you need to isolate the flag.

You expected an exact RAM total

A browser generally provides only a rounded hint about device memory, not an exact amount. Browser Info cannot turn that hint into a precise hardware inventory. Read why browsers cannot report your exact RAM before treating a value as a specification.

How to restore a predictable setup

1. Return the changed flag to its default. On Windows 11 and macOS, open chrome://flags in Chrome or edge://flags in Edge, locate the flag, and select its default option. Relaunch the browser when asked. Flags are experimental and may change or disappear between browser versions.
2. Reset flags only if you are unsure what changed. The flags page may offer an option to reset all flags. This can undo other experiments too, so note any settings you still need before using it. Relaunch the browser afterward.
3. Use a normal browser profile for comparisons. Private browsing can apply different privacy behavior, so do not compare a normal window with a private one. A separate, fresh profile can help identify whether an extension or custom browser setting is affecting the report.
4. Check browser privacy controls without changing unrelated permissions. Chrome's path is Settings › Privacy and security › Site settings. In Edge, use Settings › Cookies and site permissions. These paths are the same on Windows 11 and macOS. Device memory exposure is not a camera or microphone permission, so changing those permissions will not reveal or hide an exact RAM total.
5. Restart and test again after an update. Close and reopen the browser after changing flags or updating it. Then check Browser Info again. Compare reports from the same browser version when you want to judge the effect of one flag.

Why the memory hint is limited

Web pages do not get unrestricted access to hardware details. A browser may expose a rounded memory estimate to help a page choose an appropriate workload, while withholding the exact installed RAM amount. Privacy protections can further reduce or standardize device details. A flag can affect experimental browser behavior, but it does not give a website direct access to system memory chips.

Use the report as a check of what this browser makes available, not as proof of what every website can learn or what hardware is installed. If an experimental flag is not essential, leaving it at its default is the safer baseline.