Device information

See your screen and browser details

All information is computed locally in your browser

Last updated: January 30, 2026

CreatorFrank Zhao

Screen

Screen size

unknown

Orientation

unknown

Orientation angle

unknown

Color depth

unknown

Pixel ratio

unknown

Window size

unknown

Device

Browser vendor

unknown

Languages

unknown

Platform

unknown

User agent

unknown

Introduction / overview

The Device Information tool shows a quick snapshot of your current screen and browser environment. It is especially handy when you need to explain a bug, validate responsive breakpoints, or double-check what a user means by “my screen is 2x”.

What problems does it solve?

Confirm the difference between screen size and browser window size.
Capture the exact user agent and platform for bug reports.
Check device pixel ratio to understand crispness, scaling, and screenshot fidelity.

Everything here is read directly from your browser APIs. No data needs to leave your device.

If you are troubleshooting a broken link or query string problem, pair this with our URL parser to share a clean, reproducible URL.

How to use / quick start

Open the tool and look at the Screen section for display-related values (screen size, orientation, pixel ratio).
Check Window size to confirm the current browser viewport.
Scroll to the Device section and copy the User agent for a bug report.
Rotate or resize your window to see which values change in real time.

Example 1: CSS pixels vs physical pixels

Suppose you see a window size of $1271\times 910$ with a pixel ratio of $2$ . A rough physical-pixel estimate is:

\text{physical width}

=

1271\cdot 2

=

2542

This helps explain why a UI might look “smaller” on a high-density display even when the CSS layout is identical.

Example 2: Color depth in plain numbers

If the tool shows $24\ \text{bits}$ , the number of representable colors is approximately:

2^{24} = 16\,777\,216

You usually do not need this for daily work, but it can help when investigating color banding or display limitations.

How to interpret results

Treat the values as a “context snapshot”. Screen-level values describe your display hardware and OS settings; window-level values describe the current browser viewport; user agent and platform help identify the runtime environment.

Real-world examples / use cases

Bug report that engineers can reproduce

Background: A user says “your site is broken on my laptop.” That is not actionable.

Inputs: copy $\text{platform}$ and $\text{user agent}$ .

Result: you now have a precise environment signature to attach to a ticket.

Responsive breakpoint sanity check

Background: A layout switches at $1024$ px, but someone claims it never triggers.

Inputs: confirm $\text{window width}$ .

Result: you can tell if they are resizing the window or just zooming.

Security triage: suspicious browser strings

Background: A support report includes an unusual browser identifier.

Inputs: user agent from the tool.

Result: you can compare it against known patterns and decide whether to treat it as automated traffic.

Orientation issues on tablets

Background: A web app looks fine in portrait but breaks in landscape.

Inputs: orientation type and angle.

Result: you can confirm whether the browser reports a rotation event and which mode it considers primary.

For URL-related debugging, it is often useful to include the exact link that triggered the problem. You can parse it with our URL parser and attach both the parsed result and this device snapshot.

Common scenarios / when to use

UI looks different on two machines

Compare pixel ratio and window size first.

Mobile layout is “stuck”

Check orientation and whether the viewport actually changes.

Support asks for browser details

Copy platform and user agent to avoid back-and-forth.

Investigating breakpoints

Window width is the number that usually matters.

Testing rotations

Orientation type and angle make the situation explicit.

Sharing a reproducible report

Pair this snapshot with a parsed URL for clarity.

When it may be less useful

Some browsers intentionally reduce fingerprinting details (for privacy). In that case, you may see fields reported as unknown or less specific than expected.

Tips & best practices

If you are debugging responsive CSS, focus on Window size. That is the measurement most media queries respond to.
When someone says “I have a 4K screen”, confirm whether they mean the physical screen resolution or the browser window they are using.
Do not treat user agent strings as perfectly reliable identification. They are useful hints, not proofs.
If you are testing orientation issues, rotate the device slowly and watch whether the orientation type and angle update.

For link troubleshooting, it often helps to capture the exact URL as well. Parse it with URL parser to share a clear reproduction path.

Calculation method / formula explanation

The tool mostly reports values directly from your browser. The only “math” you usually do is interpreting those values. Here are two tiny formulas that help:

Device pixel ratio

$\text{devicePixelRatio}$ relates CSS pixels to physical pixels:

\text{devicePixelRatio} = \frac{\text{physical pixels}}{\text{CSS pixels}}

Color depth to number of colors (roughly)

If a display reports $b$ bits per pixel, the theoretical number of colors is:

\text{colors} = 2^{b}

Variable definitions

$\text{CSS pixels}$ : the units your layout typically uses.
$\text{physical pixels}$ : the actual hardware pixel grid.
$b$ : bits per pixel (as reported by the browser).

Related concepts / background info

Screen size vs window size

Screen size is a display-level concept. Window size is the browser viewport. They often differ because of browser chrome, OS UI, and whether the window is maximized.

Privacy and fingerprinting

Some browsers or extensions reduce the detail in navigator fields to protect privacy. If you see unknown values, it may be intentional.

Related tools

If your debugging session involves URLs, query strings, or encoded links, you will often get faster results by combining this page with:

URL parser: break a URL into protocol, host, path, and parameters.
Encode/decode URL-formatted strings: safely handle percent-encoding.

Frequently asked questions (FAQs)

Why does “screen size” not match my monitor’s advertised resolution?

Many systems apply scaling, reserved pixels for OS UI, or report available screen dimensions. The value is still useful as a consistent reference for what the browser can access.

Is “window size” the same as the viewport used for CSS?

It is a practical approximation for most debugging. Your exact CSS viewport can also be influenced by scrollbars and browser UI, but window size is usually the number you want.

What does pixel ratio mean in everyday terms?

If $\text{devicePixelRatio}=2$ , then roughly 2 hardware pixels map to 1 CSS pixel in each dimension. That can make text look sharper while keeping layout measurements stable.

Why do I see “unknown” for some fields?

Some browsers and privacy tools intentionally hide or reduce device details to prevent fingerprinting. In those cases, the “unknown” label is expected.

Can I trust the user agent string for identification?

Treat it as a hint. User agents can be modified, and some browsers intentionally change them. It is best used together with reproducible steps and screenshots.

Limitations / disclaimers

This tool reports what your browser exposes. Values may vary by browser, privacy settings, and OS. It should not be used as a definitive device fingerprint or as a security control.

External references / sources

Related Calculators

Chronometer

Use a simple chronometer (stopwatch) to track elapsed time down to milliseconds. Runs locally in your browser.

Try Now

Email normalizer

Normalize email addresses to a standard format for easier comparison. Useful for deduplication and data cleaning. Runs locally in your browser.

Try Now

ETA calculator

Estimate the time needed to consume a total amount at a constant rate, and get an expected end time. Runs locally in your browser.

Try Now

JWT parser

Parse and decode your JSON Web Token (JWT) and display its content. All computation runs locally in your browser.

Try Now

MIME types

Know which file extensions are associated to a MIME type, and which MIME type is associated to a file extension. Includes a full MIME types table.

Try Now

Lorem ipsum generator

Generate random Lorem Ipsum placeholder text with customizable paragraphs, sentences, and word counts. Runs locally in your browser.

Try Now