File Download Time Calculator

Type size, unit, speed, and Mbps. 700 MB and 25 Mbps give 3.9 min. 4.7 GB and 100 Mbps give 6.7 min. 10 MB and 1 Mbps give 1.4 min. Binary MB, decimal Mbps.

MB is 1024² B, Mbps is 10⁶ b/s. No TCP or Wi-Fi overhead. Another GB sketch sits on data transfer time.

Input data

Quick examples:

Results

Enter data and click Calculate.

How it works

File Download Time Calculator in this calculator divides a binary size by a decimal speed. 700 MB and 25 Mbps give 3.9 min. 4.7 GB and 100 Mbps give 6.7 min. 10 MB and 1 Mbps give 1.4 min. The calculator does not add TCP and does not measure Wi-Fi.

Field dl-size is a number. Select dl-size-unit in the examples is MB or GB. Field dl-mbps is the speed. Select dl-speed-unit stays Mbps. 1 MB is 1024² B. 1 Mbps is 1,000,000 b/s. Then seconds become minutes with one decimal.

3.9 min is not a browser bar. 6.7 min does not come from a speedtest. 1.4 min does not know retransmits. You type both numbers and both units. Another unit at 700 changes 3.9 min.

Data transfer time next door takes MB and efficiency. IOPS times a disk. Here 700 MB and 25 Mbps stay 3.9 min, the unit quotient alone.

Type 700, leave MB, type 25, leave Mbps, then Calculate. The result is 3.9 min. A comma in 4,7 with GB works. Zero speed does not divide.

700 MB and 25 Mbps give 3.9 min. 4.7 GB and 100 Mbps give 6.7 min. 10 MB and 1 Mbps give 1.4 min. Another size at 25 changes 3.9 min.

Formula

seconds = (size × unit bits) / (speed × unit b/s). MB = 1024² B, Mbps = 10⁶ b/s.

How to use

  1. Type 700 and leave the size unit on MB.
  2. Type 25 and leave Mbps. Click Calculate. The result is 3.9 min.
  3. 4.7 and GB at 100 Mbps give 6.7 min. 10 MB and 1 Mbps give 1.4 min.
  4. Binary MB and decimal Mbps, not TCP.
  5. The next card times a transfer with efficiency.

700 MB and 25 Mbps give 3.9 min

Binary MB, decimal Mbps. 700 and 25 give 3.9 min. Not TCP.

File
The dl-size field. 4.7 GB and 100 Mbps give 6.7 min. Not a speedtest.
Download
File over Mbps. 10 MB and 1 Mbps give 1.4 min.
Time
The calculator result. 700 MB and 25 Mbps leave 3.9 min.

Examples

Example 1

  • 700 MB
  • 25 Mbps

3.9 min

What download time at 700 MB and 25 Mbps? 3.9 min. Binary MB, decimal Mbps.

Example 2

  • 4.7 GB
  • 100 Mbps

6.7 min

What time at 4.7 GB and 100 Mbps? 6.7 min.

Example 3

  • 10 MB
  • 1 Mbps

1.4 min

What time at 10 MB and 1 Mbps? 1.4 min.

Related calculators

Common questions

What about 700 MB and 25 Mbps?

3.9 min. Binary MB over decimal Mbps. Not TCP.

What about 4.7 GB and 100 Mbps?

6.7 min. GB is 1024³ B, Mbps stays 10⁶.

What about 10 MB and 1 Mbps?

1.4 min. A small file, a slow Mbps.

Is 1 MB 1,000,000 B?

No. On this calculator 1 MB = 1024² B. Mbps is decimal.

Does 3.9 min include TCP overhead?

No. The quotient alone. Wi-Fi and retransmits are outside this calculator.

What do the unit selects change?

MB or GB on size. Mbps on speed. The examples keep those units.

Does a comma in 4,7 work?

Yes. 4,7 and 4.7 with GB give the same 6.7 min.

How is this different from data transfer time?

That card uses MB and efficiency. Here 700 MB and 25 Mbps give 3.9 min.

Does zero Mbps count?

No. Without a speed there is no divide.

Knowledge sources

The calculator counts bits, bytes or throughput from your numbers. Below are SI and bit definitions (NIST).

Page updated in 2026.

Assumptions: ideal vs real speed

The calculator assumes a constant, fully utilized link speed for the whole transfer — no TCP slow-start, no pauses, no sharing. The result is a lower bound (“as fast as possible”), not a guarantee. An ISP’s advertised Mbps is usually a best-case ceiling, not the average over Wi‑Fi at home.

Size, bits, and Mbps

File size uses bytes (base 1024); speed uses bits/s (base 1000). Formula: time = (size × 8) / speed_bps. So 100 Mbps ≠ 100 MB/s — about 12.5 MB/s in the ideal case.

Wi-Fi, overhead, and congestion

  • Protocol overhead — TCP/TLS, retransmits, handshakes.
  • Wi‑Fi vs wired — wireless is often 30–60% below the “plan” due to interference and shared channels.
  • Latency and congestion — a distant server plus a busy network lowers effective throughput.
  • Concurrent downloads — they share the same link; each gets a smaller slice.

How to reduce download time

  • Compression / smaller assets (WebP, minify, bundle splitting).
  • A CDN closer to users (lower latency, often higher effective speed).
  • Wired instead of weak Wi‑Fi; avoid many large transfers at once.
  • Chunking / resume — does not shorten ideal time, but avoids restarting from zero.

Examples

  • 100 MB @ 10 Mbps → about 1 min 24 s; @ 100 Mbps → about 8.4 s (10× faster).
  • 700 MB @ 25 Mbps → about 3.7 min.
  • 1 GB on a slow mobile link ~5 Mbps → about 28 min — large files hurt most on weak links.