Use this bandwidth calculator to estimate file transfer time, download or upload duration, required network speed, and data moved over time. Enter a file size in MB, GB, TB, or PB and a speed in Mbps, Gbps, MB/s, or GB/s to calculate realistic transfer estimates with optional overhead and link efficiency.
Hours, minutes, seconds.
Core formulas: adjusted bits = bytes x 8 x (1 + overhead),
usable bps = line bps x efficiency, time = adjusted bits / usable bps,
and payload moved = usable bps x time / 8 / (1 + overhead).
These examples use the calculator's realistic default assumptions: 5% transfer overhead and 85% usable link efficiency. Actual results can vary with Wi-Fi quality, server limits, disk speed, congestion, and packet loss.
| Data size | 100 Mbps | 1 Gbps | 10 Gbps |
|---|---|---|---|
| 1 GB | 1m 39s | 10s | 1s |
| 10 GB | 16m 28s | 1m 39s | 10s |
| 100 GB | 2h 44m 42s | 16m 28s | 1m 39s |
| 1 TB | 1d 3h 27m | 2h 44m 42s | 16m 28s |
| 10 TB | 11d 10h 30m | 1d 3h 27m | 2h 44m 42s |
Internet plans and network interfaces are usually advertised in bits per second, such as Mbps or Gbps. File managers, browsers, and backup tools often show bytes per second, such as MB/s or GB/s. Since 1 byte equals 8 bits, divide Mbps by 8 to estimate MB/s before overhead.
| Network speed | Perfect maximum | Typical usable range |
|---|---|---|
| 100 Mbps | 12.5 MB/s | 8-11 MB/s |
| 300 Mbps | 37.5 MB/s | 24-34 MB/s |
| 1 Gbps | 125 MB/s | 90-115 MB/s |
| 10 Gbps | 1.25 GB/s | 900 MB/s-1.15 GB/s |
A 1 Gbps connection does not usually move files at a full 125 MB/s. The final transfer rate depends on protocol overhead, TCP behavior, packet loss, encryption, Wi-Fi airtime, server-side limits, disk read/write speed, and other traffic using the same link.
Required-bandwidth mode is useful for backup windows, cloud migrations, replication jobs, media uploads, and large dataset transfers.
| Goal | Approximate required nominal bandwidth | Use case |
|---|---|---|
| Move 100 GB in 1 hour | 275 Mbps | Large file delivery or media upload |
| Move 1 TB in 8 hours | 343 Mbps | Overnight backup window |
| Move 2 TB in 8 hours | 686 Mbps | Server backup or migration batch |
| Move 10 TB in 24 hours | 1.14 Gbps | Cloud migration or replication catch-up |
Bandwidth is the nominal capacity of a link, usually advertised in bits per second. Throughput is the useful rate an application actually gets after protocol overhead, congestion, retransmits, encryption, storage speed, and software limits. This calculator separates those ideas so planning numbers do not assume a perfect wire.
Use transfer-time mode when you already know the available connection speed. Use required-bandwidth mode when a backup, file move, replication job, or migration must finish inside a fixed window. Use data-moved mode when you know the speed and time window and want to estimate how much payload the link can carry. The efficiency input models how much of the nominal line rate is usable for payload data, while overhead models extra traffic that must also cross the link.
Network rates are normally decimal: 1 Mbps is 1,000,000 bits per second and 1 Gbps is 1,000 Mbps. Storage sizes may be decimal or binary depending on the tool reporting them. The unit convention selector makes that assumption explicit, which matters for large TB and PB transfers.
Data bytes: amount x unit multiplier
Adjusted bits: data bytes x 8 x (1 + overhead/100)
Usable bandwidth: nominal bandwidth x efficiency/100
Transfer time: adjusted bits / usable bandwidth
Required nominal bandwidth: adjusted bits / target seconds / (efficiency/100)
Data moved: usable bandwidth x target seconds / 8 / (1 + overhead/100)
The calculator assumes steady-state throughput. It does not model TCP slow start, Wi-Fi airtime contention, ISP congestion, storage I/O limits, or per-flow shaping.
This calculator converts the entered data size to bytes, converts network speed to bits per second, applies optional overhead and usable-link efficiency, then solves the bandwidth-time-data relationship. It is intended for planning estimates, not guaranteed speed-test results.
Last reviewed: June 2026. Calculations run locally in your browser.
| Scenario | Useful inputs | Planning note |
|---|---|---|
| 100 GB file copy over 1 Gbps | 100 GB, 1 Gbps, 5% overhead, 85% efficiency | Expect roughly 16-17 minutes, not the perfect-wire 13.3 minutes. |
| 2 TB backup in 8 hours | 2 TB, required-bandwidth mode, 8 hours | Use a realistic efficiency percentage for backup software and storage limits. |
| Cloud migration over 10 Gbps | Dataset size, 10 Gbps, measured efficiency | Large migrations are often limited by storage, API, or per-flow behavior before line rate. |
| Replication across a WAN | Binary size units, higher overhead, lower efficiency | Latency, encryption, and packet loss can reduce usable throughput materially. |
Mbps is megabits per second. MB/s is megabytes per second. Divide Mbps by 8 to get MB/s before overhead and efficiency.
Real transfers pay for headers, encryption, retransmits, disk I/O, congestion, application limits, and sometimes Wi-Fi contention.
Use decimal GB when your source reports SI storage units. Use binary mode when your source is closer to GiB/TiB values.
For per-user capacity planning, use the related Network Throughput Planner because it includes user count, peak factor, and traffic split.
Yes. Inputs are processed locally and are not submitted to a server.
Bandwidth estimates are planning aids. Validate production designs with measured throughput, vendor documentation, carrier service terms, and application behavior.
