Free Trial is currently available for our Business Plans.
Please choose an option that meets your trial needs below
$15 per user per month
Starts at 20 Users / unlimited computers
No credit card required
$2.22
per computer per month
Minimum 20 Computers
No credit card required
Compare all plans & features on the Pricing page
Remote desktop latency is the delay between a user's action, a keystroke, a click, and the visible response inside the session. What you actually feel is the sum of network round-trip time, protocol encoding and decoding, and whatever the server is doing under load. As a rough guideline, office workloads usually stay responsive under about 100ms round-trip; past that, people start to notice. Workload, packet loss, display complexity, and plain user expectations all move that number around.
Latency is the round-trip time between an action on one side and the visible response on the other.
Four things dominate here. Network distance and congestion set the floor, since round-trip time cannot be optimized below physics, and congestion just piles jitter on top of that floor. Packet loss hurts worse than raw distance does; retransmissions stall the whole display stream, which is exactly why lossy Wi-Fi feels worse than a longer wired path ever would. Transport choice matters more than people assume: RDP over UDP tolerates loss and jitter far better than falling back to TCP, so blocking UDP is a smoothness tax you are choosing to pay. Endpoint and host load, an overloaded session host or a client GPU that is struggling, produces lag no network fix will ever touch.
Windows exposes per-connection latency information through the Remote Desktop connection experience and Windows performance-monitoring tools. For a practical baseline, ping the session host or gateway from the client network for RTT and loss, then compare that against how it actually feels. Diagnosing this well means separating three things: path (RTT and loss), transport (TCP vs UDP), and load (host CPU and GPU). Each one has a completely different fix.
Shorten or clean up the path: wired over Wi-Fi, better peering, session hosts placed closer to the users. Enable UDP transport end to end. Right-size the session hosts. Tune display settings for constrained links. Architecture matters here too. A poorly placed gateway adds a hairpin to every single packet, while a direct brokered path skips the detour entirely. Mesh or relay networks with regional points of presence can shrink the effective distance for users sitting far from the datacenter.
As a rough guideline, under about 100ms round trip for office work. Graphics-heavy work wants noticeably less than that.
Bandwidth is rarely the actual constraint. RTT, packet loss, or blocked UDP usually are.
Typically yes: encryption overhead plus a hairpin through the concentrator.
Where TruGrid fits. TruGrid SecureRDP routes sessions over an optimized mesh with UDP support, so there is no VPN hairpin sitting there inflating round-trip time. Explore SecureRDP →
TruGrid SecureRDP delivers Zero Trust remote desktop access: MFA, least privilege, and zero open inbound ports.
Explore SecureRDP →
TruGrid simplifies Access and Device Security for organizations by reducing complexity and associated costs.
