Mesh Node Placement: How Many Nodes and Exactly Where
Mesh node placement without guesswork: how many nodes your square footage really needs, the node-to-node dBm window, the two-hop limit, and when to wire a node.
Mesh kits are sold by node count and covered square footage, which is close to the least useful way to plan one. The number you need depends on what your walls are made of, the shape of the floor plan, and where the gateway is allowed to live. A 2,000 sq ft open bungalow can be fine on two nodes; a 1,400 sq ft brick townhouse can struggle on three.
Here is how to decide the count, where each node goes, and the signal target that tells you a node is in the right place. If you have not settled the question of whether mesh is even the right purchase, start with whether mesh or an extender fits your home.
How many nodes you actually need#
Vendor coverage claims — commonly "up to 1,500 or 2,000 sq ft per node" — assume open, drywall-partitioned space with the node out in the open. Real homes eat that budget quickly. As a planning rule of thumb, work from roughly 1,000–1,500 sq ft per node in open, timber-framed drywall construction, and 700–1,000 sq ft per node in brick, block, plaster or anything with metal studs.
| Floor area | Layout | Construction | Nodes including the gateway |
|---|---|---|---|
| Under 1,200 sq ft | One floor | Drywall | 1 — fix router placement first |
| 1,200–2,000 sq ft | One or two floors | Drywall | 2 |
| 2,000–3,000 sq ft | Two floors | Drywall, timber floors | 2–3 |
| 3,000–4,000 sq ft | Two or three floors | Mixed | 3–4, wire at least one |
| Any size | Any | Brick, block, plaster, metal stud | Add one node over the row above |
| Any size | Detached garage or garden room | Any | Do not solve this with a node — wire it |
Two adjustments matter more than the square footage itself:
- Count floors and stairwells, not just area. A concrete slab between floors can cost 15–25 dB on its own, which is more than several interior walls. In a multi-floor home you are usually placing one node per floor near the stairwell, whatever the area says.
- More nodes is not better. Every additional wireless node shares the same airtime and adds another handoff decision for your devices. Three well-placed nodes beat five crowded ones, and a fourth wireless node in a small home usually makes things marginally worse.
Where the first node goes#
The gateway is a node, and it is the one that determines everything else. Central and high beats tucked into the coax closet by the front door — moving the gateway fifteen feet toward the middle of the house routinely removes the need for a third node entirely. Work through where to put your router before you position a single satellite, because every satellite position is measured from the gateway.
Two constraints usually fight you here: the cable entry point and the power outlet. If the gateway is trapped at one end of the house, accept it and plan a chain outward rather than pretending the house is symmetrical around it.
The node-to-node signal window#
A satellite has to hear its parent clearly before it can help anyone. The working target is -55 to -65 dBm on the backhaul band, measured node to node. Most mesh apps report this as a link quality or node health figure, and many show the raw dBm if you dig one screen deeper.
| Node-to-node signal | What it means | What to do |
|---|---|---|
| Stronger than -55 dBm | Nodes are overlapping; you paid for reach you are not using | Move the satellite further out |
| -55 to -65 dBm | The target window: fast backhaul, maximum reach | Leave it alone |
| -66 to -70 dBm | Usable, but the backhaul link rate is dropping | Accept only for the last node in a chain |
| Weaker than -70 dBm | The backhaul is now your bottleneck | Move it back toward the parent, or wire it |
In practical distance, that window is roughly 30–40 feet through one interior drywall wall on 5 GHz, and 15–25 feet through masonry. A concrete floor often consumes the whole budget by itself, which is why the stairwell path matters so much.
Separately from the node-to-node link, you want the client coverage of neighboring nodes to meet at around -67 dBm. That gives devices a clearly better alternative to move to before the current one becomes unusable — the mechanics of why a phone hangs onto a node it has already walked away from are covered in what makes devices cling to a distant node.
Chain, not star, in long homes — and the two-hop limit#
There are two ways to hang satellites off a gateway, and the floor plan decides which is right.
Star — every satellite links directly to the gateway. Correct for compact, roughly square homes where the gateway is near the middle. Each node is one hop from the source, so nothing is penalized twice.
Chain — gateway to node A, node A to node B. Correct for long, narrow or L-shaped homes, railroad apartments, ranch footprints and tall townhouses. Trying to run a star in a 60-foot-long house means the far satellite sits at -75 dBm from the gateway, and a node with a bad parent link is worse than no node.
The limit on chaining is hard: two wireless hops from the gateway, and no more.
- On a dual-band system that shares one radio between backhaul and clients, each hop costs roughly half the throughput. 400 Mbps at the gateway becomes about 200 at node A and about 100 at node B.
- On a tri-band system with a radio dedicated to backhaul, the penalty is smaller — typically 10–30% per hop — but it is not zero, and each hop adds a few milliseconds of latency.
- A third wireless hop typically delivers less than the room's own weak direct signal from the gateway. If a room needs a third hop, it needs a cable instead.
For homes past about 3,500 sq ft the arithmetic stops working on wireless backhaul alone; planning coverage for a large home treats wiring as the default rather than the upgrade.
When wired backhaul rewrites all of this#
Run a cable to a node and every rule above relaxes. A wired node has no parent-signal requirement, so you place it purely where the coverage is needed. It adds no hop penalty. It cannot be knocked out by a neighbor's channel choice.
| Backhaul type | Realistic throughput to the node | Placement freedom |
|---|---|---|
| Cat5e or Cat6 Ethernet | About 1 Gbps, full duplex | Anywhere with power |
| MoCA over existing coax | Roughly 400–900 Mbps by adapter generation | Anywhere with a coax outlet |
| Powerline | Highly variable, often 30–150 Mbps | Same circuit works best |
| Wireless 5 GHz backhaul | Roughly half the gateway rate per hop on a shared radio, 10–30% off with a reserved backhaul band | Constrained by the dBm window |
The rule that follows: wire any node you can, and if you can only wire one, wire the furthest one. That converts a two-hop chain into two independent one-hop legs, which is the single biggest improvement available to most mesh setups. Wired backhaul with MoCA or Ethernet covers what that actually involves in an existing house.
A node placement procedure#
- Fix the gateway first. Central, out in the open, at least waist height. Do not position satellites around a badly placed gateway.
- List the rooms that must work, in priority order. The office and the living room are requirements; the garage probably is not.
- Draw the straight line from the gateway to each priority room and count the walls and floors it crosses. The room with the worst path decides where node A goes.
- Place node A along that line, at the furthest point that still reads -55 to -65 dBm back to the gateway — same principle as the halfway-in-signal rule for extenders, applied to backhaul.
- Check the node's reported link quality in the app and give it two minutes to settle before believing the number.
- Only add node B if a priority room is still weak. Place it relative to whichever existing node gives it the best parent link, keeping the two-hop ceiling in mind.
- Walk the house on a call from one end to the other. Handoffs you can hear mean the overlap between nodes is too thin, so pull the nodes slightly closer together.
Deciding the node count before you buy the kit#
The expensive version of this article is buying the three-pack, discovering that two would have done, and leaving the spare in a drawer. Range Up settles that argument on paper. Draw the rooms, set the material preset to the way the house is built and push the wall and floor loss figures up if it is heavier than that, and stand the gateway where the coax outlet and the power outlet force it to live. The heatmap that comes back is your honest starting point — per floor, in the 3D view, when the house has more than one.
From there the count answers itself. Name the room that has to work, let the app rank satellite spots against it, and read the side-by-side view for its pick. If one well-chosen satellite already carries that room into usable coverage, the third box in the kit is spare, and you learn that before the courier arrives rather than after. What no simulation can do is read your live network: it predicts from the building, so treat it as the step that cuts five plausible spots down to one, then confirm the parent link in your mesh app once the node is plugged in. Install Range Up, or start with the extender placement hub.
Frequently asked questions#
How many mesh nodes do I need for a 2,000 sq ft house?
Two is the usual answer for a 2,000 sq ft home built with drywall partitions, and three if it is brick, plaster, or spread over three floors. Count the walls and floors between the gateway and your worst room rather than trusting the square footage alone. If the gateway can sit centrally and high, two nodes cover most homes of that size comfortably.
How far apart should mesh nodes be?
Far enough that they are not duplicating coverage, close enough that the satellite still reads -55 to -65 dBm from its parent. In practice that is roughly 30–40 feet through one interior drywall wall on 5 GHz, or 15–25 feet through masonry. Distance is a proxy: the signal reading between nodes is the number that actually matters.
Can you have too many mesh nodes?
Yes. Wireless nodes share airtime with each other and with your devices, so extra nodes in a small home add contention and more handoff decisions without adding useful coverage. If two nodes see each other at better than about -55 dBm, they are too close and one of them is not earning its place.
Should mesh nodes be stacked on the same spot on each floor?
Near the stairwell is usually better than directly stacked. Signal travels between floors far more easily through an open stair than through a concrete or joisted slab, so a node on the landing typically links back to the gateway better than one placed vertically above it. Stacking works best in timber-framed homes with thin floors.
Do mesh nodes need line of sight to each other?
No, but every wall and floor in between subtracts from the backhaul budget. One drywall wall is fine, two is usually fine, and a masonry wall or concrete floor can consume the whole allowance on its own. If you cannot get a satellite stronger than -70 dBm from its parent, the answer is a different position or a cable, not a stronger node.
Is it worth wiring one mesh node with Ethernet?
Almost always, and it is the highest-value change you can make to a mesh network. A wired node removes the per-hop throughput penalty entirely and frees you to place it purely for coverage rather than for backhaul signal. If only one node can be wired, wire the one furthest from the gateway.
Will more mesh nodes make my internet faster?
No. Nodes redistribute the connection you already have; they cannot exceed what your plan and router deliver. Extra nodes help when rooms are failing because of weak signal, and do nothing at all when the bottleneck is your ISP speed, an old client device, or a congested channel.