FakeFlashTest and ValiDrive look similar at first glance because neither one fills your entire drive in the way a full verification tool does. Both spot-check. That is where the similarity ends. They sample in different places, they treat your existing data very differently, and one of them tells you something about speed that the other does not. If you understand those differences, you can pick the right spot check for the job in front of you instead of assuming that a pass in either tool means the same thing. In short, these are two spot checks with opposite trade-offs.
FakeFlashTest, by Steve Si of RMPrepUSB, is freeware for Windows, portable, and must be run as Administrator. Its latest v1.1.5 is the developer’s latest Beta. ValiDrive is by Steve Gibson of Gibson Research Corporation, is also free and Windows-based, and was built specifically to expose drives whose reported capacity is far larger than their real capacity. Both tools exist because fake drives are common: hacked controller firmware reports a small amount of real flash as a huge capacity, and anything written past the real limit wraps around and overwrites older data.
How the sampling differs
The Quick Size Test in FakeFlashTest writes 512-byte marker blocks at intervals, starting from the end of the drive. Starting at the end is a deliberate shortcut: if a drive claims a huge capacity it does not have, the far end is exactly where the lie lives, so checking there first can expose a fake without testing every block. The developer is explicit about the limit: a quick test does not thoroughly test all the memory and does not check for faults. FakeFlashTest also offers Test Empty Space, which fills free space with test files and reads them back, designed to preserve existing files, though you should still back up first.
ValiDrive spot-checks randomly chosen spots across the drive’s reported capacity. Instead of working in a fixed pattern from the end, it picks places spread over the whole reported size and checks whether data written there can be read back correctly. It also measures access speed as it goes. That speed reading matters because fake areas often behave strangely, responding suspiciously fast or suspiciously slowly compared with real flash. A drive can therefore look wrong on timing even before you think about capacity alone, and ValiDrive surfaces that clue in a way FakeFlashTest does not.
| Tool | Method | Destructive? | Thoroughness | Platform | Cost |
|---|---|---|---|---|---|
| FakeFlashTest (Quick) | Marker blocks at intervals from the end of the drive | Yes | Quick screen; not a full test | Windows | Free (freeware) |
| ValiDrive | Random spot checks across reported capacity, plus speed measurement | Normally does not destroy data on a good drive | Spot check; not 100% verification | Windows | Free |
The data-safety difference that decides most cases
For many people the deciding factor is not sampling style but what happens to files already on the drive. The Quick Size Test is destructive: do not run it on a drive containing the only copy of anything. Move everything off first, or use a different approach. ValiDrive, by contrast, normally does not destroy data on a good drive, which makes it the more comfortable first look at a drive that already holds files you care about. “Normally” and “on a good drive” are important qualifiers. No test can protect data that sits on a fake drive whose controller is already overwriting it, so back up before any test whenever you can. Our download page explains both FakeFlashTest modes so you do not pick the destructive one by accident.
Think of it as a sequence rather than a contest. If a drive is empty or newly bought, a destructive screen costs you nothing and FakeFlashTest is a natural start; follow how to test a USB flash drive for fake capacity step by step. If a drive already holds files and you want a non-destructive first signal plus a speed reading, start with ValiDrive. Whichever you start with, remember what a spot check is: evidence about the spots that were checked, not a guarantee about every block that was not. For the drives you will trust, follow up with a full test as described in FakeFlashTest vs H2testw.
What a pass and a fail really mean
A fail in either tool is serious. It means the drive did not behave like a drive with the capacity it claims, and you should stop putting important data on it, preserve the result, and read what to do next when a fake drive is confirmed. A pass is narrower: the sampled spots behaved correctly at the time of the test. It does not rule out faults elsewhere, slow or failing areas the sample missed, or a fake whose real capacity happens to cover the spots checked. Learning to read FakeFlashTest results in those terms stops the most common mistake, which is treating any pass as a clean bill of health.
Speed deserves a final word. ValiDrive’s access-speed measurement is useful context, especially when a supposed high-capacity drive responds in a way real flash should not. But speed alone never proves capacity, and a fast drive can still be fake while a slow drive can be perfectly genuine and simply old or connected through a slow reader. Use speed as a clue alongside the capacity result, never as a verdict on its own. Our roundup of the best fake USB drive test tools places both tools in the wider picture, including the full-test options.
Verdict
Pick FakeFlashTest for a fast, free, destructive screen on an empty or backed-up drive, especially when you want to check the far end of the claimed capacity first. Pick ValiDrive when you want a normally non-destructive spot check with a speed readout on a drive that already holds files. Pick neither as your final word when the data matters: follow a spot check with a full write-and-verify test. That layered approach, screen then prove, is the honest way to use both tools, and it respects what each developer actually claims for them. Start from the FakeFlashTest download if your drive is backed up and ready for the quick screen.