Keep the goal in view while you choose. A quick screen tells you fast whether a card is obviously fake. A full test writes across the claimed capacity and verifies everything, which is the only proof that stands up for a refund or for trusting a card with a camera’s day of photos. Screens sample; full tests fill. Identification tools describe the controller without proving capacity. Every row in the matrix should be read in those terms, and any card that will hold something irreplaceable deserves a full test on whichever platform you have, through the best reader you own.

The platform matrix

Windows and Mac: the two complete toolkits

On Windows you have the full ladder. Start a new card with FakeFlashTest, freeware by Steve Si, portable, run as Administrator, latest v1.1.5 being the latest Beta, from our download page, following how to test a microSD card for fake capacity. Promote survivors to H2testw for proof, use ValiDrive for a normally non-destructive spot check with a speed view, and add ChipGenius only for controller identification, never as capacity proof. The comparisons FakeFlashTest vs H2testw, FakeFlashTest vs ValiDrive, and FakeFlashTest vs ChipGenius sort the ladder rung by rung, and reading FakeFlashTest results correctly is what turns a screen into a decision.

On a Mac, F3 is the whole toolkit and it is enough: install it with Homebrew, fill the card with f3write, verify with f3read, and you hold a full proof, as walked through in how to test an SD card on a Mac. Linux uses the identical F3 workflow, with f3probe as a quicker experimental probe for a first signal, per how to test a USB drive on Linux and the method comparison in FakeFlashTest vs F3. On both systems, identify the correct device twice before filling anything, use a dependable reader such as those via card reader options or the SanDisk route at the SanDisk store for genuine replacements, and keep a backup habit with a service such as pCloud for the files that matter most.

Phones, Chromebooks, and the online myth

Android’s row in the matrix is deliberately sobering. An app can display the capacity the card reports, which is precisely the number the firmware fakes, and can benchmark speed, which is a clue and never a proof. There is no built-in equivalent full capacity test, so the definitive test happens on a computer, as testing an SD card on Android explains without inventing capabilities phones do not have. ChromeOS cannot run the Windows tools either; its Files app manual fill test in checking a flash drive on a Chromebook catches obvious fakes, with a borrowed PC as the settlement step. And the online row is empty for a principled reason set out in the online fake flash test explainer: no web page can test your card.

Whichever platform tested your card, the ending is the same. A full-test pass earns trust, with normal backups. Any fail means stop, preserve the output, and follow what to do next when a fake drive is confirmed, applying the same steps to suspicious bulk drives in the fake SSD guide. The wider hub at best fake USB drive test tools and the alternatives list in H2testw alternatives complete the picture. Find your platform in the matrix, run its real tool to the finish, and never let a card’s claimed capacity, on any screen, stand in for a test.

One arrival routine for every platform

Whichever row of the matrix is yours, the routine on arrival is identical. Unbox the card, put it in your best reader, back up nothing because it is still empty, and run your platform’s real test to completion before the card takes its first real job. Keep the result with the receipt until the return window closes. Cards that pass fully can be labelled with their tested date and trusted with normal backups. Cards that fail go back, with the test output attached to the claim. That single habit, applied on any platform, removes almost all of the risk that fake capacity ever reaches your photos, your work, or your backups.

Calibrate your suspicion with one market fact: genuine USB flash drives top out at around 2 TB today, and portable SSDs live in that same plausible neighbourhood. A listing advertising an external SSD of, say, 256 TB is not a breakthrough and not a bargain; at consumer level today it is physically impossible, and it should be treated as a fake until a full test proves otherwise, which it will not. The same scepticism applies at smaller claimed sizes when the price is a fraction of what genuine drives of that capacity cost everywhere else. Price and capacity together are your first test, and these listings fail it before any software runs.

What is actually inside, and why your files die quietly

Open-up reports of these products follow a pattern: a large, sometimes weighted enclosure containing a small memory card or basic board, occasionally with extra tricks to make the device feel substantial in the hand. None of that theatre changes the storage maths. The real capacity is the small card’s capacity. Everything your system writes beyond it is written over earlier data, while directory entries keep listing files as if nothing happened. That is why victims discover the fraud late, when they finally open an older file and find it corrupt, by which point the overwritten originals are usually unrecoverable. Back up anything you have already put on a suspicious drive, if it will still read, before you test it, and put nothing new of value on it at all.

Do not let an operating system’s calm display reassure you. Every system reports the capacity the firmware claims, formats the drive to that claimed size without complaint, and copies files without warning until the wrap-around has already done its damage. Properties dialogs, format success, and a few successful small copies are not tests. Only writing across the claimed capacity and verifying, or spot-checking intelligently across it, counts as evidence, which is why the workflow below uses the same tools as our flash-drive guides, starting from our download page.

How to test a suspicious external drive on Windows

On Windows, begin with ValiDrive, by Steve Gibson of Gibson Research Corporation, which spot-checks randomly chosen spots across the drive’s reported capacity and also measures access speed. For an enormous claimed capacity, random spot checks are an efficient first strike: spots addressed far beyond any plausible real capacity either fail or behave suspiciously, and fake areas often respond at speeds real storage should not. ValiDrive normally does not destroy data on a good drive, but back up first regardless, because a fake drive is not a good drive and its controller is already your data’s enemy. Read the pairing in FakeFlashTest vs ValiDrive for how spot checks and screens differ.

When you need full proof, for a refund claim or for your own certainty, run H2testw’s write-and-verify across the available space, understanding it can take a very long time on a drive claiming a huge capacity, and that a fake will typically fail long before the claimed end is reached because verification meets overwritten data early in relative terms. FakeFlashTest’s Quick Size Test also has a role on an empty or backed-up unit as a fast screen from the end of the reported capacity, per how to test a USB flash drive for fake capacity; just respect its stated limit that a quick screen does not test all memory, as FakeFlashTest vs H2testw explains, and learn to read the results before you quote them to a seller.

Stop, preserve, and refund

The moment a test fails, stop testing and stop using the drive. Preserve the test output, screenshots, listing, and order details together, and follow how to get a refund for a fake USB drive, whose evidence and dispute steps apply to these SSD-costume fakes in the same way, together with what to do next when a fake drive is confirmed. Do not reformat and keep the drive “at its real size” for anything important; the hardware was sold to deceive you and its small real storage is the least trustworthy storage you own. Replace it from a reputable seller, test the replacement on arrival using the best fake USB drive test tools hub or the platform software overview, and remember the listing test for next time: if the capacity is impossible, the deal is the product, and you are what is being sold.

Buying the replacement without repeating the lesson

When you replace a confirmed fake, change the buying pattern that produced it, not just the product. Buy from the manufacturer’s own store or a well-known retailer, be wary of marketplace listings whose price undercuts every reputable seller by a wide margin, and treat any capacity claim beyond what mainstream brands currently sell as disqualifying on its own. On arrival, test the new drive before moving your files onto it, keep the result until the return window closes, and only then let it become part of your backup routine. A genuine drive bought at a genuine price and verified once is cheaper, in every currency that matters, than a miraculous bargain verified too late.

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.

A real capacity test has a non-negotiable shape. Software must write known data across the drive’s entire reported capacity, then read all of it back and verify it. Only that process exposes the fake-drive fraud, in which hacked controller firmware reports a small amount of real flash as a huge capacity and writes past the real limit wrap around and overwrite older data. FakeFlashTest does a fast sampled version of this on Windows, H2testw and F3 do the full version, and all of them run as real programs with real access to your device. A browser tab is not a real program in that sense, and the difference is deliberate, for your protection.

Why the browser cannot do it

Browsers run web pages inside a sandbox designed to keep websites away from your hardware. A page can ask you to pick a file, and it can work with the files you hand it, but it has no raw block access to your USB drive: it cannot write test patterns to chosen sectors across the device, cannot fill the device on its own, and cannot verify the device beneath the filesystem in the way a capacity test demands. That restriction is a security feature. The same barrier that stops an “online test” from testing your drive also stops a malicious page from quietly reading or wiping it. Granting every website raw access to every drive you plug in would be a catastrophe, which is why no mainstream browser offers it.

Consider what an online page can do, and why it proves nothing about capacity. It can let you upload a file and hash it, which proves the file you uploaded arrived intact; it says nothing about whether your drive can hold its claimed capacity, because the file travelled from the drive once, at one size, through your computer. It can benchmark a small transfer or display the capacity your system reports, which is the firmware’s claim repeated back to you, and the claim is the very thing under suspicion. None of these touches the far end of the drive, fills it, or checks whether earlier data survived later writes. A page that dresses any of this up as a capacity verdict is giving you theatre, not a test.

The real options, by platform

On Windows, download a real tool and run it locally. FakeFlashTest gives you a fast destructive Quick Size Test and a gentler Test Empty Space mode; H2testw gives you full proof. Start from our download page, follow how to test a USB flash drive for fake capacity, and compare methods in FakeFlashTest vs H2testw. On macOS and Linux, F3 fills and verifies the device, covered in how to test an SD card on a Mac and how to test a USB drive on Linux. The overview in fake SD card test software for every platform gathers every route in one table.

If your only hardware is a phone or a Chromebook, the honest position is limited but not hopeless. Testing an SD card on Android can raise suspicion through reported size and speed sanity checks, and checking a flash drive on a Chromebook describes a manual fill test using the Files app. Both are workarounds; the definitive test still needs a computer, even a borrowed one, for one full run. If that run confirms a fake, follow what to do next when a fake drive is confirmed and learn to read FakeFlashTest results if you screened on Windows. Do not pay for, sign up for, or trust any “online” verdict in the meantime: the test it claims to have run is one its own sandbox forbids.

The takeaway

There is no online FakeFlashTest, no browser edition of H2testw, and no website that can verify your drive’s real capacity from a tab. There are only local tools, run on a real computer, with real access to the device, and they are all free. That is genuinely good news disguised as an inconvenience: the real test costs nothing, takes one download, and gives you an answer a web page never could. Get the tool from the FakeFlashTest download on Windows, or use F3 on Mac and Linux, and let any site promising an online USB test keep its promise unclicked.

How to spot the next version of this claim

The online-test claim returns in new wrappers: a page that asks you to select your drive letter and then shows a progress bar, an app whose entire test happens suspiciously fast, or a service that offers a certificate for your drive after a short browser session. Apply one question to all of them: did anything actually write data across the whole claimed capacity and read it back? If the answer involves only uploads, small samples, displayed sizes, or a few seconds of activity, no capacity test occurred, whatever the result screen says. Real tests announce their thoroughness in their method and their duration. If a service cannot explain, in those terms, how it wrote and verified your specific device, it did not test your device at all.

The catch is that reported capacity is exactly what a fake card lies about. Hacked controller firmware tells every device, phone or computer, that a small amount of real flash is a huge capacity. When an Android app reads the card’s size, it is asking the liar for its story and repeating the answer. A card that “shows” its full claimed size in Settings has shown you nothing except that the firmware is consistent. The fraud only appears when data is written across the claimed capacity and read back, because writes past the real limit wrap around and overwrite older data. That write-everywhere-and-verify-everything test is what a real capacity test is.

What Android checks can usefully do

Used as sanity checks rather than verdicts, phone checks still earn their place. Look at the reported capacity for absurdity: genuine cards top out at sizes the market actually sells, and a claim far beyond plausible products, or a huge card for a tiny price, is a red flag before any software runs. Run a speed benchmark and think about plausibility: a card that behaves wildly inconsistently, or far from how a genuine card of its class should behave in ordinary use, deserves a proper test. Copy a large set of files you can verify elsewhere, then check them on a computer, and treat any corruption as a stop sign. Our download page and the computer-based guides it connects to are where suspicion becomes proof.

What none of these checks can do is substitute for a full test. A benchmark measures speed at the spots it touches, not capacity everywhere. A file copy you do not verify byte-for-byte can look successful while the data is already ruined, because listings survive even when contents do not. And a phone that has happily used a fake card for weeks proves only that you have not yet written past its real capacity; the failure arrives later, all at once, usually with the photos you most wanted to keep. Overwritten data is usually unrecoverable, so “it worked until it didn’t” is the most expensive way to learn this lesson.

The definitive test needs a computer

The definitive test runs where the proper tools run. On Windows, FakeFlashTest offers a quick screen and H2testw a full write-and-verify; start with how to test a microSD card for fake capacity and how to test a USB flash drive for fake capacity. On a Mac or Linux machine, F3 fills and verifies the card, as in how to test an SD card on a Mac and how to test a USB drive on Linux. You will need the card in a reader attached to the computer for the duration; plan it like any long test, back up first, and let it finish. Borrowed computers count. A library, workplace, or friend’s PC that can run one full test gives you more certainty than any number of phone apps.

If the computer test confirms a fake, keep the output with your order details and follow what to do next when a fake drive is confirmed, including the refund path while your window is open. If it passes fully, put the card back in your phone with confidence and normal backups. For the platform-by-platform overview, see fake SD card test software for every platform, and for the related myth that a website could do this job for you, read whether there is an online fake flash test. Android is a fine place to notice a problem. A computer is where you prove it.

Protecting photos while the card is unproven

Until a card has passed a full test on a computer, treat everything on it as temporary. Turn on whatever cloud or computer backup your phone setup offers, copy new photos off the card regularly rather than letting months accumulate in one place, and avoid filling an unproven card anywhere near its claimed capacity, because the wrap-around failure only begins once writes pass the real, much smaller limit. A card used lightly can look healthy for a long time while being fake underneath. If a backup copy ever shows corruption that the phone copy shares, stop trusting the card immediately and run the computer test before anything else is written to it. When you do replace a confirmed fake, buy the replacement from a reputable seller, test it on arrival in the same way, and only then let it become the card your phone relies on every day. Suspicion on the phone, proof on the computer, and backups in between: that combination keeps a fake card from ever becoming a lost archive.

One more practical habit helps while you wait for computer access: keep notes. Write down where and when you bought the card, the capacity it claimed, the price you paid, and any odd behaviour you noticed, such as files vanishing or a copy that seemed to finish impossibly fast for its size. Those notes take a minute on the phone itself, and they turn a vague feeling that something is wrong into the beginnings of the evidence bundle you will complete once the card meets a real test on a real computer.

The fraud those commands expose is a firmware lie. A fake drive’s hacked controller reports a small amount of real flash as a huge capacity. Linux, like every other system, believes the reported size until a test proves otherwise. Writes beyond the real capacity wrap around and overwrite older data, so a drive can list your files correctly while their contents are already destroyed, and overwritten data is usually unrecoverable. Filling the drive with known data and reading it all back is the definitive counter: either every test file verifies, or the drive was lying.

Installing F3 and identifying your drive safely

F3 is available in most distro repositories, and also via Homebrew on macOS if you work across both systems, so installation is normally a single package-manager step for the f3 package. Confirm f3write and f3read respond before you begin. Then comes the step that deserves your full attention: identifying the right device. List your block devices and mounts, note the test drive’s device name, size, and mount point, and compare them against what you physically plugged in. Our download page documents the Windows alternative for dual-boot machines, but on Linux the safety rule is universal: never point a fill test at a system disk, a backup disk, or any device you have not positively identified twice.

Back up the test drive first if it holds anything, because f3write fills the target volume. If several removable drives are attached, unplug the ones you are not testing so there is nothing to confuse. Use a good reader or port: a flaky connection that drops mid-test invalidates the run and wastes hours. These precautions take a minute and are the difference between a confident verdict and an expensive misunderstanding, especially on a machine that also holds your real backups.

Running the full test, and the quicker probe

Mount the drive, run f3write against its mount point, and let it write test files until the device is full. Then run f3read against the same mount point and let it verify everything. Read the summary carefully: F3 tells you how much was validated and whether data was corrupted. Corruption on verification is the fake signature: test data written later overwrote test data written earlier because the real capacity was far smaller than reported. A clean run means the capacity you tested behaved honestly. Give the job the time it needs; on large or slow media a full fill and verify is a long run, and interrupting it leaves you with no verdict at all.

F3 also offers f3probe, a quicker probe component. Treat it with the modesty its status deserves: it is described as experimental, and it is best used as a fast first signal, the Linux cousin of a quick screen, not as a substitute for the full f3write and f3read proof when a drive will hold important data or support a refund claim. That layered approach mirrors the Windows advice in FakeFlashTest vs H2testw and FakeFlashTest vs F3: screen quickly if you like, prove fully before you trust. For cards rather than sticks, the same commands apply through a reader, as in how to test a microSD card for fake capacity and how to test an SD card on a Mac.

After the verdict

If verification fails, preserve the terminal output with your order records, stop using the drive for anything that matters, and follow what to do next when a fake drive is confirmed. Do not let a reformat talk you into trusting it again; formatting changes the filesystem, not the hardware’s real capacity. If the drive passes fully, use it with normal backups and keep the result until the return window closes. For the complete cross-platform picture, see fake SD card test software for every platform, the best fake USB drive test tools, and the general method in how to test a USB flash drive for fake capacity. Linux gives you the full proof natively, in two commands, with no Windows machine required.

Testing cards, sticks, and second-hand drives

The same two-command proof covers every removable flash device you can mount: USB sticks, SD and microSD cards in a reader, and second-hand drives whose history you do not know. Second-hand media deserves the full test most of all, because a previous owner’s clean experience proves nothing about the capacity a full write will reach. If you test drives regularly, keep a short log of each device, its claimed size, its tested result, and the date. Patterns in that log, such as one seller’s drives failing repeatedly, are exactly the evidence that protects your next purchase and strengthens any dispute. A drive that passes fully can join your working kit with normal backups. A drive that fails should leave your kit entirely, however small its real capacity turns out to be, because storage that began as a deception has no safe second career holding anything you value.

Why testing matters at all deserves one paragraph. A fake card uses hacked controller firmware to report a small amount of real flash as a huge capacity. Your Mac believes the reported size, and writes past the real limit wrap around and overwrite older data. Photos can appear in Finder while their contents are already ruined, and overwritten data is usually unrecoverable. The only trustworthy response is to write known test data across the card and read it back, which is exactly the F3 workflow. Back up anything already on the card first, because the full test fills the device.

What you need before you start

You need the card, a reliable card reader, and F3 installed. Many Macs have no built-in SD slot, and a poor reader can make a long test slower and less trustworthy, so use the best reader you have; a dedicated reader such as those reached via our card reader options is a sensible testing accessory, not a luxury. Install F3 with Homebrew, the standard Mac package manager, by installing the f3 package from Terminal, then confirm the two commands that do the work are available: f3write, which fills the device with test files, and f3read, which verifies them. Our download page is still worth bookmarking: it explains the Windows FakeFlashTest workflow you will use if you ever test on a PC, and it links the companion guides in this series.

Before writing anything, be certain which volume you are about to fill. F3 writes to the mounted volume you point it at, so double-check the card’s name and size in Finder and Disk Utility, eject other removable drives if there is any chance of confusion, and never point a fill test at your Mac’s internal drive or a backup drive. This sounds obvious until the day it is not. Take ten seconds here; the test itself will take far longer, and starting it against the wrong volume is the one mistake in this guide that cannot be undone with patience.

Running f3write and f3read, step by step

Insert the card, let it mount, and note its mount point, typically under /Volumes with the card’s name. Run f3write against that volume and let it fill the card with its numbered test files. Do not use the card, sleep the Mac, or pull the reader out while this runs. When the write finishes, run f3read against the same volume to verify every test file. F3 reports how much data was written and validated and whether corruption was found. A clean verification means the tested capacity behaved as claimed. Errors during verification mean the card overwrote its own test data, the signature failure of a fake, and you should treat the claimed capacity as false.

Set your time expectations qualitatively and generously. A full fill-and-verify on a large or slow card through a slow reader is a long job, measured in hours rather than minutes on big media, and that is normal, not a sign that anything has hung. Start the test when you do not need the Mac or the card for a while, keep the machine awake and powered, and let the verify step finish: an interrupted test proves nothing in either direction. If you need the background on why a full test outranks a quick screen, FakeFlashTest vs F3 compares the two methods directly, and FakeFlashTest vs H2testw explains the same thoroughness question on Windows.

What to do with the result

If F3 verifies cleanly, you have the strongest assurance any of these tools gives, and you can use the card with normal backup habits. If it fails, stop: do not entrust the card with photos or work, keep the F3 output and your order details together, and follow what to do next when a fake drive is confirmed. The same workflow covers USB sticks on a Mac and microSD cards in an adapter; for the card-specific Windows walk-through, see how to test a microSD card for fake capacity, and for the general method, how to test a USB flash drive for fake capacity. The cross-platform overview in fake SD card test software for every platform and our hub of best fake USB drive test tools place the Mac workflow alongside every other system.

One last boundary: testing diagnoses, it does not repair. A failed card does not become trustworthy by reformatting, and a passed card still deserves backups. Test every too-cheap card before its first real job, keep the F3 result until the return window closes, and your Mac, a decent reader, and F3 together give you everything a Windows user gets from FakeFlashTest and more: not a screen, but a proof.

Testing USB sticks and larger cards the same way

Nothing in this workflow is specific to one card size. A USB stick mounted on your Mac can be filled and verified with the same f3write and f3read pairing, and a large card simply means a longer run and more reason to start it when you will not need the machine. If a card will live in a camera, test it before its first real shoot rather than after a day of irreplaceable pictures, and keep the verification output until the seller’s return window closes. That timing, test on arrival and keep the proof, matters more than any single setting in the test itself.