The short answer
A transfer that starts at high speed and then drops sharply is the drive’s write cache filling, which is normal on cheap SSDs and USB sticks. A transfer that is slow from the start is usually the port, the cable, or many small files rather than a few large ones. Check which pattern you have before changing anything.
Copying files involves a source, a destination, a connection and a file system, and the slowest of those sets the speed. The useful diagnostic is the shape of the transfer over time, because each bottleneck produces a different shape.
Reading the pattern
- Fast then collapses to a low steady rate: the destination’s write cache is full. Common on budget SSDs, USB sticks and shingled hard drives.
- Slow and steady from the start: the connection, the port, or an old mechanical drive.
- Erratic, with pauses: many small files, a failing drive, or antivirus scanning each file.
- Very slow for small files, fine for large ones: normal, because each file carries fixed overhead. Thousands of small files will always be slow.
- Starts fast, stalls completely, resumes: often a failing drive retrying bad sectors, which deserves immediate attention.
Check the connection
Check which USB port you are using
Blue or marked SS ports are USB 3 at 5Gbps or more. Black ones are USB 2 at 480Mbps, which caps a transfer at around 40MB/s no matter how fast the drive is.
Check the cable
A USB-C cable rated for charging only carries USB 2 data. This is the single most common cause of an external SSD performing like a memory stick.
Avoid hubs for large transfers
Especially unpowered ones, and especially with other devices connected sharing the same bandwidth.
For network transfers, test wired
Wi-Fi is usually the limit, and a wired connection at gigabit gives around 110MB/s in practice.
Check the drive's own interface
An external enclosure with a slow bridge chip limits a fast drive inside it. The enclosure specification matters as much as the drive.
Useful reference speeds: USB 2 tops out near 40MB/s, USB 3 around 400 to 450MB/s for a good SSD, gigabit Ethernet around 110MB/s, a mechanical hard drive 80 to 160MB/s, and a typical Wi-Fi connection anywhere from 5 to 60MB/s. Comparing your actual speed against these tells you immediately which limit you have hit.
The cache collapse explained
Most consumer SSDs write quickly into a fast cache area and then slow dramatically once it is full, sometimes to below hard drive speeds. On a 1TB drive the cache might be 100GB, so anything smaller than that copies fast and larger transfers collapse partway.
There is no fix beyond buying a drive with a larger cache or a better controller. What you can do is split very large transfers, and avoid filling the drive, since the cache shrinks as the drive fills. A drive above 80 percent full performs noticeably worse.
The same applies to inexpensive USB sticks, which may write at 10MB/s sustained after a brief fast start regardless of their read speed.
Software causes
- Antivirus scanning every file during a copy, which is particularly slow with thousands of small files. Temporarily excluding the folder is a legitimate test.
- Windows indexing the destination as files arrive.
- Cloud sync clients uploading each file as it lands, which is the usual reason copying into a synced folder is slow.
- Remote differential compression and network protocol overhead on Windows network shares, where a different transfer tool is often much faster.
- A file manager showing an inaccurate estimate, which is not a performance problem but does explain apparently stalled progress bars.
The file system
Drives formatted as FAT32 cannot hold files over 4GB and are slower with large transfers. exFAT is the right choice for drives shared between Windows and Mac. NTFS is best for Windows-only drives. A drive formatted for a camera or a television and then used for file transfer is often the slow one.
Fragmentation matters on mechanical drives and not on SSDs, which should never be defragmented. Windows handles this correctly by default.
A transfer that stalls for long periods and then resumes, with the drive making repeated noises, indicates a failing mechanical drive retrying bad sectors. Stop, copy the most important data first, and check the drive’s health with a SMART tool. Continuing to hammer a failing drive is how people lose the rest of it.
Practical improvements
- Archive small files first. Copying one 5GB archive is dramatically faster than copying 50,000 small files, and unpacking at the other end is quick.
- Use a better copy tool for large jobs. Tools that queue transfers, retry automatically and show accurate speeds make a real difference on unreliable connections.
- Copy one job at a time. Two simultaneous transfers to the same drive are slower than the same two in sequence, because the drive spends its time switching.
- Leave headroom on the destination. Above about 80 percent full, most drives slow down.
- For network transfers, wire both ends. This is usually the single biggest improvement available.
Why does my transfer start fast and then slow down?
The destination drive’s write cache has filled. Once it is full, writes proceed at the drive’s true sustained speed, which on budget drives can be very slow. It is normal behaviour rather than a fault.
Why are small files so much slower than one large file?
Each file carries fixed overhead for creating the entry, writing metadata and verifying. Thousands of small files means thousands of those operations. Archiving them into one file first is far faster.
How fast should a USB 3 external SSD be?
Around 400 to 450MB/s for reads and writes within the cache. If you are seeing 40MB/s, you are on a USB 2 port or using a charge-only cable.
Does antivirus slow down file copying?
Noticeably, particularly with many small files, because each one is scanned as it is written. Excluding a folder temporarily is a reasonable test and should be reversed afterwards.
Is it bad to fill a drive completely?
Yes for performance. Most drives slow considerably above about 80 percent full, and SSDs in particular lose cache capacity as they fill.
The order
Watch the shape of the transfer, since that names the bottleneck. Check the port and the cable before anything else, because a charge-only cable and a USB 2 port explain most cases of an external drive being unexpectedly slow. Archive small files into one before copying. Leave headroom on the destination. And treat stalling with drive noises as a failing drive rather than a performance problem.
