DPI Scaling Calculator
Find the optimal Windows/macOS display scaling for your monitor
Enter Your Resolution
Input your monitor’s native resolution. Common resolutions: 1920x1080 (FHD), 2560x1440 (QHD), 3840x2160 (4K).
Enter Screen Size
Input your monitor’s diagonal size in inches. The calculator uses this with resolution to determine pixel density (PPI).
Apply Recommended Scaling
The calculator suggests optimal scaling based on a target of approximately 110 PPI effective density, which provides comfortable text and UI sizing.
Why Scale Matters
High-resolution displays pack more pixels into the same space, making text and UI tiny. Scaling enlarges everything proportionally for readability.
Integer Scaling
100%, 200%, 300% provide pixel-perfect rendering. Non-integer values like 150% may cause slight blurring in some apps.
Effective Resolution
At 150% scaling, a 4K display (3840×2160) renders UI as if it were 2560×1440, but with sharper text and graphics.
macOS vs Windows
macOS uses @2x Retina scaling (200%). Windows offers finer control with 25% increments. Both achieve similar results at proper settings.
Frequently Asked Questions
What DPI scaling should I use for a 4K 27-inch monitor?
At 163 PPI, a 27-inch 4K panel at 100% scaling renders text and icons at physically small sizes optimized for 96 PPI displays. Windows recommends 150% scaling (equivalent to a logical 2560×1440 resolution) for this panel, while macOS applies its 2x Retina mode (logical 1920×1080 equivalent). 150% is generally the sweet spot: text is crisp at full physical resolution with adequate size.
Why does my app look blurry on my high-DPI display?
Applications that are not DPI-aware render at the logical resolution and are upscaled by Windows using bitmap stretching, causing visible blur. You can force an app to use 'System (Enhanced)' or 'Application' DPI mode via Properties > Compatibility > Override high DPI scaling behavior. Modern apps using Win32 Per-Monitor DPI Awareness v2 (PMv2) or UWP/WPF with automatic DPI scaling render sharply at any scale factor.
What is the difference between 200% and Retina 2x scaling?
They are functionally equivalent: both render at exactly 2x the logical pixel count on each axis, resulting in 4 physical pixels per logical pixel. Windows achieves this at 200% DPI scaling; macOS at its Retina 2x mode. The result is that vector graphics, fonts, and properly implemented HiDPI assets render at full physical resolution sharpness, while non-HiDPI content is scaled bilinearly and appears slightly soft.
Can I use fractional DPI scaling like 125% or 150%?
Yes, but fractional scaling can produce blurry non-integer rendering unless the application fully supports Per-Monitor DPI v2. At 125% on a 1920×1080 display, Windows renders at a logical 1536×864 and then scales to 1920×1080 — not a clean integer ratio, so some elements blur. At 150%, a 1920×1080 display renders at a logical 1280×720 — also non-integer. For cleanest results, integer multiples (200% on a 1080p display, or 100%/150% on a 1440p display) are preferred.
Does DPI scaling affect GPU performance or frame rates?
In desktop applications, DPI scaling is handled by the CPU/compositor and has negligible GPU impact. In 3D games, the internal rendering resolution is controlled by the in-game resolution setting and resolution scale, independent of Windows DPI scaling. Running a game at a native 4K internal resolution is far more GPU-intensive than running at 1440p with 150% DPI scaling applied to the Windows desktop. Confusing OS scaling with game rendering resolution is a common misunderstanding.