One name for both is the right default, because devices then move between the bands on their own as conditions change. Separate names are worth having only when a specific device needs pinning to a specific band.
The choice looks like a naming preference and is really a choice about who decides which band a device uses.
What one name does
When the bands share a name, the device chooses. It looks at what it can hear, joins the band it prefers, and moves to the other one when conditions change — walking from the room with the router to the far end of the house, a phone can slide from the higher band down to the lower one without anybody noticing.
That is almost always what you want, because the device knows things the router does not: how strong the signal is where it is standing, and what its own radio can do.
It also means one name and one password on every device in the house, which is worth more in a household than any tuning.
What separate names do
They take the decision away from the device and give it to whoever typed the name in. That is useful in exactly three situations.
A device that must stay on 2.4 GHz. Some equipment has no 5 GHz radio, and some of it will not complete its initial setup while a shared name is being broadcast on several bands. Makers who know this publish it in their setup instructions.
A device that must stay on 5 GHz. A fixed machine near the router, where you would rather it never fell back to a crowded lower band.
Diagnosis. Temporarily separating the names is a quick way to find out whether a problem belongs to one band, and then to put the names back.
Where the real problem usually is
People separate the names because a device sticks to the wrong band, and the sticking is normally a roaming behaviour rather than a naming one: a phone that joined the higher band near the router keeps holding on to a weak signal rather than moving to the stronger, lower-band one.
That behaviour lives in the client, not in the router. Some access points and mesh systems implement mechanisms that encourage a device to move on, and makers describe them in their own words on their own management pages. They help; they do not overrule a device that has made up its mind.
Guest networks are a separate question
A guest network is a second name for a different reason — separation, not band selection — and it should follow the same rule internally: one guest name across the bands unless something specific needs pinning.
The default worth starting from
One name for 2.4 and 5 GHz. Decide about 6 GHz separately, because roaming between a 6 GHz radio and the others is where implementations differ most. And keep a separate 2.4 GHz name in reserve, unused, for the day a new device refuses to be set up any other way.
The questions that come up before an order
Why will one old device not join the network at all?
Some older equipment only has a 2.4 GHz radio and some of it is confused by a network broadcast on several bands under one name. Where a maker publishes a setup requirement of that kind, the usual remedy is a separate 2.4 GHz name, kept for those devices and used by nothing else.
Does the 6 GHz band follow the same rule?
It can be broadcast under the shared name or under one of its own, and the two behave differently for a device that roams. It also carries a condition the other bands do not: operation there requires WPA3, so a network name on 6 GHz is always a protected one.
Last reviewed 10 September 2026