A single VoIP call uses roughly 85 to 100 kbps in each direction, which is about 0.1 Mbps up and down. That is a tiny amount of data, far less than streaming a video or even loading a busy web page. Because each call is so light, even a busy office needs much less bandwidth than most people assume. The real question is never "is my internet fast enough for one call," it is "how many calls happen at the same time, and what else is sharing the line."
How much one call really uses
A VoIP call sends a steady stream of small audio packets in both directions. With a common, good-quality codec, the audio itself is light, and once you add the overhead the network wraps around each packet, you land at roughly 85 to 100 kbps per direction. Round it to 0.1 Mbps and you have a number that is easy to plan with.
To put that in perspective, a single standard-definition video stream can use 30 to 50 times more bandwidth than a voice call. So if your connection can handle one person watching a video, it can comfortably handle a room full of phone calls. Voice is one of the lightest things you can run over the internet. For the bigger picture of how the audio becomes data in the first place, see how does VoIP work.
A simple way to estimate your office
The mistake people make is sizing for their total number of phones. You do not need bandwidth for every handset, only for the calls happening at once. Most teams are never all on the phone simultaneously. Here is the simple method:
- Count concurrent calls, not phones. Estimate how many people will realistically be on a call at the same time during your busiest hour. A 20-person office might peak at 6 to 8 concurrent calls.
- Multiply by about 0.1 Mbps per direction. 8 concurrent calls need roughly 0.8 Mbps of upload and 0.8 Mbps of download just for voice.
- Add headroom. Build in extra room, often 2x the voice number, so a busy moment does not push you to the edge.
- Account for everything else. Your connection is also carrying web, email, file syncing, video meetings, and cloud apps. Size your overall internet plan around all of that, with voice as a small slice on top.
Worked example: 10 concurrent calls need about 1 Mbps in each direction for voice. With headroom that is around 2 Mbps. Almost any modern business broadband or fiber plan clears that with room to spare, which is why bandwidth is rarely the thing that holds VoIP back.
Why quality beats raw speed
Here is the part that surprises people: a fast connection can still deliver bad calls. Voice is sensitive to how steadily data arrives, not just how much of it can flow. Three quality factors matter as much as the speed on your bill:
- Latency: the delay between speaking and being heard. High latency causes that awkward talking-over-each-other lag, even on a fast line.
- Jitter: uneven timing between packets arriving. When packets show up out of rhythm, audio sounds choppy or robotic.
- Packet loss: packets that never arrive. Even a small percentage of loss creates gaps, clipped words, and dropouts.
This is why a cheap, congested connection with plenty of advertised speed can sound worse than a modest but stable one. If your calls are rough, the fix is usually about stability, not buying more megabits. For a full walkthrough of diagnosing bad audio, see VoIP call quality.
Practical setup tips
Once you have enough bandwidth, a few simple choices protect call quality:
- Use a wired connection where you can. Plugging phones and computers into Ethernet avoids the jitter and interference that Wi-Fi can add.
- Turn on QoS. Quality of Service on your router lets you prioritize voice traffic so a big file upload does not starve a call. This is the single most effective setting for most offices.
- Get a business-grade connection. Business internet usually offers more symmetric upload speeds and more consistent performance than a basic residential plan, both of which help voice.
- Mind your upload. Voice needs upload as much as download, and many cheap plans skimp on upload. Check that your upload number can carry your concurrent calls.
Do those four things and bandwidth stops being a worry. The goal is not a giant pipe, it is a steady one with voice given priority.
Frequently asked questions
How much bandwidth does a VoIP call use?
Roughly 85 to 100 kbps in each direction, which is about 0.1 Mbps up and down per call. That includes the audio plus the overhead the network adds. A call needs very little on its own, so the real driver is how many calls run at the same time and what else shares the connection.
How do I estimate the bandwidth my office needs for VoIP?
Count concurrent calls, not total phones, then multiply by about 0.1 Mbps for each direction. Add headroom and account for everything else on the line, such as web, email, video meetings, and cloud apps. For example, 10 concurrent calls need about 1 Mbps for voice, and you size the rest of your plan around your other usage.
Is internet speed the only thing that matters for VoIP?
No. Raw speed is rarely the problem. Latency, jitter, and packet loss degrade calls even when you have plenty of speed. A stable, low-latency, low-jitter connection beats a fast but congested one, so quality matters as much as the amount of bandwidth.
