v147 · Web APIs · demo
Memory Inspector
Read navigator.deviceMemory, probe the worker exposure from NavigatorDeviceMemory, and compare Chrome 147's implementation-defined Android and desktop bucket limits with the older 0.25-8 GiB range.
live API read
The value is a rounded, clamped device-class hint, not exact installed RAM.
- NavigatorDeviceMemory
- Sec-CH-Device-Memory
- This page opts in with
Accept-CH: Sec-CH-Device-Memory. Run the HTTP probe to check the echoed request header.
bucket simulator
Chrome 147 profile
Chrome <=146 clamps at 8 GiB.
Desktop/other can expose higher coarse buckets.
Use the bucket as a hint for quality, not a RAM measurement.
edge-case trace
Waiting for scenario.
The reported value remains coarse to reduce fingerprinting surface.
HTTP Client Hint probe
Sec-CH-Device-Memory is a structured decimal request header. This page is served with Accept-CH: Sec-CH-Device-Memory; the probe fetches a local server echo endpoint twice and shows whether the browser actually sent the hint.
- Response opt-in
- Accept-CH: waiting
- Cache key
- Vary: waiting
- Request echo
- Sec-CH-Device-Memory: waiting
- Fallback path
- Run the HTTP probe to surface the sent-header or missing-header path.
see also
- Adaptive Loading Demo — practical tiered content loading
- Compatibility Lab — API, worker, and client-hint probes
- Back to feature index
- ChromeStatus entry
- Device Memory API specification
implementation reference
Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗