Device Info Viewer (Screen, Memory, GPU & Input)
See what your device and browser report: screen resolution, device pixel ratio, color depth, CPU cores, approximate memory, WebGL GPU name, touch points and pointer type, plus which Web APIs such as Web MIDI, Web Bluetooth, WebUSB and the Clipboard API are available. Copy the result as plain text to paste into a bug report or support request. Everything runs in your browser and no value is sent to a server. To break down a User-Agent string use the User-Agent Parser; for window width and breakpoints use the Viewport Checker.
🔒 Runs in your browser · Your data is never sent to a server
Screen
| Screen resolution (CSS pixels) | |
|---|---|
| Estimated physical pixels | |
| Available screen size | |
| Device pixel ratio (DPR) | |
| Color depth |
CPU, memory & GPU
| Logical CPU cores | |
|---|---|
| Approximate memory | |
| GPU (WebGL renderer) | |
| GPU vendor (WebGL) |
Input
| Max touch points | |
|---|---|
| Primary pointer type | |
| Hover capability |
Supported Web APIs
| API | Status |
|---|---|
| Clipboard API | |
| Web MIDI | |
| Web Bluetooth | |
| WebUSB | |
| Web Serial | |
| WebHID | |
| WebGPU | |
| Web Share | |
| Screen Wake Lock | |
| Geolocation | |
| MediaDevices (camera / mic) | |
| Battery Status | |
| Vibration | |
| Service Worker | |
| WebAuthn | |
| Notifications | |
| File System Access | |
| EyeDropper | |
| Speech Recognition | |
| WebRTC | |
| Web Audio | |
| SharedArrayBuffer | |
| WebAssembly | |
| IndexedDB |
Notes
- Fingerprinting protection (Firefox hardening, Brave, privacy extensions) can round the CPU core count, memory, GPU name and screen size, return fixed values, or hide them entirely. A value that differs from your real hardware is not a bug.
- Memory comes from navigator.deviceMemory, which is capped at 8 GB for privacy and unavailable in Safari and Firefox.
- The GPU name is read from WebGL debug info. It is missing when the browser hides it or WebGL is disabled.
- API support only checks that the API exists in this browser. HTTPS requirements, permissions, the OS and the actual hardware can still make it unusable.
- Screen resolution is affected by OS display scaling and may not match the panel. Estimated physical pixels is the resolution multiplied by the DPR.
Glossary
Device pixel ratio (DPR)
How many physical pixels one CSS pixel covers. High-density displays such as Retina report 2 or 3.
Pointer type (pointer: fine / coarse)
A CSS media feature describing the accuracy of the primary input. A mouse or pen is fine; finger touch is coarse.
WebGL renderer
The name of the GPU or graphics driver WebGL is using, read from the WEBGL_debug_renderer_info extension. Some browsers hide it.
FAQ
Why do the CPU cores or memory not match my real device?
Browsers may round these values or return fixed ones as fingerprinting protection. Memory is capped at 8 GB and is unavailable in Safari and Firefox.
Why is the GPU name not shown?
The GPU name comes from WebGL debug info. It shows as unavailable when the browser hides it or WebGL is disabled.
If an API says Supported, will it definitely work?
No. This only checks that the API exists in the browser. HTTPS, user permission, the OS or missing hardware can still prevent it from working.
Why does the resolution differ from my display spec?
The value is in CSS pixels and is affected by OS display scaling. An estimate of physical pixels (resolution times DPR) is shown alongside it.
Share this page