What a browser file test can't measure about IOPS

A USB drive can show a good speed in a browser test and still feel slow when opening lots of small files. That is because transfer speed and IOPS describe different kinds of work. A browser-based test can help you compare read and write throughput, but its result is not a dependable IOPS measurement.

Use the USB & SD Speed Test to check how quickly a flash drive or memory card reads and writes data. Then use the limits below to understand what those numbers can, and cannot, tell you.

Check the drive's read and write speed

1. Open the USB & SD Speed Test on a computer with the drive or card connected.
2. Connect the device directly to the computer if possible. If you need a card reader or adapter, keep using the same one when comparing results.
3. Follow the instructions shown by the test to check reading and writing. Read each prompt before proceeding, and do not select a drive or file you cannot safely test.
4. Note the displayed read and write speeds and their units. Record which drive, port, card reader, and adapter you used.
5. Repeat the test under the same conditions if you want a comparison. Compare consistent results, not just the highest number from one run.

Close file copies and other tasks that are actively using the drive before testing. If the device contains important files, back them up first. A speed result is not a check that the drive is safe for long-term storage.

What the result means

A high read or write speed

The drive handled the test's data transfer quickly in those conditions. The result is usually expressed as data per second, such as MB/s. It is a throughput measure: the amount of data moved over time, not the number of separate file operations completed.

Write speed is lower than read speed

This is common. Flash storage often reads faster than it writes, and its write speed can change as the drive fills or its internal cache runs out. The card reader, USB port, adapter, file system, and other active tasks can also limit the result. A slower write number by itself does not prove the drive is faulty.

The result changes from one run to another

Small variations are normal. The operating system may have other work to do, the drive may be warm, or a previous transfer may still be affecting it. A hub or adapter can also make the connection slower or less consistent. Repeat the test with the same setup before drawing a conclusion.

You want an IOPS number

The test does not give you a standardized IOPS score. IOPS means input/output operations per second. It counts how many separate read or write requests a storage device completes, often using small blocks of data. Do not convert the displayed MB/s value into an assumed IOPS rating.

How to make a fair comparison

1. Keep the connection the same. Use the same computer port, card reader, adapter, and hub setup for each drive. A USB connector's shape does not tell you the speed of the connection behind it.
2. Stop other transfers. Pause file copies, backups, and downloads that use the same drive or connection. They can compete for time and affect the measured throughput.
3. Keep power settings consistent. On Windows 11, check Settings › System › Power & battery › Power mode. On a Mac laptop, check System Settings › Battery and keep Low Power Mode the same between runs.
4. Compare like with like. Compare read speed with read speed, and write speed with write speed. Use the same test, device capacity, and connection, and avoid comparing a nearly full drive with an empty one if you can.
5. Look for a repeated pattern. Run the check more than once and consider the typical result. One unusually fast or slow run can reflect background activity rather than a lasting difference between devices.

Why IOPS needs a different test

IOPS depends on more than how much data moves in a second. A proper comparison needs to define the size of each operation, whether requests are random or sequential, the mix of reads and writes, how many requests can be in progress at once, and how long the test runs. These details are often called the workload. Change them and the IOPS result can change substantially.

For example, a drive may transfer one large file quickly but take longer to open thousands of small files scattered across folders. The large transfer emphasizes throughput. The many small requests emphasize response time and IOPS. A browser file test that reports read and write speed is useful for the first kind of comparison, but it does not reproduce every app's small-file workload.

A browser also works through the operating system and its file system, rather than controlling the storage device directly. System caching, the file system, the controller, and the device's own firmware can all affect the result. A browser test cannot hold every part of that path constant or provide all the low-level controls needed for a standardized IOPS benchmark.

If you need IOPS for a specific app or workload, use a benchmark designed to test that workload and follow its instructions carefully. Treat its score as specific to the test settings, not as a universal rating of the drive.

When the drive may be faulty

A low speed result alone is not enough to diagnose a failing drive. But repeated disconnects, read or write errors, files that become unreadable, or a device that is no longer recognized are warning signs. Back up anything you can still access, then test the drive on another computer or reader. If the same problems follow the drive, stop relying on it and check its warranty or replace it.

The USB & SD Speed Test checks transfer speed in your browser. Files used in the test stay on your device.