How Long Does It Take to Transfer 1TB? Calculator
Calculate how long 1TB takes to transfer at 100 Mbps, 1 Gbps, or 10 Gbps, then adjust for real-world link utilization and protocol overhead.
At a perfect, sustained 1 Gbps, transferring 1 TB takes 2 hours, 13 minutes, and 20 seconds. Using an illustrative 80% utilization assumption, it takes about 2 hours and 47 minutes.
Use the calculator with your file size and connection speed. If you have measured sustained throughput on the actual route, use that result to refine the utilization assumption.
Interactive calculator
Estimate your transfer time
Enter a data size greater than 0.
Enter a connection speed greater than 0.
Use 70–85% for planning unless you have measured sustained throughput.
This is a network-time estimate, not a WarpSend performance promise. File count, latency, packet loss, storage speed, encryption, verification, and competing traffic can change the result.
1TB transfer time at common speeds
The table uses decimal 1 TB (1,000 GB). The planning estimate assumes the transfer sustains 80% of the connection’s advertised speed.
| Connection speed | Best-case minimum | Planning estimate at 80% |
|---|---|---|
| 100 Mbps | 22 hr 13 min 20 sec | 27 hr 46 min 40 sec |
| 500 Mbps | 4 hr 26 min 40 sec | 5 hr 33 min 20 sec |
| 1 Gbps | 2 hr 13 min 20 sec | 2 hr 46 min 40 sec |
| 2.5 Gbps | 53 min 20 sec | 1 hr 6 min 40 sec |
| 10 Gbps | 13 min 20 sec | 16 min 40 sec |
These numbers describe network transfer time. Reading the source, creating destination files, encryption, verification, congestion, and retransmission can add more time.
The file transfer time formula
The basic calculation is:
Time in seconds = file size in bits ÷ sustained transfer rate in bits per second
For 1 TB over 1 Gbps:
1,000,000,000,000 bytes × 8 ÷ 1,000,000,000 bits/s = 8,000 seconds
Eight thousand seconds is 2 hours, 13 minutes, and 20 seconds.
To plan at 80% utilization:
8,000 seconds ÷ 0.8 = 10,000 seconds
That produces the 2-hour, 46-minute, 40-second estimate.
Mbps is not MB/s
Internet connections are normally advertised in megabits per second (Mbps) or gigabits per second (Gbps). File managers commonly display megabytes per second (MB/s).
There are eight bits in one byte:
- 100 Mbps = 12.5 MB/s at the theoretical maximum.
- 1 Gbps = 125 MB/s at the theoretical maximum.
- 10 Gbps = 1.25 GB/s at the theoretical maximum.
At 80% utilization, a 1 Gbps path carries about 100 MB/s of payload.
TB and TiB are different
This article uses decimal units:
- 1 TB = 1,000,000,000,000 bytes
- 1 TiB = 1,099,511,627,776 bytes
A 1 TiB transfer contains about 9.95% more data than a 1 TB transfer. At 1 Gbps and 80% utilization, that difference adds roughly 16 minutes.
The calculator lets you select either unit.
Why real transfers take longer
Your internet plan is not your sustained application rate
An advertised 1 Gbps service describes a line rate under specific conditions. Shared traffic, Wi-Fi, VPNs, rate limits, routing, and provider congestion can reduce the rate available to one transfer.
Long-distance latency can leave bandwidth unused
A high-bandwidth path needs enough unacknowledged data in flight to remain busy while acknowledgements travel back. This relationship is called the bandwidth-delay product.
Modern transports can use larger windows, several flows, QUIC, or other scheduling strategies to keep work in flight. The useful question is not only “What is the line speed?” but “What sustained payload rate does this application achieve on this route?”
Read high-speed file transfer over long distance for a deeper explanation.
File count changes the result
One 1 TB file and one million 1 MB files contain approximately the same payload, but they are not the same workload.
Every file can add metadata, source and destination open/close work, verification, and network coordination. Across a high-latency route, repeated per-file waits can dominate the payload time.
See why transferring thousands of small files is so slow.
Storage can be the bottleneck
A 10 Gbps path can theoretically carry 1.25 GB/s. If either storage system sustains only 400 MB/s after filesystem and verification work, the network cannot make the transfer finish at the 10 Gbps minimum.
Encryption and verification consume resources
Encryption, content hashing, and whole-file verification are useful work. They consume CPU and storage bandwidth, and should remain enabled during a meaningful benchmark.
How much utilization should I enter?
Use a measured sustained rate whenever possible. If you only know the advertised connection speed:
- 90–95%: controlled, well-tuned route with fast storage.
- 70–85%: reasonable planning range for a healthy business connection.
- 40–70%: shared path, Wi-Fi, VPN, storage constraints, or uncertain routing.
- Below 40%: investigate file count, RTT, packet loss, rate limits, CPU, and storage.
The calculator does not attempt to predict WarpSend, FTP, SFTP, or Aspera performance from the product name. Enter the utilization you have measured—or use a conservative planning assumption.
For a concrete NAS planning example, see how to seed a Synology Snapshot Replication initial copy with a USB drive instead of sending the full first replica over a constrained WAN.
How to make the estimate more accurate
- Measure the route between the actual sender and receiver.
- Record sustained application throughput, not a nearby speed-test server.
- Use the real file pattern: one large file, medium batch, or many small files.
- Keep encryption and verification enabled.
- Include dispatch, startup, and final verification in wall-clock time.
- Repeat the run and use the median result.
Compare the current releases using the same files, route, storage, and security settings. Record transfer-phase throughput separately from the time until the recipient has a verified copy. The WarpSend vs FTP benchmark method explains how to run that comparison; an FTP result does not establish performance against SFTP or Aspera.
Frequently asked questions
How long does 1TB take to upload at 100 Mbps?
The theoretical minimum is 22 hours, 13 minutes, and 20 seconds. At 80% sustained utilization, plan for approximately 27 hours and 47 minutes.
How long does 1TB take at 1 Gbps?
The theoretical minimum is 2 hours, 13 minutes, and 20 seconds. At 80% utilization, plan for approximately 2 hours and 47 minutes.
How long does 1TB take at 10 Gbps?
The theoretical minimum is 13 minutes and 20 seconds. At 80% utilization, plan for approximately 16 minutes and 40 seconds—if the source, destination, CPU, and storage can sustain the required rate.
Does latency change the mathematical minimum?
The payload-only formula does not include latency. In practice, latency can reduce the sustained rate achieved by the transport, especially when windows are too small or the workflow performs serialized per-file operations. Represent that effect with a lower measured utilization.
Does the calculator upload my files?
No. It only performs arithmetic in your browser. It does not read or upload a file.
Try WarpSend on your real route and replace the planning assumption with measured sustained throughput.