Device Info

View your browser and device information

Developer Tools

How to Use Device Info

  1. 1Open the page
  2. 2Your device information is displayed automatically
  3. 3Copy any value with the copy button

About Device Info

Device Info displays detailed information about your current browser, operating system, screen, and device capabilities — all read directly from your browser's standard APIs. No installation, no extensions, and no server communication required.

Developers, QA engineers, and support teams frequently need to capture environment details when debugging browser-specific issues. Instead of navigating through browser settings menus or reading raw user agent strings, this page surfaces all relevant details in a clean, copyable format.

All data is read from standard browser APIs and stays entirely on your device.

Key Features of Device Info

  • Displays browser name, version, and rendering engine
  • Shows operating system and OS version
  • Screen resolution, viewport dimensions, and device pixel ratio
  • Color depth and display color gamut
  • Timezone, language settings, and locale
  • Online/offline status and connection type (if available)
  • Hardware concurrency (number of logical CPU cores)
  • Works entirely in-browser — nothing is transmitted to any server

Examples

Capture environment details for a bug report

Collect browser and OS details to include in a Jira ticket or GitHub issue.

Input

Open the Device Info page in your browser

Output

Browser: Chrome 124.0.0 | OS: macOS 14.4 | Screen: 2560×1600 (2× DPI) | Viewport: 1280×800

Verify responsive breakpoint during cross-device testing

Check the actual viewport width and device pixel ratio while testing a responsive design.

Input

Open in a mobile browser or browser DevTools device emulation

Output

Viewport: 375×667 | Device pixel ratio: 3 | Touch: Yes

Common Use Cases

  • Capturing browser and OS details for bug reports and support tickets
  • Verifying viewport dimensions and device pixel ratio during responsive design testing
  • Checking hardware concurrency to understand available threads for Web Workers
  • Documenting the test environment for QA testing across different devices
  • Confirming timezone and locale settings that affect date/time display
  • Teaching browser API capabilities by showing the data available to web applications

Troubleshooting

Operating system shows as unknown

Solution

OS detection relies on user agent string parsing. Privacy extensions or spoofed user agents may report incorrect or empty OS information.

Screen resolution shows an unexpected value

Solution

screen.width and screen.height report the physical screen dimensions. On high-DPI displays, CSS pixels differ from physical pixels.

Hardware concurrency shows 1 even on a multi-core machine

Solution

Some browsers cap navigator.hardwareConcurrency for privacy reasons. Firefox and Brave may report a reduced value to prevent fingerprinting.

Frequently Asked Questions

Is this information sent to a server?

No. All information is read directly from browser APIs and displayed locally. Nothing is transmitted to any server.

Why does the OS version sometimes appear incorrect?

OS version detection relies on parsing the user agent string, which privacy-focused browsers may spoof.

What is device pixel ratio?

Device pixel ratio (DPR) is the ratio of physical screen pixels to CSS pixels. A DPR of 2 means 4 physical pixels per CSS pixel — common on Retina displays.

What is hardware concurrency?

Hardware concurrency reports the number of logical CPU cores. Web applications can use this to decide how many parallel Web Workers to spawn.

Can I use this to test if a user is on mobile?

Yes, Device Info shows the user agent string and touch support. For production code, use feature detection rather than user agent parsing.

Does it show GPU information?

Basic GPU information may be available via the WebGL renderer string. This tool focuses on the most practically useful device properties.

Why does the viewport size differ from the screen size?

Viewport is the visible browser window area. Screen size is the total physical display resolution. These differ because browser chrome takes up space.

Can this be used for browser fingerprinting?

The properties shown here are the same ones used in browser fingerprinting. This tool surfaces them for legitimate debugging purposes only.