Wired vs. Wi-Fi for VoIP: Why the Cable Still Wins

The short answer

If you can run an Ethernet cable to your VoIP phone or the computer running your softphone, do it. Wired connections are more consistent, lower jitter, and eliminate an entire class of problems that Wi-Fi introduces. This has been true for years and remains true despite improvements in wireless technology.

That said, plenty of people take VoIP calls on Wi-Fi every day and it works fine. The question is not whether Wi-Fi can work. It is whether it will work reliably enough that you stop thinking about it.

How Wi-Fi creates problems for voice

Wi-Fi operates on a shared medium. Every device connected to an access point takes turns transmitting. The protocol that manages these turns (CSMA/CA) works well enough for most traffic, but it introduces variable delays that voice traffic is particularly sensitive to.

Contention. When multiple devices want to transmit at the same time, they back off for random intervals and retry. The more devices on a channel, the more contention, the more variable the delays. In a busy office with 30 devices per access point, those delays add up.

Interference. The 2.4 GHz band is crowded. Neighboring networks, Bluetooth devices, microwave ovens, baby monitors, and wireless cameras all operate in or near this frequency range. Interference causes packet corruption and retransmission, which means jitter spikes and occasional loss.

Signal strength variation. Move a few feet, turn a corner, or have someone walk between you and the access point, and signal strength changes. Lower signal strength means lower modulation rates and higher error rates. This happens constantly and unpredictably.

Channel switching and roaming. If your device decides to switch to a different access point or channel mid-call, there is a brief disruption. Modern fast-roaming protocols (802.11r) reduce this, but many networks are not configured for them.

The retransmissions you never see

The mechanism that does most of the damage is invisible from the IP layer, which is why Wi-Fi problems so often survive a round of network troubleshooting.

Wi-Fi retransmits at layer 2. When a frame is not acknowledged, the radio sends it again, and it will keep trying several times before giving up. From the perspective of IP, and therefore from the perspective of most diagnostic tools, nothing was lost. The packet arrived. It simply arrived late, because it took three attempts.

For a file download that is a good trade: correctness matters and a few milliseconds do not. For voice it is the wrong trade entirely, because a packet that arrives after its playout deadline is discarded by the jitter buffer and is functionally lost anyway. Wi-Fi works hard to convert loss into delay, and voice then converts that delay straight back into loss.

This is the single best explanation for the common complaint that "the network shows no packet loss but calls sound choppy." The loss is real; it is just happening after the measurement point.

One slow device can degrade everyone

Airtime is the resource that actually runs out, and it is shared unequally.

A device far from the access point, or behind a wall, negotiates a lower data rate. Sending the same amount of data at a lower rate takes proportionally longer, and while it transmits, nobody else on that channel can. A single laptop in a far corner on a poor link can consume a disproportionate share of the cell's airtime, and every other client, including the phone on the desk next to the access point, waits.

The counterintuitive consequence is that the device with the problem is often not the device with the symptom. Someone complains about call quality at a desk with excellent signal, and the cause is a tablet three rooms away clinging to the same access point. Airtime fairness features on better access points mitigate this, but the underlying physics does not go away.

DFS: the failure nobody expects

This one is worth knowing because it produces a dramatic symptom with no obvious cause.

Large parts of the 5 GHz band are shared with radar: weather radar, military and aviation systems. Access points using those channels are required to listen for radar and, on detecting it, vacate the channel immediately. Not gradually, and not at a convenient moment.

When that happens, every client on that access point is moved, and any call in progress takes a hit measured in seconds rather than milliseconds. Calls drop outright. And because the trigger is an aircraft or a weather sweep rather than anything on your network, it correlates with nothing you can see in your own monitoring.

The signature is calls failing simultaneously across everyone on one access point, with no other network event to explain it, sometimes recurring at similar times of day. If that matches what you are seeing, check whether your access points are using DFS channels and pin voice-carrying radios to non-DFS channels instead.

The numbers

The figures below are measured examples from typical office networks, not guarantees: your environment will produce its own numbers, which is why measuring beats assuming. As a representative example: baseline jitter of 5 to 15ms over office Wi-Fi during business hours, with occasional spikes to 30ms or higher, against 1 to 3ms with minimal variance on a wired connection on the same network.

Packet loss on a healthy Wi-Fi network might run 0.1% to 0.5% under normal conditions. That does not sound like much, but it can spike to 2% or more during interference events or heavy congestion. A functioning switch port shows near-zero loss at the access layer, though wired is not immune to congestion, because access ports still share uplinks and WAN queues, and a saturated uplink degrades wired and wireless clients alike. The wired advantage is predictability at the last hop, not exemption from the rest of the path.

These differences matter because VoIP quality degrades nonlinearly. Going from 1ms jitter to 10ms jitter is barely noticeable. Going from 10ms to 40ms (a spike that Wi-Fi produces regularly) can push packets past the playout deadline, where the jitter buffer starts discarding them.

When Wi-Fi actually works fine

Not every VoIP scenario needs wired reliability. Wi-Fi works well enough when:

The access point is lightly loaded. A home office with a few devices on a modern Wi-Fi 6 access point will produce excellent results. The problems start at scale.

The device is close to the access point with good line of sight. Strong signal means higher modulation rates and fewer retransmissions. If your laptop sits three feet from the router, Wi-Fi jitter will be minimal.

The 5 GHz or 6 GHz band is in use. These bands have more available channels and less interference than 2.4 GHz. They also have shorter range, which means fewer competing devices per channel.

The calls are internal or low-stakes. A quick team standup is more forgiving than a sales call with a prospect. If occasional audio hiccups are acceptable, Wi-Fi is fine.

When you need the cable

Customer-facing calls. If you are on the phone with clients, partners, or prospects, audio quality reflects on your business. One garbled sentence during a sales call costs more than a $5 Ethernet cable.

Contact centers and support desks. Covered in its own section below; this is the clearest case on the list.

Rooms with dense device counts. Conference rooms, trading floors, open offices with 50+ wireless devices per access point. The contention math works against you.

Environments with known interference. Manufacturing floors, medical facilities with wireless equipment, buildings with thick walls and lots of concrete. These create unpredictable Wi-Fi behavior.

Contact centres are a special case

For most offices this is a judgement call. For a contact centre it is not, and the reason is arithmetic rather than preference.

An agent takes perhaps sixty calls a day. A degradation rate that a normal employee would experience as "the phone was a bit odd once last month" becomes, at that volume, several damaged customer conversations every week per agent, and they are damaged in the specific way that costs most, which is the customer having to repeat themselves to someone paid to be listening.

The environment works against you too. A contact centre floor is the worst case for every mechanism above: high device density in a small area, everyone transmitting at once, and, unlike a normal office where call volume is spread thin, everyone doing it simultaneously, because agents are all on calls during the same peak hours. The contention curve and the business's busiest hour are the same curve.

Add headsets. Many wireless headsets use 2.4 GHz DECT or Bluetooth, putting more radio traffic into the same space as the Wi-Fi carrying the calls.

There is also a quieter operational cost. On a wired floor, "my audio is bad" is a fault you can investigate: the path is deterministic and the variables are few. On a wireless floor it may be the agent's position, their neighbour's laptop, a roaming event, or interference that stopped ten minutes ago. Wireless does not just add call quality risk; it adds a category of problem that is expensive to diagnose and easy to fail to reproduce.

If the floor is already wireless and recabling is not on the table, the mitigations below all still apply, but measure before and after rather than assuming. And if you are sizing a new floor, cabling desks is one of the cheapest decisions in the whole build.

Does Wi-Fi 6 change the answer?

Partly, and it is worth being precise about which part, because "we're on Wi-Fi 6 now" gets offered as a reason not to cable.

Wi-Fi 6 attacks contention directly. OFDMA lets an access point split a transmission among several clients at once instead of making each wait its turn, which suits voice unusually well: voice is many small packets from many devices, which is precisely the pattern that suffered most under the older take-turns model. Target Wake Time also reduces the power-save penalty that used to add latency after each idle period. Both are real improvements, and a modern Wi-Fi 6 or 6E deployment genuinely is better for voice than the equipment it replaced.

What it does not do is make the medium deterministic. Interference is still interference. Signal still varies as people move. Roaming still has a gap. DFS still relocates you when radar appears. And 6E's extra spectrum helps only where both the access points and the client devices support it, which on a floor of mixed-age handsets and laptops is rarely all of them.

The honest summary: Wi-Fi 6 raises the floor and narrows the gap. It does not close it, and it does not turn a shared medium into a dedicated one.

Making Wi-Fi work better for VoIP

If running cables is genuinely impractical, these steps help:

Dedicate an SSID for VoIP with WMM (Wi-Fi Multimedia) prioritization enabled. WMM gives voice-classified traffic priority over background traffic. Most enterprise access points support this.

Use the 5 GHz band and set your VoIP devices to prefer it. Band steering on the access point helps with this. The 5 GHz band has more non-overlapping channels and less interference.

Reduce access point density problems by adding more access points at lower power rather than fewer at high power. Each AP serves fewer clients, reducing contention.

Disable power save mode on devices used for VoIP. Power save mode causes the wireless radio to sleep and wake in cycles, which adds latency to the first packet after a sleep interval.

Keep firmware updated on your access points. Wi-Fi driver and firmware bugs are common and often cause the kind of intermittent issues that are hard to diagnose.

The real-world test

The best way to know if your Wi-Fi is good enough for VoIP is to test it under realistic conditions. Not at 6 AM when the office is empty, but during the afternoon when everyone is on video calls and syncing files. Jitter and loss that stay within acceptable ranges during peak load mean your wireless setup can handle voice traffic. Numbers that spike tell you where the ceiling is.

That is the kind of test our VoIP quality test is designed for. Real traffic patterns, measured over meaningful time periods, during the conditions that actually matter. Run it once from a wired machine and once over Wi-Fi from the same desk and compare the jitter numbers side by side.

For a complete look at how your local network affects VoIP quality, see Your Local Network: The Part You Control in our VoIP From the Ground Up series.