Short answer: to prove the true capacity of a USB drive, fill it completely with test data, read all of that data back, and compare what comes back with what you wrote. If the drive holds and returns everything up to its claimed capacity, it has passed. If data goes missing, comes back corrupted, or overwrites earlier files once the drive passes a certain fill level, the drive is fake or defective, whatever its label and whatever the operating system reports. ChipGenius cannot do this test. It identifies the controller; a write-and-verify tool proves the storage.
Before you start, understand two things. First, the test destroys whatever is on the drive, so back up anything you need from it first, or test a brand-new drive before you put anything on it. Second, a full test of a large claimed capacity takes a long time, because every byte must be written and then read back. That time is the price of certainty, and it is far cheaper than discovering corruption after the drive holds your only copy of important files.
Before you test: prepare the drive and the evidence
Use a computer you trust, connect the drive directly to a USB port rather than through an unpowered hub if you can, and disconnect other removable drives so there is no confusion about which device is being tested. Note the drive’s label capacity, the seller and listing it came from, and the date. Run ChipGenius from the download page and save a screenshot of its report for this drive. That report will not prove capacity, but it will support a refund claim later by showing what the drive claimed to be.
Choose a write-and-verify tool that fills the drive with verifiable data and then reads it back, rather than a benchmark that only writes a small sample. The classic tool for this job is H2testw, a write-verify utility in the style this cluster refers to throughout. Whichever tool you use, the principle is the same: write unique, checkable data to every part of the claimed capacity, then verify it. A speed test, a quick format, or a check that only writes a small file proves nothing about capacity.
Step 1: Back up, then empty the drive
If the drive already holds files you need, copy them somewhere safe first, and check that the copies open correctly before you proceed. Testing will overwrite the drive. Once you have a safe copy, or if the drive is new, format it or delete its contents so the test starts from empty. An empty starting point matters, because a test that writes over existing files without clearing them can produce confusing results.
Step 2: Run the full write phase
Start the write-and-verify tool, select the drive carefully by its letter and label, and choose the option that tests all available space, not a small sample. Let the write phase run to completion without using the drive for anything else. Do not unplug the drive, do not let the computer sleep in a way that interrupts the test, and do not run other heavy storage work at the same time. If the tool reports write errors partway through, note the point at which they began. That point is often close to the drive’s true capacity, and it is itself strong evidence.
Step 3: Run the verify phase and read the result honestly
When writing finishes, the tool reads the data back and compares it with what was written. A pass means the data read back matches, across the full claimed capacity. A failure usually appears as corrupted sectors, missing data, or a report that verification failed after a certain amount of data. Record the exact wording of the result, the amount of data verified successfully before failure if the tool reports it, and a screenshot of the final result screen. Do not round the result up or describe a partial pass as a pass. If verification fails, the drive has failed, even if it worked fine when it held only a small amount of data.
Step 4: Repeat once if the result is unclear
A single unclear result, for example a test interrupted by a loose cable, a power event, or a computer crash, should be repeated from empty before you draw a conclusion. A clean, completed failure on a second run, however, is conclusive enough to act on. There is no need to run the test five times to prove the same point, and repeated testing of a failing drive will not repair it. ChipGenius is diagnostic only: it does not repair, format, or reflash a drive, and attempting to reflash a fake drive is not a fix for missing storage hardware.
| Test outcome | What it means | What to do |
|---|---|---|
| Full write and verify pass at claimed capacity | Drive holds what it claims, at least for this test | Keep the log, use the drive, still keep backups elsewhere |
| Verify fails after a certain fill level | True capacity is below the claim, earlier data may be overwritten | Stop using it, preserve evidence, start a refund claim |
| Write errors partway through | Drive cannot even accept data to its claimed size | Stop, screenshot the error, preserve evidence |
| Test interrupted by cable or power | Result is inconclusive, not a pass or a fail | Repeat once from empty on a direct port |
What not to do during or after a failed test
Do not format the failed drive and try to sell it on, describe it by its label capacity, or give it away as a working drive. That passes the problem to someone else. Do not try to partition the drive down to its apparent true size and treat it as a reliable smaller drive either, unless you understand that its firmware has already shown itself untrustworthy and you are willing to accept that risk for non-important data only. For most people, the right outcome for a fake drive is a refund or a return, not a second life as a compromised drive.
Do not delete the test log, the ChipGenius screenshot, or the listing screenshots after a failure. Those files are the evidence pack described in the companion refund guide, and rebuilding them later is often impossible once the listing changes or the drive is returned. Keep them until the claim is fully resolved.
After the test: replace, do not repair
When a drive fails, the honest branch is replacement, not repair. No software tool can add flash memory that is not physically present, and ChipGenius in particular cannot repair, format, or reflash a drive back to health. Buy the replacement from a seller you can hold accountable, and test it on arrival with the same full write-and-verify procedure before it becomes the only copy of anything. As a starting point for comparison, you can look at the Samsung BAR Plus or the SanDisk Ultra Fit listings. Whichever drive you choose, the test on arrival is what earns your trust, not the brand on the box.
Bottom line
Capacity is proven by writing and reading back, not by reading a label, a properties window, or a ChipGenius report. Back up first, test all available space from empty, record the exact result, and act on a failure by preserving evidence and seeking a refund. A drive that passes a full write-and-verify test has earned its place; a drive that fails it has not, whatever it claims to be.
Related in the Fake Drives cluster
Keep reading in this cluster: Fake 1TB and 2TB USB Drive Anatomy; VID/PID and Label Mismatch; How to Prove Fake USB Capacity, Step by Step; ChipGenius Refund Evidence Pack; and ChipGenius v4.23 Debunked and the Official Site Safety Question. Start from the download page if you still need a copy of ChipGenius for the checks described here.
Do not buy a replacement the same way: once a drive has lied about its capacity, the next purchase matters more than the refund. Read what not to buy in a USB drive first, then pick from the best USB flash drives after a fake drive and verify the new drive on arrival with the capacity test above.