USB drive test for fake capacity and real speed
A free browser-based tool to test USB flash drives for fake capacity. Many cheap drives sold online are counterfeits — a "128 GB" drive might only have 8 GB of real storage with firmware that lies about the size. This tool writes unique verification patterns across the free space, checks earlier blocks while writing, and measures the exact real capacity of a fake — no software to install.
How to Test a USB Drive
Insert the USB flash drive into your computer and make sure it appears in your file explorer.
Choose the USB drive folder from the browser directory picker. Chrome or Edge 86+ required.
The tool writes 1 MB blocks up to the drive's capacity while spot-checking earlier blocks in the background.
If the controller lies about capacity, the test halts immediately and measures the real capacity.
When no tampering is found, every block is read back and compared. Final verdict with speed stats.
Verify USB drive capacity and expose counterfeit flash drives in your browser
Browser Not Supported
This tool requires the File System Access API, which is only available in desktop Chrome and Edge browsers.
Click the button below and choose the root folder of your USB drive (selecting the whole drive gives the most accurate capacity report).
Ready to start. The test fills the free space with verification data, then reads it back to verify every byte.
How the check works and what each verdict means
The test writes known data into the drive’s free space and reads it back. A drive that lies about its size gives itself away here: the extra gigabytes come back as something other than what was written.
| Verdict | What it means |
|---|---|
| GENUINE | Everything written came back byte for byte. The declared capacity is real. |
| FAKE DRIVE | Part of the data came back wrong: the controller reports more memory than the chip has, so anything past the real limit is lost silently. The report shows the capacity actually found. |
| DEGRADED | The size is real, but some blocks failed to read back correctly — the memory is wearing out. Files stored there can be damaged. |
How it is done
- Data is written in 1 MB blocks, each carrying a marker and a checksum, grouped into 1 GB files — so a mismatch is spotted at the block that failed, not at the end.
- Only free space is used; existing files are not touched, and the test files are removed afterwards.
- Direct drive access needs the File System Access API — that means desktop Chrome or Edge. Firefox, Safari and phones cannot grant it.