WinEdt and dpi-awareness

Windows applications may be deployed on monitors with very different resolutions (form basic 96dpi to UHD 288dpi or more) and this presents developers with serious challenges. If you are new to the concept of dpi-awareness you can consult MS guidelines (if you find them complicated it is because they are indeed non-trivial):

Microsoft guide for dpi-aware applications

WinEdt 11 is system dpi-aware: it comes with high-quality graphic resources at different sizes and at startup it automatically adjusts its GUI to high-resolution displays (without stretched or blurred graphics and text). For most users this is the desired behavior. It has been extensively tested on 288dpi (300% magnifications). Its graphic controls have been adjusted for this version. Dpi-dependent settings for users that want to further adjust WinEdt's GUI have been simplified.

Windows 8 introduced per monitor dpi-awareness. In principle this makes it possible for applications to adjust to the resolution of the monitor on which they are paced rather than the system resolution of the primary monitor which may be different when multiple or external monitors are used. Alas, this functionality does not work properly for (desktop) MDI applications.

This being explained WinEdt will be subject to DPI Virtualization and scaling if placed on a secondary monitor with a different resolution than the primary one (Windows system dpi setting/ magnification). It this case it may appear blurry. Thus it is best to run WinEdt on a primary monitor or a monitor with the same resolution as the primary one.

WinEdtPDF is dpi-aware on per monitor basis and will work find on secondary monitors regardless of the resolution and magnification.

Note: WinEdt versions prior to 9 are not dpi-aware!

Example: WinEdt and its PDF Viewer next to each other on Windows 11 (with 288 dpi high resolution display):