Device Intelligence Panel
What Device Are You Using?
OS, browser, hardware, screen, and sensor capabilities — scanned live from the moment this page loads.
Understanding Every Signal
What each device property above actually means and how it was detected.
Operating System & Browser
Operating System, Version & Browser Engine
Detected using the User-Agent Client Hints API where available (Chrome-based browsers on Android and Windows), falling back to traditional User-Agent string parsing. Client Hints are more reliable because they're structured data the browser explicitly provides; UA string parsing is heuristic and can be spoofed.
Browser & Browser Version
The browser name and version reported by your device. Version detection via Client Hints is exact. Via User-Agent string it's accurate for most browsers but some browsers deliberately report modified UA strings for privacy reasons — Brave, for example, reports as Chrome.
Architecture, Bitness & Detection Source
Architecture (x86, ARM) and bitness (32 or 64-bit) are available through Client Hints on modern Chromium browsers. Detection source confirms whether data came from the structured Client Hints API or fell back to UA string parsing, so you know how much confidence to place in the version and architecture values.
Device & Hardware
Device Type & Brand
Type classifies the device as desktop, mobile, or tablet based on screen size, touch support, and pointer capabilities. Brand is extracted from Client Hints where available — this is the manufacturer name (Samsung, Apple, Google) that the device reports directly, not inferred from the UA string.
CPU Cores & RAM Estimate
CPU core count comes from navigator.hardwareConcurrency — the number of logical processors available to JavaScript. RAM estimate comes from navigator.deviceMemory, which deliberately reports only coarse values (0.25, 0.5, 1, 2, 4, 8 GB) to limit its use as a fingerprinting signal. The real RAM may be higher than shown.
Screen & Display
Screen Dimensions, Viewport & Pixel Ratio
Screen width and height are the physical resolution of the display. Viewport is the visible area your browser content actually occupies — smaller than screen size on desktop due to browser chrome, and often scaled differently on mobile. Pixel ratio shows the density of physical pixels per CSS pixel — high-DPI retina screens typically show 2 or 3 here.
Color Depth, Color Gamut & HDR Support
Color depth is the bits used per pixel (almost always 24). Color gamut confirms whether the display can render wider-than-sRGB color spaces. HDR support indicates whether the display and browser combination can show high dynamic range content. These together describe the display's visual capability beyond raw resolution.
Input & Sensors
Touch Support, Max Touch Points & Pointer Support
Touch support confirms whether the screen is touch-enabled. Max touch points shows the maximum simultaneous touches detected — phones typically report 5 or 10; a non-touch laptop reports 0. Pointer support distinguishes between fine (mouse/trackpad) and coarse (touch/stylus) pointing devices, which matters for how interfaces should be sized.
Orientation Support, Current Orientation & Vibration Support
Orientation support confirms whether the device can detect and report physical rotation. Current orientation tells you whether you're in portrait or landscape right now. Vibration support is a simple check for the Vibration API — present on most Android devices, not available on iOS or desktop.
Why Device Data Matters Beyond Just Knowing Your Specs
It's a major component of your fingerprint
Screen resolution, pixel ratio, CPU core count, and RAM estimate together are among the most distinctive combinations in fingerprinting databases. Unlike network-level data, this information doesn't change when you use a VPN — it's tied to the physical device, not the network path.
Browser privacy features are closing some of these gaps
The deliberate coarsening of deviceMemory to only a few possible values is an example of browsers actively reducing fingerprint surface. Firefox's strict mode randomizes screen dimensions. Brave normalizes several hardware-concurrent values. The trend is toward browsers deliberately limiting what device intelligence is available to pages — which makes the values shown here more meaningful to check now rather than later.