📊 Screen Info
Comprehensive information about your display - resolution, size, pixel density, color space, and more.
Resolution
Pixel Density
Color Space
Refresh Rate
Device Type
Browser
📏 Measure Physical Size
To calculate accurate PPI, we need your screen's physical size. Use a ruler or credit card to measure.
💳 Credit Card Method
A standard credit card is 3.375 inches (85.6mm) wide. Place it on your screen and adjust the box below to match.
🔧 Technical Details
🔧 Common Issues & Solutions
🖥️ "Browser shows 1920x1080 but Windows says 2560x1440" (Logical vs physical resolution)
What's happening: DPI scaling confusion. Windows 10/11 scaling affects reported resolution. Physical resolution: Actual pixels on panel (2560x1440). Logical resolution: What apps/browsers see after scaling (1920x1080 at 133% scale = 2560x1440 physical). JavaScript window.screen reports logical pixels, not physical. Example: 4K monitor (3840x2160) at 150% scaling reports 2560x1440 to browser. Chrome DevTools: Shows CSS pixels (logical), not device pixels (physical).
Device Pixel Ratio (DPR): Multiplier between logical and physical. DPR 1.0 = no scaling (100%), DPR 1.5 = 150% scaling, DPR 2.0 = 200% (Retina/HiDPI). To get physical resolution: logical width × DPR = physical width. Why this matters: Web developers see logical pixels. Graphics/games use physical pixels. Screenshots capture physical pixels. Browser viewport != full screen resolution if taskbar visible. window.screen.width includes all monitors (incorrect), use window.innerWidth for viewport.
✅ Solution: Check Windows Settings → Display → Resolution (shows physical resolution). Check DPR: JavaScript window.devicePixelRatio or this page. Calculate physical: screen.width × DPR. For true panel specs: Right-click desktop → Display Settings → Advanced → Monitor properties → shows native resolution. NVIDIA Control Panel → Change Resolution → lists native resolution. Use DisplayCAL or monitor test software to detect true panel resolution. Common confusion: 1080p laptop at 125% scale reports 1536x864 to browser but is 1920x1080 panel.
🔬 "Calculated PPI doesn't match monitor specs" (Marketing PPI vs actual)
What's happening: PPI formula: √(width² + height²) ÷ diagonal inches. Example: 27" 1440p: √(2560² + 1440²) ÷ 27 = 108.79 PPI (often rounded to 109 PPI in specs). Manufacturer specs may lie: List "110 PPI" when actual is 109 (rounding up). List diagonal including bezel (27.2" viewable but sold as 27"). Some ultrawide specs use 21:9 diagonal math incorrectly. Actual vs advertised size: 27" monitor may have 26.8" viewable diagonal (bezel eats 0.2"), affecting PPI by 1-2%.
Why PPI matters: Determines text/UI size at 100% scaling. 90-110 PPI: Comfortable for most users. 110-140 PPI: Small but usable. 140-180 PPI: Needs scaling for comfortable reading. 180+ PPI: Retina class, requires 150-200% scaling. Common PPI values: 24" 1080p = 92 PPI, 27" 1440p = 109 PPI, 27" 4K = 163 PPI, 32" 4K = 138 PPI, 24" 4K = 184 PPI. Apple: 27" 5K iMac = 218 PPI (true Retina at 2x). Pixel pitch: mm per pixel = 25.4 / PPI. 109 PPI = 0.233mm pixel pitch.
✅ Solution: Calculate PPI yourself: Measure diagonal with ruler (exclude bezel, measure glass corner to corner). Use formula above with your measured size. Check reviews: RTINGS, TFTCentral measure actual viewable diagonal and calculate real PPI. For multi-monitor: Matching PPI critical - 109 PPI (27" 1440p) + 92 PPI (24" 1080p) = text size mismatch. Buy identical monitors or match PPI manually. Professional work: 109-138 PPI range ideal (27" 1440p or 32" 4K). Gaming: PPI less critical, refresh rate more important. Retina equivalent: 220+ PPI at 2x scaling.
⚡ "Refresh rate shows 59.94Hz instead of 60Hz" (NTSC video timings)
What's happening: 59.94Hz is correct for many displays. NTSC video standard: 59.94Hz (not 60Hz exactly). HDMI/DisplayPort: Can carry 59.94Hz or 60Hz timings. Why 59.94Hz exists: NTSC TV standard from 1950s-60s used 59.94 fields/sec (29.97 fps interlaced) for color broadcast compatibility. Computer displays inherited this via HDMI. DisplayPort vs HDMI: DP more likely to use true 60.00Hz. HDMI more likely 59.94Hz (video standard). Difference: 0.1% slower, imperceptible in practice.
Browser/OS reporting: Chrome DevTools: May round 59.94 to 60. JavaScript requestAnimationFrame: Syncs to actual refresh (59.94 or 60). Windows: Display Settings shows "60 Hz" but may be 59.94 Hz actual. Check with UFO test (testufo.com) or frame time measurement. Gaming impact: Minimal - 59.94Hz vs 60Hz = 0.01ms frame time difference. 144Hz monitors: Usually true 144.00Hz, not 143.86Hz. 240Hz: True 240.00Hz. Variable Refresh Rate (VRR): G-Sync/FreeSync eliminates refresh rate mattering for gaming.
✅ Solution: 59.94Hz is normal and fine - don't try to "fix" it. If you want true 60.00Hz: Use DisplayPort (not HDMI), check advanced display settings. NVIDIA Control Panel → Change Resolution → Customize → Create custom resolution → 1920x1080 @ 60.00Hz (may not work on all monitors). AMD: Radeon Settings → Display → Custom Resolutions. Test with testufo.com to measure actual refresh rate. For competitive gaming: 144Hz+ matters far more than 59.94 vs 60. Variable refresh rate (G-Sync/FreeSync) makes fixed refresh irrelevant - enables VRR instead.
🌈 "HDR monitor but Windows doesn't detect HDR" (HDMI 2.0, cable, drivers)
What's happening: HDR requires specific hardware chain. Monitor must support HDR10 (DisplayHDR 400/600/1000 certification). HDMI 2.0+ or DisplayPort 1.4+ required for 4K HDR. HDMI 1.4 can't carry HDR metadata. Cable matters: Cheap HDMI cable may not support 18 Gbps (HDMI 2.0 spec). Use certified "Premium High Speed HDMI" or "Ultra High Speed HDMI" (HDMI 2.1). DisplayPort: Use certified DP 1.4 cable (some DP 1.2 cables fail at 4K HDR).
Windows HDR requirements: Windows 10 1809+ or Windows 11. GPU: NVIDIA GTX 10-series+, AMD RX 400+, Intel UHD 600+. Enable in Settings → Display → HDR → "Use HDR" toggle (only appears if HDR detected). Common failures: Monitor in SDR mode (check OSD, enable "HDR mode"). GPU driver outdated (update NVIDIA/AMD/Intel). HDCP 2.2 handshake fail (try different HDMI/DP port). Hub/adapter in chain: Most USB-C hubs don't support HDR passthrough. Fake HDR: DisplayHDR 400 certification = barely HDR (no local dimming). DisplayHDR 600+ for real HDR experience.
✅ Solution: Verify cable: Use HDMI 2.0+ or DP 1.4+ certified cable (look for label/packaging). Try different port on monitor and GPU. Update GPU drivers: NVIDIA GeForce Experience, AMD Adrenalin, or Intel Graphics Command Center. Enable HDR in monitor OSD: Look for "HDR," "Game Mode," or "DisplayHDR" setting. Windows: Settings → Display → Windows HD Color settings → Play HDR games and apps = On. Test with HDR content: Netflix HDR, YouTube HDR, or Windows HDR Calibration app. If still not working: Check monitor specs - some "HDR compatible" monitors lack HDR10 certification (marketing lie).
🎨 "Browser says sRGB but monitor claims DCI-P3/Rec.2020" (Color space vs coverage)
What's happening: Color space != color gamut. sRGB: Standard RGB, 100% = ~35% of visible colors. DCI-P3: Digital cinema, 125% of sRGB, more saturated reds/greens. Rec.2020: Future TV standard, 170% of sRGB, most monitors can't achieve. Browser detection: CSS media query @media (color-gamut: srgb/p3/rec2020) tests if browser/OS thinks display supports it. Many monitors claim "95% DCI-P3" but OS reports sRGB (no wide gamut ICC profile loaded).
Why mismatch occurs: Monitor physically supports P3 gamut but Windows uses sRGB color profile by default. ICC profile not installed: Manufacturers provide .icm/.icc files (often not installed). macOS: Automatically detects wide gamut displays (MacBook Pro, iMac). Windows: Requires manual color management. Gamut coverage specs: Marketing lies: "90% Adobe RGB" may only be 70% measured (check RTINGS/TFTCentral). sRGB is enough for web/gaming. DCI-P3 for HDR content, photography. Adobe RGB for print work. Browser color management: Chrome respects ICC profiles, Firefox can too (gfx.color_management.mode), Safari best on macOS.
✅ Solution: Install monitor ICC profile: Download from manufacturer website or use colorimeter (X-Rite i1Display Pro, Datacolor SpyderX) to create custom profile. Windows: Settings → Display → Advanced → Color management → Add profile → Set as default. Verify in browser: Chrome DevTools → Rendering → Emulate CSS media → color-gamut (should show p3 if profile loaded). For wide gamut work: Calibrate with hardware colorimeter, target DCI-P3 or Adobe RGB. For web/gaming: sRGB enough - P3 oversaturates colors unless content mastered for it. Check reviews: Many "P3" monitors only cover 80-90% P3 (measured), not 100%.