Remote desktop on slow internet: what actually helps

2026-09-24

A remote session has to capture the screen, compress it, send it across the network, decode it, and send your input back, dozens of times a second. On a slow or unstable connection, every step matters.

Delay matters more than bandwidth

Most people look at download speed, but what makes a session feel sluggish is round-trip delay and packet loss. Keep the remote computer on a wired link if you can, and close video calls or large downloads on either end.

Outbound HTTPS is enough

The RemoteHub agent only needs outbound HTTPS on port 443. No inbound ports and no UDP. If a proxy inspects TLS, add app.remotehub.app and remote.remotehub.app to its bypass list. See Firewalls and proxies.

Lower the quality in the session

The session toolbar has a quality setting. On a weak link, a lower quality keeps the mouse and keyboard usable. Fit the desktop to the window instead of scrolling a huge remote display.

Quick wins

  • Use a wired connection on the remote computer if you can.
  • Close video calls and large downloads on either end during the session.
  • Drop the quality setting if the pointer feels late.
  • Keep one session open at a time on Free.