How to Fix WiFi Slowdowns Caused by Wrong MTU Size: Finding the Optimal MTU for Your Connection
A mismatched MTU setting forces your router to fragment every packet, silently killing throughput. Here’s how to find your optimal MTU and fix the slowdown in minutes.
Your speed test shows 300 Mbps but large file downloads feel sluggish, web pages take a beat too long to paint, and video calls occasionally freeze for a fraction of a second. One surprisingly common culprit: your router’s MTU setting is wrong. It’s a single number buried deep in your router’s WAN settings, and when it’s off by even a few bytes it can cause every packet on your network to be fragmented — adding CPU overhead and latency to every single transfer.
What Is MTU and Why Does It Matter?
MTU stands for Maximum Transmission Unit — the largest data payload (in bytes) that can be sent in a single network frame. The standard Ethernet MTU is 1500 bytes. When your router tries to send a packet larger than the MTU of any link along the path, one of two things happens:
- Fragmentation: The packet is split into smaller pieces, each piece gets its own header, and every piece must be reassembled at the destination. This adds processing overhead on both ends.
- Silent drop: If the “Don’t Fragment” (DF) bit is set and the packet is too large, the packet is simply discarded — causing retransmissions and apparent slowness that look identical to packet loss.
Most of the time 1500 works fine. But several common connection types require a lower MTU, and if your router is set to 1500 on one of them, you pay a fragmentation tax on every byte you send or receive.
Connection Types That Need a Lower MTU
PPPoE (DSL and Some Fiber Services)
PPPoE adds an 8-byte header to each frame. With a physical layer limit of 1500 bytes, the usable MTU for your data is 1492 bytes (1500 − 8). Routers that default to 1500 on a PPPoE WAN connection will fragment every large packet. The fix is to log into your router’s WAN settings and manually set the MTU to 1492. Some routers expose a “PPPoE MTU Auto” option that handles this automatically — enable it if available.
VPN Tunnels
Every VPN protocol (OpenVPN, WireGuard, IPsec) wraps your original packet in its own envelope, consuming 40–80 bytes of overhead depending on the protocol and encryption mode. On a connection with a 1500-byte MTU, this leaves only 1420–1460 bytes for the actual payload. If your VPN client doesn’t clamp the MTU automatically, set it to 1420 as a safe starting point. See our guide on fixing WiFi disconnects when a VPN is active for the full walkthrough.
Some Cable and Fiber Modems
A minority of ISPs run VLAN tagging or additional encapsulation on their last-mile connections, consuming 4–8 extra bytes. If your ISP uses Q-in-Q VLAN tagging, the effective MTU may be as low as 1492 even on a non-PPPoE service. Your ISP can confirm the correct value if you call their technical support line.
How to Find Your Optimal MTU with a Ping Test
The most reliable way to find the correct MTU is the ping-with-Don’t-Fragment method. You send increasingly large packets with the DF bit set and find the largest size that gets through without fragmentation, then add the IP+ICMP header overhead (28 bytes) to arrive at your MTU.
Windows
ping -f -l 1472 8.8.8.8Start with 1472 (which equals an MTU of 1500 after adding the 28-byte header). If you see “Packet needs to be fragmented but DF set”, reduce the value by 10 and try again. Keep lowering until the ping succeeds. Add 28 to the successful value to get your MTU. For example, if -l 1464 succeeds, your MTU is 1492.
macOS
ping -D -s 1472 8.8.8.8The -D flag sets the Don’t Fragment bit. The -s value is the payload size — same arithmetic as Windows. Reduce until you get a successful reply, then add 28.
Linux
ping -M do -s 1472 8.8.8.8The -M do flag prohibits fragmentation. When a packet is too large, Linux prints “Frag needed and DF set (mtu = XXXX)” — giving you the bottleneck MTU directly.
How to Change the MTU on Your Router
Log into your router admin panel (typically 192.168.1.1 or 192.168.0.1). Navigate to WAN Settings or Internet Settings. Look for an MTU field — it’s usually near the connection type selector. Enter your optimal value and save. The router will reconnect to your ISP using the new MTU within seconds.
If your router doesn’t expose an MTU field, you can set it per-adapter on Windows:
netsh interface ipv4 set subinterface "Wi-Fi" mtu=1492 store=persistentOn macOS, use networksetup -setMTU Wi-Fi 1492. On Linux, use sudo ip link set dev wlan0 mtu 1492.
After Changing the MTU
Run a speed test immediately after the change. Large-file download speeds and latency are the most sensitive metrics — you should see throughput hold steady on big downloads and ping times drop slightly. If speeds got worse, you went too low; increase the MTU by 4–8 bytes and re-test.
MTU is rarely the only cause of slow WiFi, but when it’s the culprit the fix is free and takes under five minutes. For a broader diagnostic, see our guide on why your WiFi is slow or check our channel width explainer if you suspect your radio settings need tuning.
Related Articles
How to Enable and Verify Beamforming on Your Router for Stronger Directed WiFi Signals
Beamforming focuses your router’s WiFi signal directly at your devices instead of broadcasting in every direction. Here’s how to enable it, verify it’s working, and understand when it actually helps.
How to Prioritize Devices on Your WiFi Network (QoS Guide)
When multiple devices compete for bandwidth, QoS lets your router put the right traffic first. Here’s how to set up device prioritization on every major router brand.
How to Fix WiFi Slowdowns Caused by WPA3 Transition Mode: Security Handshake Overhead and Compatibility Fixes
WPA3 transition mode can silently slow down older devices or cause association delays of up to a minute. Here’s exactly why it happens and how to fix it without sacrificing security.