Frame rate is limited to 30 FPS in Windows-based remote sessions
This article provides a solution for remote desktop protocols to change the frame rate limit in a remote session.
Original KB number: 2885213
Setting frame rates
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For protection, back up the registry before you modify it so that you can restore it if a problem occurs. For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows.
To work around the issue, create a
DWMFRAMEINTERVAL entry in registry subkey
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations to change the maximum frame rate limit on the remote session host. To do this, follow these steps:
Start Registry Editor.
Go to the following registry subkey:
On the Edit menu, select New, and then select DWORD(32-bit) Value.
Type DWMFRAMEINTERVAL, and then press Enter.
Right-click DWMFRAMEINTERVAL, and select Modify.
Select Decimal, type 15 in the Value data box, and then select OK. This sets the maximum frame rate to 60 frames per second (FPS).
This registry entry sets the maximum frame rate limit that the remote display protocol can deliver to the remote session client. This setting does not set the actual frame rate for the remote session client. The actual frame rate in the remote session depends on other factors such as application and computer hardware resources. Additionally, not all remote display protocols support a frame rate that is greater than 30 FPS. For example, Remote Desktop Protocol (RDP) limits the frame rate to 30 FPS. Please contact the remote display protocol providers for more information.
Exit Registry Editor, and then restart the computer.
Frame rate mapping
- 15 decimal = 60 frames
- 10 decimal = 40 frames
- 5 decimal = 20 frames
- 1 decimal = 4 frames