What to do when cloud gaming feels laggy
A diagnostic checklist. Most cloud-gaming "lag" is not actually latency — it's something you can fix yourself in five minutes.
Three different things people call 'lag'
It helps to know which one you have, because the fixes are completely different. Input lag is the delay between pressing a button and seeing the result — fixed by reducing end-to-end latency. Stutter is intermittent freezing, usually caused by network jitter or buffer underruns. Compression artifacts (blocky textures, smearing motion) are caused by an encoder dropping bitrate to keep latency low.
Below are diagnostics in order of how often they're the actual problem.
1. Run a wired test once
Even if you'll go back to Wi-Fi after, plug an ethernet cable into your gaming device for 5 minutes and re-run the session. If the problem disappears, your issue is your Wi-Fi link, not your provider or ISP.
Common Wi-Fi fixes: switch to 5GHz or 6GHz band (not 2.4); move closer to the router; check that no other device is saturating the upload (a Zoom call, a backup, a streaming upload). On Wi-Fi 6/6E, enable WMM / WMM-PS in the router for explicit gaming QoS.
2. Check your jitter, not just your speed
Most internet speed tests give you a single peak Mbps number. That number is almost meaningless for cloud gaming. What matters is sustained throughput plus jitter (variation in ping over time).
fast.com (Netflix-hosted, free) gives you both. Aim for <5ms jitter to your nearest cloud data center. If jitter is high, the issue is your ISP's routing, not your bandwidth — call them or change your DNS to a less-loaded resolver (1.1.1.1 or 9.9.9.9).
3. Pick the right server region manually
Every service has an auto-detected region. Sometimes it's wrong, especially if you use a VPN, a custom DNS, or live near a country border. In GeForce Now, switch in Settings → Server Region. In Boosteroid, set it during signup. In Xbox Cloud, region is tied to your Microsoft account locale.
Manually picking the geographically closest data center is the single biggest one-click latency reduction available to you. We've seen 40ms → 22ms swings just from this.
4. Lower the resolution, not the framerate
If quality is good but input feels mushy, drop one quality tier: 4K to 1440p, or 1440p to 1080p. Keep the framerate the same. Lower resolution = lower bitrate = faster encode/decode at both ends, often cutting another 4–8ms of input latency.
Counter-intuitively: do not switch from 60fps to 120fps to 'feel snappier' if your latency is high. Higher framerates eat more upload from the server and can make stutter worse.
5. Restart your router. Yes, really.
Modern consumer routers leak memory over weeks or months and the symptoms first show up in latency-sensitive workloads (cloud gaming, online voice). A 60-second power-cycle of the router fixes a surprising number of 'my GeForce Now got worse this week' complaints we get.
6. Update the cloud client
Native cloud clients ship encoder/decoder improvements regularly. The GeForce Now PC and Mac apps in particular have shipped meaningful latency cuts every 4–6 weeks through 2025–2026. Browser-based PWAs auto-update; native apps don't always.
7. Check for upload-heavy background tasks
Cloud Drive sync, OneDrive, Dropbox, iCloud backup, Time Machine over network, Synology Backup, Steam library uploads — any of these can starve your latency budget at the worst time. Pause backups during gaming sessions.
When to give up on a service
If you've tried everything above and a service consistently feels worse than its competitors on your network, the issue is the network path between you and that provider's data center. That's not fixable on your end. Switch to a service with a closer data center: our regions index shows which providers actually have local server presence in your country.