How to interpret storage test read and write speeds

Your storage test shows one read speed and a different write speed. That difference can look alarming, especially if one number is much lower. But read and write speeds measure different work, and they do not have to match.

Use the Storage Test to compare how your drive handles large files and small writes. Then check whether the gap is expected for your setup or worth investigating.

Compare read and write speeds

1. Open the Storage Test on the computer and drive you want to check.
2. Run the test and note the read and write results. Also note whether the result refers to large files or small writes.
3. Run the test again under the same conditions. Close file transfers and apps that are actively saving or syncing data first.
4. If you are checking an external drive, keep it connected to the same port and cable for each run. Avoid moving it while the test is running.
5. Compare the repeated results with each other, rather than comparing one result directly with a drive manufacturer's peak speed.

A difference that repeats is more useful than a single unusually high or low reading. If the numbers vary a lot between runs, investigate background activity or the connection before judging the drive.

What the result means

Read speed is higher than write speed

This is common. Reading means retrieving existing data. Writing means saving new data, and the drive may need to organize or erase storage before it can save more. Some solid-state drives also use a fast write cache, a temporary area that can fill during longer writes. When it does, sustained write speed may fall.

Small writes can be slower than large-file transfers because they involve many separate operations. A mechanical hard drive may need to move its read head between locations, while a solid-state drive still has to manage its memory cells. A large gap is not, by itself, proof that the drive is failing.

Write speed is higher than read speed

This can happen in a short browser test because the operating system or drive temporarily caches data, or because the read and write parts of the test use different workloads. It can also result from background activity affecting just one part of a run. Repeat the test before drawing a conclusion.

If the write result stays higher, the drive may simply perform differently on the tested tasks. The numbers are not a promise that every real file copy will follow the same pattern.

Large-file results look good, but small writes are slow

Large-file work is mostly about moving a continuous stream of data. Small writes involve many separate changes, which are a different workload. That means a drive can transfer a large video quickly but take longer to save lots of small files or update an application.

A browser test does not provide a complete measure of small-file behavior or storage input/output operations per second (IOPS). For context, see what a browser file test can't measure about IOPS.

Both results are low or change sharply between runs

Check for a nearly full drive, active downloads, file copies, backups, or cloud syncing. An external drive may also be limited by its cable, port, hub, or enclosure. If the test slows after several runs, let the drive cool and wait for other storage activity to finish before testing again.

How to investigate a slow result

1. Retest while the computer is idle. Pause file transfers, backups, downloads, and sync jobs, then repeat the test. Other storage work can compete with the test and lower its result.
2. Check available space. A drive that is nearly full may have less room to manage new writes. On Windows 11, open Settings › System › Storage. On macOS, open System Settings › General › Storage. If space is tight, remove only files you know you no longer need, then test again.
3. Reconnect an external drive directly. Unplug it safely, then connect it to another port without a hub or extension if possible. Keep the same cable when comparing ports, so you change one factor at a time.
4. Check the power mode on a laptop. Battery-saving settings can affect device performance. In Windows 11, check Settings › System › Power & battery. On a Mac, check System Settings › Battery and turn off Low Power Mode if it is enabled for the current power condition.
5. Compare the drive on another connection or computer. If an external drive is slow only through one port or hub, the connection is a stronger suspect than the drive. Keep the test and workload as similar as possible.
6. Back up important files if the problem continues. Repeated slowdowns, disconnects, read errors, or files that become damaged deserve more attention than one low speed number. Copy important data before doing further tests or seeking repair.

When to suspect the drive itself

Consider the drive suspect if slow writes continue across repeated tests after background work has stopped, the drive is not almost full, and an external drive behaves the same on another suitable port or computer. More concerning signs include frequent disconnects, errors when opening or copying files, or data that changes unexpectedly.

A speed test cannot confirm the drive's health or identify every fault. Back up important data first. If the drive is under warranty, contact the manufacturer or seller. If it contains important files and is failing, stop repeated testing and ask a qualified repair or data-recovery service what to do next.

Why advertised speeds may not match

Drive makers often quote a peak speed for a particular workload and test setup. Your result depends on the drive model, its connection, available space, temperature, power settings, operating system activity, and the work the browser test performs. Read speed, large-file write speed, and small-write speed are not interchangeable measurements.

Use the Storage Test mainly to compare the same drive under similar conditions, such as before and after changing a port or clearing background activity. For why fast drives can still take time with small files, read why a fast SSD takes time to open small files.