The shared enemy is worth restating. Fake drives use hacked controller firmware to report a small amount of real flash as a huge capacity. Writes past the real capacity wrap and overwrite older data, usually unrecoverably. Every tool here attacks that lie differently: by sampling it, by filling the drive, by checking random spots, or by identifying the hardware. None of them repairs a fake, and none of them, H2testw included, should be run on the only copy of your data without a backup first.

The six alternatives, honestly assessed

1. FakeFlashTest is the speed alternative. By Steve Si of RMPrepUSB, freeware, portable, Windows-only, run as Administrator, latest v1.1.5 being the latest Beta. Its Quick Size Test writes 512-byte markers at intervals from the end of the drive for a fast screen, and Test Empty Space fills free space and reads it back, designed to preserve files. Limit, in the developer’s own terms: the quick test does not thoroughly test all memory. See FakeFlashTest vs H2testw for the full pairing and get the tool from our download page. 2. ValiDrive, by Steve Gibson of Gibson Research Corporation, free for Windows, spot-checks randomly chosen spots and measures access speed; fake areas often respond suspiciously fast or slow. It normally does not destroy data on a good drive. Limit: a spot check is not a 100% verification. See FakeFlashTest vs ValiDrive.

3. F3 (Fight Flash Fraud) is the cross-platform full-test alternative: open source for Linux, macOS, and Windows, with f3write filling the device and f3read verifying, plus f3probe as a quicker experimental probe. Limit: the full workflow takes full-test time, like H2testw itself. See FakeFlashTest vs F3. 4. CheckFlash (ChkFlsh), by Misha Cherkasoff, Windows freeware, runs read and write cycles and can show speed and a drive map. Limit: full cycles take time, and it is Windows-only. See FakeFlashTest vs CheckFlash. 5. Flash Drive/Card Tester is a generic Windows tool in the same full-test family, writing and reading to detect counterfeit capacity. Limit: allow full-test time and back up first. 6. RMPrepUSB Quick Size Test is the built-in parent feature FakeFlashTest grew from: destructive, with reformatting needed afterwards, inside a multipurpose tool with different licensing. See FakeFlashTest vs RMPrepUSB.

How to choose without regret

Choose by constraint, not by fashion. Short on time with an empty drive? FakeFlashTest screen first, following how to test a USB flash drive for fake capacity. Drive full of files you have not backed up? Back up, then consider ValiDrive’s gentler first look. Not on Windows? F3, via testing an SD card on a Mac or testing a USB drive on Linux. Need the strongest evidence? That is still H2testw’s home ground, or a completed F3 run; do not let any alternative talk you out of a full test when the stakes need one. Need controller identity as well? Add the identification step from FakeFlashTest vs ChipGenius, remembering it proves nothing about capacity alone.

Whichever you choose, finish the job properly: read the results in the tool’s own terms, act on a fail with what to do next when a fake drive is confirmed, and test cards the same way via the microSD testing guide. The hub of best fake USB drive test tools reorganises this same shortlist by situation if you prefer to start there. H2testw remains an excellent tool. These six simply cover the moments, platforms, and time budgets where even an excellent tool is the wrong shape for the job. Start with the FakeFlashTest download for the fastest screen, and keep H2testw itself for the proof.

A final caution about lookalike downloads

Popular test tools attract copycat download pages, so fetch any tool in this list from its developer’s own site or your system’s package repositories, and be suspicious of bundled installers and download managers wrapped around a free program. Our download page exists for exactly this reason on the FakeFlashTest side: one clear route to the current build, with the mode differences explained before you run anything. Once you have the right tool from the right place, the rest of the advice on this page applies unchanged: back up first, test on arrival while returns are still possible, keep the result with your order records, and let the job in front of you, not a headline, decide whether a screen, a spot check, or a full verification is the honest level of proof.

First, the fraud itself, because it explains every method below. A fake drive uses hacked controller firmware to report a small amount of real flash memory as a huge capacity. Your computer believes the reported size, writes happily past the real limit, and those writes wrap around and overwrite older data. Files appear in listings while their contents are already destroyed, and overwritten data is usually unrecoverable. Genuine USB flash drives currently top out at around 2 TB, so listings far beyond that, or far below a plausible price, deserve a test before they deserve your data. Testing is not paranoia; it is the only way to know.

The tools at a glance

By situation: what to run first

New drive, Windows, need a fast answer: start with FakeFlashTest’s Quick Size Test on the empty drive. It writes 512-byte markers at intervals from the end of the drive, where the lie lives, and its developer states plainly that it does not test all memory. Get it from our download page, follow how to test a USB flash drive for fake capacity, and compare the logic in FakeFlashTest vs H2testw. Drive already holds files: back up first, consider ValiDrive’s normally non-destructive spot check as a first signal, and see FakeFlashTest vs ValiDrive. Need proof for a refund or for a drive you will trust: run a full test, H2testw on Windows or F3 anywhere, and keep the output.

On a Mac or Linux: F3 is the standard answer, since FakeFlashTest has no Mac or Linux version. See FakeFlashTest vs F3, how to test an SD card on a Mac, and how to test a USB drive on Linux. Want to know what chip is inside: add ChipGenius for controller identification, understanding it proves nothing about capacity alone; FakeFlashTest vs ChipGenius explains the pairing. Already use RMPrepUSB: its built-in Quick Size Test is the parent feature of FakeFlashTest; see FakeFlashTest vs RMPrepUSB Quick Size Test. Prefer a visual full test: CheckFlash adds a drive map; see FakeFlashTest vs CheckFlash.

Cards, phones, and the online myth

microSD and SD cards fail in exactly the same way as USB sticks, and the same tools apply with a good card reader; start with how to test a microSD card for fake capacity and the platform overview in fake SD card test software for every platform. If your only device is a phone or a Chromebook, be honest about the limits: testing an SD card on Android can only go so far, a Chromebook fill test is a manual workaround covered in checking a flash drive on a Chromebook, and no website can test your drive for you, as the online fake flash test explainer sets out. The definitive test always runs on a computer with real access to the device.

After any result

Learn to read FakeFlashTest results before you act on them. A fail means stop, preserve evidence, and follow what to do next when a fake drive is confirmed. A pass on a screen means test further before trusting the drive; a pass on a full test is the strongest statement any of these tools can make. Suspicious external SSDs and hard drives follow the same logic, covered in how to test a suspicious external drive. Whatever you run, back up before destructive tests, never store the only copy of anything on an untested drive, and let the situation, not a league table, choose your tool.

Three rules that apply to every tool on this page

First, back up before any destructive or fill test, without exception. Second, test on arrival, while the return window is open and the drive is still empty, because that is when a fail is cheapest to act on. Third, keep every result until that window closes, filed with the order details it belongs to. Follow those three rules and the choice between tools becomes a matter of minutes and method. Ignore them and even the best tool cannot help you: a perfect full-test pass on a drive you tested after filling it with the only copies of your photos has protected the diagnosis, not the photos. The tools differ. The discipline does not.

Both come from the same developer, which is why their test logic feels familiar. FakeFlashTest is freeware, Windows-only, and portable, with latest v1.1.5 described as the latest Beta, and it must be run as Administrator. RMPrepUSB is the larger, multipurpose program. One licensing distinction matters and is easy to get wrong: FakeFlashTest’s executable may be freely distributed under its freeware terms, while RMPrepUSB itself has different licensing and must not be redistributed. Keep that boundary straight if you ever share either tool with someone else.

The shared test at the centre

The Quick Size Test, in either home, writes marker data at intervals across the drive to expose the classic fake: hacked controller firmware reporting a small amount of real flash as a huge capacity. Once writes pass the real capacity, they wrap around and overwrite older data, so markers that should survive do not. The test is destructive in both tools. Nothing about running it inside RMPrepUSB makes it gentler, and nothing about the standalone tool makes it harsher; the check itself is the check. In RMPrepUSB’s case, the drive needs reformatting afterwards before it goes back into normal use, so plan for that step rather than being surprised by it.

FakeFlashTest adds a second mode its parent’s quick test does not centre on: Test Empty Space. That mode fills only the free space with test files and reads them back, with interval checks along the way, and it is designed to preserve existing files, although backing up first remains the sensible rule. That second mode is the clearest sign of FakeFlashTest’s purpose: it is not a general USB workshop, it is a testing tool, and its modes are arranged around the two situations testers actually face, an empty drive they can test destructively and a partly full drive they would rather not wipe.

Which one should you actually use?

For almost everyone reading this site, the answer is FakeFlashTest. It does one job, its two modes are labelled for the situations you will meet, and you can carry it as a small portable program without installing or learning a multipurpose suite. Our download page provides the current build, and how to test a USB flash drive for fake capacity walks through the standalone workflow from first launch to final result, including running as Administrator and reading the results correctly.

RMPrepUSB’s built-in test makes sense when you already use RMPrepUSB for its other USB work and the drive is already on your bench inside that workflow. Even then, remember the scope both tools share: a quick size test is a screen, not a full verification and not a fault check across all memory. The developer says so about FakeFlashTest, and the same honesty applies to the parent feature. If a drive passes the quick test and will hold important data, graduate to a full write-and-verify test such as H2testw, as laid out in FakeFlashTest vs H2testw, before you trust it.

After the test, whichever tool you used

A fail means the same thing in both programs: the drive is not the capacity it claims, data written past the real limit has likely been overwritten and is usually unrecoverable, and the drive should not be used for anything that matters. Follow what to do next when a fake drive is confirmed rather than reformatting and hoping. A pass, equally, means the same modest thing in both: the sampled check found no lie. Treat passes as permission to test further, not as proof. Our hub of the best fake USB drive test tools and the guide for testing microSD cards show the full ladder from screen to proof.

One habit whichever version you run

Both versions reward the same discipline: test on arrival, before the drive earns a job. A quick size check is at its most valuable in the first days you own a drive, while the return window is open and the drive is still empty, when a destructive test costs you nothing and a fail costs the seller, not you. Test every bargain drive this way, even from sellers who were honest last time, because marketplace stock changes without notice. Keep the result until the return window closes, and only then promote the drive to ordinary use, still with backups for anything that matters. That arrival ritual, more than any single program, is what stops fake capacity from ever reaching your real files.

Verdict

FakeFlashTest is the tool to download for fake-capacity testing: focused, portable, free, and built for exactly this job. RMPrepUSB’s Quick Size Test is its respected parent feature, worth using if RMPrepUSB is already your workshop, with reformatting afterwards and different licensing to respect. Same developer, same core idea, different scope. For a single-purpose test with the clearest workflow, start with the FakeFlashTest download, and keep the parent tool in mind as the broader suite it was always meant to be.

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. ChipGenius is a Windows utility that reads USB device and controller information, including VID and PID, controller vendor and part, and NAND flash information where the device reports it. It writes nothing to test capacity, and that single fact defines both its safety and its limit: it cannot prove real capacity by itself, no matter how detailed its report looks.

What ChipGenius can and cannot tell you

When you plug in a suspicious drive, ChipGenius can tell you what the device claims to be at the controller level: who made the controller, which part it reports, and what flash information is exposed. That is genuinely useful. Fake drives use hacked controller firmware to report a small amount of real flash as a huge capacity, and knowing the controller identity is the identification step that comes before anyone goes looking for controller tools, often called MPTools, for that specific chip. Without the controller identity, that search has nowhere to start.

What ChipGenius cannot do is verify that the reported capacity is real. Reading information the controller reports is not the same as writing data across the claimed capacity and reading it back. A lying controller can report plausible information while still wrapping writes around past its real limit and overwriting your files. Treating a tidy ChipGenius readout as proof of capacity is one of the most common and most expensive misunderstandings in this area. Identification is not verification, and no readout screen changes that.

The workflow order that makes sense

Start with ChipGenius when the drive already holds files or when you simply want a no-write first look, because reading controller information does not put data at risk. Note the VID, PID, and controller details and keep a record of them alongside any photos of the listing and packaging. Then back everything up, and run FakeFlashTest for the capacity answer: the Quick Size Test for a fast screen, or Test Empty Space where appropriate. Our download page sets out both modes, and how to test a USB flash drive for fake capacity gives the full sequence, including the Administrator step people most often miss.

If FakeFlashTest confirms the drive is fake, the ChipGenius details become supporting evidence and context rather than the verdict itself: the verdict comes from the capacity test. Follow what to do next when a fake drive is confirmed and learn to read FakeFlashTest results so your refund claim rests on a test, not on a readout. Some technically confident users then research controller tools for their specific chip. Go into that with clear eyes: it is a separate, controller-specific topic, it is not what either tool in this comparison does, and a drive built on this fraud should never graduate to holding important data again whatever you do to it.

Why “use both” is not just a slogan

Consider the two failure modes. Test capacity without identifying the controller, and you know the drive is fake but know nothing about what is actually inside it. Identify the controller without testing capacity, and you have a parts list for a drive whose central claim, its size, remains completely unverified. Together, the two tools give you a diagnosis and a description: how big the drive really behaves, and what hardware is making those claims. That combination is also what makes your notes useful if you report the seller or warn other buyers. For the wider toolkit, see the best fake USB drive test tools and FakeFlashTest vs H2testw for the full-proof step, plus our guide for microSD cards, where the same identify-then-test logic applies.

Keeping records that actually help

Whichever tool you run first, save its output properly. Screenshot or copy the ChipGenius readout in full, including the VID, PID, and controller fields, and save the FakeFlashTest result from the same session alongside it, dated and tied to the same drive. Sellers and support agents respond far better to a capacity test result paired with a clear device identification than to either document alone, because together they show both what the drive claims inside and how it behaves when written to. Keep your order details in the same folder until the return window has fully closed. If the drive passes the capacity screen, those same records become the baseline you compare against if it ever starts behaving strangely later.

Verdict

Do not choose between FakeFlashTest and ChipGenius; sequence them. ChipGenius first for a safe, no-write identification of the controller and flash information, FakeFlashTest second, on a backed-up drive, for the capacity proof ChipGenius can never give. One names the chip, the other proves the capacity, and a buyer armed with both has everything needed to return a fake with confidence. Start with the FakeFlashTest download for the proof step, and keep the ChipGenius readout in the same folder as your test results.

FakeFlashTest, by Steve Si of RMPrepUSB, is freeware, portable, and latest v1.1.5 is the developer’s latest Beta. It must be run as Administrator. CheckFlash is Windows freeware in the full-test family, alongside tools such as H2testw and F3. Both are free. The fraud they target is identical: hacked controller firmware that reports a small amount of real NAND flash as a huge capacity, so that writes past the real limit wrap around and silently overwrite older data. Directory listings keep looking normal long after the files themselves are ruined, which is why a real test, not a file copy you eyeball, is essential.

How each test spends your time

The Quick Size Test writes 512-byte marker blocks at intervals, beginning at the end of the drive. That ordering is the whole trick: the end of a fake drive’s claimed capacity is fiction, so checking there early can expose the fraud without writing everywhere. The developer’s own limit applies in full: the quick test does not thoroughly test all the memory and does not check for faults. FakeFlashTest’s Test Empty Space mode is broader, filling free space with test files and reading them back at intervals, designed to preserve existing files, with a backup still advised before you start.

CheckFlash spends your time the other way. Read and write cycles across the drive take as long as the drive takes, and on large or slow media that can be a long session. What you get in return is coverage and a visual sense of the drive: the speed information and drive map help you see the test as a picture of the device rather than a single pass-or-fail line. That does not make its verdict magic; it makes it thorough in the same practical sense as other full tests. If the cycles uncover errors, the drive has failed a test that actually visited the areas in question, which is stronger evidence than a sampled pass and sobering evidence for a refund claim.

A sensible order to run them in

Start with FakeFlashTest on any empty or backed-up drive. If the quick screen fails, you already have your answer for shopping purposes: the drive is not what it claims to be, and there is little value in spending hours characterising exactly how bad it is unless you need fuller evidence for a dispute. Preserve the result, read how to read FakeFlashTest results, and move to what to do next when a fake drive is confirmed. If the screen passes and the drive will hold anything important, graduate to a full test, CheckFlash or H2testw on Windows, before you rely on it. Our download page and the step-by-step guide to how to test a USB flash drive for fake capacity cover the first stage in detail.

There is one exception to that order. If a drive already contains files and has not been backed up, do not start with a destructive quick test. Back the files up first if the drive will still let you, because a fake drive overwrites its own contents as it fills, and overwritten data is usually unrecoverable. Only once a copy exists elsewhere does the destructive screen become a cost-free diagnostic. The same caution applies to any write-cycle test: testing a failing drive is safe for your verdict, not for the only copy of your data.

Limits to keep in mind

Neither tool can fix a fake drive, recover overwritten files, or guarantee that a passing drive will never develop faults later. A full test is a statement about the drive as tested, on that day, through that reader. A quick screen is a narrower statement still. Confusing those scopes is how people end up storing wedding photos on a drive that only ever passed a spot check. Compare the other pairings in this series, including FakeFlashTest vs H2testw and FakeFlashTest vs ValiDrive, or start from the hub of best fake USB drive test tools if you are choosing from scratch, including for microSD cards, which fail in exactly the same way.

Verdict

Use FakeFlashTest when you want the fastest honest answer to the capacity question on Windows. Use CheckFlash when you want full read and write cycles, a speed view, and a drive map, and you can give the test the time a full surface pass needs. Used in sequence, they are complementary: a quick screen that respects its limits, followed by a full test for anything you plan to keep. That order saves hours on obvious fakes without ever pretending that a screen is a proof. Begin with the FakeFlashTest download, and promote the survivors to a full test before they earn your trust.

FakeFlashTest, by Steve Si of RMPrepUSB, is freeware, portable, and must be run as Administrator on Windows. Its latest v1.1.5 is the developer’s latest Beta. F3 works differently and is split into components: f3write fills a device with test files, and f3read verifies those files afterwards. That write-then-read pattern puts F3 in the full-test family alongside H2testw, rather than in the quick-screen family where FakeFlashTest’s Quick Size Test belongs. Both tools are free, both exist to catch the same fraud, and both are honest about what they do, which makes choosing between them refreshingly straightforward.

Method: sampled markers versus filling the device

The Quick Size Test writes 512-byte marker blocks at intervals, starting from the end of the drive. Because fake drives use hacked firmware to report a small amount of real flash as a huge capacity, the far end of the reported size is where the deception is easiest to catch, and checking there first saves a great deal of time. The cost of that speed is coverage: the developer states clearly that the quick test does not thoroughly test all the memory and does not check for faults. FakeFlashTest’s second mode, Test Empty Space, fills free space with test files and reads them back, and is designed to preserve existing files, though backing up first is still the right habit.

F3 makes no such shortcut in its main workflow. f3write writes test files until the device is full, and f3read then checks every file it wrote. If writes past the real capacity wrapped around and overwrote earlier data, verification exposes it. That is thorough, and thorough takes time, especially on large or slow media. F3 also offers f3probe, a quicker probe component described as experimental, so keep claims about it modest: it is a faster probe, not a replacement for the full write-and-read proof when you need certainty.

Choosing on Windows, Mac, and Linux

On Windows, use FakeFlashTest as triage and F3, or H2testw, as proof. Screen a new purchase in minutes of work rather than hours, and only invest in a full test for drives that pass the screen and will actually be trusted. Our download page and the tutorial on how to test a USB flash drive for fake capacity walk through that Windows workflow. On a Mac, skip straight to F3: our dedicated guide on how to test an SD card on a Mac covers the f3write and f3read flow. On Linux, the same F3 workflow applies, and how to test a USB drive on Linux explains how to pick the right device safely.

One practical point crosses all platforms: the reader and connection matter. A slow card reader makes a full test feel endless and can muddy your sense of whether the media itself is slow. Test with the best reader you have, keep the device connected for the whole run, and do not judge a drive by a test that was interrupted. If a full test fails, the conclusion is the same everywhere: stop trusting the drive, save the output, and follow what to do next when a fake drive is confirmed. Data written past real capacity is usually overwritten and usually unrecoverable, on every operating system.

What neither tool can do

Neither tool repairs a fake drive, restores overwritten files, or turns a small drive into the size printed on its packaging. Testing is diagnosis. That boundary matters because disappointed buyers often go looking for a “fix” tool next, and the honest answer is that a confirmed fake should be refunded and replaced, not rehabilitated for important data. Learn to read FakeFlashTest results for the Windows screen, and treat an F3 verification failure with exactly the same seriousness. For a wider view, compare FakeFlashTest vs H2testw and browse the best fake USB drive test tools by situation.

A note on readers, cables, and fair tests

Whichever side of this comparison you land on, give the test a fair setup. A worn card reader, a loose adapter, or a hub that drops the connection mid-run can interrupt a full F3 verification or cut a FakeFlashTest screen short, and an interrupted test proves nothing in either direction. Retest through a known-good reader before you argue with a seller about a result. Keep the result output, the order confirmation, and a note of which reader and computer you used together in one folder. That small bundle is what turns a frustrating discovery into a straightforward refund conversation, and it costs you nothing but a minute of tidiness at the moment you are most tempted to just throw the drive in a drawer.

Verdict

If you are on Windows and the drive is empty or backed up, start with FakeFlashTest for speed, then prove keepers with a full test. If you are on macOS or Linux, F3 is your standard tool, full stop. If you move between systems, learn F3 once and you have a method that travels with you, while keeping FakeFlashTest as the fastest first look on any Windows machine you use. Platform first, thoroughness second, and never mistake a quick screen, on any system, for a full verification. Get the Windows tool from the FakeFlashTest download and the platform guides linked above for every other case.

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.

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.

FakeFlashTest, by Steve Si of RMPrepUSB, is a freeware, portable, Windows-only tool. Its latest release, v1.1.5, is described by the developer as the latest Beta, and it must be run as Administrator or it will not list your drives. H2testw is also a Windows tool, originally written in German with an interface that can be switched to English, and it has been the long-standing reference test for fake capacity for many years. Both are free. Neither can repair a fake drive. What separates them is method, thoroughness, and time.

How each tool actually tests

The Quick Size Test in FakeFlashTest writes small 512-byte marker blocks at intervals across the drive, starting from the end of the drive and working back. That design is deliberate. A fake drive lies about its size: hacked controller firmware reports a small amount of real flash memory as a huge capacity. Writes that go past the real capacity wrap around and overwrite older data. By checking the far end first, a quick screen can often expose that lie without writing to every single sector. The trade-off is stated plainly by the developer himself: the quick test does not thoroughly test all the memory, and it does not check for faults across the whole device. It is a screen, not a certificate.

H2testw takes the opposite approach. It fills the whole available space with test files, then reads every file back and verifies it. If any part of the reported capacity is fake, the verification step will eventually meet data that was overwritten or never really stored, and the test fails. That is why H2testw is treated as the thorough reference: nothing is sampled and nothing is skipped. The cost is time. On large or slow media the write and verify cycle can take hours, and you need to plan for that rather than interrupt it halfway and wonder what the partial result meant.

When FakeFlashTest is the right first step

Use FakeFlashTest first when you have just received a drive, you have several drives to triage, or you need a fast reason to start a return before a deadline closes. Its other mode, Test Empty Space, fills only the free space with test files and reads them back, with interval checks as it goes. That mode is designed to preserve existing files, although you should back up first anyway, because a file that already sits in a bad area can still be damaged. For a step-by-step walk-through, see our guides on how to test a USB flash drive for fake capacity and how to test a microSD card for fake capacity. You can get both tools’ context and the current FakeFlashTest build from our download page.

Speed here should be understood honestly. A quick screen is quick compared with filling an entire drive, not instant in every case. A small, fast, genuinely fake drive can fail very quickly because the end of the drive is checked early. A large drive, a slow card reader, or a drive that is mostly genuine will take longer. Do not treat any single timing you read online as a promise for your hardware. What you are buying with the quick test is triage: an early, credible signal that lets you decide what to do next.

When you still need H2testw

Run H2testw when you need certainty: when FakeFlashTest passes but the price or listing still looks suspicious, when you are gathering evidence for a dispute, when a seller asks for proof, or before you trust a drive with photos, work files, or a backup you cannot recreate. A pass on a sampled test can never prove that every block is good, and the developer of FakeFlashTest does not claim otherwise. That honesty is a strength. The honest workflow is fast screen first, full proof when it matters: screen everything with FakeFlashTest, then fully verify the drives you will actually keep and rely on.

There is also a middle situation worth naming. If H2testw reports errors, do not re-run tests hoping for a different answer, and do not keep using the drive for anything important. Data that was written past the real capacity has usually been overwritten, and overwritten data is usually unrecoverable. Follow what to do next when a fake drive is confirmed and learn to read FakeFlashTest results correctly before you file anything. If you are comparing other pairings, our FakeFlashTest vs F3 comparison and the hub of the best fake USB drive test tools show where each tool fits.

Verdict

Choose FakeFlashTest when you need a fast, destructive screen on Windows and you understand its limits. Choose H2testw when you need a thorough write-and-verify result and you can give it the hours it may need. Used in that order, the two tools do not compete; they complete each other. Screen first, prove second, and never store the only copy of anything on a drive that has only passed a spot check. That single habit will protect you from most fake-capacity losses, whichever tool you start with. Get started via the FakeFlashTest download and keep H2testw in reserve for the drives that pass the screen and earn a place in your kit.