Device & Browser Information

Overview

Shows what your own browser reveals about your device: user agent, platform, language, CPU core count, memory hint, screen geometry, pixel ratio, timezone, touch support, connection type and - where the browser allows - the actual GPU renderer string. Everything is read locally and each value is click-to-copy.

How It Works

Open the tool and a grid of cards fills immediately from the browser's own APIs - no button, no waiting. Click any card to copy that value. The GPU card appears only when the browser exposes WebGL renderer information; the connection and memory cards appear only where the browser supports those APIs. The page makes no requests and reports nothing anywhere.

Step-by-Step Usage Guide

1. Open the tool and read the cards; the grid populates from live browser APIs on load.
2. Click any card to copy its raw value - the user agent string is the one most often needed in bug reports.
3. Compare values across browsers on the same machine to see which APIs are Chromium-only and which report differently.
4. Note which cards are absent - a missing GPU or memory card means your browser restricts that API, which is itself information.

Technical Specifications & Standards

Each card maps to a specific API surface, and knowing which one explains why values differ across browsers. The user agent comes from navigator.userAgent - still the classic fingerprinting vector, still trivially spoofed. CPU cores come from navigator.hardwareConcurrency and the memory hint from navigator.deviceMemory, both Chromium-only in practice, both deliberately coarse (memory rounds down to a power of two, capped at 8) to limit fingerprinting. Screen geometry and color depth come from the screen object; pixel ratio from devicePixelRatio, which is what makes CSS pixels differ from hardware pixels on high-density displays. The timezone is resolved through Intl from the operating system's setting. Connection type is the Network Information API's effectiveType - Chromium-only, and an estimate, not a measurement. The GPU string uses the WEBGL_debug_renderer_info extension, which modern browsers restrict or gate precisely because it was a high-value fingerprinting target. The honest framing: this page shows you your own fingerprint surface. Every value here is something any script on any site could read - the tool's value is making that visibility concrete, not gathering anything new.

Targeted Use Cases

• Collecting the standard diagnostic block - user agent, screen, timezone, cores - for a bug report in one click each.
• Seeing your own fingerprint surface: every value on the page is readable by any website's JavaScript.
• Verifying how a user-agent switcher or privacy extension changes what the browser reports.
• Checking WebGL renderer strings when a graphics bug reproduces on some machines and not others.

Notes & Gotchas

• Use it to understand exposure, not as a security boundary - a spoofable value shows you what a spoofed value could hide.
• When filing bugs, copy the user agent and screen cards verbatim; paraphrased versions lose the details support engineers need.
• Remember several cards are Chromium-only: empty connection or memory fields in Firefox or Safari are expected, not broken.
• The GPU string can identify your specific hardware model; it is shown here because it is equally visible to any site you visit.

Frequently Asked Questions