What is Device Info Checker?
A Device Info Checker computes device info checker from the inputs you provide. It applies the standard formula to the values you enter and returns the result instantly, without sending any data to a server. Shows your browser, OS, screen resolution, viewport, color depth, language, timezone, online status, hardware concurrency.
Device Info Checker
View your device, browser, OS, screen, language, timezone, and network info - all from the browser.
TLDR
The page reads navigator.* and screen.* properties and displays them. Useful for debugging compatibility issues, sharing 'works on my machine' details, and quick OS/browser identification.
How to use this tool
- Open the page. The checker reads your device and browser details automatically on load; there is nothing to type.
- Scan the panels. Browser, operating system, screen, window, and locale details are grouped together for quick reading.
- Resize the window to watch window dimensions and device pixel ratio update live, useful for responsive-design debugging.
- Copy any value to paste into a bug report, a support ticket, or a compatibility test matrix.
- Trust the privacy. Every value is read locally; nothing about your device leaves the browser.
About this tool + how it works
A device info checker reports the technical details your browser already knows about itself and your hardware, the same details every website can read silently the moment you connect. This tool surfaces them in one place so you can see exactly what your browser broadcasts. It is handy for filing precise bug reports, debugging responsive layouts, confirming a screen resolution or pixel ratio, and understanding your own privacy exposure. It reads the values with standard Web APIs:
navigator.userAgent / platform / language / hardwareConcurrency screen.width / height / colorDepth / pixelDepth window.innerWidth / innerHeight / devicePixelRatio Intl.DateTimeFormat().resolvedOptions().timeZone
You can verify by opening the browser developer tools and watching the Network tab; you'll see no requests fired during normal use beyond the initial page and library load. Every reading happens on your device.
What your browser exposes, field by field
Each value this tool shows comes from a specific browser property. Here is what they mean and why a site might read them:
| Field | Source | What it tells a site |
|---|---|---|
| User agent | navigator.userAgent | Browser, version, OS, rendering engine |
| Platform | navigator.platform | Operating system family (Win32, MacIntel, Linux) |
| Language | navigator.language | Preferred UI language and region (en-US) |
| CPU cores | navigator.hardwareConcurrency | Logical processor count, a rough power hint |
| Screen size | screen.width / height | Display resolution in CSS pixels |
| Pixel ratio | window.devicePixelRatio | High-DPI / Retina scaling factor |
| Colour depth | screen.colorDepth | Bits per pixel, usually 24 |
| Time zone | Intl.DateTimeFormat | Your region, a strong fingerprint signal |
Real-world scenarios where this tool helps
Quick local use
Avoid the cloud round-trip when you just need a fast device info checker.
Bookmark for later
Stays handy as a tab; no signup, no cookies.
Privacy-sensitive content
Sensitive strings / API keys / personal data stay in your browser.
Mobile and slow connections
Local processing beats waiting on an API response.
What this tool does
- Runs the device info checker 100% in your browser - no upload, no API, no signup.
- Live error messages when input is malformed.
- One-click Copy and Clear buttons.
- Works on phones, tablets, and desktops; loads in under a second.
- Free forever; no premium tier.
What it does NOT do
- Does not store, log, or send your input anywhere.
- Does not require an account, an API key, or a paid plan.
- Does not fix malformed input - garbage in produces an error message.
- Does not need an internet connection after first page load (libraries cache).
Common misreadings and pitfalls
- Trusting the user agent as truth. Browsers can spoof it, and many now freeze or trim it. Treat it as a hint, not a guarantee of the real browser or OS.
- Confusing CSS pixels with hardware pixels. screen.width reports CSS pixels; multiply by the device pixel ratio to get the native panel resolution on a high-DPI display.
- Reading window size as screen size. window.innerWidth is the viewport (minus toolbars and scrollbars), not the full display. They differ, especially on mobile.
- Assuming CPU cores mean performance. hardwareConcurrency counts logical threads and is often capped or rounded by the browser for privacy, so it is only a rough signal.
- Thinking this hides you. Viewing your fingerprint does not change it. To reduce tracking you need a privacy browser or anti-fingerprinting settings, not just this readout.
Frequently asked questions
What information does this device info checker show?
It reads what your browser already exposes to every website: your user agent string, operating system and platform, browser and version, screen and window dimensions, device pixel ratio, colour depth, CPU core count, preferred language, and time zone. These values come from the navigator, screen, and window objects and the Intl API, read live with JavaScript on your device.
Is my device information sent anywhere?
No. Everything is read and displayed in your browser. Nothing is uploaded, stored, or logged by this tool. The same values are technically visible to any site you visit, but this checker simply shows them to you and keeps them local.
What is a user agent string?
The user agent is a text string your browser sends with every request to identify itself, for example 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) ... Chrome/120.0'. It encodes the browser, version, operating system, and rendering engine. Sites use it for compatibility decisions, though modern browsers are freezing and reducing it to limit fingerprinting.
What is device pixel ratio and why does it differ from screen resolution?
Device pixel ratio (DPR) is the number of physical screen pixels per CSS pixel. A Retina or high-DPI display has a DPR of 2 or 3, so a 1280 CSS-pixel-wide window actually spans 2560 or 3840 hardware pixels. That is why screen.width (CSS pixels) can look smaller than the panel's advertised native resolution.
Can websites use this data to track me?
Partly. Individually these values are common, but combined they form a browser fingerprint that can be fairly unique, especially with screen size, time zone, language, and fonts. That is why privacy browsers like Tor standardise these values and why this tool is useful: seeing your own fingerprint helps you understand how identifiable your browser is.