Device Information

Web

Display browser, OS, screen, GPU and runtime info with viewport, pixel ratio and more. Debug responsive layouts and feature detection checks on the fly.

Loading device info…

About Device Information

When debugging responsive layouts or chasing compatibility issues, you often want to see the current device's screen size, pixel ratio, viewport, browser, and OS at a glance. This tool reads and displays these runtime parameters locally in your browser: screen resolution and available area, devicePixelRatio, viewport width and height, color depth, time zone, language, touch support, and more — all from the browser's own APIs. The data is shown only on your page and is never collected or reported. Diagnosing "only some users see it" usually starts by establishing the actual environment: screen size and pixel ratio, browser and platform versions, input mode whether mouse, touch or stylus, and accessibility settings such as reduced motion. Users describe these inaccurately; reading them directly is far more precise. The implementation queries the environment interfaces the browser exposes, reading screen and viewport dimensions, pixel density, current language and timezone, input capabilities and several preference settings. Many of these readings are approximations. The pixel ratio may already reflect system scaling, and viewport size on mobile changes as the address bar shows and hides. Screen size on a folding device or with an external monitor does not represent usable area, so judge layout problems from the viewport and from measured element sizes rather than the screen. Practical notes: Attaching this information to a bug report cuts back-and-forth sharply, and a one-click copy button in the feedback form is far more reliable than asking users to transcribe it. When debugging, compare your own readings with the reporting user's, focusing on pixel ratio and viewport width, since those differences decide whether a breakpoint is being hit. Limits: For privacy, browsers limit the precision of some values, so screen dimensions and pixel ratio may be rounded or blurred, and interfaces such as available fonts are deliberately narrowed, which makes an empty reading normal rather than a failure. Some fields depend on user permission, as with location, or on the environment, such as battery information unavailable in some browsers, so features need fallbacks. Finally, combining several signals forms a device fingerprint, so for privacy such data should not be stored long term or used for cross-site tracking. Data and privacy: device information is identifying and becomes personal data once linked to an account. If you paste the result into a public forum, remove fields such as timezone and language that could help locate you.

How It Works Internally

Readings come from the environment interfaces browsers expose, and many are approximations: the pixel ratio may already reflect system scaling, the viewport changes on mobile as the address bar shows and hides, and screen size does not represent usable area on a folding device or with an external monitor. Judge layout from viewport width. For privacy, some fields are blurred or need permission, so an empty reading is expected.

InputA 1080p display at 150% scaling
OutputScreen size reports 1920×1080 while the device pixel ratio is about 1.5 and the viewport depends on the window — judging breakpoints from screen size misleads

Measured on This Page

Self-consistentAll 7 fields match the browser's live API values (screen W×H, innerWidth×innerHeight, language, hardwareConcurrency, timezone, UA prefix, devicePixelRatio)
Data sourceEverything is read live from local APIs with zero uploads — the page is purely client-side display
Capability probingWebGL/ServiceWorker/Clipboard etc. are reported by feature presence ('in' checks), not runtime tests

The two field classes differ in trustworthiness: deterministic fields (screen size, language, timezone, DPR) read APIs directly and are exact; privacy-protected fields are deliberately blurred by browsers — hardwareConcurrency may be clamped (often to 8), deviceMemory reports 0.25-granularity approximations, and the UA is being progressively frozen (Windows 11 still reports NT 10.0). So the 'core count' shown here means 'the core count the browser is willing to reveal' — this is browser environment info, not hardware info.

How this was measured: Within one browser instance both the page's displayed values and the raw navigator/screen/Intl API values were read and compared item by item: screen size, viewport, language, core count, timezone, UA and devicePixelRatio. · Measured 2026-10-30

How to Use

  1. Open "Device Information"
  2. The page reads system, screen and GPU details automatically
  3. Check the OS, resolution, viewport and pixel ratio
  4. Expand the CPU and GPU sections to verify the renderer
  5. Click "Copy" to paste the full report into a ticket or debug note

Use Cases

  • Responsive debug — Watch live viewport size and pixel ratio against your breakpoints to confirm media queries fire.
  • HiDPI assets — Read devicePixelRatio to decide whether to serve 2x or 3x images for Retina screens.
  • Environment capture — Ask a user to screenshot the info page to quickly gather the environment needed to reproduce a bug.
  • Touch detection — Confirm touch support to decide whether to enable gestures or a hover fallback.
  • Time zone & locale — Check the reported time zone and language to debug localization and date display.
  • Zoom testing — Check the actual viewport vs devicePixelRatio to confirm CSS media queries match physical pixels.
  • Browser fingerprint — Inspect a snapshot of your browser's exposed parameters to assess the fingerprinting surface.

FAQ

Why do screen size and viewport size differ?

screen.width/height is the whole display's physical resolution, while innerWidth/innerHeight is the browser's visible area (viewport), which shrinks with the address bar, zoom, and window size.

What does devicePixelRatio mean?

It is the ratio of physical to CSS pixels. A Retina screen is 2, meaning one CSS pixel is drawn by a 2x2 block of physical pixels, which tells you whether to prepare HiDPI assets.

Can this info uniquely identify me?

No single field can, but combining several (screen, fonts, time zone) forms a browser fingerprint. This tool only displays locally and collects nothing.

Why are some fields empty or restricted?

For privacy, modern browsers narrow some capabilities; battery, exact model, and similar may be unavailable or need permission, so reading undefined is normal.

Do values update after rotating the phone?

Yes. Viewport size, orientation, and others change with rotation or resizing; the tool listens to the resize event and refreshes the display live.

The reported screen size does not match what I see. Why?

Screen size reports the display physical pixels while rendering depends on the viewport and the device pixel ratio. System scaling, browser chrome, and the address bar showing or hiding on mobile all make the two differ, and folding screens plus external monitors differ even more. Judge layout problems from viewport width and treat screen size as reference only, or you misjudge which breakpoint applies.

Some fields come back empty. Is that a bug?

Usually not. For privacy, browsers restrict or blur certain values: screen dimensions may be rounded, the available font list is deliberately narrowed, and battery or geolocation readings require user permission. An empty reading is expected rather than a failure, so design features with a fallback instead of assuming a given field always exists.

The reported resolution differs from my system settings?

The browser reports CSS pixels (before devicePixelRatio scaling) while the OS shows physical pixels. A 2x-scaled 4K display differs by exactly 2x — expected. Use CSS pixels for responsive layout and physical pixels only for wallpapers or display adaptation.