IT Infrastructure & Cloud
Calculating Office Internet Bandwidth Requirements by Headcount and Application
Office bandwidth requirements cannot be guessed from headcount alone. This guide calculates them from the applications in use, the number of people active at the same time, and upload and download separately, then lists the questions to ask your internet provider.
SEO and Content Specialist
7 min read
Short answer: office bandwidth requirements are calculated from the heaviest applications used at the same time, not from headcount alone. Take the per-user requirement from the application vendor’s official page, multiply it by the number of users active at the same time during peak hours, calculate upload and download separately, add other traffic measured on your own network, then leave headroom and prepare a backup internet link.
The question “how many Mbps do we need” usually comes up when an office moves building, when video meetings keep breaking up, or when an internet contract is about to be renewed. The most common answer, “so many Mbps per employee”, is rarely right: an office of 50 people who seldom hold video meetings is very different from an office of 50 where half of them meet clients all day. This guide sets out a defensible way to calculate office bandwidth requirements, and a list of things to ask your internet provider before signing a contract.
Start from applications, not headcount
Bandwidth requirements are determined by the activities that use the internet at the same time. Headcount is only the upper limit; what matters is how many people are doing heavy activities at the same moment. So the first step is to list the activities that use the internet, then group employees by their working pattern:
- Video meetings and voice calls (Zoom, Google Meet, Microsoft Teams). Usually the heaviest activity, and the only one whose figures vendors publish clearly.
- Web and cloud applications: email, web-based ERP or accounting systems, online office applications.
- File synchronization and uploads: cloud storage, design files, video, or large documents.
- Scheduled traffic: operating system updates, offsite data backups.
- Access from outside the office: employees connecting to the office over VPN use the office’s upload capacity.
Group employees into a few profiles, for example administrative staff who mainly use web applications, a sales team that is often in video meetings, and a team that sends large files. These profiles are what you calculate, not an average per head.
Requirements published by meeting application vendors
For video meetings, use the figures on the vendor’s official page, not estimates. The table below summarizes the figures published by the three major vendors, per user or per device:
| Application and activity | Upload | Download | Vendor note |
|---|---|---|---|
| Zoom, group video meeting 720p | 2.6 Mbps | 1.8 Mbps | Recommended figure |
| Zoom, group video meeting 1080p | 3.8 Mbps | 3.0 Mbps | Recommended figure |
| Zoom, VoIP audio | 60-80 kbps | 60-80 kbps | Direction not specified |
| Google Meet, video (average for large organizations) | 1 Mbps | 1.3 Mbps | Average per participant |
| Google Meet, audio only (average for large organizations) | 12 kbps | 18 kbps | Average per participant |
| Microsoft Teams, video meetings | 2,500 kbps | 4,000 kbps | “Recommended” figure per device |
| Microsoft Teams, meeting audio | 58 kbps | 58 kbps | “Recommended” figure per device |
Two important things stand out in this table. First, the figures differ widely between vendors and quality levels, so the calculation must use the application your office actually uses. Second, video meetings use almost as much upload as download, and in Zoom’s case the upload figure is even higher. Microsoft also notes that one person joining from a laptop and a phone at the same time counts as two devices.
Count concurrent users, then upload and download separately
Google gives the simplest calculation method for Meet: multiply the average bandwidth per participant by the peak number of concurrent participants, and the result is the minimum requirement. Google also estimates the share of users in meetings at the same time: 10-20% if video meetings are a high priority, 1-4% for normal use, and 0.01-0.5% for low priority.
An example calculation for an office of 100 employees where video meetings are a high priority:
| Step | Google Meet (average) | Microsoft Teams (Recommended) |
|---|---|---|
| Concurrent participants (20% of 100) | 20 people | 20 devices |
| Upload per participant | 1 Mbps | 2.5 Mbps |
| Download per participant | 1.3 Mbps | 4 Mbps |
| Meeting upload requirement | 20 Mbps | 50 Mbps |
| Meeting download requirement | 26 Mbps | 80 Mbps |
This example is an illustration from vendor figures, not a plan recommendation for any particular office. The 20% share is Google’s estimate; the real figure in your office may be lower or higher, for example if meeting rooms are used in turn all day. Note also that an office using Teams at the recommended quality needs far more capacity than the Meet calculation for the same number of people.
Add other traffic from your own measurements
Applications other than video meetings rarely have official figures you can calculate with, and their usage depends heavily on working patterns. For this part, measure rather than guess:
- Measure real usage on the office router or firewall over several normal working weeks, especially during peak hours. Record peak upload and download, not the daily average.
- Separate scheduled activities. Offsite data backups and system updates should run outside working hours so they do not compete with meetings. Backups to the cloud use upload capacity, which is usually the most limited; the backup pattern is discussed in the article The 3-2-1 Backup Strategy for Company Servers.
- Watch VPN access. Employees outside the office who connect over VPN use the office’s upload for every file they open. Microsoft recommends that Teams traffic does not go through the VPN (split tunnel), partly because VPNs are typically not designed for real-time media.
Leave headroom, then prioritize what matters
The result of the multiplication above is the minimum requirement. Google says the network needs extra capacity for other needs beyond meetings, but vendors do not set a standard percentage for this headroom. How much to leave is a company decision, taking into account plans to hire more employees, new applications to be adopted, and how costly meeting disruptions are for the business.
Large capacity also does not guarantee smooth meetings if all traffic is treated the same. Two steps Microsoft recommends for Teams apply generally to video meetings: configure QoS so voice and video packets are prioritized, and design Wi-Fi for real-time media. When capacity is short, meeting applications lower their own quality: Teams prioritizes audio quality over video, and Meet lowers the video definition.
Questions for your internet provider before signing
Plan names differ between providers, so what matters is the content of the contract. Ask the following in writing:
| Question | Why it matters |
|---|---|
| Is the capacity guaranteed, or “up to” and shared with other customers? | This is where dedicated and broadband plans differ; shared capacity can drop at peak hours |
| What is the upload speed, and is it the same as download? | Video meetings, VPN, and cloud backups depend on upload |
| What does the SLA cover: availability, response time to outages, and compensation? | Without written figures, there is nothing to claim when the connection goes down |
| How many public IP addresses are provided? | Needed for inbound VPN or services accessed from outside |
| What physical route does the connection take into the building? | Determines whether a backup link is truly separate |
A backup internet link
A single internet link means a single point of failure. A backup link should come from a different provider and, where possible, enter the building through a different physical route, so that one cut cable does not take down both. The backup link does not need the same capacity as the main link; size it for activities that must not stop, such as client meetings and core applications, then configure the router or firewall to switch over automatically when the main link fails.
How Legia does it
Capacity from the internet provider is only half the story; the other half is how that connection is distributed inside the building. In the Office Network Installation service, Legia starts with a site survey (2-5 working days), then installs LAN and fiber cabling, wireless access points, a firewall, and VPN, and separates the guest, office, and operational networks so that one faulty device does not drag down the others. Every point is tested and the results are recorded before handover, and the whole process for a medium-sized office usually takes 3-6 weeks. The internet subscription is billed separately from this work. The order of the work is covered in the New Office Network Installation Checklist, and the other services in this pillar are under IT Infrastructure & Cloud.
Frequently asked questions
How many Mbps per employee does an office need?
There is no per-employee figure that applies generally. Calculate from the heaviest application used at the same time, for example video meetings, using the vendor’s official figures and the number of concurrent users at peak hours, then add other measured usage.
Why does the office internet feel slow even though the plan is large?
Common causes are small upload capacity, shared capacity that drops at peak hours, scheduled activities running during working hours, or bottlenecks in the internal network such as Wi-Fi. Measurement on the router or firewall helps tell the causes apart.
Does the backup internet link need to be as large as the main link?
Not necessarily. The backup link only needs to cover activities that must not stop. More importantly, it should come from a different provider and not use the same physical route as the main link.
Should we recalculate after the internet is installed?
Yes, especially when headcount grows, new applications are adopted, or working patterns change. Compare measured peak usage with the contracted capacity regularly.


