WiFi mesh vs wired access points for venues: which is right?

Here is a myth that costs venues money. The fella in the box shop says the kit is "mesh, it just blankets the whole place, no wires needed." Sounds brilliant. You buy three nodes, plug them in, and on a quiet Tuesday it is perfect. Then Saturday comes, the place fills up, and the WiFi behind the bar starts treacle-ing. Card machine spins. The booking tablet drops. You assume the broadband is the problem. It is not.

The problem is that two of those three boxes are talking to each other over the air, and they are doing it on the same radios your guests are trying to use. Mesh is not magic. It is a trade. You trade running a cable for losing throughput, and in a busy room that trade rarely pays off.

So let me be blunt up front, because the brief here is to have an opinion and not hedge. For a venue, wired access points win almost every time. Mesh is a last resort for the one corner you genuinely cannot reach with a cable. It is not a plan for the whole building. Below is why, in plain terms first and then with the real specs for anyone speccing the kit.

Mesh vs wired in plain English

An access point (AP) is the box on the wall or ceiling that broadcasts the WiFi. Both mesh and wired setups use APs. The difference is how each AP gets its data back to your router and out to the internet. That return path is called the backhaul.

A wired AP sends its data back over an Ethernet cable. The same cable usually carries the power too, using Power over Ethernet (PoE), so one wire does both jobs. Clean and simple.

A mesh AP (often called a node or satellite) has no data cable. It relays its traffic wirelessly to the next node, which relays to the next, until it reaches one node that is actually plugged in. Each wireless leg between nodes is a "hop." The signal that goes to your guests' phones is the "fronthaul." The signal between nodes is the backhaul. On most consumer and dual-band kit, both share the same radio, and that is where the trouble starts.

Wired backhaul keeps 100 percent of the wireless spectrum free for your guests. Wireless backhaul makes the AP share that spectrum with itself.

Why wireless backhaul costs you throughput

This is the technical heart of it, and it is not vendor spin. It comes from how WiFi physically works. IEEE 802.11 WiFi is half-duplex: a radio can transmit or receive at a given moment, not both at once. It listens before it speaks, a scheme called CSMA/CA (carrier-sense multiple access with collision avoidance). One radio, one conversation at a time.

Now picture a single-radio mesh node. To pass a guest's data along, it must receive the frame from the upstream box, then turn around and retransmit it on the same channel to the next box. It spends roughly half its airtime listening upstream and half talking downstream. The result, in the words of the engineering literature on 802.11 repeaters, is "a 50% minimum reduction in network throughput compared to an AP-to-station network without the repeater."

You do not have to take my word for it. Every major vendor states the same thing:

• Cisco (Wireless Mesh Access Points Design and Deployment Guide): "The overall throughput of backhaul radio decreases by half for each hop of a mesh tree."
• Ubiquiti (UniFi Help Center): "Wireless meshing is much less performant than a wired connection (about 50% lower for each wireless hop)."
• TP-Link (Omada FAQ 4307): "each wireless 'hop' starting from the wired main AP will reduce stability and result in a performance degradation of about 50%," which they attribute to "the half-duplex characteristic of wireless communication and signal loss during the transmission process."

So one hop roughly halves your usable throughput. Two hops roughly quarters it. That is why Ubiquiti recommends a maximum of two wireless hops and TP-Link says the same, even though Omada APs technically support three.

What about tri-band and "dedicated backhaul"?

Better mesh systems fight this with a third radio reserved purely for the node-to-node link, usually marketed as "dedicated backhaul" on a tri-band unit. Because the client-serving radios no longer share airtime with the backhaul, as the explainer site Dong Knows Tech puts it, "all other bands can be fully used for fronthaul connectivity without bandwidth-sharing penalties."

It helps. Tech press testing suggests a good tri-band system drops the per-hop penalty from roughly 50 percent down to around 15 to 25 percent. Note the word: drops, not eliminates. You still lose throughput, you still add latency, and you have now spent more on a tri-band node than the Ethernet cable would have cost. Dedicated backhaul is a way to make a compromise hurt less. It is not a reason to choose the compromise.

Mesh vs wired APs: side by side

If you are still choosing the AP hardware itself rather than the backhaul method, our companion guide on how to choose an access point for guest WiFi walks through bands, client counts and brands. And if you are working out how many APs you need at all, see how many access points your venue needs.

Latency, hops and the chain problem

Throughput is the headline, but latency is the quiet killer. Even on a tri-band system where the throughput penalty is mostly solved, each wireless hop still adds delay, and that delay stacks up roughly hop by hop. Wired backhaul adds almost none. For a guest scrolling Instagram, a few extra milliseconds is invisible. For your card reader confirming a payment, your booking tablet, or a video call in a coworking space, accumulated latency and the odd dropped frame are exactly what people complain about.

There is also the topology trap. Mesh can be wired in a "star" (every node hops directly back to the wired box) or a "chain" (node to node to node). TP-Link is clear that a star outperforms a chain, because a chain stacks the per-hop penalty: node three is two hops deep and gets a fraction of the original throughput. People build chains by accident all the time, simply placing nodes where there is a plug socket rather than where the signal makes sense.

When mesh is actually acceptable

I am not anti-mesh. There is a real, sensible use for it. The vendors define the conditions and they are worth stating plainly. Mesh is acceptable when:

• You genuinely cannot run a cable. A listed building where you are not allowed to drill, a detached smoking shelter or beer garden bar, a marquee, a pop-up. Ubiquiti's own line is that meshing is "an alternative, especially in homes or spaces that aren't wired for Ethernet."
• The load is light. A handful of guests checking menus and emails, not a packed room streaming. Performance "degrades most under multi-AP, high-density conditions," which is precisely the venue Saturday-night scenario.
• It supplements wired, it does not replace it. One wired AP covering the main room, one meshed node reaching the garden. That is a fine design. Three meshed nodes covering a busy two-floor pub is not.
• You keep it to one hop, two at the absolute most. Beyond that the maths stops being worth it.

Run a cable if you possibly can. PoE means one wire delivers both data and power, so it is often less disruptive than people fear. PoE+ (the 802.3at standard) supplies 30W at the switch port, comfortably enough for a modern WiFi 6 or WiFi 7 AP, and a single Cat5e or Cat6 run reaches the full 100 metres. Our PoE and cabling guide for guest WiFi covers switches, injectors and which cable to pull.

The captive portal works on both

Here is the part that matters for the marketing side of your WiFi, and the part we know well: it makes no difference to your guest WiFi sign-in screen whether the network behind it is mesh or wired. A captive portal operates above the link-layer, at the IP and HTTP-redirect layer, so it is independent of how the APs talk to each other.

To be honest about what we are: CaptiFi is a guest-WiFi marketing platform, a branded captive portal that sits on top of whatever network you already run. We do not sell, ship, install or wire hardware, and we are not electricians. We work with venues running UniFi, TP-Link Omada, Cisco Meraki, Aruba, MikroTik, Ruckus, Cambium and DrayTek, authorising guests through the controller API with no RADIUS server needed. There is also a free plug-and-play device if you would rather not touch a controller at all.

Whichever backhaul you choose, the portal layers a branded splash page, email capture and Google review automation on top. Venues using CaptiFi typically capture 40 to 60 percent of connecting guests as email subscribers, often 300 to 500+ emails per location per month, and see a 3 to 5x lift in Google reviews within 60 days. Consent is GDPR and PECR compliant out of the box. One caveat from the technical side: some older portal implementations were built only for plain open networks and stumble on newer encrypted-open standards, which we cover in our guide to WPA3 and Enhanced Open.

How to decide for your venue

Strip away the jargon and the decision is short. Walk your space. Can you get a cable to where each AP needs to live, within 100 metres of a switch or router? If yes, wire it. The cabling is a one-off cost and the network just works on your busiest day, which is the only day that tests it.

If there is one spot you truly cannot cable, mesh that single spot, keep it to one hop, accept it will be slower, and make sure it is supplementing a wired backbone rather than carrying the whole venue. A pub garden, a courtyard, an upstairs room with no route for a cable: that is the job mesh is for.

What you should not do is buy a three-pack of mesh nodes for a busy room because it looked easy in the shop. Easy on Tuesday, treacle on Saturday. If you want to see how a branded portal sits on top of either setup, the hardware page lists what we integrate with, and you can start a 30-day free trial with no card. Plans start from $69/mo. For the wider picture on doing more with the network you already have, the complete pub WiFi marketing guide ties it together.

Sources: IEEE 802.11; Cisco Wireless Mesh Access Points Design and Deployment Guide; Ubiquiti UniFi Help Center ("Considerations for Optimal Wireless Mesh Networks"); TP-Link Omada FAQ 4307; Dong Knows Tech; IEEE 802.3at PoE+ and TIA/EIA structured-cabling standards. Tri-band penalty range from tech-press testing (illustrative, hardware-dependent). CaptiFi figures are typical venue outcomes, not guarantees. Specs, standards and prices were correct at the time of writing (June 2026) and may change.