New to Telerik UI for WinForms? Download free 30-day trial

DPI Support

Telerik UI for WinForms suite gives your Windows Forms applications a new power today - built-in support for high resolution DPI monitors.

In R2 2017 we introduced built-in HDPI support in the Telerik UI for WinForms suite. This coincides with the HDPI improvements Microsoft is bringing with .NET 4.7 and the Windows 10 Creators Update. The best part is that you will get this support no matter which .NET framework you are targeting (currently supported from .NET 2.0 and up).

With R2 2022 we have introduced some improvements in the HDPI scalling in Telerik UI for WinForms suite. Read More

All you will have to do is to declare your application as DPI aware and all RadControls will scale their UI elements in accordance to the current DPI settings automatically. To do that, you have to add an app.manifest file and/or an app.config file with several lines of code. You can see examples of that in our blog post on the High DPI in WinForms matter. We will look into the technical details further down this article.

With the changes we have introduced, the common problem of bad scaling when your applications run on high resolution monitors goes away. So, your app will ship with higher quality on more systems instantly. The problem with the blurry fonts and unreadable texts will be eliminated and the potential of modern hardware will be utilized fully.

In order to produce as good layout as possible when running your application on monitors with different DPI scaling, it is important to have some thoughts in mind before you start designing the application: HDPI Tips and Tricks.

Although it is a bit tricky to demonstrate HDPI support with a single image, here is an example with screen shots of the same application on two different monitors. You will notice that the first image will become blurry, unlike the second one.

Resolution: 3840 x 2160 - Scaling: 250%
dpi-support 001
dpi-support 002

There are four different DPI awareness modes in Windows.

  • Unaware – bitmap stretching is used.
  • System – Introduced in Windows Vista. The OS treats all displays with same DPI of the primary display. Bitmap stretching is used.
  • Per-Monitor – Introduced in Windows 8.1. Every display has its own DPI and the application window is notified of DPI change.
  • Per-Monitor V2 – Introduced with Windows 10 Creators Update (1703). On top of the previous mode there is automatic scaling of the non-client area and certain controls and dialogs.

How to Enable HDPI Support in Your Application

When building a DPI-aware application, firstly you must declare it as such, so the OS would know how to handle it. Furthermore, you can have DPI awareness per process or per thread.

There are two main approaches for making your application DPI aware:

Application Manifest File

The most common way to declare an application as DPI aware is through the application manifest file. There are two settings that you can use - <dpiAware> and <dpiAwareness>. Here is a small table that describes the different states that you can use with each setting:

Minimum Supported OS States DPI Mode
<dpiAware> Windows Vista
System aware
Per-monitor aware
<dpiAwareness> Windows 10, version 1607
System aware
Per-monitor aware
Per-monitor-v2 aware

You can use both settings in the manifest file. If so, Windows 10, version 1607, will ignore <dpiAware> and use only the newer <dpiAwareness>. Older versions will ignore <dpiAwareness>. Here is how the manifest should look if you want to configure DPI awareness for different Windows versions.

<?xml version="1.0" encoding="utf-8"?>
<asmv1:assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1"
                xmlns:asmv3="urn:schemas-microsoft-com:asm.v3" >
  <assemblyIdentity version="" name=""/>

    <asmv3:windowsSettings xmlns="">
      <dpiAware xmlns="">true/PM</dpiAware>
      <dpiAwareness xmlns="">PerMonitorV2</dpiAwareness>

  <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
      <!-- A list of all Windows versions that this application is designed to work with. 
      Windows will automatically select the most compatible environment.-->
      <!-- Windows 10 -->
      <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
      <!-- Windows 8.1 -->
      <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
      <!-- Windows Vista -->
      <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
      <!-- Windows 7 -->
      <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
      <!-- Windows 8 -->
      <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>


Applications not manifested for Windows 8.1 or Windows 10 will return the Windows 8 OS version value (6.2). It is mandatory to manifest your applications for Windows 8.1 or Windows 10. Please refer to Targeting your application for Windows.

Note that declaring DPI awareness in the app.manifest file breaks ClickOnce applications. The following KB article demonstrates how to deal with this problem: ClickOnce Application is Broken.

App.Config File

Another way that was introduced for Windows Forms in .NET Framework 4.7 is in the app.config file. Microsoft added a new element to add different features to a Windows Forms app called . In order to use it you need to do the following:

  • Declare compatibility with Windows 10 in the app.manifest file:

 <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
    <!-- Windows 10 compatibility -->
    <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}" />

  • Use the new element in the app.config file:

  <add key="DpiAwareness" value="PerMonitorV2" />

With the element you can set other DPI features as well. For more information you can check this article.

Using <dpiAware>/<dpiAwareness> in the manifest file overrides the settings defined in the app.config file.

In R3 2017 we introduced the EnableDpiScaling property that allows you to enable/disable this on a global level. This is a static property of RadControl and must set before any controls are initialized. For example in the form's constructor.

In R2 2020 SP1 we introduced the EnableImageDpiScaling property indicating whether the RadControls scaling logic will be used to resize the images when the application is run in a high DPI environment. This is a static property of RadControl and must set before any controls are initialized. For example in the form's constructor.

Native API

Even though it is not a common approach, there are several native API calls that can set awareness. Additional information is available in this blog post.

Static Method in .NET Core 3.0/.NET5 Preview

With .NET Core 3.0 Microsoft introduced a new way to set a high DPI mode for Windows Forms. A static method called Application.SetHighDpiMode(HighDpiMode), where HighDpiMode is enum with the following values:

  • DpiUnaware
  • SystemAware
  • PerMonitor
  • PerMonitorV2
  • DpiUnawareGdiScaled

The call must be done at the application entry point. If you have used a manifest file to set the DPI awareness mode, this method call will fail.

HDPI Scale Improvements

With the R2 2022 we have added some improvements to how our controls are scaled in their parent Forms/RadForms. The introduced improvements are listed below.

These new functionalities are controlled by the static RadControl.EnableRadAutoScale property. In a case, you want to disable these improvements you can set it false.

  • RadControl is dynamically scaled now when it is added runtime.
  • RadControl is scaled correctly in a System.Windows.Forms.Form.
  • RadControl is scaled correctly in an UserControl.
  • Scaling works in all .NET versions and DPI Awareness modes combinations except in .Net4 Framework. In this version, the scaling will not work in Microsoft Form.
  • Fixed various DPI-related scaling issues.

See Also

In this article