How to Reduce Ping for Gaming: Settings That Actually Work

Published July 26, 2026 · 8 min read

The most common piece of gaming advice, upgrade your internet plan, is also one of the least effective fixes for high ping. Ping is a latency problem, not a bandwidth one, and a faster plan does nothing about the actual causes: WiFi contention, an overloaded connection, or an unmanaged queue in your router. Here are the changes that genuinely move the number, ranked by how much difference they typically make.

Ping Is About the Path, Not the Pipe

Before the fixes, it helps to know what you are actually chasing. Ping measures how long a round trip takes between your device and the game server, in milliseconds. A bigger internet plan increases how much data you can move per second; it does nothing to shorten that round trip. That is why someone on a modest connection with a clean, low-contention path to a nearby server routinely beats someone on a much faster plan whose traffic is stuck behind WiFi interference or a congested queue.

1. Get Off WiFi (Biggest Single Improvement)

If your gaming device can take an Ethernet cable, this is usually the single largest ping improvement available, often shaving off many milliseconds at once, and it is completely free. WiFi adds latency from several sources at once: contention with every other device sharing the same radio channel, retransmissions caused by interference, and the inherent overhead of the wireless protocol itself. A wired connection removes all of it in one step.

If running a cable is not practical, at minimum move the router closer, remove physical obstructions, and confirm you are on the least congested channel using a WiFi Analyzer scan.

2. Fix Bufferbloat with SQM (Second Biggest)

This is the fix most people have never heard of and it is often the difference between stable, low ping and ping that spikes into the hundreds of milliseconds the moment anyone else in the house streams or uploads something. The cause is bufferbloat: oversized buffers in your router or modem that let packets queue up under load instead of being sent promptly.

1. Look in your router settings for SQM, QoS, or Adaptive QoS, and turn it on.
2. Set the upload and download limits to roughly 85 to 95 percent of your measured speed, not the full number your ISP advertises. This deliberately keeps the queue in your router, where it can be managed, instead of in unmanaged ISP equipment.
3. If your router supports it, choose CAKE or fq_codel as the queue algorithm.

Done right, this is the fix that stops your ping from suddenly tripling every time someone else in the house starts a download during your match.

3. Keep Bandwidth-Heavy Devices Off Your Gaming Band

If you are gaming over WiFi, put streaming boxes, smart TVs, and other bandwidth-heavy devices on the 2.4GHz band and keep your gaming device on 5GHz, or on whichever band has the least other traffic. Fewer devices sharing your radio channel means fewer collisions and less time your device spends waiting its turn to transmit.

4. Choose the Nearest Server Manually

Automatic matchmaking does not always pick the lowest-latency server, particularly in games with cross-region play or population-based matchmaking. Where the game allows a manual region or server choice, pick the physically nearest data center. A traceroute or MTR to a couple of candidate server IPs will show you which path is actually shorter and cleaner before you commit to it.

5. Rule Out Background Traffic

A single large upload, like a cloud photo backup or a game download finishing in the background, can saturate your connection and, without SQM in place, drag your ping up with it. Pause large transfers before a session, and if other people share the connection, a quick heads-up before a ranked match is cheaper than troubleshooting mid-game.

6. Rule Out Your ISP

If ping is consistently high even wired, on an idle connection, with SQM configured, the remaining likely cause is upstream: a congested or poorly peered path from your ISP to the game server. Run traceroute or MTR to the server and look for a jump in latency at a specific hop. Consistent per-hop delay outside your own network is something to raise with your ISP, not something local settings can fix, and it is also worth checking whether your ISP is throttling the connection during peak hours.

Measure Before and After Every Change

Do not guess whether a change helped. Run a continuous ping test against the same target before and after each fix, ideally while under the same load conditions, so you can actually see which change moved the number and by how much, rather than attributing an improvement to the wrong fix.

The Bottom Line

Ping is fixed by shortening and stabilizing the path your packets take, not by buying more bandwidth. Wire your gaming device directly to the router if you possibly can, fix bufferbloat with SQM so a busy household does not tank your latency mid-match, keep other devices off your gaming band, and pick the nearest server manually when the game allows it. Work through those in order and most high-ping complaints resolve well before you get anywhere near your ISP.

Frequently Asked Questions

Does a faster internet plan lower ping?

Usually not. Ping measures latency, the round-trip time to a server, while an internet plan's speed measures throughput, how much data moves per second. A faster plan can leave the same WiFi contention, bufferbloat, and routing issues untouched.

Does Ethernet really lower ping that much?

Yes, often noticeably. WiFi adds latency from channel contention, interference-driven retransmissions, and protocol overhead that a wired connection avoids entirely. For competitive gaming it is usually the single biggest fix available.

What is the single most effective fix for high ping while gaming?

For most people, connecting via Ethernet instead of WiFi. For households where multiple people share the connection, enabling Smart Queue Management (SQM) to fix bufferbloat is often just as impactful.

Why does my ping spike only when someone else is streaming or downloading?

That is a classic bufferbloat symptom: your connection's buffers fill up under load and delay time-sensitive game packets behind bulk traffic. Enabling SQM and capping bandwidth slightly below your line rate fixes this.

Can I lower ping by choosing a different DNS server?

DNS server choice affects how fast a name resolves to an address, a one-time lookup, not the ongoing round-trip latency of your actual game connection. It will not meaningfully change in-game ping.