Browser Info & Screen Resolution Detector
Read your screen resolution, viewport size, device pixel ratio, GPU, CPU cores, time zone and connection quality from one table — including the physical pixel count behind the scaling.
100% private — everything runs in your browser
How to Use
- 1
Open the page — detection starts on its own, there is no button to press.
- 2
Read the Display block for the panel resolution, the usable area after the taskbar and dock, and the viewport you are actually designing inside.
- 3
Multiply check: the Physical resolution row is the screen resolution times the device pixel ratio, which is the number that matters for screenshots and export sizes.
- 4
Press Detect again after changing a monitor, toggling browser zoom, or rotating a tablet.
- 5
Copy everything at once with Copy all when you need to paste the numbers into a bug report or a design hand-off.
Examples
A 27-inch 4K monitor at 150 % scaling
Input
Screen 2560 × 1440 · device pixel ratio 1.5 · browser zoom 100 %Output
Screen resolution 2560 × 1440
Physical resolution 3840 × 2160
Viewport roughly 1707 × 960Phone with a high-density screen
Input
Screen 412 × 915 · device pixel ratio 2.6Output
Screen resolution 412 × 915 (CSS pixels)
Physical resolution 1071 × 2379
Orientation portrait · Touch points 5FAQ
What is my screen resolution?
The Screen resolution row is the full pixel size of the panel your browser is on, reported by the operating system in CSS pixels. On a scaled display it is smaller than the native panel resolution: a 4K monitor at 150 % scaling reports 2560 × 1440. Multiply by the device pixel ratio to recover the real 3840 × 2160, which is what a screenshot file will contain.
Why is "Screen resolution" different from "Viewport"?
Screen resolution describes the whole display, Available screen subtracts the taskbar and dock, and Viewport is the rectangle the web page actually renders inside — minus browser chrome, extensions and any open panel. Developers hit this difference when a layout fits on screen but still scrolls: the viewport is smaller than the display. Resizing the window or changing browser zoom moves the viewport while the resolution stays put.
What is device pixel ratio and why should I care?
Device pixel ratio (DPR) is how many physical screen pixels represent one CSS pixel. A DPR of 1 is a ordinary monitor, 2 is a Retina or typical phone display, 3 is common on recent flagships, and desktop scaling settings push it to values like 1.25 or 1.5. It decides whether a 1× image looks soft, when to serve @2x assets, and at what size an SVG or canvas should be drawn to stay crisp.
Why do some rows show a dash?
Browsers withhold hardware details deliberately. Device memory is rounded down to a short list of values and Safari reports a fixed one; GPU renderer strings are blocked in Safari and Firefox because they made people easy to fingerprint; connection type is Chromium-only; touch points are zero on laptops without a touchscreen. A dash is a missing permission, not a malfunction.
Can a website fingerprint me with this information?
This combination — resolution, DPR, cores, GPU string, time zone, language list — is what browser fingerprinting uses, since it is often unique enough to recognise a returning visitor without cookies. Modern browsers push back: Safari freezes device memory, Firefox and Safari hide the GPU renderer, and Chromium is reducing the User-Agent to a major version only. Nothing on this page is transmitted, but the same fields are readable by any site you visit.
Does it work offline?
Yes. Every value here is read from local browser APIs, so the detector keeps working after the page has loaded without a network — the Online row then simply reports no.