To save a Flipnote, Studio first queues its metadata, thumbnail, animation and sound for serialisation. A separate packaging step adds the trailer after those sections. The file still has to be written and pass the checks used when opening it, so check those later steps as well as the serialiser's result. [1][2]
Loading and scanning
The local library reads files and scans storage separately from the editor's save routines. The research covers folder selection, list order, filename identity checks and the checks used to accept a file. Test a new file in the intended client as well as a third-party decoder. [1][3]
When testing a writer, inspect the byte layout, frame decoding and metadata, then open the result through the intended client path. The original research distinguishes on-console and SD-card behaviour, and leaves unresolved cases explicit. [1]
Follow the full save and open paths
- Save controller and worker explains the asynchronous save UI, transaction handling, destination choice and file-write success conditions. [1]
- Original PPM serialisation shows how editor state becomes body bytes in each studied build. [1]
- Packaging and acceptance separates trailer creation from later input validation. [1]
- Library scanning covers local reads, SD enumeration, name grouping and display order. [1]
For an interoperable host-side writer, stage output in a temporary file and validate it before replacing a destination. This is a practical safeguard, not a claim about Nintendo's own write algorithm. [1][2]
SD-card locations and user folders
DSiBrew records the following normal SD-card directories. These are paths on the SD card, distinct from the NAND title directory containing public.sav. [4]
| Release | Normal SD directory |
|---|---|
| Europe | /private/ds/app/4B475556/001 |
| North America | /private/ds/app/4B475545/001 |
The documented user-folder arrangement places a custom folder alongside 001, under the same regional application directory. In Studio, open View Flipnote → SD Card, then use Choose Folder at the top. The folder selector initially lists the normal folders; selecting its Normal control again switches to user folders. This selects a sibling directory, so PPMs in a custom folder do not have to be moved into 001. [4]
The historical article suggests that custom folders might work around a library-index limit, possibly in dirmemo2.lst. The folder selection steps were observed, but the suggested cause and any limiting field have not been demonstrated. [4]