ERROR: ADOBE APP HIGH DPI 4K SCALING ISSUE.
Installing Adobe Creative Cloud software apps on your PC with a high DPI or 4k monitor, may cause a common problem that displays the menu, fonts and icons very small.
This Adobe App scaling issue incorrectly scales the start screen and panels while makes it appear tiny or offset.
This issue may or may not occur based on the hardware and or Adobe application being used but in this case, the specifications were as follows:
- • Hardware: Microsoft Windows Surface Laptop
- • OS: Windows 10
- • Monitor Display: 13.5″ 2256 x 1504 (201 PPI)
- • Adobe application: Photoshop, Illustrator, InDesign
This Adobe App Scaling issue on High DPI Displays isn’t specific to the specifications above and the solution below should also be applicable for other Adobe applications while using high resolution monitors and 4k displays.
SOLVED: ADOBE APP HIGH DPI 4K SCALING ISSUE
In the solution below, we’ll use Adobe Photoshop as the example but the solution should also fix issues with other Adobe Creative Cloud apps. There are other ways to tackle this problem but the method discussed will the fastest and easiest way without getting too intrusive with editing system files.
Fix-time: 1 minute
- Close your Adobe Photoshop application if opened.
- Locate the “Photoshop.exe” file in Program Files or right-click on Photoshop desktop icon and click Properties.
- Once in Properties, select the “Compatibility” tab and click the “Change high DPI settings” button.
- Make sure “Override high DPI scaling behavior” is checked.
- From the “Scaling performed by:” drop-down menu, select either “System” or “System (Enhanced)”.
- Click OK, and from Properties, click Apply then OK.
- Launch Adobe Photoshop and the menu and icons should be larger and legible.
One caveat is that the start screen, menus, icons, and panels may seem slightly pixelated and not as sharp as it could be. This is because Photoshop does not support the Override high SPI scaling behavior function.
Comment below if anybody found a workaround to fix this but it appears a solution does not exist unless Adobe decides to support this function in the future.