How Many Devices Can Your Router Actually Handle?

The verdict up front: the "supports 200+ devices" number on the box is an arithmetic limit, not a performance promise. There are three separate ceilings — how many IP addresses your router will hand out, how many clients its firmware will keep associated, and how much airtime its radios can divide — and it is almost always the third one that ruins your Wi-Fi. The honest planning number for a modern consumer router or mesh node is roughly 20–50 actively used devices, and manufacturers quietly say so themselves: eero publishes a 128-device maximum per unit and then recommends no more than 30 per unit when those devices are actually busy. Idle smart plugs barely count. One old 2.4 GHz camera can cost more airtime than twenty phones.

"How many devices can my router handle?" is really three questions with three different answers, and vendors are free to quote whichever one flatters the product.

Work through them in order, because the fix for each is completely different.

Your home network almost certainly runs on a `/24` subnet: `192.168.1.0` through `192.168.1.255`, or the `192.168.0.x` equivalent. That block contains 254 usable host addresses, minus one for the router itself, which leaves 253 devices that can hold an address at the same time.

That 253 is where "a router supports 250+ devices" comes from. Linksys states it plainly in its own support documentation — "a typical home router can support up to 253 devices connected via wired or wireless connections at the same time" — and then, in the same article, concedes that consumer routers handle "about 20 to 50 devices comfortably."

Here is the part worth checking tonight. The subnet holds 253 addresses, but the DHCP pool — the slice of it your router actually hands out automatically — is a separate setting, and the defaults vary wildly by brand.

TP-Link's own user guides spell it out: the IP address pool "is from 192.168.1.100 to 192.168.1.199 by default." That is a hundred leases on a subnet with room for 253. A house with a lot of smart-home gear plus guests cycling on and off — every phone that visits burns a lease until it expires — can genuinely bump into a 100-address pool, and the symptom is bizarre: a device connects to Wi-Fi, authenticates fine, and then sits there with no internet and a self-assigned `169.254.x.x` address.

The fix is free. In your router's LAN or DHCP settings, widen the pool (for example, start at `.20` and end at `.250`), and shorten the lease time from the common 24-hour default to a few hours so departed guest devices release their addresses faster. While you are in there, set DHCP reservations for the handful of devices you actually want at fixed addresses — printers, NAS, a Pi-hole — rather than giving them static addresses inside the pool, which causes conflicts.

If you genuinely need more than 253 devices at home, you do not need a bigger router; you need a second subnet, which is what VLANs are for.

Every device connected to your Wi-Fi occupies a slot in the access point's association table, and each slot costs memory: encryption keys, negotiated data rates, power-save state, buffered frames waiting for a sleeping device to wake up. A router is a small Linux computer, and this table lives in its RAM alongside the NAT connection table tracking every open session your devices have to the internet.

This is where the per-unit maximums come from. They are firmware and memory limits, not physics, and they are the reason a $60 router and a $500 router can quote wildly different numbers with identical radios:

Those numbers are real in the narrow sense that the hardware will hold that many associations. They are useless as a shopping guide, because association capacity is almost never what breaks first. Cheap routers do run out of RAM — an old dual-core router with 128 MB juggling 60 clients and a big NAT table will drop connections or reboot itself — but a current mid-range router has enough memory that you will hit the airtime wall long before the table fills.

Wi-Fi is a half-duplex shared medium. On a given channel, exactly one transmission can be in the air at a time. Every device on that channel takes turns, and the turn-taking is the whole ballgame.

MU-MIMO and OFDMA soften this — the first lets a router beam to several devices simultaneously, the second lets it pack several small transmissions into one — and they are the main reason Wi-Fi 6 and 7 handle crowds better than Wi-Fi 5 did. But they do not repeal the rule. They just make each turn more efficient.

What matters is not how many devices exist. It is how much airtime each one consumes, and that varies by a factor of well over a hundred depending on how fast the device can talk.

Read the first and last rows together. Moving the same 10 MB, the struggling 2.4 GHz camera occupies the channel roughly 185 times longer than the Wi-Fi 6 phone. While it transmits, nothing else on that channel can. (These are PHY-rate figures; real throughput lands around 60–70% of them after protocol overhead, but the ratio between devices holds.)

This is why device counts are so misleading:

That is the real reason "how many devices" has no fixed answer. Fifty devices in a house where forty-five of them are idle sensors on 2.4 GHz and five active clients sit on 6 GHz is a comfortable network. Fifteen devices where six are streaming from marginal signal on a congested 2.4 GHz channel is a miserable one.

The most honest number in this entire industry comes from eero, because they publish both figures in the same place. Their support documentation states that one eero can support up to 128 devices — and then immediately adds that if those devices are heavily using the internet, you will see the best results with up to 30 devices per eero.

That is a 4x haircut, from the vendor, on their own spec. It is also why eero sells packs rather than one bigger box: the Eero Max 7, their Wi-Fi 7 flagship, adds capacity by adding nodes — each with its own radios and its own pair of 10G ports — rather than by raising the per-unit number.

It matches everyone else's real-world guidance once you go looking. Linksys puts consumer routers at 20–50 devices comfortably and business-grade gear at 100+. Business access points advertise 200 to 1,000+ simultaneous clients, and the capacity-planning guidance for deploying those same access points typically lands at 25–50 active clients each — which is why a busy office puts an AP in every couple of rooms rather than one big one in the middle.

So here is the planning table worth actually using:

Count "actively used" as devices that move meaningful traffic — phones, laptops, TVs, streaming boxes, cameras, game consoles, work machines. Count idle sensors and plugs at roughly a tenth of that weight.

Most people badly underestimate their own count. A fairly ordinary household:

That is easily 30–60 devices, and a router's connected-device list is usually the shock — open your router app and count. But look at the right column: the two rows that decide whether your network is healthy are the TVs and the cameras, not the thirty light bulbs.

Different ceilings fail in different ways. Match yours:

Capacity comes from three things, in this order: more radios in more places, newer standards, and more spatial streams. Device-count claims on the box are not on the list.

Your router has a 253-address ceiling, a firmware association limit somewhere north of a hundred, and an airtime budget that runs out at around 20–50 genuinely active devices — and only the last one is the number that determines whether your Wi-Fi feels good. eero publishes both ends of that gap themselves: 128 devices on the spec sheet, 30 when those devices are busy. Before you buy anything, widen your DHCP pool, put the TV and the console on Ethernet, and hunt down the one weak-signal camera that is quietly eating a tenth of your channel. If you are still short after that, the fix is another radio in another room, not a bigger box in the same one.