Remote desktop latency explained simply: why it lags and what helps

When you click in a remote session, a lot happens before you see the result:

• Your click travels from your computer to the remote PC.
• The PC does what you asked, and its screen changes.
• The PC captures the new picture and compresses it.
• The picture travels back to you.
• Your computer decodes it and draws it on your screen.

The time all that takes is the latency, or delay. Most of it is usually the two trips across the internet, which depend on the distance and the networks in between, not on how fast either PC is.

Delay

How long a round trip takes. High delay makes the mouse feel like it's dragging through mud, even when the picture is sharp.

Frame rate

How many new pictures arrive each second. A low frame rate looks jerky. It also adds to the delay you feel: after the PC has reacted, you may still wait for the next picture to be sent.

Bandwidth

How much data the connection can carry. When there isn't enough, the picture gets blurrier or the frame rate drops, because the PC adapts to fit. More bandwidth doesn't lower the delay, but too little makes everything worse.

The screen is sent from the PC you're reaching, so its upload speed is usually the bottleneck. Home internet often uploads far slower than it downloads. A PC on Wi-Fi far from the router, or one busy uploading a cloud backup, will feel slow to everyone who connects to it, however fast your own connection is. Mobile and satellite links vary through the day too; if the PC is on one, see remote access behind CGNAT, 4G/5G and Starlink for the settings that help.

In the RemoteAccessApp Console, press Ctrl+Alt+Shift+I during a session to open connection health. It rates the connection from Excellent to Poor with the reason, and shows how the PC is reached, the delay, frames received and shown, the speed in each direction, the codec and the picture size, with the last minute of delay and frame rate as small graphs. It also estimates the input delay: the delay plus the wait for the next frame. When things are bad, it suggests low-bandwidth mode, one click away.

The toolbar's signal bars show the same rating while the panel is closed. On the website, the session's settings show which codec is in use. Before you connect at all, our internet speed test for remote access measures the latency and download speed between your device and the RemoteAccessApp server.

• A cable on the remote PC. It usually helps more than anything else, because Wi-Fi adds delay and drops.
• Stop big uploads and downloads on either end while you work: cloud backups, game updates, video calls.
• Show one monitor instead of all of them, and keep the window a sensible size. Fewer pixels, faster pictures. The guide to multi-monitor remote desktop shows how to switch between screens.
• Try another codec. In the Console's Display menu, Auto picks a codec both PCs support; H.264 can suit an older PC, and Classic works anywhere. The help article on slow or choppy sessions shows where to see the codec in use.
• Pick the right quality in a browser. Saves data on a weak link, Balanced for everyday use, Sharpest for small text on a fast one.
• Close sessions you aren't using. Each open PC sends its own screen.

Lag and drops are different problems. If a session freezes and comes back, RemoteAccessApp shows Reconnecting and picks up again by itself. If it happens often, see remote desktop keeps disconnecting.