Physical input
24 GiB
Nearest power-of-two result: 16 GiB.
v147 · Web APIs · Performance
Compatibility Lab
Probe the real NavigatorDeviceMemory API, test the Sec-CH-Device-Memory client hint opt-in, and simulate how Chrome 147's platform-specific buckets affect legacy memory-tier code.
Live API probes
Run these checks in the page and a dedicated worker. The Device Memory spec exposes the same deviceMemory getter on Navigator and WorkerNavigator, in secure contexts only.
Client hint opt-in
This page is served with Accept-CH: Sec-CH-Device-Memory. Click the test to fetch a local echo endpoint twice and see whether the browser sends the request header after this origin opts in.
Response opt-in
Accept-CH: waiting
Vary: waiting
Request echo
Sec-CH-Device-Memory: waiting
Run the check to surface the supported or missing-header path.
Client hint response JSON will appear here.
Bucket compatibility simulator
Change the physical RAM and platform. The simulator applies the spec's nearest-power-of-two rounding, then compares the old Chrome bounds with Chrome 147's implementation-defined platform bounds.
Old vs Chrome 147 values
Old Chrome <=146
8 GiB
Recommended lower and upper bounds were 0.25 and 8 GiB.
Chrome 147
16 GiB
Desktop / other platforms use 2, 4, 8, 16, and 32 GiB.
Failure modes to handle
Compatibility-safe tier pattern
references
implementation reference
Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗