Is an Android DraStic Save File .SAV or .DSV? Understanding Emulator Save Formats

If you've been using DraStic DS Emulator on Android and started digging through your file storage looking for save files, you've probably noticed two different file extensions floating around: .sav and .dsv. It's a genuinely confusing situation, and the answer isn't as simple as "it's one or the other" — because DraStic actually uses both, for different purposes.

Here's what's actually going on.

The Two Types of Save Files in DraStic

To understand why two extensions exist, you need to know that Nintendo DS games save data in two distinct ways. DraStic mirrors this behavior, which is why you end up with two file types on your device.

.SAV Files — Cartridge Save Data

The .sav format represents the cartridge battery save — the equivalent of the data that would have been written to flash memory on a physical DS cartridge. This is the save data the game itself generates: your story progress, your caught Pokémon, your completed levels.

When you play a game in DraStic, it creates a .sav file that mirrors what the original hardware would have stored on the cartridge chip. The filename typically matches the ROM filename — so PokemonBlack.nds would produce PokemonBlack.sav.

These files are broadly compatible across many DS emulators, not just DraStic. That compatibility is intentional and useful — .sav files follow a relatively standardized format for DS cartridge saves, which means you can often transfer them between emulators like DeSmuME or melonDS with little friction.

.DSV Files — DraStic's Save State Format

The .dsv extension is DraStic-specific. These are the emulator's internal save states — snapshots of the entire emulated DS system at a specific moment in time. Think of them as a photograph of the game's exact state: CPU registers, RAM contents, graphics pipeline, everything frozen at one instant.

Save states are not the same as in-game saves. They're a convenience feature that lets you pause mid-battle or mid-platforming section and resume exactly where you left off, regardless of whether the game itself has a save point nearby.

Because .dsv files capture the full emulator state rather than just cartridge data, they're not transferable to other emulators. A .dsv file created in DraStic will not load in DeSmuME or melonDS — those emulators use their own proprietary state formats.

Where DraStic Stores These Files on Android

By default, DraStic places save files in a specific folder structure on your Android device's internal storage or SD card. The exact path can vary depending on your Android version and how storage permissions are configured, but typically you'll find:

• Battery saves (.sav): stored alongside your ROMs or in a dedicated /DraStic/backup/ or /DraStic/saves/ directory
• Save states (.dsv): usually in a /DraStic/savestates/ folder, organized by game

Android's storage access framework changes — particularly those introduced in Android 10 and expanded in Android 11 and 12 — have affected how emulators like DraStic can read and write files. Some users find their saves in app-specific storage paths that aren't directly browsable through a standard file manager without root access or specific folder navigation.

Key Differences at a Glance 📁

Why This Distinction Actually Matters

If you're backing up your saves, the .sav file is the one you most need to protect. It's your actual game progress, and it's the file you'd transfer if you moved to a different device or switched emulators. Losing a .sav file means losing your in-game saves — there's no recovering a 100-hour playthrough from a save state alone if the underlying battery save is gone.

The .dsv save states are convenient but supplementary. They're useful for mid-session flexibility, but they depend on the .sav file existing and being consistent underneath them. If the two fall out of sync — which can happen if you move files around incorrectly — you can end up with loading errors or corrupted state behavior.

Compatibility When Moving Between Devices or Emulators 🔄

If you're migrating from DraStic on Android to a desktop emulator like DeSmuME or melonDS, bring your .sav files. Those will load directly in most other DS emulators with minimal setup. Leave the .dsv files behind — they won't be recognized.

Going the other direction — importing saves from a desktop emulator into DraStic — also typically works at the .sav level, though occasional format variations between emulators mean it's worth verifying the save loaded correctly before overwriting anything.

One variable worth knowing: some DS games use 512KB, 256KB, or other save sizes, and mismatched save sizes between emulators can cause issues even when the file extension matches. If a transferred save isn't loading correctly, save size incompatibility is one of the first things worth investigating.

The Part That Depends on Your Setup

Whether managing these files is straightforward or genuinely complicated depends on several things that vary from user to user: which version of Android you're running, whether you're using an SD card or internal storage, whether your device is rooted, and how your file manager handles app-specific directories.

DraStic's behavior around file paths has also changed across its own updates, meaning the folder structure on a device running an older DraStic version may differ from a fresh installation on a current Android build. Your specific combination of app version, Android version, and storage configuration will determine exactly where your files live — and how easily you can find, back up, or transfer them.