See your screen, available desktop, live viewport and device pixel ratio, plus an estimated refresh rate and pointer and color capabilities.
This report is computed locally from standard browser APIs. Nothing is uploaded, stored or shared.
Screen
—
Full display size as the browser reports it, in CSS pixels.
Available desktop
—
Screen minus taskbars and docks — this is the space a maximized window can take.
Browser viewport
—
The page area right now; resize the window and it updates live.
Device pixel ratio
—
Real panel pixels behind the CSS pixels above — multiply to get physical size.
Refresh-rate estimate
Frames are counted for 2 seconds. Results are vsync-capped and browsers throttle background tabs, so treat this as a lower-bound estimate, not a spec sheet number.
The four main cards read four nested rectangles. window.screen.width/height report the full display as the browser sees it; availWidth/availHeight subtract the OS chrome (taskbar, dock) that a maximized window cannot cover; innerWidth/innerHeight measure the actual rendered page area and re-measure on every resize; and devicePixelRatio scales each of those CSS pixels to the physical panel pixels behind them.
Not reliably from a web page. Browsers deliberately expose scaled, CSS-level numbers, not the panel's hardware mode, and the OS display scale, browser zoom and fullscreen all rewrite them. For the native figure, check your OS display settings (Windows: Settings > System > Display; macOS: About This Mac) or the monitor's own on-screen menu — those read the hardware directly.
Because every value here is in CSS pixels. A 200% browser zoom halves the reported viewport and screen sizes; a HiDPI display keeps the CSS numbers but raises devicePixelRatio, so more real pixels render each CSS pixel. The DPR card shows the physical-pixel equivalent so you can see both layers at once.
No: rotating swaps width and height in every readout, and the viewport card re-measures on the orientation change. Notches and system bars shift the available-desktop figures too, which is normal behavior of the underlying APIs.
Browsers sync animation frames to vsync and typically cap at 60 Hz unless the page is marked as animation-critical; power-saving modes and battery saver also clamp it. A reading of about 60 on a 120 Hz panel is a browser limit, not a screen fault, and this page cannot prove the higher rate — it can only show what it actually achieves.
No. The report is assembled from local browser APIs (window.screen, matchMedia, requestAnimationFrame) inside this page and never sent anywhere. The copy button only puts text on your own clipboard.
If you just finished with Screen Resolution Checker, the natural next steps are Keyboard Tester, Metronome, Camera & Mic Test, or browse every tool in Daily Tools.