Is there a maximum number of Wi-Fi clients for a hotspot on the Raspberry Pi 3 (using the built-in Wi-Fi chip: Broadcom BCM43438)?

Regarding the software, I'm using hostapd to manage the Access Point (on Raspbian).

The goal is to serve some PHP pages hosted on the Pi. There isn't much computation and I think the bottleneck will be the number of clients supported by the hotspot.

I'm interested in the theoretical limit (e.g. the driver) as well as "experienced" limits.

  • Read en.wikipedia.org/wiki/IPv6_address for the possible number of addresses (IPv4 isn't dead, it just smells funny). The number of practical usable connections depends on the traffic. 100.000 clients making one request per minute are easier to handle than 1.000 streaming clients. – ott-- Jun 21 '16 at 20:04
  • @ott-- I'm only interested in clients connecting via the built-in wifi of the Pi (so more expecting a limit below 100) – oliverpool Jun 22 '16 at 6:18

my real world limit was 22 school kids in a classroom connected via there smartphones directly to the pi, now the access point was an open hotspot so the overhead was reduced drastically reduced as no encryption took place, also my pi-3 hadn't actually reached its limit as I'm sure more clients could have connected but was preforming rather sluggishly especially since every student had to click the same link at the same time to follow along.

I found that page loads took on average 2.5-3seconds for me. With the server being node.js http server and the content being returned the contents of a static file that were being stored in a string.


On a off-line Pi configured as a hotspot thanks to Using your new Raspberry Pi 3 as a Wi-Fi access point with hostapd, I configured a hard coded 40 IP address limit. Seems to handle all of them properly. Because using web sockets for real-time interactions among all connected users on my Node.js app, I didn't try more.

More generally, I think that though the Pi may offer this feature with a bit of custom configuration, it is not optimized for this use. If you wan't to get satisfying Wi-Fi performance for each client, I suggest you restrain the number of physical clients: I mean, it's not because it's wireless that each client won't consume less resource about handling its connection / IP session.

Many routers offer to assign much more IP addresses, but that's about DHCP and assigning addresses to connected clients, not about handling 50 Wi-Fi traffic-wise distinct connections and contexts.

Ex: All Apple Airport stations have a limitations of 50 users for instance... see Compare AirPort family.

UPDATE: Months (!) later, eventually had the opportunity to test with lots of devices. It appears that the Pi 3B with a Jessie based Raspbian and its default WIFI component could accept no more than 32 MAC addresses, even with dnsmasq configured to allow up to 60 IPs.

Based on some Raspi Community Forums thread I assume this might be caused by a hard coded limit in the brcmfmac driver for the WIFI chip used on the board, still looking into this...

The Pi 3B+ with Stretch based Raspbian (9.4) could accept only up to 16 connections (same hostapd/dnsmasq config). As this is only half as much as the Pi 3B, I have nothing but hypothesis for this:

-either the Stretch embedded brcmfmac driver for the WIFI chip now limits to 16 MAC addresses (unlikely IMHO)

-or it is linked to the new WIFI chip used in the new board, now dual band 2,4/5 GHz when in client mode, but I could configure the AP only using the 2,4GHz, so only half the resources would be allocated therefore half the Pi 3B maximum capacity as a result (seems more plausible to me, but definitely not verified)


No, not really, although you will be limited depending on the subnet your Access Point creates - decided by your DHCP configuration. E.g. 253 hosts for a subnet with a netmask of, but more than 64000 hosts for a subnet of

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.