v147 · Quality Tier Picker
Quality Tier Picker
Use navigator.deviceMemory as a coarse hint, then clamp it into Chrome 147's Android or desktop bucket limits before selecting a quality preset. The picker also shows the conservative fallback when the API is unavailable.
Reading the browser capability...
Pick a scenario to see the clamp and tier policy.
Live mode uses the browser's numeric value when available. Missing mode forces the fallback policy.
The same raw memory can map to different maximum buckets by platform.
This is intentionally not what the API exposes. The reported value is bucketed and clamped.
Fallbacks should avoid high-cost assets because no reliable memory hint exists.
-
-
-
Chrome 147 bucket limits
Quality recommendation matrix
| Reported GiB | Tier | Image plan | Video plan | Prefetch | Background work |
|---|---|---|---|---|---|
| No API | Fallback safe | Responsive 480-720p, lazy decode | 360p default, upgrade on demand | Off | User-visible tasks only |
| 1 | Low | 480p compressed images | 360p max | Off | Disabled |
| 2 | Careful | 720p WebP/AVIF where supported | 480p default | Current route only | Critical cleanup only |
| 4 | Standard | 1080p responsive images | 720p default | Two likely routes | Deferred after idle |
| 8 | High | 2x images with lazy loading | 1080p default | Section-level prefetch | Workers allowed |
| 16 | Rich desktop | 2x images plus richer previews | 1440p where available | Next workflow prefetched | Workers and warm caches |
| 32 | Max desktop | Highest responsive source set | 4K where supported | Broad prefetch budget | Full background pipeline |
Visible outcomes
-
-
-
-
-
-
-
References
implementation reference
Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗