Disable Nagle's Algorithm to Reduce Game Lag (TCP No Delay Fix)

If your online game feels a touch less responsive than your ping suggests it should, Nagle’s algorithm may be adding a small, invisible delay. It’s a decades-old TCP feature that bundles small packets together for efficiency — great for file transfers, not ideal for the constant stream of tiny, time-sensitive packets a game sends. This guide shows you how to disable it safely in the Windows registry and what to realistically expect.

Nagle batches small packets to save bandwidth — for games, that batching can cost a few milliseconds of input-to-server delay.

What Nagle’s algorithm does

TCP sends data in packets. When an app fires off lots of very small packets (like a game sending your movement and fire inputs), Nagle’s algorithm holds a small packet back for a moment to see if more data is coming, then sends them together. This reduces the overhead of shipping dozens of tiny packets per second.

For bulk data that’s a win. For a competitive game, that brief “wait and combine” step can add a few milliseconds between your click and the packet actually leaving your PC — on top of your real ping. Disabling Nagle (the TCP_NODELAY flag) tells Windows to send those small packets immediately.

Important caveat up front: many modern games already set TCP_NODELAY themselves, and most current shooters use UDP, which Nagle doesn’t touch at all. So this tweak helps some titles and does nothing in others. It’s low-risk, so it’s worth applying — just calibrate your expectations.

Before you touch the registry

Nagle is a fine-tuning step, not a fix for real network problems. If you have spikes, high ping, or packet loss, sort those first — they cost far more latency than Nagle ever will:

• Use a wired Ethernet connection instead of Wi-Fi where possible.
• Rule out packet loss and route problems with how to fix high ping and packet loss.
• Do the broader network pass in how to optimize your internet connection for gaming.

Do those, then apply Nagle as a final polish.

How to disable Nagle’s algorithm in Windows

You disable Nagle per network interface by adding two registry values to your active adapter’s key. First, find your adapter, then edit its interface key.

Step 1 — Find your interface ID

1. Press Win + R, type cmd, and press Enter.
2. Run ipconfig /all and note the IPv4 Address of your active connection (e.g. 192.168.1.50).

Step 2 — Open the interfaces key

1. Press Win + R, type regedit, and press Enter.
2. Navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces

3. You’ll see several subkeys with long GUID names. Click through them and find the one whose DhcpIPAddress (or IPAddress) matches the IPv4 address from Step 1. That’s your active adapter.

Step 3 — Add the two values

Inside that interface subkey, create two DWORD (32-bit) values and set each to 1:

Value name	Type	Data
TcpAckFrequency	DWORD (32-bit)	1
TCPNoDelay	DWORD (32-bit)	1

To create each one: right-click in the right pane → New → DWORD (32-bit) Value, name it exactly as above, then double-click it and set the value to 1 (hexadecimal or decimal, both are 1).

TCPNoDelay = 1 disables Nagle’s batching. TcpAckFrequency = 1 disables delayed ACKs, a related feature that otherwise waits before acknowledging packets — the two are usually changed together for gaming.

Step 4 — Reboot

Restart your PC so the network stack reloads with the new settings. (Disabling and re-enabling the adapter also works, but a reboot is cleaner.)

How to test whether it helped

Because the effect is small and title-dependent, measure it:

• Check your in-game network/latency graph or netgraph before and after in a TCP-based game.
• Compare input feel in the same map/mode, not across different servers.
• If you see no difference in the games you play, they likely use UDP or already disable Nagle — that’s expected, and there’s no harm in leaving the values in place.

How to undo it

Reverting is simple: in the same interface key, delete the TcpAckFrequency and TCPNoDelay values (or set both to 0), then reboot. Windows returns to its default behavior.

Where this fits in the latency picture

Disabling Nagle trims network-side delay. To cut the delay between your hand and the screen — the part you actually feel most — pair it with the input-chain tweaks that matter more:

• How to minimize input delay for competitive gaming — the full input-lag checklist.
• The ultimate guide to timer resolution for gaming — lower system timer latency, the most consistent local input-lag win.

Bottom line

Disabling Nagle’s algorithm with TCPNoDelay and TcpAckFrequency is a safe, reversible tweak that can shave a few milliseconds off TCP-based games by sending small packets immediately instead of batching them. It won’t fix high ping, packet loss, or Wi-Fi problems — sort those first — and it does nothing for UDP games or titles that already disable Nagle. Apply it as a final network polish, test in your own games, and revert cleanly if you don’t feel a difference.