Low score for small-file writes? What it means

Your storage test may show a weak result for small-file writes even when large files copy quickly. That can make a drive look faulty, but the two results measure different kinds of work.

Use the Storage Test to compare the small-write result with large-file speed. This guide explains what the difference can mean, how to get a fair retest, and when to investigate the drive further.

Check the small-file write result

1. Open the Storage Test and run the test, following the prompts on screen.
2. Note the small-file write result and the large-file read and write speeds. The test also gives an overall score out of 100.
3. Run it again under the same conditions. Close downloads, file copies, backups, and other heavy tasks first.
4. Compare the repeated results. A similar low score is more useful than one result taken while the computer was busy.

Do not compare a small-file result directly with a drive's advertised maximum speed. Advertised figures usually describe large, sequential transfers, while small writes involve many separate operations.

What the result means

Small-file writes are low, but large-file speeds look normal

The drive can move a large stream of data quickly, but this test's smaller writes take longer. Small operations can involve extra work from the file system, the operating system, browser storage, and security or sync software. This difference does not prove the drive is damaged.

If normal tasks feel fine, treat the result as a sign of weaker performance for this type of workload, not as a diagnosis. It may matter more if you often create or update many small files, such as source code, email archives, or application data.

Both small writes and large-file speeds are low

The slowdown may affect the storage path more broadly. A nearly full drive, background activity, a slow connection, or a drive operating through a hub or adapter can all contribute. Retest after the checks below before deciding the drive itself is the cause.

The result changes a lot between runs

Storage activity can vary as the computer handles other work. Background updates, cloud sync, a backup, or heat can affect a short test. A browser-based result also reflects the browser and operating system, so it is not a direct measurement of every drive operation.

The score is low, but everyday use seems normal

The score out of 100 is a useful comparison within the test, not a universal drive-health grade or a promise that a device should score 100. A low score alone does not confirm failing storage. Look for real symptoms such as repeated freezes during file saves, errors copying files, or a drive disconnecting unexpectedly.

How to get a more reliable result

1. Wait for other storage work to finish. Pause large downloads, file copies, backups, and cloud sync temporarily, then repeat the test. Avoid running another benchmark at the same time.
2. Close apps you are not using. A browser with many active tabs, an editor saving large projects, or a game updating files can compete for storage. Close those tasks, but keep the test page open.
3. Check available space. On Windows 11, open Settings › System › Storage. On macOS, open System Settings › General › Storage. If the drive is nearly full, remove files you no longer need or move them elsewhere, then test again.
4. Reconnect an external drive directly. If you are testing storage connected by USB, connect it directly to the computer rather than through a hub or dock. Try another port and cable if the result stays low.
5. Restart and retest. A restart can stop a background process or stalled transfer from affecting the next run. Use the same browser and storage setup so the results are easier to compare.

Change one thing at a time where possible. If you switch the cable, move the drive, and close several apps all at once, you will not know which change mattered.

When to suspect a storage problem

Take a low score more seriously if it repeats after a restart and the drive also causes everyday problems. Warning signs include files that fail to save or open, repeated copy errors, unexplained disconnects, or a computer that pauses whenever it accesses that drive. Back up important files before trying further tests, especially if errors are appearing.

If the problem follows an external drive to another computer and another cable, the drive may need service or replacement. If only one computer shows the slowdown, check its connection, available space, and background activity before blaming the drive. A browser test can show a performance difference, but it cannot confirm the physical health of storage components.

Why small writes differ from large transfers

A large-file test mainly measures how quickly data moves in a sustained stream. Small-file writes break that work into many separate operations. Each operation can involve locating file-system records and handling other software requests, so the final speed may be much lower even on the same drive.

This is why a low small-write result does not necessarily mean your drive will copy a single large video slowly. For more on the limits of browser storage measurements, see what a browser file test can’t measure about IOPS. To understand a difference between large reads and writes, see how to interpret storage test read and write speeds.