Flipper Zero microSD Card Guide: Choosing, Formatting, Fixing Errors, and Directory Layout
The Flipper Zero stores nearly everything useful on its microSD card: saved Sub-GHz captures, NFC and RFID dumps, infrared remotes, BadUSB scripts, apps and asset packs. Without a working card, the device falls back to a small amount of internal memory and many features stop working. Most "my Flipper is acting weird" problems turn out to be card problems. This guide covers choosing a card, formatting it properly, reading the error messages, and understanding what is on it.
Choosing a Card
FactorRecommendationWhy Capacity8 to 32 GB is plentyFlipper files are tiny; large cards only add formatting issues BrandA known brand, bought from a reputable sellerCounterfeit cards report false capacity and fail unpredictably Speed classClass 10 or U1 is enoughSpeed is not the bottleneck FilesystemFAT32 (or exFAT on larger cards)The Flipper reads both, but FAT32 is the most compatible choiceCards larger than 32 GB usually ship formatted as exFAT, which is fine on the Flipper's current firmware, but a small FAT32 card is the least likely to cause trouble.
Formatting the Card on the Flipper
The easiest and safest way to format is on the device itself. In the settings, look under Storage for the SD card options, choose Format SD Card, and confirm. This erases everything on the card, so back up any saved files first, including the folders holding your Sub-GHz captures, NFC dumps and infrared files. After formatting, the Flipper recreates its expected folder structure automatically.
Formatting on a Computer
- Insert the card in a reader and confirm the drive.
- Format it as FAT32 with a tool that supports cards of that size, such as the SD Association's SD Memory Card Formatter.
- Eject it safely, insert it in the Flipper and power it on. The device creates the missing folders.
Folder Layout
FolderContents subghzSaved Sub-GHz captures and signal files nfcNFC card and tag dumps lfrfid125 kHz RFID saves infraredSaved remotes and the IR database badusbBadUSB scripts appsInstalled applications by category apps_dataData belonging to each app updateFirmware update packagesFolder names can vary slightly with the firmware version you run, so use what your device creates as the reference.
Common Errors and Fixes
SymptomLikely causeFix No SD card or SD card error on bootCard not seated or dirty contactsPower off, reseat the card, clean the contacts gently Card is detected but shows an unknown filesystemUnsupported or corrupt filesystemBack up on a computer if possible, then format on the Flipper Files save and then vanishCard failing or fake capacityTest with a card verification tool and replace the card Slow menus or hangs when browsingToo many files in one folder, or a slow cardOrganise files into subfolders, switch to a better card Apps do not loadIncomplete app install or mismatched firmwareReinstall the apps and match them to the firmware version Card works in a computer but not in the FlipperFilesystem type or partition layoutReformat as FAT32 with a single partitionBackups
Copy the whole card to a computer every so often, especially before updating firmware or experimenting with custom builds. You can remove the card and use a reader, or use the desktop application to browse and download files over USB. Keep one dated copy of a known-good state so you can restore quickly if the card fails.
Care and Handling
- Power the Flipper off before removing the card, to avoid corrupting files while a write is in progress.
- Avoid using the same card in a camera or phone where other software may write files or change the structure.
- Replace the card if you see repeated errors; cards are inexpensive and wear out.
- Keep sensitive dumps, such as NFC and RFID captures of your own cards, in a folder you can find and delete, and remove them before selling or lending the device.
Closing
A reliable card is the foundation of a well-behaved Flipper. Buy a small card from a real brand, format it on the device, keep periodic backups, and treat unexplained errors as a sign to test or replace the card before you blame the firmware.