Skip to main content

Tech & wiring

Bandwidth Calculator: Download Time & Hosting Needs

Compute download times, hosting bandwidth needs, and understand bits vs bytes.

By Jeff Beem

Updated

Base

Windows uses binary; networking and storage specs often use decimal.

01

Download / upload time

Quick presets
15%
Theoretical time
00:00

Perfect conditions, no overhead

Real-world estimate
00:00

Includes 15% TCP/IP overhead

Information hub

The bit/byte rule

Mixing b (bits) and B (bytes) is the #1 cause of "incorrect" results.

SymbolMeaningUse
KbKilobitsSpeed (rare)
KBKilobytesFile size
MbMegabitsSpeed (Mbps)
MBMegabytesFile size
GbGigabitsSpeed (Gbps)
GBGigabytesFile size
bvsBb = bits (speeds). B = bytes (file sizes). 1 B = 8 b.

Why 100 Mbps ≠ 12.5 MB/s: TCP/IP headers and latency add 10 to 20% overhead. Plan for ~85% of advertised speed.

The redundancy factor

Traffic isn't flat; it spikes at specific times (product launches, flash sales, viral posts). A 1.2× factor adds 20% headroom for typical variance.

1.2× to 1.5×: Recommended for blogs, portfolios, steady traffic. Handles moderate spikes without over-provisioning.

2×: For event-driven sites (ticketing, launches) where traffic can double or triple during peak hours. Prevents throttling and failed requests.

Rule of thumb: If your traffic peaks at predictable times, use 1.5× to 2×. Unknown or viral risk? 2× or higher.

Standard speeds

Mobile (4G/5G)
TypeSpeed
4G LTE20 to 50 Mbps
4G LTE-A100 to 300 Mbps
5G (Sub-6)100 to 500 Mbps
5G (mmWave)1 to 3 Gbps
Residential (DSL/Fiber)
TypeSpeed
Dial-up56 Kbps
DSL10 to 25 Mbps
Cable50 to 300 Mbps
Fiber 100100 Mbps
Fiber 300300 Mbps
Fiber 500500 Mbps
Fiber 1G1 Gbps
Enterprise (T1/OC3)
TypeSpeed
T11.544 Mbps
T3 / DS345 Mbps

70 GB at 100 Mbps

A 70 GB download on a 100 Mbps line is about 1h33 in raw math and closer to 1h48 once you budget 15% for TCP/IP and Wi‑Fi overhead. The same page converts a 2 TB/month hosting cap into ~6.17 Mbps sustained over 30 days, or sizes a site from daily page views and page weight.

Four things that change the number

Mbps is bits; your file size is bytes

ISPs quote Mbps and Kbps (lowercase b = bits). Windows and game launchers show MB and GB (uppercase B = bytes). One byte is eight bits, so MB/s=Mbps8\text{MB/s} = \frac{\text{Mbps}}{8}: 100 Mbps caps out at 12.5 MB/s before overhead. Treating 100 Mbps as 100 MB/s is off by a factor of eight.

1024 vs 1000 is not pedantry when you match a bill

Windows reports file sizes with 1 KB = 1024 B. Many ISPs and drive labels use 1 KB = 1000 B. A vendor “1 TB” drive often shows ~931 GB in Explorer because 1024⁴ ≠ 1000⁴. Flip binary vs decimal in the tool so your download estimate lines up with the cap or invoice you are checking.

Advertised speed is not sustained file throughput

TCP and IP headers, retransmits, and link framing eat bandwidth that never lands as “file bytes.” On a good home line, plan for roughly 85% of the headline rate (100 Mbps behaving like ~10–11 MB/s). The overhead slider defaults to 15%; nudge it if your installs consistently run slower or faster than the math.

Monthly caps and traffic spikes are different questions

A 2 TB/month cap spread evenly over 30 days (2,592,000 seconds) is about 6.17 Mbps if it ran flat the whole time. Hosting math is separate: page views × page size × a redundancy factor (1.2× for a quiet blog, 1.5–2× for launches) turns into required line speed. Sites rarely draw evenly; the redundancy line is for the hour everyone shows up at once.

Bandwidth calculator: download time, hosting, and data caps

70 GB at 100 Mbps is about 1h33 in theory and ~1h48 with 15% overhead. A 2 TB/month cap is roughly 6.17 Mbps if you used it evenly across 30 days.

What this calculator does

Three modes share one page: Download/Upload Time (file size + line speed → theoretical and adjusted duration), Website Hosting Planner (daily views, average page size, redundancy → monthly bandwidth and minimum Mbps), and Hosting Bandwidth Converter (monthly cap ↔ sustained Mbps). Binary/decimal base and a protocol overhead slider apply where they affect the math.
  • Outputs:
    Download: theoretical and real-world time. Hosting: monthly bandwidth and required line speed. Converter: cap ↔ sustained Mbps for the period you choose.
  • Limits:
    Steady-speed model; no burst billing tiers or CDN edge caching. Hosting assumes average page weight times views; it does not model video segments or API calls unless you fold them into page size. Converter spreads a cap evenly over the period; real usage is spiky.

The math

Bits-to-bytes: MB/s=Mbps8\text{MB/s} = \frac{\text{Mbps}}{8}. Download time divides file bits by effective bits per second after overhead. Hosting rolls views into a monthly bit total, then into Mbps. Caps divide total bytes by seconds in the billing window.
  • Download time:
    t=File Size (bits)Speed (bps)×(1−overhead)t = \frac{\text{File Size (bits)}}{\text{Speed (bps)} \times (1 - \text{overhead})}

    Worked: 70 GB at 100 Mbps, 15% overhead → theoretical ~1h33m; real-world ~1h48m. Toggle binary if the game reports GiB; decimal if the store label uses GB.

  • Hosting bandwidth:
    BWmonth=Views×Page Size×Redundancy×8Seconds in month\text{BW}_{\text{month}} = \frac{\text{Views} \times \text{Page Size} \times \text{Redundancy} \times 8}{\text{Seconds in month}}

    Example: 5,000 daily views, 800 KB average page, 1.2× redundancy → multiply out, then convert to required Mbps for the host quote.

  • Cap to sustained Mbps:
    Mbps=Cap (bytes)×8Seconds in period×106\text{Mbps} = \frac{\text{Cap (bytes)} \times 8}{\text{Seconds in period} \times 10^6}

    2 TB over 30 days (2,592,000 s): (2 × 10¹² × 8) / (2,592,000 × 10⁶) ≈ 6.17 Mbps. Answers “what constant speed would burn this cap if it never idled?”

  • Bits vs bytes (quick check):
    100 Mbps → 12.5 MB/s max before overhead. Lowercase b = bits; uppercase B = bytes. Mixing them inflates or shrinks estimates by 8×.
  • Binary vs decimal:
    Use 1024 when matching Windows or macOS file properties; use 1000 when matching ISP or hosting invoices. Same label on a drive can differ by ~7% between bases.
  • Overhead:
    10–20% is typical for TCP/IP and framing on a wired link; Wi‑Fi, VPN, or congested uplinks can look worse. The slider only scales throughput; it does not model latency or packet loss.

Using the calculator

Pick the mode that matches the question (how long a file takes, how much hosting to buy, or what Mbps a cap implies). Align binary/decimal with whoever printed the number you are comparing.
  • Download/Upload Time:
    File size and connection speed. Read theoretical vs real-world; bump overhead if installs always exceed the theoretical line.
  • Website Hosting Planner:
    Daily page views, average page size in KB, redundancy (1.2× steady site, 1.5–2× for promos or product drops).
  • Hosting Bandwidth Converter:
    Enter cap → sustained Mbps, or Mbps → cap for the same period. Useful when a host quotes TB/month but you think in line speed.
  • Binary / decimal:
    1024 for OS-reported sizes; 1000 for carrier and vendor specs.
  • Overhead slider:
    Default 15% for most home links; lower only if you measure sustained throughput near the raw Mbps÷8 figure.
  • Privacy:
    All math runs in the browser; nothing is sent to a server.

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÷8=12.5 MB/s100 \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 ≈6.17 Mbps\approx 6.17\,\text{Mbps} over 30 days. The math: GB×8×1092,592,000×106\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.

Mathematical Reference Note

Calculation Logic: This tool uses standard mathematical algorithms. While we strive for accuracy, errors in logic or user input can result in incorrect data.

Verification: Results should be cross-checked if used for important academic, professional, or personal calculations.

Standard Terms: This tool is provided free of charge and as-is. CalcRegistry provides no warranty regarding the accuracy or fitness of these results for your specific needs.

© 2026 CalcRegistry Reference Last System Check: May 2026Free Online Utility Tools