Is this information sent to a server?

No, every value comes from your own browser's navigator, screen and Intl APIs and is rendered directly on the page; nothing here is transmitted or logged anywhere.

Why is my device memory listed as unavailable?

The deviceMemory API is only implemented in Chromium-based browsers; Firefox and Safari don't expose it, so the field shows "unavailable" rather than a made-up number.

Why does CPU core count seem lower than my actual processor?

navigator.hardwareConcurrency reflects what the browser chooses to report, and some browsers cap or round this value for privacy reasons rather than exposing the true logical core count.

Can a website see this same information about me?

Yes, screen size, platform, languages, CPU cores and the user agent are standard JavaScript properties any page can read without special permission, which is exactly what this tool displays about your session.

Device Information

See what your browser exposes: screen, viewport, platform, languages and more, locally.

Local, Runs entirely in your browser, your data never leaves your device.

Loading tool…

What your browser tells sites about your device

This page reads and displays the values your browser's JavaScript APIs expose about your current session: screen and viewport size, device pixel ratio, color depth, platform, language list, CPU core count, device memory, time zone and the full user agent string. It's useful for debugging responsive layouts, checking what a site can see about a visitor, or confirming a user agent before writing browser-specific code. Everything listed comes from navigator, screen and Intl in your own browser and is read fresh on load and on resize; none of it is transmitted anywhere.

How to use the Device Information

Load the page and read the list of values as detected in your current browser.
Resize the window to watch viewport, screen and orientation fields update live.
Hover a row and use its copy button to grab that single value.
Compare device pixel ratio and color depth if you're debugging a display issue.

Some fields depend on the browser: device memory is Chromium-only and shows "unavailable" in Firefox or Safari, and CPU core count reflects hardwareConcurrency, which some browsers cap or round for privacy reasons.

This reads properties already exposed to any page's JavaScript, the same ones analytics scripts and fingerprinting libraries read. Seeing them here just makes visible what your browser already reveals on every site you visit.

Frequently asked questions

Is this information sent to a server?: No, every value comes from your own browser's navigator, screen and Intl APIs and is rendered directly on the page; nothing here is transmitted or logged anywhere.
Why is my device memory listed as unavailable?: The deviceMemory API is only implemented in Chromium-based browsers; Firefox and Safari don't expose it, so the field shows "unavailable" rather than a made-up number.
Why does CPU core count seem lower than my actual processor?: navigator.hardwareConcurrency reflects what the browser chooses to report, and some browsers cap or round this value for privacy reasons rather than exposing the true logical core count.
Can a website see this same information about me?: Yes, screen size, platform, languages, CPU cores and the user agent are standard JavaScript properties any page can read without special permission, which is exactly what this tool displays about your session.