Skip to content

My Screen Size

Use this free screen resolution checker to see the screen dimensions and live browser viewport reported in CSS pixels. Check aspect ratio, orientation, device pixel ratio (DPR), estimated device pixels, color depth, and touch capability; copy the full display report, refresh the readings, or open the panel in fullscreen. Detection runs locally and does not pretend to measure physical screen inches, PPI, monitor model, refresh rate, or guaranteed native resolution.

Reading your display

How to Check Your Screen Size and Resolution

Open the tool and wait for the live display panel to appear. No measurements or device details need to be entered manually.

The large result shows the current screen width and height reported by the browser in CSS pixels. The cards below show viewport size, estimated device pixels, aspect ratio, DPR, color depth, and touch capability.

Resize the browser or rotate a supported device to watch the relevant readings update. Use Refresh when you want to request a new snapshot, Copy to place a complete text report on the clipboard, or Fullscreen to enlarge the panel.

Screen Size Here Means Pixel Dimensions, Not Inches

The phrase screen size can mean either pixel dimensions or a physical diagonal. This tool reports browser-accessible pixel dimensions; it does not estimate how many inches or centimetres the display measures diagonally.

A dependable physical-size calculation would require accurate hardware dimensions or pixel density. Standard webpage APIs do not consistently provide that information, so the calculator does not invent a diagonal size or PPI value.

Screen Resolution Versus Browser Viewport

Screen resolution is the logical width and height exposed through the browser's Screen interface. The viewport is the interior layout area currently available to the webpage.

A screen can report 1,536 × 864 while the webpage receives a viewport of 1,200 × 700. Browser tabs, toolbars, side panels, developer tools, scrollbars, and a non-maximised window can all reduce the webpage area.

Use viewport dimensions when reproducing responsive breakpoints. Use screen dimensions when you need the logical display size reported to the browser.

Choose the right screen measurement

Choose the right screen measurement
QuestionUse this valueWhy
How much width does this webpage currently have?Browser viewportResponsive layouts react to the webpage's available layout area, not the full display
What screen dimensions does the browser report?Screen resolutionThis is the logical width and height exposed through the Screen API
Why does the operating system show a larger resolution?Screen resolution and DPR togetherOperating-system scaling can map multiple device pixels to one CSS pixel
What dimensions should I use to reproduce a breakpoint?Browser viewportMedia queries and page layout are normally driven by viewport dimensions
Can I infer the approximate high-density pixel grid?Estimated device pixelsThe tool multiplies screen CSS dimensions by the reported DPR
Is the display landscape or portrait?Aspect ratio and orientationThey compare the browser-reported screen width and height

Swipe horizontally to view the full table.

CSS Pixels, Device Pixels, and Device Pixel Ratio

Web layouts use CSS pixels. A CSS pixel is a logical browser unit and does not always correspond to one hardware pixel on a high-density or scaled display.

Device pixel ratio, usually called DPR, describes the browser-reported relationship between device pixels and CSS pixels. A DPR of 2 means the browser generally maps a two-by-two device-pixel area to one CSS pixel in each dimension.

The panel keeps screen resolution and estimated device pixels separate so a logical browser measurement is not mislabeled as verified hardware resolution.

Display measurements explained

Display measurements explained
MeasurementBrowser source or calculationWhat it meansUseful for
Screen resolutionwindow.screen.width × window.screen.heightThe current display dimensions reported to the browser in CSS pixelsChecking the logical screen area and orientation
Browser viewportwindow.innerWidth × window.innerHeightThe layout area currently available to the webpageResponsive design, breakpoint testing, and layout troubleshooting
Estimated device pixelsScreen CSS pixels × device pixel ratioA derived estimate of the device-pixel dimensions associated with the reported screenUnderstanding display scaling and high-density rendering
Aspect ratioScreen width compared with screen heightThe reported screen dimensions reduced to their simplest whole-number ratioRecognising widescreen, portrait, square, and unusual display shapes
Device pixel ratiowindow.devicePixelRatioThe browser-reported ratio of device pixels to CSS pixelsHigh-DPI graphics, canvas sizing, and image-rendering checks
Color depthwindow.screen.colorDepthThe color depth value exposed by the browserBasic environment reporting, not display-quality assessment
Touch inputmaxTouchPoints and coarse-pointer detectionWhether the browser reports touch-capable inputInput-capability context, not device-type identification

Swipe horizontally to view the full table.

How Estimated Device Pixels Are Calculated

Estimated device width equals the reported screen width in CSS pixels multiplied by DPR. Estimated device height uses the same calculation.

For example, 1,536 × 864 CSS pixels at a DPR of 1.25 produces an estimate of 1,920 × 1,080 device pixels.

The result is useful for understanding scaling and high-density rendering, but it does not prove that 1,920 × 1,080 is the panel's native resolution. Browser zoom, operating-system scaling, and privacy behaviour can affect the inputs.

Aspect Ratio and Orientation

Aspect ratio compares the reported screen width with its height and reduces the values to a simpler whole-number ratio. A 1,920 × 1,080 or 1,536 × 864 report reduces to 16:9.

Landscape means width is greater than height, portrait means height is greater than width, and square means the values match.

An unusual ratio is not necessarily an error. Display scaling, browser reporting, rotated devices, folding displays, and uncommon monitor shapes can produce less familiar values.

Color Depth and Touch Support

Color depth is the bit-depth value exposed by the browser. It is useful as an environment detail, but it does not measure color accuracy, gamut coverage, HDR quality, calibration, or how many colors the physical panel can truly display.

Touch support is inferred from touch-point and pointer-capability signals. It means touch-capable input was detected; it does not identify the device as a phone or tablet and does not prove the current display itself is touch-sensitive.

Why the Numbers May Differ From Device Specifications

A laptop advertised as 1,920 × 1,080 can report 1,536 × 864 CSS pixels when operating-system scaling is set to 125%. In that example, a DPR of 1.25 produces a 1,920 × 1,080 device-pixel estimate.

Page zoom, display scaling, browser window size, mobile browser controls, developer tools, multiple displays, and privacy features can all change or limit what a webpage sees.

Treat the panel as a transparent report of browser APIs, not as a hardware-diagnostic certificate.

Why screen and viewport values can change

Why screen and viewport values can change
FactorPossible effect
Operating-system display scalingThe browser can report fewer CSS pixels than the panel's advertised hardware resolution
Browser page zoomDPR and the relationship between CSS pixels and device pixels can change
Browser toolbars, tabs, sidebars, and window sizeThe viewport can be much smaller than the screen dimensions
Phone rotation or changing window sizeViewport, orientation, and sometimes screen-context values can update
Moving the browser between displaysScreen dimensions, DPR, orientation, or color-depth reporting may change
Browser privacy and compatibility behaviourValues can be reduced, standardised, unavailable, or reported differently

Swipe horizontally to view the full table.

Using the Tool for Responsive Design and Troubleshooting

Developers can resize the browser and watch the viewport card while reproducing a breakpoint, debugging overflow, or checking how much layout space a page receives.

Designers can compare viewport size with DPR and estimated device pixels when preparing screenshots, canvases, or high-density graphics. Final exported-image dimensions should still be checked in the capture or design application.

Support teams can copy the display report and attach the measurements to a bug report without asking the user to find values in operating-system settings.

What Browsers Can and Cannot Detect

The browser can expose useful layout and display-context values, but it is intentionally not a complete monitor inventory system.

The tool avoids fake precision: it does not calculate physical diagonal, PPI, monitor model, panel type, serial number, exact refresh rate, color calibration, or guaranteed native resolution when the browser cannot verify them.

Browser-accessible information and limitations

Browser-accessible information and limitations
Available or derivableNot reliably detectable
Screen width and height in CSS pixelsDependable physical diagonal in inches or centimetres
Live browser viewport dimensionsGuaranteed native panel resolution
Device pixel ratio and a derived device-pixel estimateReliable PPI or DPI without physical-size data
Aspect ratio and orientation contextMonitor manufacturer, model, serial number, or panel type
Browser-reported color depth and pixel depthColor gamut, calibration accuracy, HDR capability, or bit depth of the physical panel
Touch-input capability signalsProof that the current display panel itself is touch-sensitive
A copied browser reportExact refresh rate or a complete hardware inventory

Swipe horizontally to view the full table.

Live Updates, Fullscreen, Copying, and Privacy

The component listens for browser resize, supported orientation changes, and visual-viewport resize events, then reads a fresh snapshot. The manual Refresh control is available when a browser delays an update.

Fullscreen enlarges the report but does not unlock additional hardware information. It can change the viewport because browser chrome and the displayed panel area change.

Detection and formatting happen locally. The Copy control writes a text report to the clipboard only after you activate it and only when the browser permits clipboard access.

Screen Resolution, DPR, and Aspect-Ratio Formulas

The tool reports browser values directly where available and labels calculated values as estimates.

Formula variables

Browser-reported screen width in CSS pixels
Browser-reported screen height in CSS pixels
Browser-reported device pixel ratio
Estimated device-pixel width
Estimated device-pixel height
Estimated device-pixel width
Estimated device-pixel height
Device pixel ratio
Aspect ratio

Examples

Scaled Full HD laptop display

1

Input

Screen: 1,536 × 864 CSS pixels; DPR: 1.25.

Show result

Result

Estimated device pixels: 1,920 × 1,080; aspect ratio: 16:9; orientation: landscape.

This is consistent with a scaled Full HD context, but the browser values alone do not certify the panel's native resolution.

Responsive breakpoint troubleshooting

2

Input

Screen: 1,920 × 1,080; viewport: 760 × 900.

Show result

Result

A layout using a 768-pixel breakpoint can remain in its narrower state because the webpage receives only 760 CSS pixels of width.

Use viewport width for responsive layout debugging rather than the full screen width.

High-density mobile display

3

Input

Screen: 390 × 844 CSS pixels; DPR: 3.

Show result

Result

Estimated device pixels: 1,170 × 2,532; orientation: portrait.

The estimated device-pixel dimensions are derived from the reported CSS dimensions and DPR.

Browser window with developer tools open

4

Input

Screen: 1,536 × 864; viewport: 980 × 720.

Show result

Result

The difference indicates that browser UI, window sizing, or docked tools are using part of the available display area.

Preparing a support report

5

Input

A website displays incorrectly on one device.

Show result

Result

Copy the display report and include the screen, viewport, DPR, orientation, color-depth, and touch details with the bug description.

The report supplies browser context but does not replace a screenshot, browser version, or operating-system details when those are relevant.

Frequently Asked Questions

What is my screen resolution?

The large result shows the width and height reported by your browser's Screen interface in CSS pixels. It is the browser-visible logical resolution, not guaranteed proof of the physical panel's native pixel grid.

Is screen size the same as screen resolution?

The phrases are often mixed together. Screen resolution means pixel dimensions, while physical screen size normally means the diagonal in inches or centimetres. This tool reports pixel dimensions, not physical diagonal size.

Why does my computer say 1,920 × 1,080 while the browser reports 1,536 × 864?

Operating-system scaling can expose a smaller logical CSS-pixel grid. At 125% scaling, 1,536 × 864 with a DPR of 1.25 produces an estimated 1,920 × 1,080 device-pixel grid.

What is the difference between screen resolution and viewport size?

Screen resolution describes the logical display dimensions reported to the browser. Viewport size describes the current webpage layout area inside the browser window.

Which value should I use for responsive design?

Use the live viewport width and height because responsive page layouts and media-query breakpoints are based on the webpage's available layout area.

What is device pixel ratio?

Device pixel ratio, or DPR, is the browser-reported relationship between device pixels and CSS pixels for the current display context.

Are estimated device pixels the native monitor resolution?

Not necessarily. The estimate multiplies screen CSS pixels by DPR. Browser zoom, operating-system scaling, privacy behaviour, and display handling can prevent that result from proving the native hardware resolution.

Can this calculate my screen size in inches?

No. A reliable diagonal calculation requires physical dimensions or trustworthy pixel-density data, which standard webpage APIs do not consistently provide.

Can it calculate PPI or DPI?

No dependable PPI value can be calculated without accurate physical screen dimensions. Using a fixed conversion from CSS pixels would be misleading.

Why does the viewport change when I resize the browser?

The viewport is the webpage's current layout area. Resizing the window, opening developer tools or sidebars, rotating a device, and changing browser UI can alter that space.

Does browser zoom affect the results?

It can. Page zoom can change devicePixelRatio and the mapping between CSS pixels and device pixels. Viewport behaviour can also vary by browser and zoom method.

Will the values change when I move the browser to another monitor?

They can. Displays can use different logical dimensions, scaling, DPR, orientation, and color settings, and browsers or operating systems can update the current screen context differently.

What does color depth mean?

It is the bit-depth value reported by the browser. It does not certify HDR, gamut coverage, calibration, or the physical panel's actual color performance.

Does touch support mean this is a phone or tablet?

No. Laptops, hybrid computers, external input devices, emulators, and other systems can report touch capability. It is an input signal, not a reliable device-category test.

Does fullscreen reveal more accurate screen information?

No. Fullscreen enlarges the interface and can change viewport dimensions, but it does not grant access to hidden monitor hardware data.

Does the tool update automatically?

Yes. It schedules a new reading when the browser resizes and listens for supported orientation and visual-viewport resize changes. The Refresh control requests a new snapshot manually.

Can it detect my monitor model or refresh rate?

No. Standard browser properties do not reliably expose the monitor manufacturer, model, panel type, serial number, or exact refresh rate.

Are my display details uploaded or stored?

No. Detection and formatting run locally in the browser. The report is written to the clipboard only when you press Copy and the browser permits clipboard access.