If you bought an SD or microSD card that claims a huge capacity for a suspiciously small price, your Mac can test it properly, just not with FakeFlashTest. There is no FakeFlashTest for Mac: the tool by Steve Si is Windows-only, and that will not change by downloading harder. The standard answer on macOS is F3, Fight Flash Fraud, an open-source tool that fills a device with test files and then verifies them. In other words, on a Mac, F3 does the job FakeFlashTest cannot, and it does the thorough version of the job: a full write-and-verify test rather than a quick screen.
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.