CLI Storage & File Commands: Managing SD Card from Terminal
Why Use CLI Instead of qFlipper for This
qFlipper's GUI file browser is fine for occasional drag-and-drop, but the CLI storage commands are scriptable and faster for repetitive tasks — bulk operations, checking file existence in a script before an app runs, or automating backup routines.
Connecting
See the serial console access guide for getting a terminal connected — this assumes you're already at Flipper's CLI prompt.
Core Commands
storage list /ext # list contents of a directory storage list /ext/subghz # list a specific subfolder storage read /ext/somefile.txt # print file contents to terminal storage info /ext # SD card space info (used/free) storage md5 /ext/somefile.sub # checksum a file — useful for verifying transfers storage remove /ext/somefile.txt # delete a file storage mkdir /ext/my_new_folder # create a directory storage rename /ext/old.txt /ext/new.txt # rename/moveChecking SD Card Health
storage info /extShows total/free space — useful as a quick health check before assuming a write failure is a software bug rather than "the SD card is actually full," which is a more common cause than people expect once a signal/NFC library grows large.
Practical Scripting Example: Automated Backup Check
Since CLI commands can be scripted from your computer side (piped into the serial connection via a script rather than typed interactively), you can build a simple routine that runs storage md5 against known important files (your Sub-GHz library, saved NFC cards) and compares against a stored checksum from your last backup — flagging if anything's changed since you last backed up the SD card via qFlipper.
Bulk Operations
The CLI doesn't have native wildcard/glob support in most firmware versions — for genuine bulk operations (renaming/organizing dozens of files at once), it's often faster to pull the SD card out and use your computer's own file manager or a script operating directly on the mounted card, then push changes back via qFlipper, rather than fighting the CLI's more limited single-file command model.
Storage Path Reference
- /ext/ — the SD card (external storage) — this is where your saved signals, NFC cards, apps, etc. actually live
- /int/ — internal flash storage — much smaller, mostly used for firmware/system files, generally not where you're managing personal captures
Related Guides
- How to Update the Flipper Zero SD Card Structure Correctly
- Saving and Organizing Your Flipper Zero Files with qFlipper
- Flipper CLI Over USB: Serial Console, Commands, Debugging
- Scripting Flipper from a PC: CLI Automation
- The Flipper Zero Mobile App: Bluetooth Pairing, Remote Control, and Managing Your Flipper from Your Phone
- How to Install Custom Firmware and Develop Apps for the Flipper Zero
- How to Use Bluetooth HID on the Flipper Zero for Wireless BadUSB Attacks
- How to Analyze EMV Payment Cards with the Flipper Zero: NFC, APDU Commands, and Security Architecture