Screen Resolution Guide: CSS Pixels, Zoom and Browser Size
Admin ·
ToolMellow’s screen resolution tool reads the dimensions and display information that your browser exposes. Open the workspace on the display you want to investigate, read the screen and browser-window sizes, and use Refresh readings after changing displays or zoom. You can copy the current details or download a plain text report.
A browser reading is useful for comparing layouts and describing a problem to someone else. It is not a direct inspection of the panel inside your monitor. CSS pixels, device pixel ratio, operating-system scaling and page zoom describe different parts of the display process; understanding those differences explains why two plausible resolution numbers can disagree.
Read the seven values as a browser report
The workspace samples the current browser APIs and presents seven report fields. Screen resolution and Browser window also appear as large summary values; the repeated Browser window entry in the details is the same measurement, not a second kind of window size.
The screen, available-area and window dimensions are CSS-pixel measurements. Pixel ratio is a ratio, color depth is a reported bit count, and orientation is a classification calculated from the screen dimensions. Do not interpret every number as a physical-pixel count.
| Report field | What it uses | How to interpret it |
|---|---|---|
| Screen resolution | screen.width and screen.height | The screen area exposed by the browser in CSS pixels. |
| Estimated physical pixels | Rounded screen dimensions multiplied by pixel ratio | An estimate derived from other reported values; not proof of native panel resolution. |
| Pixel ratio | window.devicePixelRatio, with a fallback of 1 if falsy | The current device-to-CSS-pixel ratio; displayed with at most two decimal places. |
| Browser window | window.innerWidth and window.innerHeight | The layout viewport inside this browsing context, including relevant scrollbars. |
| Usable screen area | screen.availWidth and screen.availHeight | The screen area the browser reports as available, which can exclude reserved interface areas. |
| Color depth | screen.colorDepth | A browser-reported bits-per-pixel value, which can be standardized or limited. |
| Orientation | Screen width compared with screen height | Landscape when width is at least height; otherwise Portrait. |
CSSOM View: zoom, screen areas and display measurementsMDN: Screen width in CSS pixelsMDN: Available screen widthMDN: Browser layout viewport widthMDN: Browser-reported color depth
Separate CSS size, pixel ratio and native panel resolution
A CSS pixel is a unit used to lay out web content. It does not have to map to one physical pixel on a panel. Scaling and high-density displays can map a smaller CSS layout onto a larger device-pixel surface, so a smaller screen reading does not by itself indicate a broken monitor.
Native panel resolution describes the panel’s physical pixel grid. The operating system can also have a configured output resolution that differs from that grid. ToolMellow reads browser-exposed values; it does not query the monitor’s hardware specification or verify the operating system’s selected output mode.
CSSOM View: zoom, screen areas and display measurementsMDN: Screen width in CSS pixelsMDN: Device pixel ratio and zoomweb.dev: CSS pixels, device pixels and rendering
Compare the browser window with the usable screen area
Browser window means the layout viewport returned by the inner-width and inner-height APIs. It excludes the surrounding browser chrome rather than measuring the outside edge of the application window. The width can include a vertical scrollbar, so it is not necessarily the same as a document element’s content width.
Usable screen area belongs to the exposed screen rather than to the current page. A system taskbar or another reserved area can make it smaller than the full reported screen. A resized browser window can be smaller again. These are different rectangles; they are not expected to match.
MDN: Browser layout viewport widthMDN: Available screen widthCSSOM View: zoom, screen areas and display measurements
Distinguish display scaling, page zoom and pinch zoom
Operating-system display scaling affects the relationship between device and CSS pixels. As an illustrative case, a 3840 × 2160 panel at a scale of 1.5 could correspond to 2560 × 1440 CSS pixels. That arithmetic helps explain a reading; it does not establish what any particular browser must expose.
Page zoom changes the size of a CSS pixel relative to device pixels and can change the pixel ratio and layout viewport. Zooming in and zooming out do not both raise the ratio. Returning page zoom to 100% can make a comparison easier, but it does not turn off operating-system scaling or browser privacy behavior.
Pinch zoom magnifies the visual viewport without the same device-pixel-ratio change. Mobile keyboards can also affect the visible region in browser-dependent ways. This tool does not read window.visualViewport, so Browser window should not be treated as the exact currently visible region after every pinch or keyboard change.
CSSOM View: zoom, screen areas and display measurementsMDN: Device pixel ratio and zoomMDN: Visual viewport, pinch zoom and mobile keyboardsMDN: Browser layout viewport width
Understand the estimate and its rounding
For each dimension, the tool calculates Math.round(screen.width * ratio) or Math.round(screen.height * ratio). Here ratio is the raw window.devicePixelRatio value, falling back to 1 if that value is falsy. The estimated dimensions are integers; the displayed ratio is separately rounded to at most two decimal places.
The examples below are calculations from supplied browser values, not measured hardware configurations. Multiplying the rounded ratio printed on screen may give a different result from the tool’s calculation with the raw ratio. Page zoom, emulation, privacy protections and rounding can also prevent the estimate from matching a native panel specification.
| Reported CSS screen size | Raw pixel ratio | Calculated estimate |
|---|---|---|
1920 × 1080 | 1 | 1920 × 1080 |
2560 × 1440 | 1.5 | 3840 × 2160 |
1920 × 1080 | 2.625, displayed as 2.63 in English | 5040 × 2835 |
MDN: Device pixel ratio and zoomCSSOM View: zoom, screen areas and display measurementsweb.dev: CSS pixels, device pixels and rendering
Refresh after changing a display or zoom
Measurements are first taken when the workspace’s JavaScript starts, and are taken again when the browser sends a window resize event. The tool does not continuously poll the screen. A changed display or density value does not justify assuming that every browser will emit the event this page listens for.
Select Refresh readings to reread all seven values after moving the window to another display, changing zoom or adjusting system settings. This action also clears the workspace’s copy or clipboard-failure notice. It does not modify system settings, undo an earlier clipboard write or replace a report file you already downloaded.
Interpret orientation and color depth conservatively
Orientation uses the reported screen shape: width greater than or equal to height produces Landscape, including a square screen. A narrow browser window on a wide screen can therefore still show Landscape. This is not a rotation sensor reading or a Screen Orientation API result.
Color depth is the value exposed by the browser, rather than a complete display-quality test. A reading of 24 does not establish whether a panel supports HDR or a particular color gamut. Compatibility and privacy behavior can affect what is reported.
- The workspace does not test brightness, contrast, dead pixels or color accuracy.
- It does not measure monitor refresh rate, animation frame rate or input latency.
- It does not read physical dimensions in inches or calculate a verified physical pixels-per-inch value.
CSSOM View: zoom, screen areas and display measurementsMDN: Browser-reported color depth
Account for multiple displays, frames and remote sessions
Move the browser window to the display you want to investigate, then refresh the readings. The tool has no monitor picker and does not call getScreenDetails(), the separate API for enumerating displays. Browser policy determines which screen values are exposed; privacy protections or emulation can substitute a restricted screen area.
Inside an embedded tool, Browser window describes the frame’s own layout viewport. It is not the width and height of the entire parent page. Open the full workspace if that is the browsing context you intend to describe.
A remote desktop, virtual machine or emulated device can report the display environment presented to that browser. Save those readings as context for that environment rather than as proof of the physical monitor attached to another computer.
CSSOM View: zoom, screen areas and display measurementsMDN: The separate screen-details APIMDN: Browser layout viewport widthMDN: Visual viewport, pinch zoom and mobile keyboards
Make a repeatable comparison
A useful screen report needs context. Before comparing two readings, identify the display, browser, page zoom and system scaling that you mean to compare. Change one setting at a time so you can tell which change affected the result.
For a web-layout problem, focus on Browser window and the page’s actual behavior. For a monitor-configuration problem, compare browser values with operating-system display settings and the monitor specification. The report cannot replace either of those checks.
- Open the full workspace in the browser and display being investigated; let the measurement placeholders finish loading.
- Choose Refresh readings after your change, then read the screen, window, ratio and estimate together.
- Copy or download a new report and record the relevant settings separately; the exported report does not add a timestamp or a monitor name.
MDN: Browser layout viewport widthMDN: Device pixel ratio and zoomCSSOM View: zoom, screen areas and display measurements
Copy or download the current seven-line report
Copy details writes the seven localized labels and values to the clipboard, separated by line feeds with no extra final line feed. The clipboard operation can fail because of browser permissions or context. If the workspace reports that the clipboard is unavailable, use Download report.
Download report saves UTF-8 plain text named toolmellow-screen.txt, with one additional final line feed. The browser controls the destination and may rename a repeated download. The report is a snapshot of the displayed state when the action is selected; refresh before exporting if you want to sample changed settings.
The report contains the seven measurements, not a screenshot, browser history, monitor serial number or an inventory of every connected screen. Refreshing or closing the page does not erase copies already placed on the clipboard or saved as files.
MDN: Writing text to the clipboardMDN: Text strings in a Blob
Know what stays in the workspace
The screen-measurement workspace reads these APIs locally and has no report-upload action. It deliberately omits this site’s analytics tag. Links into that workspace request a full page load so a previous page’s analytics state is not retained by client-side navigation.
Opening the site still makes ordinary page and asset requests, and other site pages have their own loading behavior. Copy details and Download report intentionally export the displayed report when you choose them. A third-party page embedding the tool can have its own behavior; the embed’s resize message contains its layout height, not the seven-line screen report.
MDN: Writing text to the clipboardMDN: Text strings in a Blob
Troubleshoot a reading that does not look right
First separate a stale snapshot from a different definition of size. Refreshing solves the first situation by taking a new reading; it does not force CSS pixels, physical pixels and viewport dimensions to become the same quantity.
If privacy settings, emulation or the browser limit what an API exposes, the tool cannot recover the hidden value. Report the browser-visible result with that context, or use system settings for the information you actually need.
| Observation | Useful next step | What that step does not prove |
|---|---|---|
| Values remain the same after a display or zoom change | Select Refresh readings, then compare the fields again. | That every future transition will automatically trigger a resize. |
| The screen dimensions are lower than the panel specification | Check scaling, page zoom and the distinction between CSS and native pixels. | That multiplying by the displayed ratio always reconstructs the panel. |
| A pinch or mobile keyboard changes the visible page area | Distinguish the visual viewport from the reported layout viewport. | That the tool measures the visual viewport. |
| The page stays on measurement placeholders | Enable JavaScript and reload the workspace. | That instructions require JavaScript; they remain available to read. |
| Copy fails | Download a fresh report instead. | That an earlier clipboard copy has been removed. |
CSSOM View: zoom, screen areas and display measurementsMDN: Device pixel ratio and zoomMDN: Visual viewport, pinch zoom and mobile keyboardsMDN: Browser-reported color depth
Choose the measurement that fits the task
For responsive webpage debugging, the layout viewport is usually the useful size to record alongside the page zoom and device pixel ratio. A large reported screen can still contain a small browser viewport. Resizing that window tests a different condition from changing the monitor’s configured output.
For an image, inspect the image file’s own pixel dimensions with an image tool; this workspace does not read image files. For physical size, native panel resolution, refresh-rate settings or HDR capability, use the operating system and manufacturer information appropriate to the device.
MDN: Browser layout viewport widthMDN: Device pixel ratio and zoomweb.dev: CSS pixels, device pixels and rendering
Common questions
Why does my browser show a lower resolution than my monitor?
Browser screen dimensions are CSS-pixel values. Display scaling and browser behavior can make them smaller than native panel dimensions. Check the pixel ratio, zoom and system settings together; a smaller number alone does not show a monitor fault.
Can I find native monitor resolution by multiplying by pixel ratio?
That multiplication gives an estimate from browser-exposed values. The tool rounds screen dimensions multiplied by the raw ratio, but page zoom, rounding, privacy behavior or emulation can prevent the result from matching native panel resolution.
What is the difference between Screen resolution and Browser window?
Screen resolution reads the exposed screen area. Browser window reads the inner layout viewport for the current page or frame, including relevant scrollbars. The latter can be much smaller and does not include the outer browser chrome.
Why do page zoom and pinch zoom behave differently?
Page zoom affects the relation between CSS and device pixels and can change the ratio and layout viewport. Pinch zoom magnifies the visual viewport without the same ratio change. This tool does not measure the visual viewport.
Why did the reading stay unchanged after moving the browser?
Automatic updates listen for window resize events. If the browser exposes a changed value without sending that event, the displayed snapshot can remain old. Select Refresh readings to sample the current APIs.
Why is the orientation Landscape when my window is tall?
Orientation compares screen width with screen height rather than the window dimensions. It reports Landscape when screen width is at least screen height, including equal dimensions, and Portrait otherwise.
Does 24-bit color depth prove that my display supports HDR?
No. This is a browser-reported value that can reflect compatibility or privacy behavior. It is not an HDR, gamut, brightness or panel-quality test.
Can this tool measure screen size in inches or physical PPI?
No. Browser CSS dimensions and pixel ratio do not establish the physical dimensions of the panel. Use the monitor specification or a suitable physical measurement for that task.
Does the tool list all connected monitors or change resolution?
No. It reads the current browser-exposed screen values and has no display enumeration, monitor selector or control for system resolution, scaling or rotation.
What does the downloaded report contain?
It contains seven localized fields: screen resolution, estimated physical pixels, pixel ratio, browser window, usable screen area, color depth and orientation. It is UTF-8 plain text named toolmellow-screen.txt, with a final line feed and no timestamp or monitor identifier.
Are the measurements uploaded to ToolMellow?
The measurement workspace has no report-upload action and does not load this site’s analytics tag. Ordinary page and asset requests still occur. Copy and Download intentionally export the report when you choose them.
Do I need to enable JavaScript?
Yes, to measure, refresh, copy or download the values in the workspace. Without it, the instructions and limitations remain readable, but the measurement placeholders are not a screen result.
Sources and further reading
- CSSOM View: zoom, screen areas and display measurements
- MDN: Screen width in CSS pixels
- MDN: Available screen width
- MDN: Device pixel ratio and zoom
- MDN: Browser layout viewport width
- MDN: Visual viewport, pinch zoom and mobile keyboards
- MDN: Browser-reported color depth
- MDN: Window resize events
- MDN: The separate screen-details API
- web.dev: CSS pixels, device pixels and rendering
- MDN: Text strings in a Blob
- MDN: Writing text to the clipboard