WiFi Beacon Interval Explained: How Changing Your Router’s Beacon Rate Affects Battery Life, Discovery Speed, and Network Overhead

Open most routers’ advanced wireless settings and you’ll find a field labeled “Beacon Interval” set to 100 by default. Most guides tell you to leave it alone. That’s usually correct — but understanding why helps you recognize the handful of real scenarios where adjusting it changes something meaningful. The beacon interval controls how often your router announces itself to the world, and that single number sits at the intersection of power management, roaming latency, and management-frame overhead on your wireless channel.

What Is a Beacon Frame?

A beacon frame is a small 802.11 management frame transmitted by your access point at regular intervals. Unlike the data frames that carry your actual traffic, beacons are broadcast — sent to every device within range, whether they’re connected or not. Each beacon contains a fixed set of information about the network:

• SSID: the network name
• BSSID: the access point’s MAC address
• Supported rates: the data rates the AP can use
• Channel and band information: including HT, VHT, HE, and EHT capability elements for WiFi 4 through WiFi 7
• Security parameters: WPA2, WPA3, and RSN information elements
• TIM (Traffic Indication Map): a bitmap indicating which connected devices have buffered data waiting
• DTIM period: a count of how many beacon intervals pass between Delivery Traffic Indication Messages
• Timestamp: used to synchronize clocks across the network

The timestamp and TIM elements are the most important for understanding why the beacon interval matters in practice.

How the Beacon Interval Is Measured

The beacon interval is expressed in time units (TUs). One TU equals 1,024 microseconds — just slightly over one millisecond. The 802.11 standard defines the default beacon interval as 100 TUs, which works out to 102.4 milliseconds, or about 9.8 beacons per second. Router UIs display this simply as “100” and accept values measured in TUs. When you set the interval to 200, you get one beacon every 204.8 ms; set it to 50 and you get one every 51.2 ms.

Typical router firmware allows values between 25 and 1,000 TUs. Some enterprise firmware and open-source alternatives like OpenWrt permit a wider range, but the 25–1,000 window covers every practical use case.

DTIM Period: The Companion Setting

The beacon interval works closely with a second setting: the DTIM period. DTIM stands for Delivery Traffic Indication Message. The DTIM period (usually configurable as 1, 2, or 3) determines how many beacon intervals occur between DTIMs. The DTIM beacon is the one that triggers the release of buffered broadcast and multicast frames held at the access point for sleeping devices.

Here’s the relationship: a device in power-save mode doesn’t have to wake up for every beacon — it only needs to wake for the DTIM beacon. With a 100 TU beacon interval and a DTIM period of 2, the device can sleep for up to 200 TUs (about 205 ms) between wake cycles. Increase the beacon interval to 300 TUs with a DTIM period of 2, and the device can sleep for 600 TUs — more than 600 ms — between mandatory wake-ups. This is directly relevant to how long a phone’s WiFi chip can stay in a low-power state while staying associated with the network.

How the Beacon Interval Affects Battery Life

The 802.11 power-save mechanism works as follows: a client device tells the access point it is entering power-save mode. The AP then buffers any unicast frames destined for that device rather than transmitting them immediately. The device’s radio enters a low-power “doze” state and wakes up just before each DTIM beacon. It reads the TIM bitmap to check if the AP has buffered data waiting. If the TIM indicates buffered traffic, the device sends a PS-Poll frame to retrieve it; if not, it dozes again until the next DTIM.

The implication: a longer beacon interval means devices spend more time in the doze state between mandatory wake-ups, saving power. For a smartphone that spends most of its time idle with the screen off, a longer beacon interval (say, 300–500 TUs) allows the WiFi radio to stay dormant longer. Battery impact varies by device and usage pattern, but independent measurements have shown 10–30% reductions in WiFi radio power draw when beacon intervals are extended from 100 to 300 TUs on lightly-loaded networks.

IoT sensors on battery power benefit even more. A temperature sensor that transmits a reading every few minutes has almost no data to receive from the AP, so it spends the vast majority of its time in the doze state. A longer beacon interval (combined with a higher DTIM period) allows these devices to minimize their radio wake cycles substantially. Some embedded IoT firmware is hardcoded to assume a 100 TU interval, so verify that your specific devices remain reliable before making large changes.

How the Beacon Interval Affects Discovery Speed

When a device scans for WiFi networks — either during initial connection or as part of a roaming decision — it listens on each channel for a beacon to confirm a network’s presence and parameters. A shorter beacon interval means beacons arrive more frequently, so a scanning device finds the network faster.

With the default 100 TU interval, a device scanning a channel expects to hear a beacon within about 102 ms. At 50 TUs, that shrinks to 51 ms. At 200 TUs, it extends to 205 ms — a device with a short channel dwell time might miss the beacon entirely on the first pass.

This matters most in roaming scenarios with multiple access points. When a device decides to roam to a stronger AP, it needs to hear a beacon from the target AP to gather the information it needs before initiating the association. A shorter beacon interval reduces the time a device spends scanning before it can complete the handoff. In environments where 802.11k/v/r fast roaming is enabled — as on most modern mesh systems — the AP provides neighbor reports that help devices pre-gather beacon information, reducing the practical impact of a longer interval. Our guide on how 802.11r fast BSS transition works explains the full roaming handoff sequence.

How the Beacon Interval Affects Network Overhead

Every beacon frame transmitted consumes airtime. At the default 100 TU interval with 9.8 beacons per second, beacons represent a small but measurable fraction of your wireless medium. The overhead depends on beacon frame size (typically 100–300 bytes), the legacy transmission rate used (beacons must be sent at the lowest supported rate to reach all devices), and channel width.

Because beacons are broadcast at the most conservative rate — often 1 or 6 Mbps depending on band — they consume airtime disproportionate to their size. On a busy 2.4 GHz network already contending with neighbor networks and legacy devices, reducing beacon frequency by increasing the interval to 200–300 TUs frees a small but real amount of medium capacity for data traffic. The effect is most noticeable in dense apartment environments. Our guide on reducing WiFi congestion in shared apartments covers the broader toolset for congested environments.

The Hidden Cost: Hidden SSID Interactions

If you’ve configured a hidden SSID (suppressed beacon SSID field), your router still sends beacons — it just omits the network name from them. Devices that know the SSID use probe request/response exchanges instead to discover the hidden network. Increasing the beacon interval on a hidden SSID network has less effect on discovery time because clients rely on probing rather than passive beacon listening. For networks with visible SSIDs, beacon interval is the primary timing constraint for passive scanning.

What Should You Actually Set It To?

For most home networks, the default 100 TU interval is appropriate. The out-of-box setting represents a reasonable balance that the 802.11 standard has validated across decades of real-world deployments. There are three specific scenarios where a change is worth considering:

• Battery-sensitive IoT deployments: If your network hosts many battery-powered devices (sensors, Zigbee/Thread border router clients, remote controls), increasing the beacon interval to 200–300 TUs in combination with a higher DTIM period can extend battery life. Test carefully, as some IoT firmware has hardcoded assumptions about beacon timing.
• Dense apartment environments: On the 2.4 GHz band with high neighbor-network congestion, raising the beacon interval to 200 TUs reduces management-frame overhead slightly. The gain is modest but real on heavily loaded channels. Check with a WiFi analyzer app to confirm you’re actually congested before making the change.
• Enterprise or multi-AP roaming: If you’re running a large home network with multiple wired access points and fast-roaming is a priority, a lower interval (50–75 TUs) can shorten the time clients spend scanning during handoffs. Most modern mesh systems handle this automatically via neighbor reports; on manually configured multi-AP setups with open-source firmware, manual adjustment may help.

Where to Find the Setting

The beacon interval lives in different places depending on your router’s firmware:

• TP-Link Archer / Deco: Advanced → Wireless → Advanced Wireless Settings → Beacon Interval
• ASUS (Asuswrt): Wireless → Professional tab → Beacon Interval
• Netgear (Nighthawk): Advanced → Advanced Setup → Wireless Settings → Beacon Interval
• eero: Not user-adjustable — eero manages beacon timing automatically as part of its mesh coordination
• OpenWrt: Network → Wireless → Interface Configuration → Advanced Settings → Beacon Interval

On routers with separate 2.4 GHz and 5 GHz radio pages, the setting applies per-band. Most networks benefit from keeping the 5 GHz interval at 100 TUs and only experimenting with the 2.4 GHz band if congestion is a confirmed problem.

The Bottom Line

The beacon interval is a real knob with real trade-offs — not a placebo setting. Lowering it costs airtime and power in exchange for faster network discovery and roaming. Raising it recovers airtime and improves battery life at the cost of slightly slower device detection. For the vast majority of home networks, the default 100 TU setting is correct, and the changes that actually move the needle are router placement, channel selection, and security configuration. If you’re unsure where your network stands, start with a speed test to establish your baseline, then use our WiFi analyzer guide to diagnose whether congestion or signal strength is the real constraint before adjusting any advanced radio parameters.