Glossary · Performance
Bandwidth: definition, explanation, and why it matters
The maximum amount of data that can be transmitted over a network link in a given period, typically measured in megabits per second (Mbps) or gigabits per second (Gbps).
Definition
The maximum amount of data that can be transmitted over a network link in a given period, typically measured in megabits per second (Mbps) or gigabits per second (Gbps).
Plain-English explanation
Bandwidth is the width of the pipe, not the speed of any individual packet. A 1 Gbps link can move 1,000 megabits per second of data in parallel — but each packet still takes the same time to traverse the link as it would on a 100 Mbps connection.
Real-world usable bandwidth (throughput) is always lower than the headline number because of protocol overhead, contention, and Wi-Fi loss.
Real-world examples
- A 4K Netflix stream needs about 25 Mbps; three concurrent streams need ~75 Mbps.
- Backing up 500 GB to the cloud is a bandwidth-bound task — a faster pipe finishes it sooner.
Why it matters
Bandwidth determines how many concurrent users and bandwidth-heavy tasks a connection can support without degrading.
It does NOT directly determine how responsive interactive applications feel — that is latency.
Common misconceptions
- Myth: More bandwidth makes everything faster.
Reality: Past the point where your applications saturate the link, extra bandwidth does nothing for them. Most browsing rarely uses more than 50 Mbps.
Frequently asked questions
- How much bandwidth do I actually need?
- For a typical 2–4 person household with streaming, video calls, and gaming, 200–500 Mbps is plenty. Gigabit is useful for large concurrent downloads or many heavy users.