Windows 10 Blurry Icons: What's Causing It and How to Fix It

Tech & Gaming
1

My desktop icons and some app windows started looking blurry after I moved to a higher-DPI monitor. Some things looked fine, some looked like they were rendering at half resolution and then being stretched. Took me a while to figure out this is a known issue with older apps and Windows’ DPI scaling system.

Here’s the full breakdown of what causes it and how to fix each case.

The root cause: DPI scaling and legacy app support

Modern displays run at higher pixel densities (150%, 175%, 200% scaling) because the physical pixel density is high. Windows has to scale UI elements up to be readable.

New apps are DPI-aware – they draw their UI using vector-based or high-res assets that look sharp at any scaling level. Old apps are not DPI-aware – they were designed for 100% scaling and Windows has to bitmap-scale them up, which creates the blurry effect.

Fix 1: Check your display scaling setting

Start simple. Right-click desktop > Display Settings > Scale. Set it to 100% if you’re on a monitor where 100% is readable. Many blurriness issues disappear at 100% because no scaling is happening. If 100% makes everything too small (likely on a high-DPI screen), proceed to the other fixes.

Fix 2: Per-app High DPI settings

This fixes blurriness in specific applications:

  1. Find the app’s .exe file (or right-click the shortcut > Open File Location)
  2. Right-click > Properties > Compatibility tab
  3. Click “Change high DPI settings”
  4. Enable “Override high DPI scaling behavior”
  5. In the dropdown, select “Application” or “System (Enhanced)” and test which looks better

“Application” lets the app handle its own DPI scaling, which usually looks sharper if the app supports it. “System (Enhanced)” uses Windows’ GDI scaling for apps that don’t have their own DPI handling.

Fix 3: Disable GPU anti-aliasing for the application (Nvidia)

If an app uses GPU-rendered UI and FXAA (Fast Approximate Anti-Aliasing) is enabled globally, it can cause the blurred-edge appearance on UI elements:

  1. Nvidia Control Panel > Manage 3D Settings > Program Settings
  2. Add the blurry application
  3. Set FXAA to Off for that specific program
  4. Apply and test

This is particularly relevant for games or apps with GPU-accelerated interfaces.

Fix 4: The System-wide “Fix blurry apps” setting

Windows has a setting that automatically adjusts blurry apps: Settings > System > Display > scroll down to “Fix apps that are blurry” or similar wording. Enable it. Windows will prompt you to relaunch apps when it detects blurriness.

The per-app Compatibility fix is more targeted and reliable for specific problem apps. The system-wide setting is better for catching everything.

This video goes through the display scaling check, the per-app Compatibility settings, and the Nvidia FXAA option in one run:

2

the per-app DPI override thing is genuinely something i didn’t know existed. i’ve been putting up with blurry git clients and terminal emulators on my external monitor for ages. going to go fix that now

3

The Nvidia FXAA point is a good one that doesn’t get mentioned often in standard DPI guides. FXAA is designed to smooth out jagged edges in games but it has the side effect of blurring sharp UI text and icons when applied globally. Disabling it per-application is the right approach.

4

The core problem – legacy apps not knowing about DPI – is going to persist for a long time. There’s a huge tail of enterprise and specialized software that hasn’t been updated in years and relies on Windows’ scaling shim. The Compatibility tab fix is going to stay relevant.

5

I had this problem with an older reading and annotation tool I use for student papers. The per-app override fix worked perfectly. Wish this was documented more prominently by Microsoft – it took me way too long to find it the first time.

6

The “Fix blurry apps” system toggle is worth trying first because it’s the lowest-effort option. In my experience it handles probably 60-70% of cases automatically. For the stubborn ones you need the Compatibility tab approach.