Use this bandwidth calculator to find transfer time, needed speed, or data moved while keeping bits, bytes, and unit differences straight.
Advanced options
Real-world estimate
Explanation note
How to use our Bandwidth Calculator
- Choose an option in What do you want to find?: Transfer time, Needed speed, or Data moved.
- Fill in the visible core fields: Data size with Data size unit, Speed with Speed unit, and Time with Time unit as needed for your choice.
- If you want a more realistic estimate, open Advanced options and enter Transfer efficiency (percent). Leave it at 100 for ideal math.
- Click Calculate, then read Answer first. Use Adjusted for efficiency, Ideal result at 100% efficiency, and Unit note to compare ideal and real-world expectations.
- Sanity-check the result: if your ISP plan is in Mbps but an app shows MB/s, compare Speed in Mbps and Speed in MB/s to make sure you did not mix bits and bytes.

Definitions
Data size: The total amount of data you want to move, such as a file, backup, or download.
Data size unit: The unit for that amount, such as MB, GB, or GiB. Lowercase b means bits. Uppercase B means bytes.
Speed: How fast data moves each second.
Speed unit: The rate unit, such as Mbps or MB/s. Mbps is bits per second. MB/s is bytes per second.
Time: How long the transfer lasts.
Transfer efficiency (percent): The share of the listed speed that actually goes toward your transfer after overhead and slowdowns. 100% means ideal math.
Answer: The main result for the solve-for choice you picked.
Unit note: A short explanation that helps you spot bit-versus-byte and decimal-versus-binary differences.
Common mistakes and quick fixes
Mistake: Entering a file size in Data size but choosing Mbps in Data size unit .
Fix: For files and storage, use a byte unit in Data size unit , such as MB , GB , or GiB .
Mistake: Typing an ISP speed into Speed and choosing MB/s in Speed unit when the plan is really in Mbps.
Fix: Match Speed unit to the plan or app exactly. Most internet plans use Mbps or Gbps .
Mistake: Solving for Needed speed but entering 10 in Time and forgetting to change Time unit from minutes to hours or seconds.
Fix: Check Time unit every time. A wrong time unit can change the answer by 60 times or more.
Mistake: Setting Transfer efficiency (percent) to 0, above 100, or leaving it blank when you meant to use it.
Fix: Enter a value from 1 to 100 in Transfer efficiency (percent) . Use 100 for ideal conditions.
Mistake: Expecting Answer and Adjusted for efficiency to be different when Transfer efficiency (percent) is 100.
Fix: That is normal. Lower Transfer efficiency (percent) only if you want a slower, more realistic transfer estimate.
Mistake: Thinking GB and GiB are the same because both look like gigabytes.
Fix: Read Unit note and choose the exact unit in Data size unit . GB uses decimal steps, while GiB uses binary steps.
Limitations & Key Assumptions / Boundary Conditions
- Results use the selected units exactly. Mixing decimal units like GB with binary units like GiB can change the number even when the labels look similar.
- The efficiency setting is a simple estimate. Real transfers can vary because of protocol overhead, network congestion, device limits, and server speed.
- This calculator treats speed as steady over the full transfer. Many real downloads and uploads speed up or slow down over time.
- Inputs must be positive for the active solve-for mode. Zero or negative data size, speed, or time does not produce a physical transfer result.
- Transfer efficiency must be from 1 to 100 percent. Values outside that range are blocked because they would make the estimate unrealistic or impossible.
- Displayed helper conversions like Speed in MB/s and Speed in Mbps are for comparison and interpretation. They do not change the main math.
Methodology
How the calculator works
The calculator first converts everything to standard base units: data to bits, speed to bits per second, and time to seconds. Then it applies the same core relationship in the direction you need.
data_bits = speed_bits_per_second * time_seconds
time_seconds = data_bits / speed_bits_per_second
speed_bits_per_second = data_bits / time_seconds
effective_speed_bits_per_second = nominal_speed_bits_per_second * (efficiency_percent / 100)
bytes = bits / 8
Unit conversions used
Bits and bytes are different sizes. The calculator uses 8 bits per byte. Decimal prefixes use powers of 1000, while binary prefixes use powers of 1024. Time converts as 60 seconds per minute, 3600 seconds per hour, and 86400 seconds per day.
How each solve-for mode is computed
Transfer time: convert the entered Data size to bits, convert the entered Speed to bits per second, then divide data by speed. If efficiency is below 100%, the adjusted time uses the slower effective speed, so the result is longer.
Needed speed: convert the entered Data size to bits, convert the entered Time to seconds, then divide data by time. The ideal result is the pure required throughput. The adjusted result shows the higher line speed you would need if actual efficiency is below 100%.
Data moved: convert the entered Speed to bits per second, convert the entered Time to seconds, then multiply speed by time. If efficiency is below 100%, the adjusted result uses the effective speed, so the transferred data is smaller.
Mini example
If Data size is 10 GB and Speed is 100 Mbps, the calculator treats 10 GB as 10,000,000,000 bytes, or 80,000,000,000 bits. At 100,000,000 bits per second, the ideal transfer time is 800 seconds, which is about 13 minutes and 20 seconds.
10 GB = 10 * 1000^3 bytes
80,000,000,000 bits = 10,000,000,000 * 8
800 seconds = 80,000,000,000 / 100,000,000
If Transfer efficiency (percent) is 90, effective speed becomes 90 Mbps, so the adjusted time is about 888.89 seconds, or about 14 minutes and 49 seconds.
Output notes
Speed in MB/s is shown because many apps report downloads in bytes per second, while Speed in Mbps is shown because internet plans usually use bits per second. Time breakdown appears when time is part of the result so you can read the same answer in more than one time unit.
Assumptions behind the math
The ideal result assumes a constant transfer rate with no interruptions. The adjusted result uses a simple efficiency factor to estimate real-world performance, but actual speeds can still differ because networks and devices do not stay perfectly steady [1].