TestMyGears

Display testing

How to Verify Native Resolution, DPR & OS Scaling

4 min read

Confirm your panel runs at native resolution and correct device pixel ratio before pixel tests. Troubleshoot scaling mismatches, fake 4K claims, and multi-monitor setup.

Open the resolution checker on the display you want to verify, set browser zoom to 100%, and compare Screen resolution (OS reported), Viewport (CSS pixels), and Physical pixels (viewport × DPR). Mismatch between advertised specs and live numbers is a red flag before you run pixel or color tests.

Screen resolution is how many pixels the operating system drives to the panel. Viewport is the browser window in CSS pixels — it shrinks when you resize or zoom. Device pixel ratio (DPR) maps logical pixels to physical pixels: DPR 2 on a 1920×1080 logical desktop often means ~3840×2160 physical output.

Screen resolution vs viewport vs DPR

ReadingMeaningExample
Screen resolutionOS-reported display size2560×1440 on a 27” QHD monitor
ViewportBrowser window in CSS px1920×947 with taskbar and chrome visible
DPRPhysical ÷ CSS pixel ratio2.0 on Retina MacBook or iPhone
Physical pixelsViewport × DPR3840×1894 at 2x DPR

For warranty checks, compare screen resolution and DPR to the manufacturer spec sheet — not just the window size.

One-minute resolution check routine

  1. Set OS scaling intentionally — use 100% on Windows/Linux for desktop QA, or your daily scaling if you are troubleshooting blur.

  2. Set browser zoom to 100% — Ctrl+0 (Cmd+0 on Mac). Zoom skews viewport readings.

  3. Open the resolution checker on the target display. On multi-monitor setups, drag the window to each screen separately.

  4. Maximize or fullscreen if you need viewport to closely match full panel size.

  5. Read screen resolution — should match native spec (e.g. 3840×2160 for 4K, 1920×1080 for FHD).

  6. Check DPR — Retina laptops and phones typically show 2.0 or higher; a “4K” claim with DPR 1 and 1920×1080 screen size suggests upscaling.

  7. Resize the window — viewport should update live; physical pixels recalculate automatically.

  8. Rotate phones/tablets — orientation swap confirms both width and height match model listings.

Common resolution targets

LabelTypical pixelsCommon devices
1080p FHD1920×1080Budget monitors, many laptops
1440p QHD2560×144027” gaming and creator monitors
4K UHD3840×2160TVs, high-end monitors, some laptops
Phone FHD+~1080×2400Mid-range Android
Phone QHD+~1440×3200Flagship OLED phones

Small gaps (e.g. 2560×1440 vs 2559×1439) can come from taskbars or scaling. Large gaps mean wrong display selected or a capped cable.

Why readings might look wrong

  • Wrong monitor — laptop lid vs external display; test ran on secondary 60Hz screen.
  • Browser zoom — always reset to 100% before comparing to specs.
  • OS scaling above 100% — lowers CSS viewport; physical pixel count may still be correct.
  • Remote desktop / VM — often reports host resolution, not your physical panel.
  • HDMI bandwidth cap — panel connected but OS limited to 1080p on an old port.

Fix cable, port, and scaling first, then re-run the checker before opening an RMA.

Pair with sizing and display checks

Resolution confirms the panel pipeline; it does not test color or motion:

When numbers are “good enough”

  • Screen resolution matches manufacturer spec for the active display.
  • DPR aligns with known Retina / HiDPI ratings for your model.
  • Viewport at maximized window is within expected range for your OS chrome and taskbar.

Screenshot the readout if you are inside a return window — evidence helps when a seller claims “works as designed.”

Keep learning: How to calculate aspect ratio · How to test refresh rate · Monitor screen test

← Back to guides