How to Optimize Your Router’s Beacon Interval for Better WiFi Performance
Your router broadcasts a beacon frame dozens of times per second — and that constant chatter consumes airtime. Here’s how adjusting the beacon interval can improve throughput, extend battery life on mobile devices, and fix roaming issues.
Every WiFi router continuously broadcasts small “beacon” frames to announce its presence, advertise network capabilities, and help devices synchronize. By default most routers send one beacon every 100 milliseconds — that’s ten per second, every second, around the clock. Changing this single number can meaningfully affect throughput, mobile battery life, and how well devices roam between access points. This guide explains exactly what the beacon interval does, when you should change it, and what value to use.
What Is the Beacon Interval?
A beacon frame is a small management packet (typically 50–300 bytes) that your router broadcasts to every device in range. It contains the network name (SSID), supported data rates, security capabilities, and — critically — a Traffic Indication Map (TIM) that tells sleeping devices whether any buffered data is waiting for them.
The beacon interval controls how frequently these frames are sent. The unit is TU (Time Unit), where 1 TU = 1.024 milliseconds. The default of 100 TUs therefore equals approximately 102.4 ms — close enough that “100 ms” is used interchangeably in every router interface you’ll encounter. Valid ranges vary by firmware but typically run from 40 TUs to 1000 TUs.
How Beacon Interval Affects Performance
Throughput and Airtime
Beacon frames are sent at the lowest mandatory data rate on the band — usually 1 Mbps on 2.4 GHz or 6 Mbps on 5 GHz — so that even the weakest clients can receive them. Sending ten beacons per second at 1 Mbps wastes a measurable slice of airtime that could carry actual data. Increasing the beacon interval to 200 or 300 TUs roughly halves or thirds that overhead, freeing bandwidth for throughput. In dense environments with many access points, this reduction in management traffic can produce a noticeable speed improvement.
Mobile Device Battery Life
This is where beacon interval has the most dramatic real-world impact. WiFi radios in phones, tablets, and IoT sensors use a power-save mode: the radio sleeps between beacons and only wakes up when a beacon arrives so it can check the TIM for buffered data. A shorter beacon interval means the radio wakes more often; a longer interval lets it sleep longer between wake cycles.
At the default 100 TUs a device wakes up roughly 10 times per second. Raising the interval to 300 TUs drops that to about 3 times per second. Studies of 802.11 power consumption show this kind of change can reduce WiFi radio energy use by 50–70% on battery-powered devices — a meaningful gain for IoT sensors running on AA batteries or phones that spend most of the day idle.
Roaming and Connection Reliability
Beacons are also how a device discovers that a better access point is available. When a device is moving through your home, it scans for beacons from neighboring APs to decide whether to roam. A very long beacon interval (500+ TUs) means devices take longer to detect a stronger AP and may cling to a weaker one for several seconds — the classic “sticky client” problem. Keeping the interval at 100–200 TUs ensures fast roaming discovery.
What Is the DTIM Period? (And Why It Matters)
Closely related to beacon interval is the DTIM (Delivery Traffic Indication Message) period. After buffering broadcast and multicast traffic (like mDNS announcements from Chromecast or AirPlay devices), the router sends a special DTIM beacon at a set interval to wake all sleeping clients so they can collect that buffered data.
The DTIM period is a multiplier of the beacon interval. A DTIM of 2 with a 100 TU beacon interval means a DTIM beacon fires every 200 TUs. A DTIM of 3 sends one every 300 TUs. Higher DTIM values let devices sleep longer and improve battery life further, but delay delivery of multicast packets — which can slightly slow local network discovery (finding printers, Chromecasts, etc.) and increase latency for multicast-dependent apps.
For most home networks, a DTIM of 1 (the default) or 2 is fine. If you have many IoT devices on a dedicated VLAN and care about battery life, a DTIM of 3–5 is a reasonable experiment.
Recommended Settings by Use Case
Standard Home Network (Laptops, Phones, Smart TVs)
Leave the beacon interval at the default 100 TUs. The overhead is negligible on a typical home network, and you get the fastest device discovery and roaming response. Only change it if you have a specific problem to solve.
Networks With Many IoT or Battery-Powered Devices
Raise the beacon interval to 200–300 TUs. This is the sweet spot: meaningful battery savings without degrading roaming or connection reliability. Pair it with a DTIM of 2 or 3 for maximum benefit. Avoid going above 300 TUs on networks where devices roam between rooms.
Dense Multi-AP or Mesh Networks
In a mesh system or enterprise-style setup with many access points, reducing management frame overhead matters more. A beacon interval of 100–200 TUs is standard in these environments. Consult your mesh system’s documentation before changing this setting — some systems (like Ubiquiti UniFi) manage beacon timing automatically across all APs.
Fixing Sticky Client / Roaming Problems
If devices cling to a distant AP instead of roaming to a nearby one, try lowering the beacon interval to 50–75 TUs. This makes APs announce themselves more frequently, helping clients make faster roaming decisions. Combine with enabling 802.11r (Fast BSS Transition) and 802.11v (BSS Transition Management) if your router supports them. For more detail see our guide on fixing sticky client roaming.
How to Change the Beacon Interval on Your Router
The setting is usually under the Advanced Wireless or Professional Wireless section of your router’s admin panel. Common paths:
- ASUS routers: Wireless → Professional → Beacon Interval
- TP-Link (Archer): Advanced → Wireless → Advanced Settings → Beacon Period
- Netgear Nighthawk: Advanced → Advanced Setup → Wireless Settings → Beacon Interval
- DD-WRT / OpenWrt: Wireless → Advanced Settings → Beacon Interval
Make the change on each radio band (2.4 GHz and 5 GHz) separately. After saving, your router will rebroadcast at the new interval immediately — no reboot required on most firmware. Test with a speed test and check that all devices reconnect normally.
What to Avoid
Do not set the beacon interval above 500 TUs on a general-purpose home network. At that level devices may fail to associate cleanly, roaming stalls noticeably, and mobile clients can take several seconds to detect the network after waking from sleep. The marginal throughput gain at extreme values is not worth the reliability cost. If you changed it and devices are now dropping or struggling to connect, restore the default 100 TUs.
Quick Reference
- 100 TUs (default): Best for most homes — fast roaming, reliable connections.
- 200–300 TUs: Ideal when you have many IoT or battery-powered devices.
- 50–75 TUs: Use to speed up roaming in multi-AP setups with sticky-client issues.
- 500+ TUs: Avoid — reliability degrades with little throughput benefit.
For more ways to squeeze performance out of your existing hardware, see our guides on choosing the best WiFi channel, fixing bufferbloat, and QoS settings explained.
Related Articles
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.
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.
How to Fix Slow Speeds When Your Router Supports WAN Aggregation but Your ISP Doesn’t: Multi-WAN and Bonding Explained
Your router touts WAN aggregation for double the speed, but your ISP hasn’t cooperated and your connection still crawls. Here’s why the mismatch happens and exactly what to do about it.