Download Time & Bandwidth Calculator
Work out how long a download takes from the file size and your connection speed, the speed you need to finish in a set time, or how much data a link moves, in MB or MiB, with real TCP/IP overhead if you want it.
How to Use
- Pick what to solve for: Download time (size and speed known), Speed needed (size and a deadline known) or Data moved (speed and time known). The answer appears in its own box, in the unit you choose beside it.
- Enter the file size and choose its unit. MB, GB and TB are decimal (1 GB = 1,000,000,000 bytes); MiB, GiB and TiB are binary (1 GiB = 1,073,741,824 bytes), the sizes many operating systems show.
- Enter your connection speed. Internet plans are sold in bits per second (Mbit/s, often written Mbps); a download window usually shows bytes per second (MB/s), which is 8 times smaller.
- For a realistic figure, set Protocol overhead to the stack you use, such as TCP over IPv4. The page works out what share of each Ethernet frame is your data, 94.93% at the standard 1,500-byte MTU, and shows the derivation.
- Read the time, throughput and the comparison with and without overhead, and check Show Work for every unit conversion.
Worked Example
A 5 GB movie at 100 Mbit/s. 5 GB = 5,000,000,000 bytes × 8 = 40,000,000,000 bits. 100 Mbit/s = 100,000,000 bits per second. 40,000,000,000 ÷ 100,000,000 = 400 s, 6 min 40 s. Over TCP and IPv4 on Ethernet, only 1,460 of every 1,538 bytes on the wire are movie, so the data arrives at 100 × 0.9493 = 94.93 Mbit/s and the download takes 40,000,000,000 ÷ 94,928,479 = 421.4 s, 7 min 1 s, in 3,424,658 full-size frames.
Speed for a deadline. To fetch 50 GB in one hour: 400,000,000,000 bits ÷ 3,600 s = 111.1 Mbit/s of data, and 111.1 ÷ 0.9493 = 117.0 Mbit/s on the line.
The common mistake: forgetting the 8. Dividing 5 GB by 100 Mbit/s as if both were bytes gives 5,000 MB ÷ 100 = 50 s, eight times too fast. The right answer is 400 s. A smaller trap is mixing GB and GiB: a file your computer shows as 4 GiB is 4,294,967,296 bytes, so at 100 Mbit/s it takes 343.6 s (5 min 44 s), not the 320 s a 4 GB file would.
Show Work
Formulas
Where the Numbers Come From
Decimal and binary prefixes. Kilo, mega and giga are SI prefixes for 103, 106 and 109, so a 100 Mbit/s link moves exactly 100,000,000 bits a second. Computers grew up counting memory in powers of two, and “kilobyte” drifted to mean 1,024 bytes. To end the clash, the International Electrotechnical Commission approved separate binary prefixes in December 1998 (kibi, mebi, gibi, tebi: Ki, Mi, Gi, Ti), published as Amendment 2 to IEC 60027-2 in January 1999. NIST’s page “Prefixes for binary multiples” gives the definitions used here: 1 MiB = 1,048,576 B and 1 GB = 1,000,000,000 B.
What an Ethernet frame costs. RFC 894 (April 1984) set the largest IP datagram on Ethernet at 1,500 octets, today’s standard MTU. Around it, IEEE 802.3 adds a 7-byte preamble, a 1-byte start-of-frame delimiter, a 14-byte header, a 4-byte CRC-32 frame check sequence and a 12-byte inter-frame gap. RFC 6349 (August 2011), the IETF framework for TCP throughput testing, adds these up to 1,538 bytes per frame, 8,127 frames a second on 100 Mbit/s Ethernet, and a maximum TCP throughput of 94.9 Mbit/s with 1,460-byte segments.
The headers inside. The IPv4 header is at least 20 bytes (RFC 791, 1981, five 32-bit words) and the IPv6 header is a fixed 40 bytes (RFC 8200, 2017). The TCP header is at least 20 bytes (RFC 9293, 2022); the Timestamps option of RFC 7323 adds 10 bytes, padded to 12 with two no-op bytes in the layout that RFC recommends. UDP’s header is 8 bytes (RFC 768, 1980). These are the minimum sizes, so the efficiency here is the best a link can do; retransmissions, Wi-Fi, VPN tunnels and server limits only lower it.
About This Calculator
Reference: Ethernet Cable Categories, Pinouts & PoE.
Reference: USB Versions & Speeds.
Reference: Wireless IoT Protocols Compared.
This calculator solves the transfer equation three ways: the time a download or upload takes, the connection speed needed to finish by a deadline, and the data a link moves in a given time. Sizes can be decimal (kB, MB, GB, TB) or binary (KiB, MiB, GiB, TiB) and speeds in bits or bytes per second, and the answer is shown in the unit you pick. Instead of a rule-of-thumb “10% overhead”, it works out the real share of each Ethernet frame left for data from the header sizes in the standards, for TCP or UDP over IPv4 or IPv6, at any MTU from 576 to 9,216 bytes.
The results are best-case figures for a steady link; they do not model TCP slow start, packet loss or a server that sends more slowly than your line. Everything runs in your browser and nothing is sent anywhere. It is for home users choosing a plan, IT staff planning backups and migrations, and students checking bit-and-byte arithmetic.
Related tools: File Size Converter, Ping Check, and IP Subnet Calculator & CIDR Visualizer.
Frequently Asked Questions
How long does it take to download 5 GB at 100 Mbps?
5 GB is 5 × 109 × 8 = 40,000,000,000 bits. At 100,000,000 bits per second that is 400 seconds, 6 min 40 s, if every bit on the line were file data. A TCP download over IPv4 and Ethernet carries 1,460 bytes of file data in every 1,538 bytes sent, so it takes at least 400 ÷ 0.9493 = 421.4 s, about 7 min 1 s. Wi-Fi, a busy server or a congested route can make it slower still.
Why does my 100 Mbps connection download at only about 12 MB/s?
Because speeds are sold in bits and files are counted in bytes, and a byte is 8 bits: 100 Mbit/s ÷ 8 = 12.5 MB/s. TCP, IP and Ethernet headers then take their share, which leaves at most 12.5 × 0.9493 = 11.87 MB/s of file data. If your download window shows MiB/s, divide again by 1.048576: 11.32 MiB/s.
What is the difference between MB and MiB?
A megabyte (MB) is 1,000,000 bytes, using the SI prefix mega = 106. A mebibyte (MiB) is 220 = 1,048,576 bytes, one of the binary prefixes the IEC approved in December 1998, as NIST explains. The gap grows with size: 1 GiB is 7.37% more than 1 GB, and 1 TiB is 9.95% more than 1 TB. Network speeds are always decimal, so 1 Mbit/s is exactly 1,000,000 bits per second.
Where does the 94.9% TCP/IP efficiency come from?
From the header sizes. A standard Ethernet frame carries up to 1,500 bytes (the MTU), and on the wire it also needs a 7-byte preamble and 1-byte start delimiter, a 14-byte header, a 4-byte checksum and a 12-byte gap before the next frame: 1,538 bytes in all. Inside the 1,500, IPv4 takes 20 bytes and TCP 20, leaving 1,460 for data. 1,460 ÷ 1,538 = 94.93%, the same figure RFC 6349 gives for 100 Mbit/s Ethernet (94.9 Mbit/s). With TCP timestamps it is 94.15%, over IPv6 93.63%.
What speed do I need to download 50 GB in an hour?
50 GB is 400,000,000,000 bits, and an hour is 3,600 seconds, so the data has to arrive at 111.1 Mbit/s. Divide by the 94.93% TCP/IPv4 efficiency and the line itself must run at 117.0 Mbit/s, so a 100 Mbit/s plan is not quite enough and a 150 or 200 Mbit/s plan is. Choose Speed needed to try your own deadline.
How do I use the Download Time & Bandwidth Calculator?
Just type your numbers. The answer shows up right away — there is no button to press. Change anything and it updates by itself.
Do I need to install or sign up for anything?
Not at all — it runs in the browser with nothing to install and no account. After it loads once, it even works without an internet connection.
Is my information private?
Yes. Everything happens in your browser. Nothing you type is sent to a server or saved anywhere.
Common Use Cases
Game and update downloads
A 50 GB game at 1 Gbit/s takes 6 min 40 s at the line rate and about 7 min 1 s over TCP/IPv4.
Backups and data migration
1 TB over a 10 Gbit/s link takes 13 min 20 s at line rate; with 9,000-byte jumbo frames TCP/IPv4 keeps 99.14% and needs 13 min 27 s.
Choosing an internet plan
Pulling 50 GB in an hour needs 111.1 Mbit/s of data, or 117.0 Mbit/s on the line once TCP/IPv4 overhead is counted.
Data caps and metered links
A link running flat out at 20 Mbit/s for an hour moves 9 GB, which a computer shows as 8.38 GiB.
Explaining a slow download
A 100 Mbit/s line delivers at most 11.87 MB/s of file data, not 100 MB/s: divide by 8 for bytes, then take off 5.07% for headers.
Sending photos and documents
A 10 MB set of photos at 50 Mbit/s takes 1.6 s, or 1.69 s with TCP/IPv4 overhead.
Last updated: