Why a storage test cannot guarantee file integrity

A storage test can report fast reads and writes while an important file is still damaged, incomplete, or missing. That is because speed and file integrity are different questions: one measures how quickly data moves, while the other checks whether the bytes you expect are actually there.

The Storage Test measures disk speed for large files and small writes. Use it to check performance, then verify important files separately before you delete the originals or trust a backup.

Run a storage speed test

1. Open the Storage Test in the browser on the device and drive you want to check.
2. Run the test and let it finish. Avoid copying large files or running another heavy task at the same time.
3. Note the read and write results. These show how the storage performs for the test workload, not whether your own documents or photos are intact.
4. If you are comparing drives, use the same computer, browser, connection, and test conditions for each one. Repeat a surprising result before drawing a conclusion.

What the result means

The speed result looks normal

The drive handled the test workload at the measured speed. This does not prove that every file is correct, that all parts of the drive work reliably, or that older data was saved without changes. A brief test samples performance, not every file and every storage location.

The speed result is low or inconsistent

The drive, cable, port, adapter, computer, or background activity may be limiting performance. A slow result is not by itself evidence of corrupted files. Repeat the test under quieter conditions and try another port or cable before blaming the drive.

The test completes, but a file will not open

That is a separate problem from speed. The file may be incomplete, damaged, in an unsupported format, or dependent on an app that is unavailable. A performance score cannot tell which explanation is correct. Keep another copy of the file while you investigate.

How to verify the files themselves

For a copy or backup, compare the copied file with a trusted original. Matching file sizes are a useful first check, but they are not proof: two different files can have the same size. A checksum gives you a stronger byte-for-byte comparison.

1. Keep the source copy. Do not erase or reformat the original drive until you have checked the destination. If there is no separate original, make another backup before testing anything that writes to the drive.
2. Compare the file sizes. Check the original and copied files in your file manager. A different size means the copies are not complete matches. Equal sizes are reassuring, but do not prove that the contents match.
3. Calculate a SHA-256 checksum for each copy. On Windows, open PowerShell and run Get-FileHash "C:\path\to\file.zip" -Algorithm SHA256. On macOS, open Terminal and run shasum -a 256 "/path/to/file.zip". Replace the example path with the location of the file.
4. Compare the checksum values. Run the command for the original and the copy. If the SHA-256 values match, the files have the same contents for practical file-transfer checks. If they differ, do not treat the copy as verified. Copy it again using a different cable or port, then compare once more.
5. Use an application's verification option when available. Backup and archive programs may offer a verify or test function after saving. This checks the archive or backup against its recorded data, which is more directly relevant than a speed score.

A matching checksum shows that two files contain the same bytes. It does not prove that the original file was already good, or that it contains the content you intended. For example, a corrupted source and an identical corrupted copy will still have matching checksums. For archives or media, also use the program that created the file to test or open it.

When to suspect a drive problem

One slow test is not enough to condemn a drive. Look for repeated errors across different files or transfers, files that disappear or change after copying, repeated read failures, or a drive that disconnects when you move its cable. Back up anything you can still read before further testing.

Test removable media carefully. A full-capacity check writes data across the drive, so it can erase existing files and should not be used as a casual integrity check. If the drive repeatedly fails read-back verification with a known-good cable and port, replace it or contact the seller while it is under warranty. For a USB or SD capacity check, see USB drive read-back integrity test for backups.

Why a browser speed test has limits

A browser runs through the operating system and its storage interfaces. It does not inspect every sector like a dedicated drive diagnostic, certify the condition of the hardware, or audit all of your saved files. Other activity, caching, and the connection between a removable drive and the computer can also affect a speed result.

Use the Storage Test to answer, “How fast did this storage handle the test?” Use a checksum or a backup program's verification option to answer, “Does this copy match the source?” Keep at least one separate copy of important files until that check succeeds.