What type of internet connection do I need for VoIP?

VoIP runs on almost any modern broadband connection, because a phone call is one of the lightest things you can send over the internet. A single voice call uses roughly 85 to 100 kilobits per second in each direction, which is well under half a megabit and a small fraction of what streaming a video takes.[3][1] The practical question is not whether your connection is fast enough in raw megabits, since most are, but whether it stays steady and has enough upload capacity to carry clear audio while everything else on the network keeps running.[1]

Speed is rarely the limit; stability is

A voice call breaks your speech into a continuous stream of small packets that have to arrive quickly, in order, and at an even pace. That makes a call sensitive to three things a speed test often hides: delay, the variation in delay known as jitter, and lost packets.[5][7] A connection can show a high download number and still deliver choppy calls if it adds too much latency under load or drops packets during busy periods, so the quality of the link matters as much as its size.

Upload capacity is half the job

Because a call sends your voice out at the same moment it receives the other person's, the upload side of your connection carries as much of the conversation as the download side.[1] Many home and small-office plans give you plenty of download speed but a much smaller upload allowance, and that upload ceiling, not the download figure, is usually what limits how many simultaneous calls a connection can handle cleanly.[8]

A single VoIP call typically uses about 85 to 100 kilobits per second in each direction once you count the headers that IP, UDP, and RTP add to every packet.[3] The exact figure depends on the codec, the software that compresses your voice. The common uncompressed codec, G.711, needs roughly 85 to 87 kilobits per second per direction, while a compressed codec such as G.729 fits the same call into about 31 kilobits per second at a small cost in fidelity.[3] Modern calling apps often use adaptive codecs: Microsoft Teams, for example, runs audio between about 10 and 76 kilobits per second per stream depending on conditions.[4]

Planning for more than one call

To size a connection for a team, count the calls you expect at your busiest moment rather than your total number of phones, since people are rarely all on the line at once. A common planning figure is about 0.1 megabits per second per call, so multiplying your peak concurrent calls by that number gives a working estimate of the bandwidth voice will need.[2] Adding 20 to 30 percent on top covers signaling overhead and leaves room for the email, file syncing, and web traffic sharing the same link.[2]

Upload is the tighter constraint

Both directions carry audio, so upload and download requirements are effectively equal per call.[1] On an asymmetric connection where upload is a fraction of download, the upload figure sets your real ceiling. A plan advertised at 200 megabits down but 10 megabits up still has ample room for voice, yet that 10 megabit upload is the number to check against your peak call count and everything else uploading at the same time.[1][8]

Three measurements decide whether a connection carries clean calls: latency, jitter, and packet loss. They describe how well packets move rather than how many can move at once, which is why a fast connection with poor numbers here still sounds bad.[5]

Latency, the one-way delay

Latency is the time a packet takes to travel from your phone to the far end. The long-standing target comes from the ITU-T standard for one-way transmission time, G.114, which treats delay up to about 150 milliseconds one way as acceptable for normal conversation.[6][5] Past roughly 150 milliseconds people start talking over each other, and by a few hundred milliseconds a call feels like a two-way radio.[5]

Jitter, the variation in delay

Jitter is how much the delay between packets varies. A receiver holds incoming audio in a small jitter buffer to smooth out uneven arrivals, but that buffer only helps up to a point, so voice traffic should generally stay under about 30 milliseconds of jitter.[7][5] High jitter is what turns a call robotic or garbled even when the average speed looks fine.[7]

Packet loss

Packet loss is the share of voice packets that never arrive. Voice tolerates very little of it: even 1 percent loss can noticeably degrade a call on the common G.711 codec, so under 1 percent is the usual working limit and lower is better.[5]

Fiber is the strongest fit for VoIP because it delivers symmetrical upload and download speeds, often up to about 10 gigabits per second, on a link that holds steady latency under load.[8] Equal upload and download means a connection rated for, say, 500 megabits gives you the same 500 megabits going out as coming in, so the upload ceiling that limits other connection types largely disappears.[8] That symmetry is why fiber suits offices running many simultaneous calls or combining voice with video meetings and cloud applications.[10][8] If fiber is available at your location and the budget allows, it removes most of the network guesswork. Its main drawback is that it reaches fewer buildings than cable or DSL and can cost more to install.

Cable internet handles VoIP well for most offices, offering download speeds up to about 2 gigabits per second, though its upload is a fraction of that.[8] For voice the asymmetry rarely matters until you run many calls at once, since even a modest upload allowance holds dozens of simultaneous calls. The point to watch is shared capacity: cable segments are shared among nearby subscribers, so upstream speed can dip during busy neighborhood hours, and a call needs that upstream to stay clear.[8] Checking the plan's upload figure against your peak call count, and asking the provider about typical peak-hour performance, tells you whether the upstream has room. For a small or midsize office that is not running a call center, cable usually carries voice cleanly.[1]

DSL carries VoIP for a small number of lines, with download speeds up to about 100 megabits per second and a noticeably smaller upload allowance.[8] Ooma, for example, treats DSL in the range of 5 to 35 megabits as adequate for voice, since a single call needs so little.[1] The limitation is upload, which sets how many concurrent calls the line can hold, and DSL speeds fall off the farther your office sits from the telephone exchange, so two buildings on the same plan can perform differently. DSL suits a home office or a small team with a few phones, and it is often the fallback where fiber and cable have not reached. Where you expect steady simultaneous calls, confirm the upload figure carefully before committing to it.

Fixed wireless and cellular data can both carry VoIP, and they are especially useful as a backup path when a wired connection fails. Fixed wireless reaches speeds up to about 400 megabits per second, and mobile networks in the United States average around 41 megabits, either of which is far more than a call requires.[8][1] The trade-off is consistency: wireless links vary with signal strength, weather, and how many users share the tower, and that variation shows up as jitter, the quality metric voice is most sensitive to.[7] For a fixed office, a well-installed fixed-wireless antenna can be steady enough for daily calling, while cellular is better suited to mobile users and to automatic failover than to being the only connection for a busy phone system.

Satellite internet works for VoIP only when the latency is low enough, and that depends on the orbit. Low-Earth-orbit services such as Starlink deliver round-trip latency of roughly 25 to 60 milliseconds, which is well within the range calls need and lets conversations feel natural.[9] Traditional geostationary satellites sit about 35,000 kilometers up, which adds 600 to 700 milliseconds of round-trip delay before any processing, enough that callers constantly talk over each other.[9] So a low-orbit connection is a reasonable choice for voice in areas without wired options, while older geostationary service is best kept for data rather than real-time calls. Satellite links can also see brief jitter during handoffs, so pairing them with a jitter buffer and quality-of-service settings helps.[9][7]

The connection into your building is only part of call quality; how voice travels across your own network matters just as much. A link that meets every target at the modem can still produce choppy calls if the office network mishandles the traffic.[4]

Wired beats Wi-Fi for fixed phones

Wi-Fi is convenient but was not designed for real-time media, and it introduces interference and variable delay that show up as jitter on calls.[4][7] For desk phones and stationary computers, a wired Ethernet connection is the more predictable choice. Where Wi-Fi is necessary, the 5 gigahertz band handles voice better than the more crowded 2.4 gigahertz band, and turning on Wi-Fi Multimedia prioritization helps.[4]

Prioritize voice with QoS

Quality-of-service settings tell your router to send voice packets ahead of email, backups, and file downloads, which keeps calls clean when the network gets busy.[4] Even a connection with plenty of bandwidth benefits from prioritization, because it protects calls during the unexpected traffic spikes that provisioning alone cannot predict.[4]

Plan for outages

A VoIP phone depends on both power and internet, so a blackout or an internet drop takes the phones with it unless you plan around that. A battery backup on the router, plus a second connection such as cellular or fixed wireless that voice can fail over to, keeps calls working when the primary link goes down.[7]

VoIP does not need a fast or expensive connection to work well, and a few common assumptions are worth setting aside.

It does not need gigabit speed

A call uses well under half a megabit per second, so gigabit service buys nothing for voice alone; the value of a bigger plan is headroom for everything else your team does online, not the calls themselves.[1] A modest connection that meets the latency, jitter, and loss targets carries voice cleanly.[5]

A fast download alone is not enough

A high download number does not guarantee good calls, because voice quality rests on upload capacity and on steady latency and low jitter, none of which a download-speed test reveals.[1][5] A connection can test fast and still sound poor under load.

It does not need a separate phone line

VoIP shares your existing internet connection rather than requiring a dedicated voice circuit, which is much of its appeal.[4] A dedicated or business-grade circuit can help a heavy-calling site by guaranteeing capacity, but it is an upgrade for reliability, not a requirement for VoIP to function.

Newer is not automatically better

A 5G or fixed-wireless link is not inherently better for a stationary office than DSL or cable; what matters is which connection meets the quality targets consistently at your location, and a steady wired line often outperforms a variable wireless one for fixed phones.[7][8]