Studio uses files shipped inside the DSiWare ROM, files it writes to system or SD storage, and files returned by online services. The same extension can appear in more than one context, and a path literal in executable code does not prove that a file is embedded in the ROM. [1]
NitroFS catalogue
The Flipnote Decompilation Project inventoried every NitroFS entry in four studied Studio ROMs: Japanese V1 has 8, Japanese V2 has 26, American V2 has 37, and European V2 has 56, for 127 entries across the set. The separate Japanese Viewer has no NitroFS entries in its declared file allocation table. Counts describe the supplied ROM images, not every release ever shipped. [1]
Open the full build-specific catalogues: Japanese V1, Japanese V2, American V2 and European V2. Each lists the original FNT path, file ID and stored byte range. [1]
| Class | Typical role | Evidence state |
|---|---|---|
.blz containing NARC | Manual and other resource packs | Compressed and container structures decoded |
.ZFTR | Localised NFTR fonts | LZ11 and glyph map decoded |
.ash | SampleData resources | Header and bytes known; payload codec unresolved |
.sdat | Sound archive | SDAT container identified |
.wav / .raw | Shutter samples | V2 WAVE parsed; V1 raw parameters unresolved |
.bmg / .tbl | Japanese V1 messages and keys | Message and table pairing checked |
Generated and remote files
PPM, temporary downloads, directory lists and UGO cache paths are named by original code but are not automatically NitroFS members. The original SD scanner classifies directories and filters extensions. Those routines have been traced, but the format of every saved list record is not yet fully documented. [1]
Audit method
Join ROM FNT path records to FAT start/end offsets, verify each byte range, then classify by bytes rather than extension alone. For a compressed resource, record both stored and decoded sizes. Do not infer a format from the first four bytes of an archive member whose record type is still unknown. [1]