TechCompare LogoTechCompare
Back

Data Transfer Calculator

Calculate how long it takes to move data across networks and drives.

Configuration

Mbps

Latency & TCP window model

Enable to model WAN and cloud-migration throughput with the TCP receive window and bandwidth-delay product.

Estimated Transfer Time
6m 40s

Speed Comparison

USB 2.0
13m 53s
480 Mbps
USB 4 / Thunderbolt 4
10s
40 Gbps
Gigabit Ethernet
6m 40s
1 Gbps
Selected
10 Gigabit Ethernet
40s
10 Gbps
WiFi 5 (ac)
16m 40s
400 Mbps
WiFi 7 (be)
1m 20s
5 Gbps
SATA SSD
1m 30s
4.4 Gbps
NVMe Gen4 SSD
7s
56 Gbps

How to use this tool

  1. Enter the file size

    Type the size of the file or folder you want to copy and pick the unit (MB, GB, or TB). The calculator converts the input into bits behind the scenes using the same decimal/SI convention drive manufacturers use (1 GB = 1 billion bytes).

  2. Pick the interface

    Choose the link the transfer will run over (USB 2.0/3.0/3.2/4, Thunderbolt 3/4, Gigabit or 10-Gigabit Ethernet, Wi-Fi 5/6/7, SATA SSD, or NVMe Gen4) or enter a custom Mbps figure for any undocumented interface.

  3. Read the transfer time

    The tool returns the expected copy time broken down into days, hours, minutes, and seconds. Treat the result as a theoretical floor - real-world overhead is lower but the figure is useful for comparison and planning.

  4. Compare two connections

    Toggle Compare to put two interfaces side-by-side and see exactly how many minutes (or hours) you'd save by upgrading from Wi-Fi to Ethernet, USB 3.0 to USB 4, or any other pair.

  5. Model WAN latency (optional)

    For cross-site or cloud transfers, open the latency panel and enter a round-trip time (or pick a preset like transatlantic or satellite) plus a TCP receive window. The tool recomputes the transfer time against the bandwidth-delay product ceiling, window divided by RTT, so you see the throughput a long-distance link actually delivers rather than the naive size-over-speed figure.

About this tool

The Data Transfer Calculator estimates how long it will take to copy a file of any size across any interface, including USB 2.0 through USB 4, Thunderbolt, Gigabit and 10-Gigabit Ethernet, WiFi 5/6/7, SATA SSDs, or NVMe Gen4 drives. Pick a preset or punch in your own Mbps figure, enter the file size in MB, GB, or TB, and the tool returns a realistic transfer time broken down into days, hours, minutes, and seconds.

For WAN and cloud migrations it also models the TCP receive window and bandwidth-delay product, the effect that caps long-distance throughput far below the link rate. Open the latency panel, enter a round-trip time (or pick a preset like transatlantic or satellite), and the tool shows the effective Mbps, the link utilization, and whether the window or the link is the bottleneck. A 1 Gbps link at 100 ms RTT with the default 64 KB window delivers about 5.24 Mbps, which is 0.52% of the rated speed.

It's the quickest way to reality check a backup plan, decide whether that external SSD is worth the money, or work out if you can finish a 200 GB game download before bed. Switch on Compare mode to put two connections head to head and see exactly how many minutes (or hours) you'd save by upgrading from WiFi to Ethernet, or from USB 3.0 to USB 4.

Formula

Transfer time is file size in bits divided by link speed in bits per second. The calculator converts your input to bits (1 byte = 8 bits, 1 GB = 8,000,000,000 bits using the decimal/SI convention drives are sold under), then divides by the Mbps figure times 1,000,000. Real-world overhead, such as TCP, USB framing, and filesystem operations, isn't modeled, so treat the result as an optimistic floor.

Latency and the bandwidth-delay product

When the optional round-trip time is set, the tool computes the TCP throughput ceiling as receive window divided by RTT and uses the smaller of that and the link speed. That ceiling is the bandwidth-delay product at work: on a high-latency link the window can't stay full long enough, so the link delivers a fraction of its rated speed. With RFC 1323 window scaling enabled the window can grow up to 1 GiB and the link fills again. Leave the RTT empty and the tool behaves exactly as the size-over-speed calculator.

When to use it

Use it before buying storage or networking gear to see whether the spec jump is worth the price, when planning a big one-off copy like a photo library migration, or when deciding between wired and wireless for a specific workload. For cloud and WAN migrations, use the latency panel to avoid committing to a cutover date the TCP window won't let you meet. Pair it with the RAID Calculator when sizing a NAS and the Display Bandwidth Calculator if you're comparing video cable throughput against the same numbers.

Pre-computed copy times for the file size + interface combinations visitors ask about most.

Frequently asked questions

How long does it take to transfer 1 TB over Gigabit Ethernet?
At a theoretical 1000 Mbps (125 MB/s), 1 TB takes about 2 hours and 13 minutes in ideal conditions. Real-world speeds over Gigabit Ethernet typically top out around 110-115 MB/s due to TCP overhead, so budget closer to 2.5 hours for a full 1 TB copy.
Why is my real transfer speed slower than the cable's rated speed?
Rated speeds are raw signaling rates in bits per second. Protocol overhead (TCP/IP, USB framing, filesystem operations), encryption, small file latency, and the slowest device in the chain (often the disk, not the cable) all reduce usable throughput. A USB 3.0 port rated 5 Gbps usually delivers around 400 MB/s in practice, not the theoretical 625 MB/s.
What's the difference between megabits (Mbps) and megabytes (MB/s)?
There are 8 bits in a byte, so 1000 Mbps equals 125 MB/s. Network speeds and ISP plans are advertised in megabits per second, while file sizes and storage speeds are measured in megabytes per second. Dividing Mbps by 8 gives you the MB/s figure you actually see when copying files.
How fast is WiFi 6 compared to Gigabit Ethernet for file transfers?
WiFi 6 can exceed Gigabit Ethernet on paper (up to ~9.6 Gbps theoretical) but real-world throughput usually lands between 500 Mbps and 1.5 Gbps depending on distance, interference, and client hardware. For a single large file transfer, wired Gigabit is still more consistent. WiFi 6E or WiFi 7 can edge ahead in ideal conditions.
Is USB 4 or Thunderbolt 4 faster for copying files?
Both use the same 40 Gbps underlying spec and deliver comparable real-world speeds of around 2800-3200 MB/s for sustained transfers. Thunderbolt 4 guarantees the full 40 Gbps and PCIe 32 Gbps tunnel; USB 4 allows 20 Gbps implementations, so check the port's actual spec rather than assuming parity.
Does file structure affect transfer speed?
Yes, significantly. Transferring one 50 GB file hits near maximum throughput, but copying 50 GB of small files (thousands of photos, say) can be 5-10x slower because every file has filesystem and metadata overhead. For large migrations, compressing into an archive first is often faster end to end.
How does network latency affect file transfer time?
On a long-distance link, latency can cap throughput far below the link rate. TCP only sends one receive window of data before waiting for an acknowledgment, so on a high-RTT path the effective speed becomes window size divided by round-trip time. A 1 Gbps link at 100 ms RTT with the default 64 KB window delivers about 5.24 Mbps, which is 0.52% of the rated speed. Use the latency panel to model this.
Why is my WAN or cloud transfer so much slower than my connection speed?
The bottleneck is usually the bandwidth-delay product, not the link. The bandwidth-delay product is link speed times round-trip time, and it is the amount of data that must be in flight to fill the pipe. When your TCP receive window is smaller than it, throughput collapses to window divided by RTT. Enable RFC 1323 window scaling on both endpoints, use a parallel-stream tool like rsync or SMB Multichannel, or check that no middlebox is stripping the TCP window scaling option.
What is TCP window scaling and should I enable it?
RFC 1323 window scaling lets the TCP receive window grow beyond the 64 KB hard cap, up to 1 GiB, by left-shifting the advertised window value. Modern Windows, Linux, and macOS enable it by default. You should leave it on because without it any transfer over roughly 10 ms RTT on a fast link is window-limited. The common failure point is older firewalls or load balancers that silently strip the scaling option.