Bandwidth Calculator: Download Time & Caps

Q: How do I figure out what speed a 2 TB/month cap equals?

That cap is equivalent to a constant ≈6.17 Mbps 6.17 Mbps≈6.17Mbps over 30 days. The math: GB×8×1092,592,000×106GB × 8 × 10^9 / 2,592{,000 × 10^6}2,592,000×106GB×8×109 Mbps (2.59M seconds in 30 days). Hosting and mobile plans quote caps; this shows the “always on” speed that would use that cap if it ran flat.

Symbol	Meaning	Use
Kb	Kilobits	Speed (rare)
KB	Kilobytes	File size
Mb	Megabits	Speed (Mbps)
MB	Megabytes	File size
Gb	Gigabits	Speed (Gbps)
GB	Gigabytes	File size

Type	Speed
4G LTE	20 to 50 Mbps
4G LTE-A	100 to 300 Mbps
5G (Sub-6)	100 to 500 Mbps
5G (mmWave)	1 to 3 Gbps

Type	Speed
Dial-up	56 Kbps
DSL	10 to 25 Mbps
Cable	50 to 300 Mbps
Fiber 100	100 Mbps
Fiber 300	300 Mbps
Fiber 500	500 Mbps
Fiber 1G	1 Gbps

Type	Speed
T1	1.544 Mbps
T3 / DS3	45 Mbps

Bandwidth Calculator: Download Time, Hosting Needs & Data Caps

Estimate download times, plan website hosting bandwidth, and convert monthly data caps to Mbps. Bits vs bytes, Binary vs Decimal. Free bandwidth and download time calculator.

What This Tool Does

Three modules in one: Download/Upload Time, plug in file size and connection speed; get theoretical and real-world times with adjustable overhead. Website Hosting Planner, page views, average page size, and redundancy factor yield required monthly bandwidth and minimum line speed. Hosting Bandwidth Converter, turn a cap like “2 TB/month” into the equivalent sustained Mbps, or the other way around.

How the Math Works

The calculator applies a few core relationships that underpin all bandwidth and data-transfer estimates. The fundamental conversion, bits to bytes, is the source of most confusion between ISP speeds and real-world file transfers.

Bits-to-Bytes Conversion:

$\text{MB/s} = \frac{\text{Mbps}}{8}$
1 byte = 8 bits. A 100 Mbps connection delivers at most 12.5 MB/s of file data before overhead.
Download Time:

$t = \frac{\text{File Size (bits)}}{\text{Speed (bps)} \times (1 - \text{overhead})}$
Overhead accounts for TCP/IP headers, retransmissions, and link-layer framing, typically 10–20% of the advertised speed.
Hosting Bandwidth:

$\text{BW}_{\text{month}} = \frac{\text{Views} \times \text{Page Size} \times \text{Redundancy} \times 8}{\text{Seconds in month}}$
Converts page views and page size into a required sustained line speed, with a redundancy factor for traffic spikes.
Cap-to-Speed Conversion:

$\text{Mbps} = \frac{\text{Cap (bytes)} \times 8}{\text{Seconds in period} \times 10^6}$
Worked example: 2 TB/month over 30 days (2,592,000 s) = (2 × 10¹² × 8) / (2,592,000 × 10⁶) ≈ 6.17 Mbps sustained.

How to Use This Calculator

Select a mode at the top: Download/Upload Time to estimate how long a file transfer takes, Website Hosting Planner to calculate required bandwidth from traffic estimates, or Hosting Bandwidth Converter to translate between monthly data caps and sustained speed. For download time, enter a file size and your connection speed. For hosting, enter expected daily page views, average page size in KB, and a redundancy factor (1.2× for steady traffic, 1.5–2× for spiky traffic like product launches). For the converter, enter a monthly cap or a sustained speed and get the equivalent in the other direction. Toggle between binary base (1024, matching Windows/OS file sizes) and decimal base (1000, matching ISP and vendor specs) to align results with your source. Adjust the protocol overhead slider, 15% is a solid default for most home connections, to model real-world throughput versus raw theoretical speed.

Bits vs Bytes: The 8x Rule

Speed is quoted in bits per second: Mbps, Kbps, Gbps. File size is in bytes: MB, GB, TB. One byte = 8 bits, so

\text{MB/s} = \frac{\text{Mbps}}{8}

. A 100 Mbps link can move 12.5 MB per second in theory. Confusing bits and bytes, e.g. treating 100 Mbps as 100 MB/s, throws results off by a factor of 8. Lowercase b = bits; uppercase B = bytes.

Binary (1024) vs Decimal (1000)

Operating systems and RAM traditionally use Base-2: 1 KB = 1024 bytes, 1 MB = 1024², and so on. Storage and network vendors often use Base-10: 1 KB = 1000 bytes. A drive sold as “1 TB” (10¹² bytes) shows about 931 GB in Windows because 1024⁴ ≠ 1000⁴. When estimating downloads or comparing caps, pick the base that matches your source.

Why Advertised Speed ≠ Real Throughput

TCP and IP headers, retransmissions, and link-layer framing consume bandwidth that never shows up as “file data.” Plan for roughly 85% of the advertised line, so 100 Mbps behaves more like 10–11 MB/s sustained. The 10–20% overhead slider lets you model this; 15% is a solid default for most home connections.

Converting Monthly Caps to Sustained Speed

A 2 TB/month cap over 30 days (2,592,000 seconds) equals

\frac{2 \times 10^{12} \times 8}{2{,}592{,}000 \times 10^6} \approx 6.17\,\text{Mbps}

running flat. Hosting and mobile plans quote caps; this formula answers “what constant speed would use that cap?” The converter handles both directions: cap → speed and speed → cap.

Bandwidth Calculator FAQ

Why does my 100 Mbps plan only download at about 12 MB/s?

ISPs advertise in megabits per second; your OS shows megabytes. Since 1 byte = 8 bits, 100 Mbps converts to

100 \div 8 = 12.5\,\text{MB/s}

in a vacuum. In practice, TCP/IP headers, retransmissions, and Wi‑Fi interference chew up 10–20% of that. Expect ~10–11 MB/s on a solid connection. The overhead slider models this gap.

Should I use Binary (1024) or Decimal (1000) for file sizes?

Depends who’s measuring. Windows and most OSes use Binary: 1 KB = 1024 bytes, so a “1 TB” drive shows ~931 GB. ISPs and hosting providers use Decimal: 1 KB = 1000 bytes. A 2 TB data cap is 2 trillion bytes. Toggle the base so your results align with the source you’re comparing against.

How do I figure out what speed a 2 TB/month cap equals?

That cap is equivalent to a constant

\approx 6.17\,\text{Mbps}

over 30 days. The math:

\frac{\text{GB} \times 8 \times 10^9}{2{,}592{,}000 \times 10^6}

Mbps (2.59M seconds in 30 days). Hosting and mobile plans quote caps; this shows the “always on” speed that would use that cap if it ran flat.

What redundancy factor do I need for a small blog?

A 1.2× factor adds ~20% headroom for normal daily spikes. For a blog or portfolio, that’s usually enough. Bump to 1.5× or 2× if you run promos, launches, or anything that could double traffic in an hour. Under-provisioning leads to throttling and timeouts when everyone hits the site at once.

Why is there a "Real-World" estimate separate from theoretical time?

Theoretical assumes every bit is file data. Real-world accounts for protocol overhead. TCP and IP headers, retransmits, and congestion windows. A 70 GB game “should” take ~1h33m at 100 Mbps; with 15% overhead it’s closer to 1h48m. The slider lets you tune that overhead to match what you see on your network.

Bandwidth Calculator: Download Time & Hosting Needs

Download / upload time

Website hosting planner

Hosting bandwidth converter

Information hub

The bit/byte rule

The redundancy factor

Standard speeds

Bandwidth, Bits & Bytes: What Actually Limits Your Speed

Six Things That Trip People Up

bits (b) vs bytes (B)

Binary vs Decimal bases

Protocol overhead

Peak vs average traffic

Caps vs sustained speed

The 8-bit conversion