Screen resolution and display info
Display, device, and browser details at a glance.
Screen resolution
800 × 600
Effective resolution
800 × 600
Device pixel ratio
1×
Color depth
24-bit
Pixel depth
24-bit
Estimated PPI
~96
Screen diagonal
1000px
Viewport size
800 × 600
Available screen
800 × 600
Outer window
0 × 0
Scroll position
0, 0
Orientation
Landscape
Touch support
No
Pointer type
None
Hover support
No
Platform
Linux x86_64
CPU cores
2 cores
Device memory
8 GB
Battery level
100%
Charging
Yes
GPU vendor
Google Inc. (Google)
GPU renderer
ANGLE (Google, Vulkan 1.3.0 (SwiftShader Device (Subzero) (0x0000C0DE)), SwiftShader driver)
User agent
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/148.0.0.0 Safari/537.36
Language
en-US
Languages
en-US
Cookies enabled
Yes
Online
Yes
Do not track
Disabled
Preferred color scheme
Light
Reduced motion
No
High contrast
No
Inverted colors
No
Connection type
4g
Downlink
1.4 Mbps
RTT
100ms
Data saver
No
This page reads what your browser knows about the screen it is being drawn on and lays it out in seven groups. Display covers screen.width and height in CSS pixels, the effective pixel count once devicePixelRatio is applied, colour and pixel depth, and a PPI estimate. Viewport tracks innerWidth and innerHeight live as you resize, alongside the available screen area, the outer window and your scroll position. Device and input reports touch points, pointer type, CPU cores and device memory. There is also the GPU renderer string, browser and language details, colour-scheme and accessibility preferences, and network hints where the browser exposes them.
Key facts about Screen resolution and display info
| Screen resolution | screen.width x screen.height, reported in CSS pixels after OS scaling |
|---|---|
| Effective resolution | those values multiplied by devicePixelRatio — closer to the panel's real pixel count |
| Device pixel ratio | physical pixels per CSS pixel: 1 on a standard display, 2 on most Retina panels |
| PPI estimate | 96 multiplied by devicePixelRatio — an approximation, since no browser exposes physical screen size |
| Colour and pixel depth | screen.colorDepth and screen.pixelDepth, almost always 24-bit in browsers |
| Live viewport | innerWidth and innerHeight, updated on every resize, scroll and orientation change |
| Available screen | availWidth and availHeight — the screen minus taskbars and docks |
| Pointer and touch | maxTouchPoints, plus pointer fine or coarse and hover support from matchMedia |
| GPU strings | unmasked vendor and renderer via the WEBGL_debug_renderer_info extension |
| Hardware hints | hardwareConcurrency for logical cores and deviceMemory in GB, both deliberately coarse |
| Accessibility preferences | prefers-color-scheme, prefers-reduced-motion, prefers-contrast and inverted-colors |
| Network hints | effectiveType, downlink, round-trip time and data saver, where navigator.connection exists |
What happens to your file
Every value is read synchronously from the browser objects already available to this page — window.screen, window.innerWidth, navigator, matchMedia and a throwaway WebGL context created only to read the renderer string. Nothing is sent anywhere, nothing is stored, and no fingerprint is assembled or retained: the values exist in memory while the tab is open and vanish when it closes. The copy button hands the whole readout to your clipboard through navigator.clipboard so you can paste it into a support ticket yourself, which is the only way any of this data leaves the page.
About this tool
- 1
Read the resolution line first
Screen resolution is the value in CSS pixels after your operating system's scaling. Effective resolution multiplies it by the device pixel ratio, which is the number that should match your monitor's specification.
- 2
Check the device pixel ratio
A ratio of 1 means no scaling, 2 is a typical Retina or HiDPI panel, and fractional values such as 1.25 or 1.5 mean Windows display scaling is set to 125 or 150 per cent.
- 3
Resize the window to watch the viewport
The viewport figures update live. Drag the window edge or open developer tools and the numbers follow, which is the quickest way to confirm which CSS breakpoint is active.
- 4
Use available screen for layout work
Available screen subtracts the taskbar, dock and any system chrome. It is the number to use when reasoning about how much room a maximised window really has.
- 5
Confirm the input model
Pointer fine means a mouse or stylus, coarse means touch, and hover support tells you whether hover styles will ever fire. Together they explain why a layout behaves differently on a touchscreen laptop.
- 6
Look up the GPU string
The unmasked vendor and renderer name the actual graphics adapter the browser is using, which is the fastest way to tell whether a laptop is on its integrated or discrete GPU.
- 7
Copy everything into a ticket
The copy button produces a plain-text block grouped by section. Pasting that into a bug report saves a long back-and-forth about what the reporter is actually using.
| Browser support | all modern browsers; individual fields degrade to N/A when unsupported |
|---|---|
| deviceMemory | Chromium only, and rounded to 0.25, 0.5, 1, 2, 4 or 8 GB by design |
| Battery readout | shown only where navigator.getBattery exists — Chromium desktop; Firefox and Safari removed it |
| navigator.connection | Chromium only; the whole Network group is hidden in Firefox and Safari |
| GPU renderer | hidden or masked in Safari and in Firefox with resistFingerprinting enabled |
| navigator.platform | deprecated and frozen in recent browsers; treat it as a hint, not a fact |
| Physical size | not exposed by any browser, which is why PPI is an estimate rather than a measurement |
| Account or install | none — no signup, no extension |
- If the resolution looks too small, you are seeing CSS pixels after scaling — multiply by the device pixel ratio to compare with the number on the monitor's box.
- Fractional pixel ratios such as 1.25 or 1.5 are the usual reason images look slightly soft on Windows laptops; they cannot map one image pixel to one screen pixel.
- The PPI figure is derived from the pixel ratio, not measured. Browsers never expose physical screen dimensions, so treat it as a rough class rather than a specification.
- Viewport width includes the scrollbar in some browsers and not in others; use it as a guide when debugging a breakpoint that fires a few pixels early.
- Zooming the page changes the reported viewport and device pixel ratio together — reset zoom to 100 per cent before recording values for a bug report.
- A GPU renderer showing an integrated chip on a laptop with a discrete card usually means the browser was launched on the power-saving GPU.
- The colour-scheme and reduced-motion rows reflect your operating system settings, so they are a quick way to verify a dark-mode or motion preference is actually reaching the browser.
- Missing rows are not errors: Firefox and Safari deliberately do not implement several of these APIs to reduce fingerprinting surface.
- Screen, effective and available resolution with device pixel ratio
- Live viewport, outer window and scroll position
- Colour depth, pixel depth and an estimated PPI
- Touch points, pointer type and hover support
- GPU vendor and renderer strings
- CPU cores, device memory and battery where exposed
- Colour scheme, reduced motion, contrast and inverted-colour preferences
- One-click copy of the whole readout
- Answering what is my screen resolution without opening system settings.
- Debugging a responsive layout by watching the viewport change as you resize.
- Checking device pixel ratio before exporting image assets at 1x, 2x or 3x.
- Confirming which GPU the browser is actually using on a dual-graphics laptop.
- Collecting display and browser details for a bug report in one paste.
- Verifying that a system dark-mode or reduced-motion preference reaches the browser.
Related tools
View allPart of Hardware testers that run in your browser
Works well with this5
More hardware testers10
More in Utilities12
Related categories1
Updated