Calculate exactly how long any file transfer, download, or upload will take. Enter file size and connection speed in any unit — KB, MB, GB, TB, Kbps, Mbps, or Gbps. Includes protocol overhead adjustment and comparison across all major connection types.
✓Verified: ITU-T data rate standards & IEEE 802.3 ethernet specifications — April 2026
📦 File Transfer Time Calculator
Enter file size in kilobytes, megabytes, gigabytes, or terabytesEnter a valid file size greater than 0.
Use Mbps for internet connections (broadband, 5G), Gbps for LANEnter a valid speed greater than 0.
Real-world transfers are slower than theoretical due to protocol headers and acknowledgment packets
Transfer Time
—
⚠️ Disclaimer: Transfer times are estimates based on ideal network conditions. Real-world performance varies due to network congestion, server limits, hardware I/O speed, and simultaneous connections. Storage device speed may be the bottleneck for very fast connections.
Sources & Methodology
✓Transfer time formula based on fundamental data rate mathematics (ITU-T). Unit definitions use SI decimal standards (1 MB = 1,000,000 bytes, 1 Mbps = 1,000,000 bps) consistent with how ISPs and network equipment measure speeds. Protocol overhead figures sourced from published TCP/IP and SMB documentation.
International Telecommunication Union standards defining data transmission rates, bandwidth measurement methodology, and the unit conventions used for network speed calculations.
Defines Ethernet data rates from 10 Mbps to 400 Gbps, the protocol overhead structure, and real-world throughput characteristics used in this calculator's connection comparison table.
The TCP specification defining header sizes, acknowledgment mechanisms, and congestion control algorithms that create the protocol overhead deducted from theoretical throughput in real-world transfers.
Methodology & Formula: Transfer time (s) = (File size in bytes x 8) / (Speed in bps)Real-world time = Theoretical time x Overhead factorThroughput (MB/s) = Speed (Mbps) / 8 (since 1 byte = 8 bits)
Unit conversions: 1 KB = 1,000 bytes, 1 MB = 1,000,000 bytes, 1 GB = 1,000,000,000 bytes (SI decimal, matching ISP and network equipment standards). 1 Kbps = 1,000 bps, 1 Mbps = 1,000,000 bps, 1 Gbps = 1,000,000,000 bps. Overhead factors: TCP/IP 5%, HTTPS/TLS 10%, SMB 15%, Wi-Fi 20%, cloud storage 30% (based on published protocol specifications).
Last reviewed: April 2026
Data Transfer Time: Complete Guide to Download & Upload Speed 2026
Understanding how long file transfers take is essential for planning backups, cloud migrations, media production workflows, network capacity planning, and everyday tasks like downloading software or uploading videos. The critical insight most people miss: network speeds are measured in bits per second while file sizes are measured in bytes. This mismatch causes constant confusion about why downloads seem slow. This guide explains the exact formula, all the factors that affect real transfer time, and practical tables for common scenarios.
The Exact Transfer Time Formula
The fundamental formula for data transfer time is based on dividing the total amount of data (converted to bits) by the speed at which bits are transferred. This is the same formula used by every network planning tool and ISP capacity calculator.
Transfer time (seconds) = (File size in bytes × 8) ÷ Speed in bps
Why Your Downloads Show MB/s but Your Speed Is in Mbps
This is the most common source of confusion in network performance. ISPs advertise speeds in megabits per second (Mbps) because larger numbers look more impressive. Your browser, operating system, and download manager show transfer progress in megabytes per second (MB/s) because file sizes are measured in bytes. The conversion is: MB/s = Mbps ÷ 8. A 100 Mbps connection delivers a maximum of 12.5 MB/s. If your download shows 11–12 MB/s on a 100 Mbps connection, you are getting exactly what you paid for. The remaining gap is normal protocol overhead.
💡 Quick conversion: To convert your Mbps speed to the MB/s you will see in download progress bars, simply divide by 8. 50 Mbps → 6.25 MB/s maximum. 1 Gbps → 125 MB/s maximum. Use our Mbps to MB/s Converter for instant conversion with full explanation.
Transfer Time for Common File Sizes & Connection Speeds
File Size
10 Mbps
100 Mbps
1 Gbps
10 Gbps
100 MB
80 sec
8 sec
0.8 sec
0.08 sec
1 GB
14 min
1.4 min
8 sec
0.8 sec
10 GB
2.2 hr
13 min
80 sec
8 sec
100 GB
22 hr
2.2 hr
13 min
1.3 min
1 TB
9.3 days
22 hr
2.2 hr
13 min
10 TB
93 days
9.3 days
22 hr
2.2 hr
Theoretical times without overhead. Real-world times are typically 10–30% longer.
Real-World Throughput: What You Actually Get vs Advertised Speed
Network equipment is rated at theoretical maximum speeds. Real-world throughput is always lower due to protocol overhead, hardware processing, and network conditions. Understanding the gap helps you plan transfers accurately.
Connection Type
Advertised Speed
Typical Throughput
Efficiency
Main Limiting Factor
Gigabit Ethernet (LAN)
1 Gbps
850–950 Mbps
85–95%
TCP/IP overhead
100 Mbps Ethernet
100 Mbps
90–95 Mbps
90–95%
TCP/IP overhead
Fiber broadband
500 Mbps
400–480 Mbps
80–96%
ISP routing, contention
Cable (DOCSIS 3.1)
200 Mbps
150–190 Mbps
75–95%
Node congestion, overhead
5G mobile
1 Gbps
100–400 Mbps
10–40%
Signal strength, cell load
Wi-Fi 6 (5 GHz)
600 Mbps
300–500 Mbps
50–83%
Air interface, interference
USB 3.0
5 Gbps
300–400 MB/s
48–64%
Storage I/O bottleneck
USB 3.2 Gen 2
10 Gbps
700–1,000 MB/s
56–80%
NVMe SSD read speed
Protocol Overhead: What Slows Every Transfer
Every byte transferred over a network includes additional bytes added by network protocols. These headers, checksums, and acknowledgment packets are necessary for reliable delivery but consume a portion of your bandwidth. TCP/IP headers add 40 to 60 bytes per packet (typically 1,500 byte packets), resulting in 2.7 to 4 percent overhead. TLS encryption for HTTPS adds a handshake and per-record overhead of 1 to 3 percent. SMB (Windows file sharing) adds significant overhead for small files due to its chatty protocol design. For large sequential file transfers, overhead is minimal. For many small files, overhead per file makes a significant difference.
Storage Speed vs. Network Speed: Which Is the Bottleneck?
For fast connections (1 Gbps or faster), the storage device — not the network — is often the bottleneck. A traditional hard drive (HDD) reads at 100 to 200 MB/s, which is the speed limit for any transfer reading from that drive, regardless of network speed. SATA SSDs read at 550 MB/s. NVMe SSDs read at 3,500 to 7,000 MB/s. For a 10 Gbps (1,250 MB/s) network connection, only NVMe SSDs can keep up. Always check both your network speed and storage read/write speed to identify the actual bottleneck.
When Shipping a Hard Drive Is Faster Than the Internet
For very large datasets, physical shipment can outperform even fast internet connections. This concept is known as Sneakernet and is the basis for AWS Snowball, Azure Data Box, and Google Transfer Appliance. At a 100 Mbps upload speed, transferring 10 TB takes approximately 9.3 days. Overnight shipping a 10 TB drive takes 24 hours. Amazon Snowball can transfer 80 TB per device. The crossover point depends entirely on your upload speed: at 1 Gbps, physical shipping beats the network at around 10 TB; at 100 Mbps, the crossover is around 100 GB for time-sensitive transfers.
Parallel Transfers: Speeding Up Large File Operations
Modern transfer tools use parallel connections to increase throughput. A single TCP connection may not fill a high-bandwidth pipe due to TCP slow-start and congestion window limits, especially over high-latency connections. Tools like rsync with multiple streams, Aspera (IBM), AWS S3 multipart uploads, and rclone with parallel transfers can achieve dramatically higher throughput by opening multiple simultaneous connections. For cloud storage, AWS recommends multipart uploads for files over 100 MB, which can increase throughput 3 to 10 times over single-connection uploads on high-bandwidth connections.
Frequently Asked Questions
Transfer time equals file size in bits divided by connection speed in bits per second. First convert file size to bits: multiply megabytes by 8,000,000 (since 1 MB equals 1,000,000 bytes and 1 byte equals 8 bits). Then divide by speed in bps. For a 500 MB file at 100 Mbps: (500 times 8,000,000) divided by 100,000,000 equals 40 seconds theoretical. Add 5 to 30 percent for protocol overhead depending on the transfer method. Use the calculator above for instant results in all time formats.
Because megabits and megabytes are different units. Network speeds are in megabits (Mbps) and download progress bars show megabytes (MB/s). Since 1 byte equals 8 bits, a 100 Mbps connection delivers a maximum of 12.5 MB/s. If your download shows 11 to 12 MB/s on a 100 Mbps connection, you are getting full speed. The gap from 12.5 theoretical to 11 to 12 actual is normal TCP/IP protocol overhead. Divide your Mbps speed by 8 to find your expected MB/s download speed.
At 1 Gbps (gigabit ethernet): approximately 2 hours 13 minutes theoretical, 2.5 to 3 hours real-world. At 100 Mbps broadband: approximately 22 hours. At 50 Mbps: approximately 44 hours. At 10 Gbps: approximately 13 minutes. At USB 3.0 with fast SSD: approximately 45 minutes. For 1 TB to cloud storage (30% overhead on typical upload speed): depends entirely on your upload speed. On a 25 Mbps upload: approximately 4 days. Enter your exact speed above for a personalized calculation.
Protocol overhead is the extra data added by network protocols like TCP/IP headers, TLS encryption handshakes, and acknowledgment packets. It reduces effective throughput below the raw connection speed. TCP/IP alone adds 3 to 5 percent overhead. HTTPS adds another 1 to 3 percent. SMB file sharing adds 5 to 15 percent especially for small files. Wi-Fi adds 15 to 25 percent due to contention and retransmissions. Cloud storage can add 25 to 35 percent due to chunking and metadata. Our calculator includes overhead presets for each transfer type.
At 1 Gbps: approximately 13 minutes theoretical, 15 to 18 minutes real-world. At 100 Mbps: approximately 133 minutes (2 hours 13 minutes) theoretical. At 50 Mbps broadband: approximately 4.5 hours. At 10 Mbps DSL: approximately 22 hours. At USB 3.0 (real-world 400 MB/s): approximately 4 minutes. For cloud backup at 25 Mbps upload: approximately 9 hours. Use the calculator above with your actual connection speed for the most accurate estimate.
Real-world transfer speed is lower than theoretical for these reasons: protocol overhead from TCP/IP headers and acknowledgments (3 to 10 percent), network congestion and shared bandwidth during peak hours, router and switch processing limits, hard drive read/write speed (HDDs 100 to 200 MB/s, SSDs 3,500 MB/s), CPU overhead for encryption, Wi-Fi interference adding 15 to 25 percent overhead, ISP throttling on certain traffic types, and high latency reducing TCP window utilization on long-distance transfers.
For very large datasets, shipping can be faster than uploading. At 100 Mbps upload: 10 TB takes about 9.3 days to upload but only 1 to 2 days to overnight ship. The crossover point depends on your actual upload speed (typically much slower than download speed on residential connections) and urgency. AWS Snowball, Azure Data Box, and Google Transfer Appliance exist specifically for this use case, handling petabyte-scale migrations where internet transfer would take months.
Each file transfer requires opening a new connection, sending metadata, receiving acknowledgments, and closing the connection. This per-file overhead is fixed regardless of file size. Transferring 1,000 files of 1 KB each takes far longer than transferring one 1 MB file even though the total data is the same, because the connection setup overhead multiplied by 1,000 dominates transfer time. Solutions: zip/tar files before transfer, use rsync with batch mode, or use tools that pipeline multiple small file transfers in parallel.
Yes, for compressible content. Text files, databases, logs, and uncompressed documents can compress 3 to 10 times, reducing transfer time proportionally. A 1 GB text file compressed to 200 MB transfers 5 times faster. However, already-compressed files (JPEG, MP4, ZIP, PDF) gain almost nothing from further compression. The CPU time to compress and decompress must also be considered: for slow connections, compression almost always saves total time; for very fast connections (10 Gbps+), CPU compression speed may become the bottleneck.
Bandwidth is the maximum theoretical capacity of a connection (like the maximum speed of a highway). Throughput is the actual data successfully delivered per second, accounting for overhead, errors, retransmissions, and congestion (like actual traffic speed on that highway). Throughput is always less than or equal to bandwidth. The ratio of throughput to bandwidth is called efficiency or utilization. For gigabit ethernet, efficiency is 85 to 95 percent. For Wi-Fi, efficiency is 50 to 75 percent. This calculator uses throughput, not raw bandwidth, for realistic estimates.
Use your actual upload speed, not your download speed. Residential internet connections are asymmetric: download speed is much higher than upload. A 200 Mbps down, 20 Mbps up connection uploads at 20 Mbps (2.5 MB/s maximum). To upload 100 GB: 100,000 MB divided by 2.5 MB/s equals 40,000 seconds equals approximately 11 hours. Add 30 percent for cloud protocol overhead (chunking, checksums, API calls) to get approximately 14 hours. Check your upload speed at fast.com or speedtest.net, then enter it above.
For local transfers: NVMe to NVMe over Thunderbolt 4 (40 Gbps) or USB 3.2 Gen 2x2 (20 Gbps) gives 2,000 to 3,000 MB/s real-world. Over a 10 Gbps network with NVMe SSDs: 1,000 to 1,100 MB/s. Standard gigabit ethernet with NVMe: 110 to 115 MB/s. USB 3.0 with HDD: 100 to 150 MB/s (HDD-limited). The bottleneck is always the slowest component in the chain: network interface, switch, storage device, or CPU encryption overhead.
This calculator uses SI decimal units consistent with how ISPs and network equipment measure speeds: 1 KB equals 1,000 bytes, 1 MB equals 1,000,000 bytes, 1 GB equals 1,000,000,000 bytes. Note that Windows displays file sizes in binary (where 1 GB equals 1,073,741,824 bytes, shown as GiB). The difference is about 7 percent for GB and 10 percent for TB. If your file size is shown in Windows Explorer, the actual transfer will be about 7 to 10 percent faster than shown because the OS displays binary but transfers decimal bytes.