A Chromebook is a perfectly good everyday computer with one hard limit for this job: it cannot run Windows tools. FakeFlashTest, H2testw, ValiDrive, and CheckFlash are Windows programs, F3 belongs on Mac, Linux, or Windows, and ChromeOS runs none of them the way this guide’s readers need. That does not leave you helpless. ChromeOS’s Files app can fill a drive manually, and a careful manual fill test can expose an obvious fake. Just keep its scope clear from the start: a Chromebook can fill a drive, not run the tools, and a fill test you supervise by hand is a workaround, not a laboratory verdict.
Why filling works at all comes back to how fakes fail. A fake drive’s hacked firmware reports a small amount of real flash as a huge capacity. Writes that go past the real capacity wrap around and overwrite older data. If you fill a drive with files you can check, then verify the earliest files still open correctly after the drive is full, you are testing that wrap-around behaviour with nothing but a file manager. It is slower and clumsier than a dedicated tool, and it depends entirely on your verification step, but the underlying logic is the same logic every real test uses.
The manual fill test, step by step
First, back up anything on the test drive, because you are about to fill it, and use a drive you can afford to wipe for the test. Second, gather filler you can verify: a set of large files whose contents you know, ideally files you also keep copies of on the Chromebook or in cloud storage, so you can compare afterwards. Copy files onto the drive in batches with the Files app, noting the order, until the drive reports full or refuses more data far earlier than its claimed size suggests. Third, and most importantly, verify: open and check the earliest files you copied, not just the latest ones. If early files are corrupt, unreadable, or have changed, the drive overwrote them, which is the fake signature. Our download page shows the dedicated Windows workflow this manual method imitates.
Expect this to be slow and hands-on. You are doing, by eye and by batch, what H2testw or F3 does automatically and exhaustively, including the bookkeeping. Keep the Chromebook awake and plugged in, do not remove the drive mid-copy, and write down what you copied in which order, because your notes are the only test report this method produces. If the drive errors out, ejects itself, or claims to be full at a fraction of its advertised size, stop and treat that as evidence, not as a glitch to retry away. Test cards the same way in a reader where your Chromebook supports one, following the spirit of how to test a microSD card for fake capacity.
The limits you must respect
A manual fill test can miss things a real tool would catch, and it can only test as much as you actually filled and verified. If you fill half the claimed capacity and check two files, you have tested half a claim with a sample of two. The method also gives you no controller information, no structured log to attach to a refund claim, and no protection against your own bookkeeping mistakes. Treat a pass as “no obvious fake found by a manual fill” rather than proof, and treat the whole exercise as triage. Related limits apply elsewhere too: testing on Android is likewise a suspicion-raiser, and no website can run this test for you from a browser tab, on a Chromebook or anywhere else.
When you need a real PC
Borrow a Windows, Mac, or Linux computer whenever the stakes are real: before the drive holds photos or work you cannot replace, when you need solid evidence for a refund, when the manual test gives a borderline or confusing result, or when the drive is large enough that filling it by hand is impractical. One session is enough. On Windows, run FakeFlashTest for a screen or H2testw for proof, via how to test a USB flash drive for fake capacity and FakeFlashTest vs H2testw. On Mac or Linux, run F3 via the Mac F3 guide or the Linux F3 guide. If the borrowed-PC test confirms a fake, follow what to do next when a fake drive is confirmed. The full map is in fake SD card test software for every platform and the best fake USB drive test tools. Use your Chromebook’s fill test to catch the obvious fakes today, and a real PC to settle the question for good.
Making your manual result count as evidence
If your fill test exposes a fake, turn your notes into a usable record before you contact the seller. Photograph or screenshot the drive’s claimed capacity in the Files app, list the files you copied in order with their sizes, note which early files failed verification and how, and keep the order confirmation with those notes. That bundle will not have a dedicated tool’s tidy log format, but it tells the same story in plain terms: the drive accepted data up to a point, then destroyed data it had accepted earlier. Present it calmly and promptly, while the return window is open. Then still borrow a computer for the replacement drive’s arrival test, so the next drive starts its life with a proper verdict rather than another workaround.