Bandwidth Calculator
Estimate how long it will take to download or upload a file based on your internet connection speed. Enter the file size and your bandwidth to see the estimated transfer time.
Internet speed is measured in bits per second; file size is measured in bytes. That single mismatch — 8 bits to a byte — is why your 100 Mbps connection doesn't download a 100 MB file in one second. It downloads it in about ten. Once you internalize the unit conversion, bandwidth math becomes predictable: connection speed in megabits ÷ 8 = throughput in megabytes per second, multiplied by however many seconds you're willing to wait.
This calculator handles the conversion between file size units (KB, MB, GB, TB), bandwidth units (Kbps, Mbps, Gbps), and time. Use it to estimate download or upload duration, plan video conference quality, size a backup window, or figure out whether your home connection can keep up with a 4K stream while someone else downloads a game.
Real-world transfer speeds are almost always slower than the theoretical maximum because of TCP/IP overhead, Wi-Fi loss, server-side rate limiting, ISP throttling, and shared upstream congestion. A reasonable rule of thumb is to multiply the calculator's answer by 1.1–1.5x for real-world transfer times. For uploads, double-check your plan — many residential connections are heavily asymmetric (100 Mbps down, 10 Mbps up).
Inputs
Results
Download Time
1 min 20 sec
File Size
1,000 MB
Speed
100 Mbps
Seconds
80.00
Transfer Details
| Detail | Value |
|---|---|
| File Size | 1000 MB |
| File Size (MB) | 1,000 MB |
| File Size (bits) | 8000.0 Mbit |
| Connection Speed | 100 Mbps |
| Speed (Mbps) | 100 Mbps |
| Speed (MB/s) | 12.50 MB/s |
| Download Time | 1 min 20 sec |
| Time (seconds) | 80.00 |
Formula
How to use this calculator
- Enter the file size in your preferred unit (KB, MB, GB, TB).
- Enter your connection speed — usually advertised in Mbps for residential, Gbps for fiber or enterprise.
- The calculator converts both to a common unit (bits or bytes) and divides to find time.
- Add a 10–50% buffer for real-world overhead, especially over Wi-Fi or congested links.
- For uploads, use your upload speed (often much lower than download on residential plans).
- For ongoing streams (video calls, 4K streaming), use the per-second rate, not total file size.
Worked examples
Cloud backup of a photo library
**Scenario:** You want to back up a 250 GB photo library to a cloud service. Your upload speed is 25 Mbps. **Calculation:** 250 GB = 2,000,000 megabits (250 × 8 × 1000). At 25 Mbps: 2,000,000 ÷ 25 = 80,000 seconds = 22.2 hours theoretical. Real-world ~26–30 hours with TCP overhead and rate limiting. **Result:** The initial backup will take about a day and a half running continuously. Start it on a Friday night so it finishes by Sunday. Incremental backups after that are tiny — only new/changed files transfer.
Game download on fiber
**Scenario:** You're downloading a 120 GB AAA game on a 1 Gbps fiber plan. **Calculation:** 120 GB = 960,000 megabits. At 1 Gbps (1,000 Mbps): 960,000 ÷ 1,000 = 960 seconds = 16 minutes theoretical. CDN/server-side throttling usually caps real speed at 400–700 Mbps for a single connection. **Result:** Theoretically 16 minutes; realistically 25–40 minutes depending on whether the publisher's CDN can saturate your line. Steam, Epic, and PSN often parallelize downloads to get closer to line speed.
Sizing a video conference call
**Scenario:** How much bandwidth does a 4-person Zoom call at 1080p use? Zoom recommends 3 Mbps up and 3 Mbps down per participant for HD group calls. **Calculation:** Per participant: 3 Mbps both directions. A 1-hour call: 3 Mb × 3600s = 10,800 Mb = 1,350 MB = 1.35 GB of data per direction, per participant. Across 4 people for the whole call: ~5.4 GB total bandwidth consumed by the host. **Result:** A 1-hour 4-person HD call uses ~1.35 GB per participant per direction. On a metered connection (mobile hotspot, satellite), this adds up fast. Lowering to 720p or audio-only cuts usage 60–90%.
When to use this calculator
**Use bandwidth math when you need to:**
- **Size a backup window**: full backups of laptops and servers must fit between business hours. Calculate before you schedule. - **Plan media delivery**: do you have enough upstream to stream 4K live? To deliver a release-day patch to all customers? - **Choose an internet plan**: 4-person household streaming 4K and gaming needs ~50 Mbps minimum, ideally 100+; remote work with video calls needs symmetric upload too. - **Diagnose slow transfers**: if downloads take 3× the theoretical time, the bottleneck might be Wi-Fi, the server, or rate limiting — not your plan. - **Estimate cloud egress costs**: AWS, GCP, Azure all charge for outbound bandwidth. A 1 TB monthly egress can cost $80–100 at standard rates. - **Compare plans across measurement units**: a "1 Gigabit" home plan and a "100 megabytes per second" cellular plan are roughly the same (1000 Mbps ÷ 8 = 125 MB/s).
**Signs your bandwidth is the bottleneck:** - Speed test shows you're getting <70% of plan during off-peak hours - Video calls degrade when someone else streams - Uploads take 10× longer than downloads (asymmetric plan; expected on most residential cable/DSL) - Multiple devices saturating simultaneously
**Signs the bottleneck is something else:** - Single transfer slow but speed test fast → server-side or rate limit - Wired fast but Wi-Fi slow → Wi-Fi distance, interference, or router age - All apps slow but speed test fine → DNS, ISP routing, or local network issue
Common mistakes to avoid
- Mixing megabits (Mb) and megabytes (MB). 100 Mbps is 12.5 MB/s, not 100 MB/s. The lowercase 'b' vs uppercase 'B' matters.
- Assuming download speed equals upload speed. Most residential plans are asymmetric — 200 Mbps down / 20 Mbps up is typical.
- Forgetting overhead. Transfer time is ~10–30% longer than the math says due to TCP, Wi-Fi, and server slowdowns.
- Conflating Wi-Fi link speed with internet speed. Your Wi-Fi might say "866 Mbps" but if your internet plan is 100 Mbps, that's your real cap.
- Calculating per-device when bandwidth is shared. A 100 Mbps home connection split across 4 streaming devices gives each ~25 Mbps, not 100.
- Ignoring latency. Bandwidth measures how much data per second; latency measures how fast each packet arrives. Gaming and video calls need low latency more than high bandwidth.
- Trusting advertised "up to" speeds. ISPs guarantee far less than the advertised max in their fine print — read the SLA, not the marketing.