Device Information
What your browser reveals about your device — screen, hardware hints, platform and capabilities, read locally with zero network calls.
Browser
Screen
Hardware
Platform
Capabilities
Examples
Structured support ticket
open page → Copy JSON{"browser": {…}, "screen": {…}, "hardware": {…}, "platform": {…}, "capabilities": {…}}Five named sections paste straight into a ticket, replacing the what-browser-are-you-on round trip.
Wide-gamut asset decision
Screen group, Display-P3 rowYes (or "No (sRGB)")The same media query your CSS uses — if it says No, shipping P3-only profiles wastes bytes for most of your audience.
DPR sanity check
screen 2560 × 1600, viewport 1280 × 800, DPR 2logical pixels = physical ÷ DPRThe three rows together explain why a retina screenshot is double the CSS size your layout works in.
About this tool
Every browser holds a surprising amount of information about the device it runs on, and it shares different slices of it through different APIs. The Device Information tool gathers those slices into one page: the User-Agent Client Hints (UA-CH) brand list with the platform and mobile hints that are replacing the legacy user-agent string, the screen facts (viewport, physical resolution, device pixel ratio, color depth), the hardware hints the spec exposes (logical CPU cores via hardwareConcurrency, approximate memory via deviceMemory where present, maxTouchPoints), a platform estimate (operating system and device type inferred from UA-CH and UA markers, browser languages, IANA timezone), and six capability booleans covering WebGL, WebGPU, WebAssembly, WebRTC, the MediaDevices camera/microphone API, and motion/orientation sensors.
The deliberately honest part is how missing data is handled. Browsers intentionally hide some values — Firefox never exposes deviceMemory, Safari doesn't ship UA-CH brand hints, matchMedia answers for color gamut only exist where the spec does — and many tools paper over those gaps with a wrong guess. This tool renders any field it cannot read as unknown, clearly styled as a muted value, because a support engineer who sees "unknown" asks the right follow-up question while one who sees a fabricated number trusts a bad report. The same rule applies to platform: the operating system row is labeled estimated because it comes from string sniffing, not from a signed fact.
Screen details go one step beyond resolution numbers. The device pixel ratio row explains why a 2560-pixel-wide panel reports a 1280-logical-pixel viewport at DPR 2, and the two media-query-driven rows answer practical shipping questions: does this display cover the Display-P3 wide gamut (so wide-color assets are worth shipping), and does it support HDR (dynamic-range: high)? Those checks run through CSS media queries, which is exactly how your own CSS decides the same question — the tool tells you what your media queries will match, not what marketing materials claim about the panel.
Everything on this page is read locally in your browser and never uploaded: there are no network calls, no geolocation lookup, no analytics payload, and the report is deliberately not persisted between visits. That makes it a safe page to open for support tickets — press Copy JSON and paste the grouped report into the ticket, and the recipient gets a structured browser/screen/hardware/platform/capabilities snapshot instead of a screenshot. If you came here from a network context, the sibling Network Info tool covers connection data and the optional public IP lookup; this page stays strictly device-side.
What this tool does not do
- Reads only what the current browser exposes — it cannot detect model numbers, serials, battery state or installed software.
- OS and device type rows are string-based estimates, not authoritative facts.
- The report is intentionally not persisted; every visit re-detects from scratch.
How to use this tool
Open the page
The report detects itself on load — no button to press. Skeleton placeholders render first and fill within a moment once the browser APIs are read.
Read the five groups
Browser, Screen, Hardware, Platform and Capabilities each list their fields; values your browser withholds show as unknown by design.
Check the practical rows
Display-P3 and HDR answer wide-color asset questions, DPR explains logical-vs-physical pixels, and Capabilities gates sensor/WebRTC features.
Copy the JSON
Paste the grouped report into bug reports or support tickets — five sections, field names preserved, unknowns inline.
Use cases
Filling in bug reports
Attach the JSON report so developers reproduce issues on the exact screen, DPR and capability set you tested on.
Feature gating decisions
Confirm WebGL, WebGPU, WebRTC or sensor availability on a real device before committing to an API-dependent implementation.
Verifying display capabilities
Check P3 wide-gamut coverage and HDR support before exporting wide-color assets or shipping HDR video.
The five report groups
| Group | Fields |
|---|---|
| Browser | UA-CH brands, UA-CH platform, UA-CH mobile flag, user-agent string |
| Screen | Viewport, screen resolution, device pixel ratio, color depth, Display-P3, HDR |
| Hardware | hardwareConcurrency (cores), deviceMemory (approx GB), maxTouchPoints |
| Platform | OS (estimated), device type (estimated), language, languages, timezone |
| Capabilities | WebGL, WebGPU, WebAssembly, WebRTC, MediaDevices, motion/orientation sensors |
Null values render as "unknown" — the browser withheld the field, and the tool never guesses.
Common mistakes
Mistake:Trusting the user-agent string as fact.
Fix:UA strings are self-reported and increasingly frozen; UA-CH hints are the structured replacement. Treat this tool's platform rows as estimates, and prefer the UA-CH fields where the browser ships them.
Mistake:Reading unknown as a broken page.
Fix:unknown means the browser withheld the field — Firefox hides deviceMemory and Safari omits UA-CH on purpose. It is a privacy feature; ask the user for the missing detail instead of assuming it.
Mistake:Confusing viewport size with screen size.
Fix:Viewport is logical CSS pixels; screen resolution is physical hardware pixels. They differ by the device pixel ratio — check all three rows before sizing images or screenshots.
Frequently asked questions
What does "unknown" mean in the report?
It means the browser declined to expose that field — the tool found nothing to read and refuses to invent a value. Firefox deliberately hides deviceMemory, Safari doesn't ship UA-CH brand hints, and some capability answers only exist where the specification provides them. Treat unknown as a privacy feature rather than a bug: it's the browser protecting details you didn't ask it to share. If a support ticket needs the missing value, ask the user directly instead of trusting any tool's guess.
Does this page send my device data anywhere?
No. Every value is read locally through standard browser APIs — navigator, window, matchMedia and Intl — and rendered on the page. There are no network calls, no geolocation lookups, no analytics payload, and the report is not persisted between visits, so reloading starts a fresh detection. That's why the page is safe to open on any machine: the only way the data leaves is if you press Copy JSON and paste it somewhere yourself.
Why do the CPU cores and memory numbers look approximate?
The web platform only exposes coarse hints, not real hardware specs. hardwareConcurrency reports logical cores but browsers may clamp the value, and deviceMemory is a deliberately rounded power-of-two estimate (0.25 to 8) that Safari and Firefox don't provide at all. These fields exist so sites can adapt workload — not for inventories. Read them as "roughly this class of machine", never as an exact specification.
What is the difference between viewport size and screen resolution?
Viewport is the CSS pixel size of the browser's content area — it shrinks when you resize the window — while screen resolution is the physical pixel size of the display. On a retina display a 2560 × 1600 panel shows a 1280 × 800 viewport because the device pixel ratio is 2, meaning four physical pixels render each CSS pixel. Check all three rows together when sizing images, screenshots or window-dependent layouts: physical pixels matter for assets, CSS pixels matter for layout.
How are the Display-P3 and HDR rows detected?
Through CSS media queries: (color-gamut: p3) reports wide-gamut coverage and (dynamic-range: high) reports HDR support. Because the tool uses the same queries your stylesheets use, the answers match what your CSS will actually match at runtime — it's what the rendering engine believes, not a spec sheet claim. A No (sRGB) result means P3-encoded profiles would be wasted bytes for that viewer, and an unknown means the browser answered neither query.
Which operating system detection is used, and can it be wrong?
The platform rows are honest estimates: the tool prefers the UA-CH platform hint where the browser ships it, then falls back to classic user-agent markers like Windows NT, Mac OS X, Android, CrOS or iPhone. User-agent strings are self-reported, increasingly frozen, and routinely spoofed by privacy tools, so the row is labeled estimated on purpose. For an authoritative answer, check the UA-CH fields first — structured hints are the direction the platform is moving.
References & standards
Related tools
Network Info
Browser connection details and optional public IP via proxy
IoT Pil Ömrü Tahminleyici
Mikrodenetleyici pil ömrünü ve uyku çevrimini hesaplayın
User Agent Parser
Parse User-Agent strings to identify browser, OS and device.
Keycode Info
Press any key to see its event.key, event.code, keyCode, location and modifier states.
Browser Compatibility Checker
Search web platform features and compare Baseline status with Chrome, Firefox, and Safari support