VoIP bandwidth requirements for businesses

About 100 kilobits (Kbps) per second, per call in each direction is a useful starting point for Voice over Internet Protocol (VoIP) bandwidth. Call quality depends on more than speed, though: latency, jitter, packet loss, upload capacity, Wi-Fi, and network equipment can all affect performance.1

A few things to keep in mind:

  • Voice traffic uses less capacity than video, but it needs steady delivery.
  • Codec settings can change the bandwidth required for each active call.
  • Peak-hour testing shows how VoIP performs under real network load.
  • Bandwidth headroom helps protect call quality when other apps create traffic spikes.

When calculating your VoIP bandwidth needs, add capacity for video meetings, cloud apps, backups, and daily internet use, especially during peak business hours.

How many people need to talk at the same time? That number helps your business and IT teams size business internet service, protect calls, and reduce network problems during busy work hours.

What is VoIP bandwidth?

VoIP bandwidth is the part of total internet capacity used to carry phone calls over a business network. It’s usually measured in Kbps for each active call.

A common planning range is 80 Kbps to 100 Kbps per active call. The exact amount depends on your system setup, network overhead, and codec, which helps voice data move efficiently across the network. In many offices, VoIP uses less capacity than video meetings or large file transfers. But voice traffic is more sensitive to delays and dropped data.

VoIP turns speech into data packets. Those packets travel across a local network and internet connection instead of Plain Old Telephone Service (POTS) lines. Late, missing, or out-of-order packets can cause gaps, echoes, robotic audio, one-way audio, or poor call quality.

In short, VoIP bandwidth gives voice packets the room they need to arrive on time and keep conversations clear. And while your network may look ready on paper, call volume decides how much of that space gets used during the busiest part of the day.

How much bandwidth is needed for VoIP?

The best way to estimate your VoIP bandwidth needs is to look at peak call demand, not total users. A 50-person office may not have 50 active calls at once, so the key question is how many calls happen during the busiest periods.

You also need to account for other high-traffic activity on the network, such as video meetings, cloud apps, and file transfers.

Consider upload capacity as well as download capacity. Each VoIP call sends and receives voice traffic, so weak upload speeds can hurt call quality even when download speeds look strong.

A per-call bandwidth estimate is a useful starting point, but real-world planning should leave room for peak call volume, other business apps, and extra capacity to help maintain steady performance.

Per-call planning

For a quick estimate, multiply the number of active calls by 100 Kbps. One active call uses roughly 0.1 megabits per second (Mbps) in each direction. Ten active calls use roughly 1 Mbps in each direction. Fifty active calls use roughly 5 Mbps in each direction, and 100 active calls use roughly 10 Mbps in each direction.

That math covers voice traffic only. Other apps still need capacity. A business running VoIP, video meetings, cloud software, and file transfers at the same time needs room beyond the voice estimate.

Codec choices and bandwidth impact

Codec names, such as G.711, G.729, and Opus, refer to encoding standards. They are not scores or quality ratings.

  • G.711 often uses 80 Kbps to 90 Kbps per call with overhead. It uses little compression and can deliver strong audio quality, but it also uses more bandwidth.
  • G.729 often uses 30 Kbps to 35 Kbps per call with overhead. It uses more compression, which lowers bandwidth use, though audio quality can be lower than G.711.
  • Opus uses an adaptive bitrate and can adjust bandwidth use based on setup and network conditions.2

Each codec balances bandwidth use, audio quality, device processing, and compatibility. Codec settings can change how many calls a network can support.

The bandwidth estimate is only a starting point. Per-call math gives teams a useful baseline. It doesn’t show how the network performs when calls run alongside video meetings and cloud apps. Large file transfers can add more strain. Call quality can be impacted when packets start waiting behind other traffic.

Taking a close look at your usage can help you mitigate the factors that can affect VoIP bandwidth and call quality.

What affects VoIP bandwidth and call quality?

VoIP bandwidth needs depend on more than the number of users. It’s shaped by the number of simultaneous calls, the codec or call settings, upload and download capacity, and other traffic on the network, such as video meetings, cloud apps, and file transfers.

Those same conditions can also affect call quality. Even when a connection has enough total speed, heavy network use or equipment limits can make voice traffic less consistent. That can contribute to the types of call issues covered above, including delays, gaps, echo, or distorted audio.3

If voice packets slow down, arrive late, or get dropped, callers may hear gaps, delays, echo, or robotic audio. These issues can happen even when a speed test shows enough bandwidth.

Latency, jitter, and packet loss

Latency is the delay between sending a data packet and receiving it. High latency can create awkward pauses during calls. Jitter is uneven delay. It happens as packets arrive at uneven times. Jitter can make audio sound choppy or unstable.

Packet loss happens as voice packets fail to reach their destination. Even small packet loss can cause missing words, robotic audio, or poor sound.

Common causes include congestion, Wi-Fi interference, routing problems, overloaded equipment, weak access links, and unstable connections.

Competing traffic and congestion

Other network activity can compete with voice traffic. Common examples include video meetings, software updates, cloud backups, large downloads, file sync tools, and streaming media.

Too many apps using the same connection can force voice packets to wait behind other traffic. That delay can make calls sound choppy, delayed, or unnatural.

Equipment and access speeds

Older modems, routers, firewalls, and unmanaged switches can struggle with many active calls.

Upload speed is important for VoIP because each call sends voice traffic out while receiving traffic from the other caller.

A connection with strong download speed and weak upload speed can still cause voice problems. Testing the full internet path gives teams a better view of call capacity.

VoIP quality depends on how consistently packets move, not just how much bandwidth a plan includes. When a call sounds bad, the cause is rarely obvious from the monthly service speed alone. Know and monitor your capacity to make sure your call quality is stable.

How to measure and verify VoIP bandwidth capacity

Testing and monitoring can show that a network has enough VoIP bandwidth during normal and peak use. A single speed test helps, but it doesn’t tell the full story. Your teams must look further to determine your VoIP bandwidth needs.

Run a speed test

A speed test measures real-world upload and download performance from one device at one point in time.

Run tests from a wired device to reduce business Wi-Fi variables. Test during peak hours, when employees are most active. Use several tests to see performance patterns over time. Upload and download results both count because VoIP calls need capacity in both directions.

Analyze results

Compare upload and download speeds with expected peak demand for active calls and collaboration tools. Many VoIP plans include extra capacity above the call estimate. This gives normal business traffic and usage spikes more room.

Test results for latency, jitter, and packet loss can provide more insight than speed alone. Low bandwidth, high latency, high jitter, and packet loss point to different network problems.

Monitor over time

Network monitoring can track use by app, location, device, or time of day. Firewalls, Simple Network Management Protocol (SNMP) tools, and cloud monitoring platforms can show patterns that a one-time test can miss.

Monitoring can also show how Quality of Service (QoS) rules perform. It can reveal how backups, updates, video meetings, or other high-use apps affect voice traffic.

Testing turns assumptions into evidence. Those results also point to the type of connection and backup design a business can trust when calls matter most.

How to plan an internet connection for VoIP bandwidth

To plan an internet connection for VoIP, start with how your business uses the network. Consider your expected call volume, video meetings, cloud apps, file transfers, and upload and download needs.

Then evaluate the connection itself. Look for enough capacity to support peak use, stable performance for voice traffic, low delay, and backup access if phone service needs to stay available during an outage.

Internet connection types

Offices with many active calls, frequent video meetings, cloud apps, and other network connections often use business fiber. Fiber commonly offers equal upload and download speeds. That can support real-time communications better than links with limited upload capacity.

Fixed wireless internet and 5G business internet can also support VoIP. Performance depends on coverage, signal quality, local network conditions, and traffic levels. In some locations, wireless service works as the main connection. In others, it supports backup access.

The connection type affects more than speed. Upload capacity, latency, stability, and availability all shape the VoIP experience that employees and customers hear.

Reliability and backup access

VoIP performance depends on a fast, reliable network because phone service, voice and collaboration tools, and many business applications all rely on the same connection.

Planning for VoIP should include enough bandwidth for peak use, stable performance for real-time traffic, and a connection that can support broader business continuity needs.

Some organizations use a primary connection with defined performance expectations, such as fiber or dedicated internet access. Many also include a failover setup that can route traffic to 5G or fixed wireless internet if the primary service has a problem.

VoIP bandwidth planning changes as your business evolves. Current usage may not reflect future demand, especially as call volume, collaboration traffic, cloud apps, and backup connectivity needs grow.

For business and IT managers, the practical takeaway is clear: VoIP bandwidth affects customer calls, employee productivity, uptime, and scalability. Strong planning should account for peak call volume, upload and download capacity, latency, jitter, packet loss, network equipment, QoS, and connection reliability.

A well-planned connection gives VoIP traffic enough room to perform today and enough flexibility to support future business needs. It can also create a clearer path for backup access, equipment upgrades, and ongoing network monitoring.

Build a network foundation that supports clear VoIP calls, collaboration tools, and business growth. Explore our voice and collaboration solutions. AT&T Business VoIP services, paired with fast, reliable AT&T Business Fiber, can help provide a strong foundation for a quality VoIP experience. To connect with an expert who knows business, contact your AT&T Business representative.

Why AT&T Business

See how ultra-fast, reliable fiber, protected by built-in security, and 5G connectivity give you a new level of confidence in the possibilities of your network. Let our experts work with you to solve your challenges and accelerate outcomes. Your business deserves the AT&T Business difference—a new standard for networking.


1 “What Speed Internet Do You Need for VoIP?”, VoIP Insight, October 23, 2025, https://voipinsight.com/what-speed-internet-do-you-need-for-voip/.

2MDN Web Docs, “Codecs Used by WebRTC,” last modified 2025, https://developer.mozilla.org/en-US/docs/Web/Media/Guides/Formats/WebRTC_codecs

3Microsoft, “Prepare Your Organization’s Network for Microsoft Teams,” Microsoft Learn, updated 2025, https://learn.microsoft.com/en-us/microsoftteams/prepare-network.