Enter how much data you’re moving, the connection, and the drives at each end. The calculator gives you the realistic transfer time, not the marketing one. Here’s the logic behind it.

Effective speed is the slower of the link and the disk, minus overhead. A transfer can only go as fast as its slowest part. If your 10GbE link can carry 1,250 MB/s but the source is a single hard drive that reads at 180 MB/s, you move data at 180 MB/s. The tool takes the lower of the two, then trims it by a real-world efficiency factor for protocol overhead.

The bottleneck readout is the useful part. It tells you whether spending money on faster networking would actually help. If the drive is the limit, a 10GbE card changes nothing until you add disks or switch to SSDs. If the link is the limit, faster networking pays off directly.

Time is just size divided by speed. Once the effective speed is set, the math is exact: a 1 TB file at 280 MB/s takes about an hour. The per-link table shows the same transfer across every common Ethernet speed so you can see where the gains flatten out for your storage.

Sizes use decimal units (1 TB = 1,000 GB) to match how both drives and network speeds are quoted.

Worked examples

These are this calculator’s own outputs, computed with the same formula the tool runs in your browser — so you can see a real answer without touching a single input.

The page’s own default state: backing up an 8 TB media library off a single 3.5" hard drive to the NAS over a 2.5GbE link, at typical efficiency. This is the exact result a reader sees the instant the page loads

  • Inputs: Amount = 8, Unit = TB, Source/target drive = Single 3.5" HDD (180 MB/s), Link speed = 2.5GbE (312.5 MB/s), Efficiency = Typical (0.92)
  • Result: Headline: 13 h 25 m. Effective speed 166 MB/s, Bottleneck “Drive”, At line rate 7 h 6 m. The drive warning fires: drive 180 MB/s vs link Math.round(312.5) = 313 MB/s. The table shows 2.5GbE, 5GbE, 10GbE and 25GbE all tied at 13 h 25 m.

Moving a 2 TB project archive between two NVMe Gen4 workstations over 10GbE at typical efficiency — the case where the network, not the storage, is the limit

  • Inputs: Amount = 2, Unit = TB, Source/target drive = NVMe Gen4 SSD (7000 MB/s), Link speed = 10GbE (1250 MB/s), Efficiency = Typical (0.92)
  • Result: Headline: 28 m 59 s. Effective speed 1.15 GB/s, Bottleneck “Link”, At line rate 26 m 40 s. Going from 10GbE to 25GbE would cut it to 11 m 35 s because the NVMe can still feed it.

The classic homelab question: seeding 4 TB onto a four-bay HDD NAS over a new 10GbE link, at typical efficiency — does the 10GbE card actually earn its money?

  • Inputs: Amount = 4, Unit = TB, Source/target drive = HDD RAID array, 4-bay (450 MB/s), Link speed = 10GbE (1250 MB/s), Efficiency = Typical (0.92)
  • Result: Headline: 2 h 41 m. Effective speed 414 MB/s, Bottleneck “Drive”, At line rate 53 m 20 s. The table flatlines at 2 h 41 m from 5GbE upward, so 10GbE and 25GbE buy nothing over 5GbE for this array.

How much data

The connection

estimated transfer time
Effective speed
Bottleneck
At line rate
Same transfer at each link speed
LinkEffectiveTime

Times assume a sustained sequential transfer at the chosen efficiency, capped by the slower of the link and the drive. Many small files, encryption, or a busy CPU will run slower. Sizes use decimal units (1 TB = 1,000 GB).

Frequently asked questions

Why is my real transfer slower than my network's rated speed?
Three reasons stack up. First, protocol overhead: TCP, SMB or NFS, and packet headers eat roughly 8 to 12 percent of the line rate, so a 10GbE link that reads as 1,250 MB/s on paper sustains closer to 1,100 to 1,150 MB/s in practice. Second, file count: a folder of thousands of small files transfers far slower than one big file because each file has its own open, write, and close overhead. Third, the drives at each end: if either the source or the destination disk is slower than the link, it sets the pace. This calculator models the first and third; the small-file penalty is workload-specific.
How do I know if my drive or my network is the bottleneck?
Compare their sustained speeds. A single 7,200 rpm hard drive holds roughly 120 to 290 MB/s depending on which part of the platter it’s reading, which is below even 2.5GbE’s ~295 MB/s ceiling. So with one mechanical drive, the disk is almost always the limit and a faster network changes nothing. You need several drives striped in RAID, or SSDs, before a 10GbE or Thunderbolt link gets to stretch its legs. Set the drive field here and the tool tells you which side is capping the transfer.
Do I actually need 10GbE at home?
Only if your storage can feed it. 10GbE moves about 1,250 MB/s, but a four-bay HDD array sustains maybe 400 to 600 MB/s and a single SATA SSD about 550 MB/s. If your NAS holds spinning disks, 2.5GbE or 5GbE usually captures most of the real-world benefit for a fraction of the cost. 10GbE earns its keep when you have a wide RAID array, NVMe storage, or you regularly move very large files and value the time saved.
Why doesn't the size match my drive's advertised capacity?
This tool uses decimal units, where 1 TB equals 1,000 GB, the same way drive makers label capacity. Operating systems often report in binary units (1 TiB = 1,024 GiB), which is why a ‘4 TB’ drive shows as about 3.64 TiB in Windows. The gap is roughly 7 to 10 percent and grows with size. For transfer-time math the decimal figure is the right one to use, since both the data size and the link speed are quoted decimally.