Why the remote cursor lags, and which of the six causes is yours

Remote desktop lag is never one number. Six separate delays stack up between moving your mouse and seeing the result, and the fix for each is different — which is why "get better internet" so often changes nothing.

What the delay is made of

Under 50 ms end to end feels immediate. Around 100 ms is comfortably usable and you stop noticing within a minute. Past roughly 200 ms, typing becomes unpleasant because the characters arrive visibly after the keystroke, and past 300 ms precise mouse work stops being viable.

Telling the causes apart

If the picture is sharp but everything responds late, the delay is network round-trip. Distance and relaying dominate here. A session relayed through a server in another country adds the round-trip to that country twice over, and no setting on either computer will recover it.

If the picture goes blocky or smeary when something moves, that is bandwidth. The encoder is being asked for more bits than the link can carry and it is dropping quality to keep up. The host's upload speed is the constraint, and on asymmetric home connections that is often a tenth of the download figure.

If it is smooth but consistently a beat behind, look at buffering and frame rate. A low frame rate adds a fixed delay before a change can even be captured.

If it is fine and then periodically stutters, that is packet loss or Wi-Fi interference rather than raw latency, and the two need opposite fixes: latency wants a shorter path, loss wants a more reliable one.

What actually helps, in order of effect

1. Put the host on Ethernet. The single largest win in most real setups. Wi-Fi adds latency, jitter and loss on the side that is sending the video, and the sending side is where it hurts.
2. Lower the resolution before lowering anything else. Halving resolution cuts the bits needed roughly fourfold, and remote work on a 1080p stream is perfectly comfortable. This is far more effective than dropping frame rate, which makes it feel worse for the same saving.
3. Turn off the desktop wallpaper, animations and transparency on the host. Screen sharing sends what changes; animated effects mean constant change to encode and transmit for no informational value.
4. Get a direct connection instead of a relayed one. If the tool tells you the session is relayed, moving either side to a network that permits direct negotiation removes an entire extra hop.
5. Check the host's upload speed before blaming anything else. A 5 Mbps upstream cannot carry a high-quality 1080p desktop stream, and no amount of tuning changes that.
6. Close whatever else is uploading on the host network — cloud sync, backups, another video call. They compete for exactly the constrained direction.

What no tool can fix

Physical distance is a floor. Light in fibre covers roughly 200 km per millisecond, and real routes are longer than straight lines, so a connection between continents has a round-trip of well over 100 ms before anything is encoded. Any product promising to eliminate that is describing something else.

The other floor is what the work needs. Text, code, spreadsheets and administration are fine at 100 ms. Video editing, drawing and anything requiring hand-eye precision are not, and the answer there is to run the work locally rather than to tune the connection — see why streaming video and games over remote desktop disappoints.

More guides