Use observed speed rather than a marketing maximum
If a drive advertises 3,000 MB/s but a representative copy actually runs at 600 MB/s, entering 600 produces a much more useful estimate.
FREE WEB TOOL
Estimate local file copy time from data size and effective transfer speed in MB/s.
đź”’ Inputs are processed locally in your browser.
Estimate local copy time from data size and an effective transfer rate in MB/s. It is useful for SSD, HDD or NAS planning when you have a realistic observed copy speed and want a rough duration.
667 seconds, or roughly 11 minutes 7 seconds.Many small files, antivirus scanning, encryption, USB/NAS variation and slow destination writes can increase actual time. The result assumes the entered effective speed remains steady.
If a drive advertises 3,000 MB/s but a representative copy actually runs at 600 MB/s, entering 600 produces a much more useful estimate.
A fast source SSD copying to a slow hard drive can be limited by the destination. Use an effective rate that reflects the whole path.
The same total capacity can take longer when it is split across hundreds of thousands of files because filesystem and metadata work occurs per item.
The estimate treats 1 GB as 1000 MB. Operating systems that display GiB-style values can show a slightly different number for the same data.
Verification, compression, snapshots or network transfer can add time beyond the raw copy step calculated here.
Related references: Digital storage units · SI prefixes & units