Sometimes you cannot — or would rather not — install or run a testing tool. The manual fill test needs no download at all: you fill the drive with files you already have, then check whether those files survive. It is slower and less precise than a dedicated tool, and this guide is honest about both points, but it rests on exactly the same principle that makes FakeFlashTest work: a fake drive cannot store more than its real capacity, no matter what it reports.
If you can run a tool, do — it is faster and gives you a log you can use as evidence. Our main guide on how to test a USB flash drive for fake capacity covers the tool route, with the software itself on the download page. Use this manual method when a tool is genuinely not an option, or as a first sanity check while a download is still in progress.
The principle: fill past the lie, then verify
A fake drive’s controller reports a large capacity while hiding a small chip. Writes within the real capacity succeed genuinely. Writes beyond it wrap around and silently overwrite earlier data, while the folder listing continues to look normal. So a manual test must do two things, not one: fill the drive well beyond any plausible real capacity for a suspicious bargain — ideally toward its full claimed size — and then verify the earliest files, because those are the ones wrap-around destroys first.
Simply copying files until Windows says the drive is full, and seeing no error, proves nothing. The copying can report success throughout, because the controller accepts the writes and discards or overwrites quietly. Verification — opening, playing, or hashing the files afterwards — is the actual test. Skipping it is the mistake that lets fakes pass casual checks in shops and in early use.
Method 1: Fill with large known files
Choose source files that are large, known-good, and easy to verify: video files you can play, large photo collections, or disc images whose behaviour you know. Keep them on your computer as the reference copies — never move the originals, always copy. Fill the suspect drive in batches, noting roughly how much genuine data you have written at each stage, and note which files went on first.
When the drive is as full as you can reasonably make it, safely eject it, reconnect it (a fresh connection prevents cached views from misleading you), and then verify starting with the earliest files you copied. Play the first videos from the start and from near the end. Open the first photos at full size. If the earliest files are corrupt while the most recent ones play, you are looking at the wrap-around signature. If you have files with known checksums, or you recorded hashes before copying, compare the hashes of the copies on the drive against the originals — a mismatch is unambiguous, and hashing is the most rigorous manual check available. Even a sample of the earliest files, fully verified, tells you more than a folder listing ever will.
Method 2: The developer’s folder approach
The FakeFlashTest developer describes a simple manual variant based on folders of known content — organising the fill into clearly labelled folders (the idea appears in his material as TESTDIR folders of photos). The structure is the value: fill the drive folder by folder, each containing photos or files you can identify at a glance, in a known order. Afterwards, open the earliest folders and check the contents display correctly.
Ordered folders make the failure point visible. If the first several folders are corrupt but the last ones are fine, you have not only detected the fake — you have estimated its real capacity, from the amount of data that survived intact. Label folders by cumulative size as you go and that estimate becomes reasonably concrete, which is useful information for a refund conversation even without a tool log.
The honest limits of the manual method
First, it is slow. Filling a drive that claims a very large capacity with real files, at real USB speeds, can take a very long time — far longer than a sampling test, which is precisely why tools like FakeFlashTest exist. Its Quick Size Test, explained in our Quick Size Test guide, checks marker blocks at intervals across the whole claimed capacity instead of occupying all of it, reaching a verdict without a full fill.
Second, it is imprecise unless you hash. “The videos seemed to play” can miss corruption near the ends of files or in files you spot-checked too briefly. Third, a manual fill gives you no standardised log to attach to a marketplace dispute; screenshots of failed files help, but a tool’s result window stating real versus claimed capacity is cleaner evidence. Fourth, like any fill, it stresses a fake’s controller for a sustained period — acceptable on a new suspect drive you may return, another reason to do it before loading anything precious.
When manual is enough — and when it is not
A manual fill test is enough to answer a personal, low-stakes question: “is this bargain drive obviously fake?” If the earliest files corrupt, you have your answer, and you should stop writing, treat the drive as a fake, and pursue the refund route with whatever screenshots you can capture. If everything verifies after a genuinely full fill and thorough checking of the earliest data, the drive has survived a stronger test than most fakes can pass.
For high-capacity drives, for evidence you intend to submit, or whenever time matters, use the real tool instead — that is the recommendation, not a footnote. Download FakeFlashTest from the download page, run it as administrator, and let the marker blocks interrogate the whole claimed capacity in a fraction of the time a fill would take. The manual method’s real value is that it works anywhere, with nothing: a borrowed computer, no download, just files, patience, and the discipline to verify the first files, not the last.