Why tiny writes are slow on cheap flash storage

A cheap flash drive may copy one large video at a reasonable speed, then crawl when you move folders full of documents or photos. That difference does not necessarily mean the drive is failing. Large files and tiny writes put different demands on flash storage.

The Storage Test compares large-file speed with small-write performance on the storage your browser can access. For a removable USB drive or memory card, the USB & SD Speed Test measures that device directly. The results can help you find a bottleneck, but they are not identical to copying a folder of real files.

Compare large-file and small-write performance

1. Open the Storage Test on the computer you want to check, then run its large-file and small-write measurements.
2. Note both results. Keep other storage-heavy tasks, such as file copying or cloud sync, paused while the test runs.
3. If you are checking a USB drive or memory card, connect it directly to the computer and use the USB & SD Speed Test to measure that removable storage.
4. Repeat the measurements once under the same conditions. A large change between runs may point to caching, heat, background activity, or a connection issue rather than a stable drive speed.

A browser storage test may measure the storage available to the browser instead of a particular external drive. Check which device the test is using before treating its result as a score for your USB stick. Browser-based measurements also have limits, as explained in what a browser file test cannot measure about IOPS.

What the result means

Large-file speed is much higher than small-write speed

This is common. A large sequential write lets the controller move data in a steady stream. Tiny writes create many separate operations, each with its own processing and bookkeeping. The gap can be especially noticeable on low-cost flash drives with simple controllers and limited ability to handle many requests at once.

Copying a folder with thousands of small files can also take longer than copying one large file of the same total size. The computer has to create each file and update directory and file-system information. That extra work is one reason small-file copying and a benchmark's small-write result are related, but not exactly the same. See why copying small files takes longer than big ones.

Small-write speed is low on a removable drive

The drive, its reader, the port, or the connection may be limiting performance. A USB speed result helps narrow this down, but a single score does not identify the exact cause. Compare the same drive in another direct port or reader if you can.

The result improves after a pause, then drops again

Some flash storage uses a fast temporary writing area, often called a cache. A short burst can fit in that area. Once it fills, the controller has to write data to the slower underlying flash and may need to reorganize existing data first. A drive can therefore start quickly and slow down during a longer transfer.

Results vary widely between runs

Background tasks, available free space, temperature, browser activity, and the connection can all affect a result. A browser test cannot reveal the exact flash chips or controller inside a drive, and its small-write measurement is not a direct measurement of every real-world workload.

How to narrow down the cause

1. Test the same device twice. Use the same computer, port, reader, and browser. Pause file copies and cloud sync, then compare repeated results instead of relying on one run.
2. Connect the drive directly. Remove hubs, docks, and extension cables for a comparison. If speed improves, reconnect one item at a time to find which part of the path is slowing transfers.
3. Check free space. Leave room on the drive and retest. A nearly full device may have less room to organize writes efficiently, and a controller may need to move existing data before it can reuse storage.
4. Let the device cool between long runs. Repeated tests can heat a small drive or reader. Stop if the device feels unusually hot, wait a few minutes, and compare again rather than running benchmarks continuously.
5. Compare on external power. If you are using a laptop, connect its charger and repeat the test. On Windows 11, check Settings › System › Power & battery › Power mode. On a Mac laptop, check System Settings › Battery and make sure Low Power Mode is not affecting the comparison.
6. Try another port or reader. If the removable drive stays slow in one setup but not another, the original port, adapter, or reader may be the bottleneck. If it is slow everywhere, the drive itself is more likely to be the limit.

Why tiny writes cost more

Flash memory does not update data in the same way a notebook updates a line on a page. The storage controller writes data in pages, but it often has to erase a larger block before it can reuse space. If a small change lands in a block that already contains other data, the controller may need to copy the still-needed data elsewhere, erase the block, and then write the new data.

This extra work is called write amplification: the flash may have to do more physical writing than the amount of new data you asked it to store. A more capable controller can combine small requests and manage this work more efficiently. Low-cost products may have less controller capacity, fewer ways to work on data in parallel, or a smaller fast cache. Those design choices can keep the price down, but make tiny writes and sustained transfers slower.

If the same removable drive remains unusually slow across different computers, readers, and ports, it may simply be built for occasional file storage rather than frequent small writes. Keep a backup of important files and replace it if it cannot keep up with the job you need it to do.