How do I test the real write speed of a USB drive without lab equipment?

In short

Write a single file larger than the drive's cache and time it — but that is a screening check, not a product guarantee. Advertised speeds are usually burst figures measured over a few hundred megabytes, which a cache absorbs; a file of 4GB or more forces a write to the actual memory, and the rate after the first 30 seconds predicts real use better than the peak. That single result is not a specification: it moves with the test host, file size, file system, cache state, how full the drive is, how many runs you average and the room temperature. Treat it as one data point, and set the speed you actually require in the purchase agreement with a defined method. WINTEL supplies this from its own plant in Shenzhen, China.

Why the number on the box does not match what you see

Flash drives contain a small cache. When you start a write, data lands in the cache first, and the cache is much faster than the memory behind it. For the first few hundred megabytes the transfer looks excellent.

Once the cache fills, the drive has to write through to the memory, and the rate drops — often by half or more. If your test writes less data than the cache can hold, you measured the cache, not the drive.

This is why a datasheet can be truthful and still useless: it reports a real measurement of the wrong thing.

A method that actually measures the drive

The procedure is deliberately boring, and it works without any special software.

  • Empty the drive, or at least ensure it has more free space than your test file.
  • Create or obtain one file of 4GB or larger. A video file works well; thousands of photos do not.
  • Copy it to the drive and watch the transfer rate. Ignore the first 20–30 seconds.
  • Record the rate once it has been steady for at least a minute. That is your sustained write speed.
  • Delete and repeat once. A large discrepancy between two runs usually means a thermal or cache effect worth understanding.

The seven conditions that make the number repeatable

One stopwatch run tells you what happened once, on your machine, with your file. It does not tell a buyer what every unit in an order will do. If you are writing a speed requirement into a purchase agreement, fix these seven variables first — otherwise two parties can run "the same test" and get different answers.

  • A number is a product guarantee only when it is tied to these conditions in writing — otherwise it is an observation.
  • Sequential speed, sustained write speed and endurance are three different claims; a pass on one is not evidence of the others.
VariableWhat to fixWhy it moves the result
Test hostNamed port (USB 2.0 vs 3.0) and machine classA USB 2.0 port caps every drive near 30–40MB/s
File sizeOne file, 4GB or largerBelow the cache size you measure cache, not memory
File systemexFAT vs NTFS vs FAT32Filesystem overhead changes small-file and some sequential results
Test capacityState how full the drive wasWrites slow as the drive fills and free blocks run down
Cache effectDiscard the first 20–30 secondsThe opening burst is cache, not sustained memory speed
Number of runsRun twice; average or explain the gapA large run-to-run gap signals heat or cache effects
EnvironmentAmbient temperature, hub vs direct portHeat throttles small bodies; hubs add artificial ceilings

Reading the result honestly

There is no single "correct" sustained speed, because it depends on the controller, the memory, the capacity and the host port. What you are looking for is whether the drive is in the range you were promised, and whether it degrades badly as it fills.

Two patterns are worth acting on. If the rate collapses to a small fraction of the burst figure after the cache fills, the memory is much slower than the marketing implies. If the rate falls steadily over several minutes, the drive is heating up and throttling — see the heat question for what that means.

What you observeWhat it usually means
Fast start, sharp drop after 30sCache exhausted — normal, but tells you the real rate
Rate keeps falling over minutesThermal throttling in a small body
Rate far below any advertised figureMemory grade lower than the quote implied
Transfer stalls entirely part-wayPossible capacity fraud — test capacity next

Sources

Figures quoted on this page are from the published reporting listed above. Where a number is an estimate rather than a published figure, it is described as approximate.

Frequently asked questions

Does the port matter when I test speed?

Yes, substantially. A USB 3.0 drive in a USB 2.0 port will be limited by the port, not the drive, and the ceiling is around 30–40MB/s regardless of how good the drive is. Confirm the port and the cable support the speed you are trying to measure, and avoid hubs during a test — they are a common source of artificial slowdowns.

Why do small files copy so slowly?

Because each small file is a separate operation with its own overhead, and the drive has to look up locations rather than stream data. This measures random access performance, which matters for some workloads but is not the same as the sequential write speed a datasheet quotes. Test with one large file for sequential speed, and with a folder of many small files only if that is your actual workload.

Should I test every drive in a batch, or a sample?

Test a sample of each batch for speed, because speed is a property of the design and the memory grade, which should be constant within a batch. A speed outlier in a sample is a signal to look at the whole carton. Full write-and-read-back capacity testing, by contrast, is worth doing more broadly, because capacity fraud is per-unit and silent.

Working on a specification?

Send us the product type, capacity, quantity and target date. We reply to business enquiries within 1 business day.

Request a quote
WhatsApp / WeChat Request a quote