Inspect screen, viewport, devicePixelRatio, and visualViewport in real time — with a tab-separated report you can paste into bug
tickets. Readings use normal browser APIs only; nothing is uploaded, matching
APK Analyzer and
APK String Extractor.
| Property | Value |
|---|
Pair with FPS Calculator for frame-time math and Viewport Resizer for iframe breakpoint checks.
Modern layout work bounces between CSS pixels, device pixels, and the layout viewport versus the visible visual viewport on mobile. This
page surfaces the usual suspects (screen, window.inner*, devicePixelRatio, and visualViewport when available) in one place — like how
APK Analyzer surfaces archive facts locally instead of hiding them behind a server.
screen.width/height describe the display in a CSS pixel coordinate system, while window.innerWidth/Height is the page viewport your document lays out into — minus
browser chrome, split tabs, and so on. Do not confuse them when filing “broken at 1920px” bugs without saying which number you mean.
Multiplying the inner viewport by devicePixelRatio gives a rough bitmap budget for full-bleed raster assets at current zoom. It is not a hardware EDID probe; for exact
panel diagnostics use OS tools or a calibration workflow.
No. Values come from standard browser APIs (screen, window, visualViewport) in your tab only — the same local-only approach as
APK Analyzer and
APK String Extractor.
Screen dimensions describe the display in CSS pixels; window.innerWidth/Height is the visible layout viewport inside the browser chrome, which excludes toolbars, sidebars, or
split windows.
It is innerWidth × devicePixelRatio and innerHeight × devicePixelRatio — a useful first guess for bitmap sizing, not a panel EDID readout.
It relates CSS pixels to device pixels for your current zoom/page. Values like 2 or 3 are common on “Retina” class displays; it can be non-integer when zoomed.
Zoom affects the CSS pixel grid and sometimes devicePixelRatio. Re-measure after changing zoom if you are debugging layout.
No — DevTools goes deeper. This page is a quick shareable summary for tickets, streams, and friends.
WebViews can report different chrome and sizes than standalone browsers. Always test on the actual wrapper you ship.
When supported, it reflects the visible viewport after mobile browser UI and pinch-zoom — useful on phones; it may be absent on older desktop engines.
Yes: nothing is transmitted to DroidXP for the readings. Only ordinary page assets load from the site or CDN.
Often yes — available height usually grows when browser chrome hides. Resize the window or toggle fullscreen and watch the live update.