Free bandwidth / download time calculator
Enter a file size and a connection speed and this bandwidth calculator shows the transfer time — bits-versus-bytes and the 1024-versus-1000 prefix split handled for you, so the estimate is never eight times off, updated live, as you type.
On this page15 sections
Theoretical maximum. Real-world speeds vary due to latency, overhead, and network congestion.
Results are estimates. Consult a professional.
What this bandwidth calculator works out
This bandwidth calculator turns a file size and a connection speed into a transfer time — how long that file takes to move across a link running at a given data rate. Enter a size (in B, KB, MB, GB or TB) and a speed (in Kbps, Mbps or Gbps), and the result updates as you type. Underneath it is one division: the file size, converted to bits, divided by the data rate in bits per second.
Bandwidth is the most data a link can move in a second — its rated capacity, fixed by the connection, regardless of how busy it is at any moment. The data rate is what that capacity delivers in practice, measured in bits per second. Because a network quotes its capacity in bits while your files are measured in bytes, the calculator handles the eight-to-one conversion for you, so the time it shows is right instead of eight times too optimistic.
How the bandwidth and transfer-time formula works
The arithmetic is simple; the units are where care is needed. To divide a file by a data rate you first put both on the same footing — bits — then divide. The calculator multiplies the file size by 8 to get bits, expands the speed prefix to bits per second, and divides.
Bits vs bytes: why Mbps is not MB/s
This is the mistake nearly every quick estimate makes. Your link is quoted as 100 Mbps and your file is 1 GB, so you divide and expect a few seconds. The catch is a single lowercase letter: ISPs and network gear quote speed in megabits (Mbps, lowercase "b"), while your operating system measures files in megabytes (MB, uppercase "B"). One byte is eight bits, so the bit figure is eight times larger than it looks.
| Data rate | ÷ 8 = bytes per second | What it feels like |
|---|---|---|
| 1 Mbps | 0.125 MB/s | slow — a small image per second |
| 25 Mbps | 3.125 MB/s | comfortable HD streaming |
| 100 Mbps | 12.5 MB/s | common home fibre/cable plan |
| 300 Mbps | 37.5 MB/s | fast multi-device household |
| 1 Gbps | 125 MB/s | gigabit — disk speed becomes the limit |
Megabits per second ÷ 8 = megabytes per second (decimal). To go from an advertised Mbps figure to the MB/s you actually feel, divide by eight.
Data-rate units: Kbps, Mbps, and Gbps
Network data rates climb in factors of 1000, the decimal SI steps. The calculator accepts the three you meet in practice — kilobits, megabits and gigabits per second — and expands each to bits per second before dividing. Knowing the ladder helps you sanity-check a result and convert a quoted speed in your head.
| Unit | Bits per second | Typical context |
|---|---|---|
| bps | 1 | the base unit — one bit per second |
| Kbps (kilobit/s) | 1,000 | legacy modems, low-bitrate audio |
| Mbps (megabit/s) | 1,000,000 | most home and office broadband |
| Gbps (gigabit/s) | 1,000,000,000 | fibre, data-centre and LAN backbones |
Decimal SI prefixes: each step is ×1000. A 1 Gbps link carries 1000 Mbps; a 50 Mbps plan carries 50,000 Kbps.
Note the asymmetry the calculator quietly manages: data rates step by 1000 (decimal), but the file sizes you pair them with step by 1024 (binary). That is why the answer is not a perfectly round number — and it is the difference that sets this tool apart from a plain decimal-only estimate.
A worked example using the bandwidth calculator
Priya needs to push a 1 GB backup over a link quoted at 100 Mbps — the calculator's default case. A bare "1 ÷ 100" guess says a fraction of a second, which is plainly wrong. Here is the real figure, step by step.
Step 1 — Convert the file size to bits (binary)
1 GB is 1024³ = 1,073,741,824 bytes. Multiply by 8 to get bits: 8,589,934,592 bits. Using binary GB (1024³) rather than decimal GB (10⁹) is what makes this tool's answer differ from a purely decimal one.
Step 2 — Put the data rate in bits per second (decimal)
100 Mbps is already in bits and uses decimal mega: 100,000,000 bits per second (12.5 MB/s). No multiply-by-8 here — the speed was never in bytes.
Step 3 — Divide
8,589,934,592 ÷ 100,000,000 = 85.90 seconds, which the calculator shows as 1 min 26 s. That is the figure for the widget's default inputs.
Transfer-time chart by file size and data rate
For a ballpark without typing, this chart gives theoretical best-case transfer times for common file sizes across typical data rates in Mbps, computed exactly as the calculator does (binary file sizes, decimal speeds). Real transfers run a little slower — see the next section for why.
| File size | 10 Mbps | 50 Mbps | 100 Mbps | 300 Mbps | 1 Gbps |
|---|---|---|---|---|---|
| 10 MB | 8.39 s | 1.68 s | 0.84 s | 0.28 s | 0.08 s |
| 100 MB | 1 min 24 s | 16.78 s | 8.39 s | 2.80 s | 0.84 s |
| 1 GB | 14 min 19 s | 2 min 52 s | 1 min 26 s | 28.63 s | 8.59 s |
| 5 GB | 1 h 12 min | 14 min 19 s | 7 min 9 s | 2 min 23 s | 42.95 s |
| 25 GB | 5 h 58 min | 1 h 12 min | 35 min 47 s | 11 min 56 s | 3 min 35 s |
Theoretical best case: file size (binary, ×8 bits) ÷ data rate (decimal bps). 1 Gbps = 1000 Mbps. Real transfers land 10–30% above these floors.
Where bandwidth math matters
The same size-over-rate relationship answers a surprising range of everyday infrastructure questions. The calculator gives you the per-transfer time; the cases below show how that figure feeds bigger decisions.
- Sizing a hosting plan. A site's monthly data transfer is roughly its average page size × monthly pageviews, often with a redundancy factor of 1.3–2× for retries, bots and assets loaded more than once. A 2 MB page served 100,000 times is about 200 GB before that buffer — a per-file estimate here helps you reason about whether a given uplink can serve it.
- Streaming and conferencing. A 25 Mbps stream needs a sustained 25 Mbps of headroom; pair that data rate with a clip's size here to see how long a download-and-watch would take versus live streaming.
- Network capacity planning. Backups, syncs and migrations are just large files over a link. Use the transfer time to schedule them inside a maintenance window instead of discovering at 3 a.m. that a 25 GB image will not finish.
- Comparing plans. Convert each advertised Mbps to MB/s (÷8) and run a representative file to feel the real difference between, say, 100 Mbps and 300 Mbps for the transfers you actually do.
Common bandwidth and data-rate mistakes
- Confusing bits and bytes. The single most common error: dividing a byte-sized file by a bit-rate without the ×8. It makes every estimate eight times too fast. Mbps is bits; MB is bytes.
- Reading "Mb" as "MB". Lowercase b is bits, uppercase B is bytes. "100 Mb" and "100 MB" differ by a factor of eight — a typo here quietly ruins a capacity plan.
- Mixing 1000 and 1024. Treating a binary GB (1024³) as a decimal GB (10⁹), or vice versa, shifts the answer by ~7%. This tool uses binary for sizes and decimal for speeds on purpose.
- Treating bandwidth as guaranteed throughput. Advertised bandwidth is a ceiling; real throughput is usually 70–90% of it after overhead and congestion.
- Ignoring the slowest link. A transfer is capped by the narrowest point on the route — often the far-end server, not your own connection.
Why real transfers run slower than the estimate
Think of the calculated time as a speed limit you will never quite reach. Advertised bandwidth measures raw signalling capacity, but only some of that capacity carries your actual file — the rest goes to keeping the connection orderly and reliable. In practice you tend to capture four-fifths or so of the rated figure, and the shortfall comes from a handful of named causes.
- Framing and headers. TCP/IP and Ethernet wrap your data in headers and acknowledgements; networking guides put this protocol overhead at roughly 5 to 15 percent of the link, so the payload never gets the whole pipe.
- The narrowest hop sets the pace. A transfer can move no faster than the slowest device between the two ends — frequently the far server's own uplink or a congested router, not your local line.
- Contention. Every other download, stream and background sync sharing the link draws from the same capacity, so a busy network divides the data rate among them.
- When latency outweighs bandwidth. Many small files spend most of their time waiting on round trips rather than transferring bits; here a faster plan barely helps, while one big file is the opposite case.
- Endpoint ceilings. Wi-Fi interference, and on gigabit links the write speed of the receiving disk, can cap a transfer below the network's rated data rate.
The practical move is to read the result as a lower bound and pad it. A ten-minute estimate is safer scheduled with a quarter or so on top; the calculator fixes the floor, while overhead and contention decide how far above it the real transfer settles.
On real-world throughput sitting below advertised bandwidth, and protocol overhead consuming part of every link: BroadbandNow's guide to megabits versus megabytes and transfer overhead.Bandwidth and data-rate definitions
How accurate is this bandwidth calculator?
The unit math is exact. File size (in binary bytes) times eight, divided by the data rate in decimal bits per second, is the precise theoretical transfer time — the calculator pins its default case, 1 GB at 100 Mbps, at 85.90 seconds (1 min 26 s). If your inputs are right, the floor figure is right to the hundredth of a second.
What it cannot know is your real-world overhead: protocol headers, the speed of the far-end server, Wi-Fi quality and competing traffic push actual time above the theoretical floor, usually by 10 to 30 percent. Treat the result as the best case and plan with headroom. If you would rather work in megabytes-per-second with the bits-vs-bytes conversion handled in decimal throughout, use our download time calculator — the same 1 GB at 100 Mbps reads 80 s there because it counts file sizes in decimal gigabytes. To plan the IP addressing for the network carrying that traffic, see the IP subnet calculator.
Binary vs decimal prefixes (KB vs KiB) and the bit/byte basis follow NIST's prefixes-for-binary-multiples reference and IEC 80000-13.Frequently asked questions about the free bandwidth / download time calculator
About this Bandwidth calculator
This bandwidth calculator runs entirely in your browser — nothing you type is sent anywhere. Enter a file size and a connection speed, switch the units to match, and the transfer time updates instantly. File sizes are read in binary (1 KB = 1024 B) and speeds in decimal (1 Mbps = 1,000,000 bps), exactly as networks and storage are really measured.
It is one of our free developer tools; for the all-decimal version see the download time calculator, or browse the full set on the calculators index.