Remote Desktop Slow or Laggy? 9 Fixes That Work

Short answer: a slow Remote Desktop is usually caused by distance to the server or a weak connection, less often by the server itself. Check the ping first, pick the connection setting that matches your network, lower the resolution and visual effects, and look at Task Manager on the server. The nine fixes below go from the most common cause to the least.

"Slow" can mean two things: input lag (you type, the letter appears late) points to latency; a blurry, choppy picture points to bandwidth. Keep that in mind as you go through the list.

011. Check the Ping

Open a terminal on your own computer and run:

ping your-server-ip

If the ping is high, the server is far away. A Windows RDP in Amsterdam, Frankfurt or Warsaw suits Europe, New York the Americas, Hong Kong Asia. Windows Server's own firewall doesn't answer ping by default; if you get no reply, use the signal icon in the Remote Desktop connection bar instead, or ping the server from a Linux VPS in the same location.

022. Set the Connection Speed

In the Windows Remote Desktop client (mstsc), open Show Options → Experience and pick the speed that matches your network instead of "Detect connection quality automatically" if auto-detect guesses wrong. On mobile hotspots, "Low-speed broadband" often feels better than the default.

033. Lower the Resolution and Colours

Every pixel has to cross the network. Under Display, choose a smaller window size instead of full screen on a 4K monitor, and High Color (16 bit) instead of 32 bit. This helps most on slow or busy connections.

044. Turn Off Visual Effects

Under Experience, untick Desktop background, Font smoothing, Desktop composition, Show window contents while dragging, and Menu and window animation. On the server itself, sysdm.cpl → Advanced → Performance → Adjust for best performance does the same.

055. Let RDP Use UDP

RDP is faster over UDP than TCP on unstable links. Windows uses both when it can. If the firewall on your server page only allows TCP 3389, add UDP 3389 too. In mstsc you can see what's used: click the connection bar's signal icon.

066. Use Cable or 5 GHz Wi-Fi

Packet loss on Wi-Fi feels worse than a high ping. If the lag comes and goes, try a cable or move closer to the router, and close downloads or video calls on the same network.

077. Check the Server Itself

Inside the RDP session, open Task Manager (Ctrl+Shift+Esc):

• CPU near 100% for a long time: a program is busy; close it, or move to a plan with more vCPU.
• Memory above about 90%: Windows starts swapping to disk and everything slows down; close browser tabs or take more RAM.
• Disk at 100% right after setup: Windows Update or Defender is running its first scan. Give it a while.

The Windows plans start at 2 vCPU and 6 GB RAM ($13/month). Several browsers or many trading terminals at once may need 4 vCPU and 8 GB ($26/month).

088. Use a Current Client

On Windows, mstsc is fine. On Mac, iPhone and iPad, use Microsoft's Windows App (it replaced "Microsoft Remote Desktop"). Old third-party clients often lack UDP and the newer codecs. How to connect lists the right app for each system.

099. Don't Stream Video Through RDP

Video and fast-moving content are the hardest thing for RDP. Watching videos or playing games through a server will stutter on almost any connection. That's how the protocol works, not a fault.

10Still Slow?

1. 1Compare at a different time of day: evening congestion at your ISP is common.
2. 2Try from another network, for example a phone hotspot. If that's fast, the problem is your home connection.
3. 3Reboot the server from your server page if it has run for weeks and feels sluggish.
4. 4Open a ticket with the ping result and a screenshot of Task Manager, and we'll look at it.

If you can't connect at all, that's a different problem: see Remote Desktop Can't Connect? 10 Fixes.