How to fix a blurry or fuzzy image over an RDP connection

A remote desktop that looks soft, smeared, or scaled to the wrong size is one of the most common complaints after a first connection to a Windows VPS or dedicated server. The cause is almost always display scaling on the local computer or an image quality setting in the connection, not the graphics hardware on the server. This tutorial matches the symptom to one of three cause families and corrects it.

Audience level: Beginner to intermediate Estimated completion time: 20 minutes End goal: By the end of this tutorial, your RDP session renders at the correct scale with a sharp image, and you know which setting caused the original blur.

Quick triage

Read the four symptoms below and go directly to the matching section. Working through the sections in order is not required.

• The whole image is soft or smeared, including graphics and window borders, not only text: go to Cause 2: image quality and compression.
• The image is sharp but text and icons are too small to read comfortably: go to Cause 1: DPI and display scaling.
• The image is sharp until you move the session window to another monitor, then it turns blurry: go to Mixed-DPI multi-monitor setups in Cause 1.
• Everything is at a low resolution that cannot be raised, and colors look flat: go to Cause 3: display adapter and driver on the server.

Prerequisites

• A Windows VPS or dedicated server that accepts RDP connections. The server-side steps in this tutorial were written for Windows Server 2022 and Windows Server 2025.
• The Remote Desktop Connection client (mstsc.exe) on the local computer, running on Windows 10 or Windows 11.
• Network access to the RDP port of the server, TCP 3389 unless the port was changed.
• Administrator rights on the server for the server-side image quality settings. The client-side settings require no elevated rights.
• Assumed knowledge: opening Show Options in the Remote Desktop Connection client, navigating Windows Settings, and using Local Group Policy Editor (gpedit.msc).
• Time required: approximately 20 minutes, including reconnects.

Cause 1: DPI and display scaling

Scaling problems produce a picture that is technically correct but uncomfortable to work with: text is crisp yet tiny, or the session looks stretched. This family accounts for most reports from high-DPI laptops and from workstations with monitors of different sizes. Nothing on the server has to change to fix it.

RDP display resolution

Start the Remote Desktop Connection client, select Show Options, and open the Display tab. The slider under Display configuration sets the resolution the session negotiates at connect time, from a small fixed size up to Full Screen. Move it to the right so that the session matches the native resolution of the monitor you work on, then connect. The desktop appears at full sharpness because every remote pixel maps to one local pixel.

Lowering the resolution to make text bigger is the wrong trade. A session at a lower resolution than the window it is displayed in has to be stretched, and stretching is what produces the soft edges. Keep the native resolution and change the scale factor instead, as described in the next two sections.

The classic client negotiates the session resolution when the connection opens. If you resize the window afterwards, the session either gains scroll bars or is scaled, depending on the smart sizing setting. Reconnect after any change to the Display tab.

Windows display scaling on the local computer

The scale factor of the remote session follows the scale factor of the local computer in current client and server combinations, so the local setting is the one to check first. Open Settings, select System, then Display, and look at the Scale value under Scale and layout.

Test the values Windows offers rather than forcing 100 percent. On a laptop with a high pixel density, the recommended value is often 150 percent or 175 percent, and dropping to 100 percent makes both the local desktop and the remote session unreadable. Change the value, reconnect the session, and judge the result at the size you actually work at. Note that a remote session does not expose its own scaling control, so this adjustment belongs on the local computer. [VALIDATE the behavior of the Display settings page inside an active session on Windows Server 2022 and 2025]

Remote session scale factor

An explicit scale factor for the session can be written into the connection file. Save the connection first: on the General tab select Save As and store the .rdp file, then open that file in a text editor and add the property.

desktopscalefactor:i:150

Accepted values start at 100 and rise in steps, with 100, 125, 150, 175, and 200 covering practical use. Save the file and start the connection from it. The session desktop appears at the same resolution as before, with interface elements drawn larger.

Smart sizing

Smart sizing tells the local client to fit the remote desktop into whatever size the session window currently has. When the window and the session resolution do not match, the client scales the received bitmap, and scaling a bitmap is a lossy operation: text edges thicken and fine lines lose contrast.

The property in the connection file is written as follows.

smart sizing:i:0

A value of 0 keeps the session at its negotiated resolution and adds scroll bars when the window is too small. A value of 1 stretches the session to the window. The same option is available while connected, from the menu in the connection bar at the top of the session window. Turn smart sizing off whenever the priority is a sharp image, and leave it on only when fitting a large remote desktop into a small window matters more than clarity. [VALIDATE the label and location of the Smart Sizing option in the connection bar menu on current client versions]

Mixed-DPI multi-monitor setups

The client reads the scale factor of the display it starts on and applies it for the session. Dragging the session window to a second monitor with a different scale factor leaves the session rendering at the original factor, and the operating system scales the result to fit. Blur that appears only after the window is moved has this cause and no other.

Three measures address it. Keep the session window on one monitor for the length of the session. Where the hardware allows, set the same scale factor on every monitor you use for remote work. After any change to a scale factor, disconnect the session and connect again so that the client picks up the new value. [VALIDATE per-monitor DPI behavior of the inbox client when the session window is moved between monitors with different scale factors]

Cause 2: image quality and compression

When the entire picture is soft, including photographs, gradients, and window chrome, the session is being delivered at reduced quality. Two layers decide that quality. The client asks for a set of visual features based on the connection speed you declare, and the host encodes the screen according to its own graphics policies. Check the client first, since it needs no administrative rights and no effect on other users.

Connection speed preset in mstsc

In the Remote Desktop Connection client, select Show Options and open the Experience tab. The list at the top, labeled Choose your connection speed to optimize performance, ranges from a modem profile through several broadband profiles up to a LAN profile, with an option that detects the connection quality automatically. The low-bandwidth profiles switch off visual features deliberately, and a profile chosen once for a slow hotel connection stays in the saved connection file afterwards.

Select the LAN profile on a fast link, or the automatic detection option on a link whose quality varies. Reconnect and compare: the desktop background returns, window animations reappear, and the general softness disappears if this was the cause. The equivalent property in the connection file is connection type, and the value that corresponds to the LAN profile is written as follows.

connection type:i:6

[VALIDATE the exact option labels in the Choose your connection speed to optimize performance list on current client versions]

Individual Experience toggles

Below the connection speed list, the same tab exposes the individual features as check boxes: Desktop background, Font smoothing, Show window contents while dragging, Menu and window animation, Visual styles, and Persistent bitmap caching. Selecting a connection speed profile sets these boxes for you, and each one can also be set by hand.

Font smoothing is the toggle that matters most for perceived sharpness. With font smoothing disabled, text is delivered without antialiasing and looks rough or jagged rather than soft, which readers often report as blur. Leave it enabled for any session used for reading or writing text. Persistent bitmap caching reduces retransmission of unchanged screen areas and is worth keeping enabled on a slow link. Visual styles affect appearance rather than sharpness.

The matching properties in the connection file are written as follows.

allow font smoothing:i:1
bitmapcachepersistenable:i:1
disable wallpaper:i:0
disable themes:i:0

[VALIDATE these property names and the visible effect of each one during the client-side GUI pass]

Color depth

Color depth sets how many bits describe each pixel in the session. At a reduced depth, smooth gradients break into visible bands and photographs pick up a blotchy texture, which is easily mistaken for a focus problem. The connection file property carries the value in bits per pixel.

session bpp:i:32

A value of 32 requests the highest quality the connection supports. Older clients exposed the same choice as a Colors list on the Display tab. Reconnect after the change and look at a photograph or a gradient wallpaper: banding that disappears confirms the diagnosis. [VALIDATE whether the Colors control is still present on the Display tab in current client versions]

Server-side RemoteFX and H.264/AVC graphics

If the client settings are already correct and every client that connects to the same server reports the same softness, the encoding policy on the host is the remaining suspect. Sign in to the server over RDP, start gpedit.msc, and expand Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, and finally Remote Session Environment.

Two policies in this node govern how the session is encoded. Configure image quality for RemoteFX Adaptive Graphics selects the quality level of the adaptive encoder, and it offers four levels: Lossless, High, Medium, and Low. With the policy left at Not configured, the host encodes at Medium. A host that was set to Low earlier to save bandwidth delivers a soft session to every client no matter how each client is configured. Prioritize H.264/AVC 444 graphics mode for Remote Desktop Connections requests the codec mode that preserves color detail in text and line graphics when both client and host support it. Where image quality matters more than bandwidth, set the image quality policy to High or Lossless and enable the AVC 444 policy.

Note the current state of each policy before changing anything. After a change, apply the policy and reconnect.

gpupdate /force

Sessions already connected keep their previous encoding settings.

Cause 3: display adapter and driver on the server

The display adapter on the server is the rarest cause and the one most often blamed. It is worth checking only when the symptoms point to it specifically.

Two symptoms indicate a genuine adapter or driver problem. The first is a resolution ceiling: the Display tab offers a higher resolution, but the session opens at a low one and refuses to go higher regardless of client settings. The second is an explicit driver fault in Device Manager.

To check, connect to the server, start devmgmt.msc, and expand Display adapters. The name listed there depends on where the reading is taken. Outside an active RDP session, at the console of the server, the host reports Microsoft Basic Display Adapter. Inside an active RDP session the display path is served by Microsoft Remote Display Adapter. Neither name is a fault in itself, and a healthy entry of either kind carries no warning icon. A yellow exclamation mark, or an entry listed under Other devices instead, means the driver did not load.

Repair a genuine fault by installing the correct driver for the platform: the guest tools package supplied by the virtualization platform for a virtual server, or the vendor driver for the physical graphics adapter on a dedicated server. Restart the server after installation and connect again. The session now negotiates the resolutions the adapter supports.

[VALIDATE the in-session adapter name and the exact wording of the Device Manager driver error state; both are confirmed during the screenshot capture pass]

Verification

Reconnect the session and check the result against the symptom you started with.

For a scaling problem, open a text-heavy window such as Notepad or the Settings app in the session. Text is readable at the working distance, window borders are single crisp lines, and the session shows no scroll bars at the resolution you selected.

For an image quality problem, display an image with a smooth gradient, or set a photographic desktop background. The gradient shows no banding and no blocky artifacts, and the edges of icons are clean rather than fringed.

For an adapter problem, confirm in Device Manager that Display adapters lists an entry with no warning icon, keeping in view that the reported name differs inside and outside an RDP session, then confirm that the session runs at the resolution requested in the Display tab. The current session resolution can be read from PowerShell in the session.

Get-CimInstance -ClassName Win32_VideoController | Select-Object 
Name, CurrentHorizontalResolution, CurrentVerticalResolution

The reported horizontal and vertical values match the resolution selected in the client, and the name returned is the adapter serving the active session rather than the one the host uses at its console. [VALIDATE the in-session output of this command on Windows Server 2022 and 2025, including the reported adapter name; confirmed during the screenshot capture pass]

Reverting changes

Server-side policy changes revert in Local Group Policy Editor. Return every policy you touched in Remote Session Environment to Not configured, which restores the default behavior of the host, then apply the change with gpupdate /force and reconnect.

gpupdate /force

Client-side changes are held in the .rdp connection file and in local Windows settings. Delete the property lines you added to the connection file, or connect once with a fresh Remote Desktop Connection client session that has no saved options, to return to defaults. A changed local scale factor reverts in Settings, System, Display by selecting the value Windows marks as recommended.

Troubleshooting

• Image is sharp but text is tiny. The session resolution is high relative to the physical monitor and the scale factor is too low. This is a scaling problem and not a driver problem. Raise the local scale factor and reconnect.
• The whole image is soft on a fast connection. A low connection speed profile is saved in the connection file, or the host is capping image quality. Check the Experience tab first, then the Configure image quality for RemoteFX Adaptive Graphics policy on the host.
• Blur appears only after dragging the window to another monitor. The monitors use different scale factors. Keep the session on one monitor, or match the scale factors and reconnect.
• Text looks rough and jagged rather than soft. Font smoothing is disabled for the session. Enable Font smoothing on the Experience tab.
• Resolution cannot be raised at all. The display adapter or its driver on the server is limiting the session. Check Display adapters in Device Manager.
• Gradients and photographs show visible bands. The client is requesting a reduced color depth. Set session bpp to 32 in the connection file and reconnect.
• Only one application looks blurry while the rest of the session is sharp. That application is not per-monitor DPI aware and kept the scale factor it started with. Restart the application, or sign out of the session and sign in again.

Conclusion and next steps

The image quality of an RDP session is decided in three places: the resolution and scale factor negotiated by the client, the visual features the client requests for the declared connection speed, and the encoding policy of the host. Working through them in that order resolves the great majority of blur reports without touching a driver, and it leaves a session configured for the connection you actually have. Record the settings that worked in a saved .rdp file so that the next connection starts from a known good configuration.

Related tutorials:

• Remote Desktop Connection via RDP
• Change Windows Server RDP port

Document Version: 1.1 | Last Updated: August 2026 | Owner: Technical Documentation Team