GPU names reveal the era
Your WebGL renderer often exposes the exact GPU model. A “Mali” hints mobile/embedded, “Intel UHD” is iGPU, while “NVIDIA RTX” shouts discrete power.
This page reveals what your browser shares with websites and what your device environment looks like to client-side code. For support teams and developers, it gathers the essentials—browser and OS versions, GPU renderer, CPU core count, memory estimate, screen and viewport sizes, time zone and languages, and feature readiness for modern web APIs (Service Worker, WebRTC, clipboard).
We also include network-related hints using the Network Information API when available: connection type, effective bandwidth, round-trip time estimates, and data saver status. Because privacy features and UA reduction are increasingly common, detection is best-effort. We show your full User-Agent string, and—where supported—structured userAgentData to improve accuracy.
Your data stays local. Aside from retrieving your public IP from a widely used IP service, everything is computed in your browser. Use “Copy All” to paste details into a ticket, or “Export JSON” for developer bug reports. If something changes (e.g., window resize, device rotation), hit Refresh to re-measure the viewport and time-sensitive fields.
Your WebGL renderer often exposes the exact GPU model. A “Mali” hints mobile/embedded, “Intel UHD” is iGPU, while “NVIDIA RTX” shouts discrete power.
Modern Chrome/Firefox are reducing User-Agent detail to fight fingerprinting. navigator.userAgentData now carries structured, privacy-preserving hints instead.
1080p screen doesn’t mean 1080p viewport. Toolbars, zoom, and DPR (retina scaling) change the CSS pixel space sites actually render into.
The Network Information API reports “effective” connection type like 4g or slow-2g. It’s advisory only—great for adaptive loading, not billing.
Most of what’s shown is already accessible to sites; this page just surfaces it for you. Aside from fetching IP, nothing leaves the browser.