Why a read-back test can uncover silent storage errors

A USB drive can appear to save a file normally, yet the file may be damaged when you open it later. An SD card can also claim more space than it can reliably store. These problems may not show an error while you are copying files.

A read-back test checks whether data written to storage can be read back correctly. The Fake USB & SD Check writes test data to a USB drive or SD card and reads it back, helping reveal unreliable storage and drives that report more capacity than they really have.

Run a read-back test

1. Open the Fake USB & SD Check on a computer in Chrome or Edge. Other browsers may offer a reduced version or no access to the drive.
2. Use a blank drive if possible, or copy important files somewhere else first. The check fills storage with test data, so do not run it on the only copy of files you need.
3. Connect the USB drive or SD card, then follow the browser's prompts to give the tool access to the removable storage you want to test. Check the selected device carefully before proceeding.
4. Start the check and let it complete its write and read-back work. Do not unplug the drive or close the browser while the test is running.
5. Review the reported capacity and whether the written data could be read back consistently. Eject the drive using your computer's normal eject option before disconnecting it.

If you are checking a drive for fake capacity specifically, see how to check a USB drive's real size. A read-back mismatch can be a sign of that problem, but it can also point to a failing drive, card, or reader.

What the result means

The data reads back consistently

The storage passed this run: the test data it wrote could be read back as expected. That is useful evidence that the drive and reader worked during the check. It does not guarantee that every file will remain safe indefinitely, or that the drive will never fail later. Keep another copy of important files.

The test finds data that does not match

Some data came back differently from what was written, or could not be read reliably. This is a real warning, even if normal file copying appeared to work. Possible causes include worn or defective storage, a poor connection, a faulty card reader, or a drive whose reported capacity is not genuine. The test points to a problem, but cannot identify the exact cause by itself.

The usable capacity is lower than the label claims

A drive may report a large capacity to the computer but fail when data is written beyond its actual storage limit. On some fake-capacity drives, new data can overwrite older data without an obvious warning. Do not rely on the advertised size for important files. A capacity result is not the same thing as a complete health check.

The test stops or cannot access the drive

This does not prove that the storage itself is bad. The browser may not have access, the drive may have disconnected, or the reader or adapter may be the weak link. Reconnect it and check access before drawing a conclusion. If the same issue happens with another port or reader, treat the storage as suspect.

What to do after a failed read-back

1. Stop saving new files to it. Repeated writes can make it harder to recover data if the drive is failing or has less capacity than it claims. If you can still read important files, copy them to a different, trusted drive first.
2. Check the connection. Remove and reconnect the drive, seat the SD card fully, and try a direct USB port instead of a hub. A loose connector or unreliable adapter can interrupt writes and reads.
3. Try another reader or port. If the same drive fails through one reader but works through another, replace or avoid the reader. To narrow down the cause, you can also test the storage on another computer using Chrome or Edge.
4. Check the file system after making a backup. On Windows 11, open File Explorer, right-click the drive under This PC, choose Properties › Tools › Check, and follow the prompts. On macOS, open Disk Utility, choose View › Show All Devices, select the volume, then choose First Aid. These checks can address file system problems, but they cannot repair damaged flash memory.
5. Reformat only after copying what you need. Formatting erases the drive's file system and may remove access to its contents. It can fix some file system problems, but it cannot make a failing or fake-capacity drive trustworthy.

When the drive needs replacement

If read-back errors continue after you have tried a different port or reader, stop using the drive for anything important. A drive that reports less usable capacity than expected, repeatedly corrupts test data, disconnects during writing, or becomes unreadable should be returned under warranty or replaced. For an SD card, replace the card before trusting it with photos or recordings. For a USB drive, replacement is usually safer than trying to repair the storage chips.

Why reading the data back matters

A successful write is not proof that the data reached the intended storage correctly. A computer can finish a copy operation while a device, connection, or storage area has failed to preserve some of the data. Reading the data back and comparing it with what was written exposes errors that a simple copy progress bar may not show.

The check is still a snapshot, not a guarantee about future use. It tests the selected storage during that run, and results can be affected by a card reader, adapter, or connection. Keep backups even when a drive passes, and do not use a failed drive as the only home for valuable files.