Data Transfer Calculator
A 10 GB file over a 100 Mbps connection takes about 13 minutes and 20 seconds in theory. A data transfer calculator works out that kind of estimate by solving for whichever value you do not already know: transfer time, transfer speed, or data size. Enter any two of the three and the tool computes the third using consistent bit and byte conversions. This is useful when you are planning a file upload, sizing a backup window, checking whether an internet plan can move a video project before a deadline, or figuring out how long a cloud sync will realistically take. The calculator supports both decimal size units (KB, MB, GB, TB) and binary size units (KiB, MiB, GiB, TiB), plus common network speed units (Kbps, Mbps, Gbps), so the numbers match whatever your operating system, router, or ISP happens to display.
Quick answer
Pick a solve mode: time, speed, or size, based on which value you don't already have.
What this tells you
- •Pick a solve mode: time, speed, or size, based on which value you don't already have.
- •The calculator converts everything to bits and bytes internally before doing any math, since network speeds are measured in bits per second while file sizes are measured in bytes.
- •Decimal units (GB, TB) use powers of 1000, while binary units (GiB, TiB) use powers of 1024. The two are close but not identical, and the gap grows at larger sizes.
- •Results are theoretical maximums based on the numbers you enter. Real-world transfers are almost always slower because of overhead, congestion, and hardware limits.
- •The tool shows the result in both raw seconds and a readable hours/minutes/seconds format so you can use whichever fits your planning.
How to Use
- 1Choose what you want to solve for in the Solve for field: Time, Speed, or Size. This tells the calculator which of the three inputs to compute and which two to treat as known values.
- 2Enter the data size and select its unit. Use GB or MB for most files, or switch to GiB or MiB if your operating system reports size in binary units (Windows File Explorer typically does).
- 3Enter the transfer speed and select its unit (Kbps, Mbps, or Gbps). This should match the number your ISP, router, or network adapter reports, which is almost always in bits per second, not bytes.
- 4Enter the transfer time and select its unit (seconds, minutes, or hours) if time is one of your known values.
- 5Click Calculate to see the estimated result, shown as a human-readable duration and in raw seconds, along with the resolved size and speed used in the calculation.
How It Works
Formula
Bits = Bytes x 8
Time (seconds) = (Size in bytes x 8) / Speed in bits per second
Speed (bps) = (Size in bytes x 8) / Time in seconds
Size (bytes) = (Speed in bps x Time in seconds) / 8File and storage sizes are measured in bytes, but network speeds are measured in bits per second, and there are 8 bits in a byte. The calculator first converts your size input to bytes and your speed input to bits per second using standard unit factors, then multiplies the byte count by 8 to get bits before solving for whichever variable you asked for. Decimal units (KB, MB, GB, TB) scale by 1000 per step, matching how storage manufacturers and most speed test tools label sizes. Binary units (KiB, MiB, GiB, TiB) scale by 1024 per step, matching how operating systems like Windows often report file and drive sizes internally. Mixing the two without noticing is one of the most common sources of a 'why doesn't this match' moment, which is why the calculator keeps them as separate, explicit unit choices instead of guessing.
Calculation note: values are processed in the order shown above, using the current input units.
Worked Examples
How long to upload a 10 GB video file
10 GB converts to 10,000,000,000 bytes, which is 80,000,000,000 bits. Dividing by a speed of 100,000,000 bits per second gives 800 seconds. This is the theoretical minimum time at a steady, uninterrupted 100 Mbps, before accounting for overhead or network variance.
Minimum upload speed to back up a DVD image before a deadline
A 4.7 GB DVD image is 4,700,000,000 bytes, or 37,600,000,000 bits. With a 600-second window (10 minutes), the required speed works out to roughly 62,666,667 bits per second, or about 62.67 Mbps. Any connection rated below that will not finish in time even under ideal conditions.
How much data a gigabit connection can move in an hour
A 1000 Mbps (1 Gbps) connection sustained for 3,600 seconds moves 3,600,000,000,000 bits, which is 450,000,000,000 bytes, or 450 GB. This is a theoretical ceiling. Real gigabit connections rarely sustain the full rated speed for a full hour due to overhead and other network activity.
Transfer time using a binary size unit
500 MiB equals 524,288,000 bytes because binary units scale by 1024, not 1000. Converted to bits (4,194,304,000) and divided by a speed of 20,000,000 bits per second gives about 209.72 seconds, which rounds to 3 minutes and 30 seconds. Using 500 MB instead of 500 MiB here would have produced a noticeably different, slightly shorter result.
Estimated time to back up a 2 TB drive over USB 3.0
2 TB is 2,000,000,000,000 bytes, or 16,000,000,000,000 bits. At the theoretical USB 3.0 ceiling of 5 Gbps (5,000,000,000 bits per second), that works out to 3,200 seconds, or 53 minutes and 20 seconds. Real USB 3.0 transfers to spinning or external drives are usually well below this because the drive's own read and write speed becomes the actual bottleneck, not the cable.
Typical transfer times by file size and connection speed
Theoretical transfer times for common file sizes at two common connection speeds, calculated the same way the tool calculates them: size in bytes x 8, divided by speed in bits per second.
| File size | Time at 100 Mbps | Time at 1 Gbps |
|---|---|---|
| 1 GB | 1m 20s | 8s |
| 10 GB | 13m 20s | 1m 20s |
| 100 GB | 2h 13m 20s | 13m 20s |
| 1 TB | 22h 13m 20s | 2h 13m 20s |
These figures assume a constant, uninterrupted connection at exactly the listed speed. Actual transfer times are typically longer because of protocol overhead, other network traffic, and storage read/write limits.
Common mistakes
- Mixing decimal and binary size units without noticing. A file listed as 500 MiB by an operating system is not the same as 500 MB, and the gap widens as sizes grow into GB and TB territory.
- Assuming an ISP's advertised speed equals sustained real-world throughput. A '500 Mbps' plan rarely delivers a full, uninterrupted 500 Mbps to a single file transfer once overhead, Wi-Fi conditions, and server-side limits are factored in.
- Confusing bits and bytes when reading speed numbers. Network speeds are almost always quoted in bits per second (Mbps), while file sizes are quoted in bytes (MB), and treating the two as interchangeable produces an answer roughly 8 times off.
- Ignoring the slower end of the connection. A fast local network speed does not help if the file is being uploaded to or downloaded from a remote server with a much lower speed cap or heavy load.
- Forgetting that storage hardware has its own speed ceiling. A theoretically fast network or USB link is still limited by how quickly the source or destination drive can read or write data, especially for spinning hard drives or heavily fragmented storage.
Embed this calculator on your site
Drop this single line where you want the calculator to appear. It is responsive, mobile-friendly, resizes automatically, and is free to use with attribution.
<script src="https://calctide.com/embed.js" data-tool="data-transfer-calculator" async></script>Preview the embed at /embed/data-transfer-calculator/.