Keystone Integration
All articles
April 29, 202612 min read

Wi-Fi 7 MLO explained: what it actually changes for a real Utah home

Multi-Link Operation is the marquee Wi-Fi 7 feature, and the most misunderstood. Here is what MLO actually does on real client devices in real Utah houses, when it matters, when it is wasted, and how we configure it on UniFi U7 installs.

Wi-Fi 7MLONetworkingAccess PointsUniFi

Multi-Link Operation (MLO) is the headline feature of Wi-Fi 7. Every product page mentions it. Almost none of them explain what it actually does in a real house, on real client devices, with real interference. Most homeowners we talk to in 2026 think MLO is just “Wi-Fi 7 is faster.” It isn’t — or rather, that’s the least interesting thing it does.

This post is the technical follow-up to our Wi-Fi 6E vs Wi-Fi 7 buyer’s guide — that one was “should you upgrade.” This one is “here’s what MLO actually changes about how your phone, your AP, and the 6 GHz band talk to each other,” with specifics drawn from installs we’ve done across the Wasatch Front since the U7 platform shipped.

What MLO actually is

Before Wi-Fi 7, a client device picked one band at a time. Your iPhone connected on either 5 GHz or 6 GHz, and the AP and the phone would handshake every packet on that single radio link. If a microwave fired, a neighbor started a Zoom call on the same channel, or a 5 GHz radar event triggered DFS, you got a glitch — because the link had nowhere else to go.

MLO lets a Wi-Fi 7 device hold multiple simultaneous links to the same AP, across different bands. A modern phone in MLO mode can be associated on 5 GHz and 6 GHz at the same time. The phone and the AP coordinate which packets go on which link and how they’re reassembled on the other side. There are three flavors:

  • STR (Simultaneous Transmit and Receive). Both links carry independent traffic in parallel. Aggregate throughput goes up. This is what marketing materials usually mean when they say “double the speed.”
  • EMLSR (Enhanced Multi-Link Single Radio). The client listens on both links but transmits on one at a time, picking whichever is currently cleanest. This is what most phones actually do — they don’t have the radio budget to truly run both bands at once on battery.
  • Packet-level redundancy. The same packet goes over both links. The first copy to arrive wins; the duplicate is discarded. Latency and jitter drop hard. This is the mode that matters for real-time apps.

In practice, current iPhones and Galaxy phones default to EMLSR with opportunistic packet redundancy when the AP supports it. M-series MacBooks with Wi-Fi 7 can do full STR if the AP and the channel layout allow it.

Why this matters more in Utah than the marketing implies

Utah’s 6 GHz environment is unusually clean. Most metros have a 6 GHz problem already brewing — dense apartments stacked vertically, every neighbor running a 160 MHz or 320 MHz channel, AFC (Automatic Frequency Coordination) constraints near major airports and weather radar. The Wasatch Front so far has none of that. We do AP surveys in Holladay, Draper, Lehi, and Park City and routinely find the entire 6 GHz band almost empty even in dense neighborhoods.

That changes the value math for MLO. In a Manhattan co-op or a downtown Seattle high-rise, MLO’s big win is dodging neighbor congestion on the fly. In a Holladay rambler or an Alpine custom build, the 6 GHz channel is yours and the second 5 GHz link mostly exists to ride out transient interference from your own house — the microwave, a 5.8 GHz cordless phone in a neighbor’s yard, the occasional DFS hit on a 5 GHz channel near KSL’s mountain transmitters.

The upshot: in most Utah homes, MLO buys you reliability, not throughput. Your speed test won’t change much. Your FaceTime calls will stop glitching.

What 6 GHz looks like inside a house, MLO or not

There’s a related point that doesn’t get made enough: 6 GHz attenuates faster through walls than 5 GHz, which attenuates faster than 2.4 GHz. That’s physics, not a Wi-Fi 7 problem. In a typical 4,000 sq ft Lehi build, a single Wi-Fi 7 AP in the great room will give you full 6 GHz performance in maybe 60% of the house. The rest of the floor plan falls back to 5 GHz, where MLO still works (5 GHz + 2.4 GHz is a valid MLO combination) but you’ve lost the headline 320 MHz channel.

This is the answer to the question we keep getting: “Why does my Wi-Fi 7 router still feel slow in the basement?” The router is fine. The 6 GHz signal isn’t making it through three interior walls and the floor. The fix is the same as it always was — more wired APs, placed correctly — not a different router.

Client adoption: what actually does MLO in 2026

The painful truth from running tcpdumps on customer networks: even when the AP and client both claim Wi-Fi 7, MLO doesn’t always engage.

  • iPhone 16 Pro / 17 lineup. EMLSR on 5 + 6 GHz, reliably. We see it on every fresh UniFi U7 Pro Max install where the channel plan is clean.
  • Samsung Galaxy S24 / S25. EMLSR, sometimes STR depending on firmware and battery state. Performance Mode helps.
  • Pixel 9 / 10 Pro. EMLSR on most firmware revisions. Google has been quietly tuning this in OTA updates.
  • M4 / M5 MacBooks. Full STR on AC power, EMLSR on battery. Throughput nearly doubles on STR-capable links.
  • Intel BE200 / BE201 laptops. STR capable, but driver-dependent. Lenovo and Dell laptops have shipped firmware that disables MLO completely until updated. We check this on every install.
  • Everything else — Ring, Sonos, TVs, IoT, older phones. No MLO at all. They speak Wi-Fi 5 or 6 to the AP, and that’s fine. These devices live on a separate IoT VLAN on most properly designed networks anyway.

If your household is a couple flagship phones and a MacBook, MLO will engage and you’ll feel it most on real-time traffic. If your household is two older iPads, four Chromebooks, and a Windows laptop from 2022, MLO will engage on basically nothing and you’re paying for a feature that’s sitting idle.

The 6 GHz channel-planning problem

Here’s a wrinkle that catches people who upgrade APs without thinking through the channel plan. 6 GHz has 59 20 MHz channels in the U.S. — far more than 5 GHz. With 320 MHz channels (Wi-Fi 7’s widest), you only get three non-overlapping blocks. With 160 MHz, you get seven. Every doubling of channel width halves the number of clean channels available.

For MLO to do anything useful on 6 GHz, that 6 GHz link has to actually be clean. If you have multiple Wi-Fi 7 APs in the same house all running 320 MHz on 6 GHz, they will fight each other. We’ve seen two-AP installs where dropping the 6 GHz channel width from 320 MHz to 160 MHz improved aggregate throughput, because the APs stopped colliding.

Practical guidance for a typical Utah single-family home with 3–5 APs:

  • Pick 160 MHz on 6 GHz, not 320. The marketing- spec speed loss is invisible in real use; the channel-overlap relief is huge.
  • Let the controller assign 6 GHz channels rather than fixing them. UniFi’s channel planner has gotten genuinely good at avoiding co-channel interference between your own APs.
  • On the 5 GHz radio (which MLO needs as the second leg), use 80 MHz channels. 160 MHz is brittle in the U.S. because of DFS — every weather radar hit bounces you off-channel.
  • Leave 2.4 GHz at 20 MHz. Always. There are exactly three usable channels (1, 6, 11) and nothing about Wi-Fi 7 changes that.

Where we’ve actually felt the difference

On installs we’ve done in the last six months, here’s where MLO has produced a noticeable improvement vs the same physical AP layout running Wi-Fi 6E:

  • A Park City client with a backyard hot tub at the far edge of 6 GHz coverage. On 6E, FaceTime audio would stutter when the wireless signal margin got thin. With MLO, the call rides 5 GHz with 6 GHz as a redundant copy and the stutters are gone.
  • A Holladay home office with two simultaneous Zoom calls on different floors. 6E worked, but occasional hiccups during high download windows. MLO holds the call clean even when someone else starts a 4K stream.
  • A Sandy basement gym with a Peloton, an Apple TV, and a kid’s Switch on the same AP. 6E was fine for any one of them. MLO let all three run at once without one starving the others, even though the 6 GHz signal is weak that far from the AP.

None of these are speed-test wins. They’re jitter and reliability wins. The speed test result looks identical.

When MLO is wasted money in 2026

  • You only have one AP. A single AP in a 3,500 sq ft house can’t cover the floor plan with 6 GHz no matter what. MLO needs both bands to be reachable, and at the basement or far corner where you actually have a problem, the 6 GHz radio isn’t there. The fix is more APs, not a better radio.
  • Your client devices are mostly Wi-Fi 6 or older. MLO requires Wi-Fi 7 on both ends. If your phone is older than a 2024 flagship, you’re not getting MLO at all.
  • You’re running a busy mesh with wireless backhaul. The wireless mesh hop eats most of the gain MLO would have given the client. Wired backhaul is the right answer.
  • You haven’t fixed the upstream side. A Wi-Fi 7 AP behind a consumer ISP router with a single 1 Gbps WAN port has nowhere to put the extra throughput. The bottleneck is the router, not the radio.

How we configure Wi-Fi 7 + MLO on a real install

For a typical 4,500 sq ft Lehi or Draper new build we’re cabling and commissioning right now, the stack looks like:

  • Three or four UniFi U7 Pro Max APs, ceiling- mounted, all wired back to the rack on Cat6A — Cat6 isn’t worth the small savings on a Wi-Fi 7 install.
  • A UDM Pro or Cloud Gateway Max in front, with multi-gig WAN to whatever fiber the client has (UTOPIA, Google Fiber Webpass, Xfinity multi-gig).
  • 6 GHz on 160 MHz channels, controller-managed. 5 GHz on 80 MHz. 2.4 GHz on 20 MHz, throttled to something modest for IoT.
  • MLO enabled, packet redundancy left at default. Client steering on, but conservative — aggressive band steering breaks more things than it fixes, especially Sonos.
  • A separate IoT VLAN and SSID on Wi-Fi 6 only — no point exposing IoT cameras and plugs to the 6 GHz radio they can’t use, and it keeps the flagship-client airtime clean.

That’s the blueprint. The differences from a Wi-Fi 6E install we would’ve done two years ago are small but real: Cat6A instead of Cat6, MLO enabled, narrower 6 GHz channels, and a slightly more conservative client-steering policy.

Bottom line

MLO is the feature that finally makes Wi-Fi feel like a wired connection for real-time traffic. It doesn’t make your speed test faster. It makes the things that actually break — video calls, online gaming, multi- room audio sync, cloud-saved game progress — stop breaking.

For the right house, with the right clients, on a properly cabled AP layout, it’s a real upgrade. For most Utah homes today, the bigger win is still “more APs, wired correctly” and not relying on wireless mesh backhaul. MLO sits on top of that foundation. It can’t replace it.

Keystone Integration designs and installs Wi-Fi 7 networks across Draper, Holladay, Lehi, Park City, and the rest of the Wasatch Front — properly channel-planned, MLO- tuned, and wired on customer-owned gear. See the full service list or get in touch for a site survey of your floor plan.

Keep reading