If you’ve spent hours playing your favorite 3DS titles on Citra, the last thing you want is to lose all your progress to a misplaced save file or a failed emulator update. A lot of new users reach out asking what does the citra emulator save file extension use, and how they can manage those files to keep their playthroughs safe. I’ve been using Citra for over 5 years to test and play hundreds of 3DS games, so I’ve picked up all the little details about how Citra handles save data that most new guides skip over. We’ll cover everything from file naming conventions to fixing corrupted saves, so you never have to restart your Pokémon or Animal Crossing playthrough out of the blue.
What Does the Citra Emulator Save File Extension Actually Use?
Citra uses different file extensions for different types of save data, and it’s easy to mix them up if you don’t know what to look for. For standard in-game saves (the same type you’d generate on a physical 3DS when you save through a game’s built-in menu), the default file extension is .sav. These files are unencrypted by default, so you can transfer them between Citra installations, other 3DS emulators, and even modded 3DS hardware without extra work in most cases.
If you import save data directly from an unmodified physical 3DS, you’ll usually see files with the .bin extension. These are encrypted save files that Citra can’t read by default, so you’ll need to use a homebrew decryption tool on your 3DS before you can load these saves in the emulator. Homebrew 3DS games occasionally use custom save extensions, but 99% of official retail and digital 3DS titles stick to the .sav format for standard saves.
It’s also important to distinguish regular saves from Citra’s save state files, which use the .cst extension. Save states are instant snapshots of your game taken mid-play, perfect for redoing hard boss fights or skipping long cutscenes, but they are not the same as regular in-game saves. We’ll cover the key differences between these two types later in this guide.
How to Locate Your Citra Save Files on Any Device
Now that you know what file extensions to look for, you’ll need to know where Citra stores these files on your device. The file path varies slightly by operating system, but all versions of Citra store save data in the same basic folder structure, so you won’t have to dig through dozens of random folders to find what you need.
- Windows: Open File Explorer, paste %appdata%/Citra/sdmc/Nintendo 3DS/ into the address bar, and you’ll find your .sav files sorted by unique game ID in nested folders.
- Mac: Open Finder, hold down the Option key, click Go in the top menu bar, select Library, then navigate to Application Support/Citra/sdmc/Nintendo 3DS/ to access your save files.
- Linux: Your Citra save files are stored in the ~/.local/share/citra-emu/sdmc/Nintendo 3DS/ directory, which you can access by enabling hidden file viewing in your default file manager.
- Android/iOS: Open the Citra app, go to Settings > Open Citra Folder, then navigate to sdmc/Nintendo 3DS/ to find all your saved game data sorted by game ID.
That means you don’t have to waste time guessing where your saves are stored once you memorize the right path for your device. I always recommend bookmarking this save folder if you plan on transferring saves or making regular backups, since it saves you a couple of minutes of searching every time you need access. If you’re not sure which folder matches the game you’re looking for, right click the game in your Citra library and select “Properties” to find its unique game ID, which will match the folder name in your save directory.
Best Practices for Managing Your Citra Save Files
Even if you know what does the citra emulator save file extension uses, you can still run into issues if you don’t manage your save files properly. I’ve lost multiple 100+ hour playthroughs early on when I first started using Citra, so these are tips I learned the hard way to avoid unnecessary frustration.
First, always make a backup of your .sav files before updating Citra or modifying any core emulator settings. Most Citra updates work perfectly fine, but every once in a while a new nightly build will have a bug that corrupts existing save data. Storing a backup in a separate folder on your device or a cloud storage service like Google Drive will save you from losing months of progress over a bad update.
Second, avoid relying too heavily on save states for long-term progress storage. Save states are great for short-term use, but they are often not compatible across different Citra versions. If you upgrade your emulator, a save state from an older build might not load at all, so you should always save through the game’s built-in menu when you’re done playing for the day. Never edit your save files with third-party cheat tools unless you have a backup stored separately, because even a small incorrect change can corrupt the entire file beyond repair.
Third, if you’re transferring saves between Citra and a physical 3DS, make sure you decrypt the save file first before moving it. Encrypted .bin saves from a stock 3DS won’t load in Citra by default, and trying to force them to load can sometimes corrupt the file entirely. There are free, open-source homebrew tools you can run on a modded 3DS to decrypt saves in just a few seconds.
How to Fix Common Citra Save File Errors
Even if you follow all the best practices, you might still run into save file errors every now and then. Most of these issues are easy to fix without losing your progress, as long as you don’t panic and overwrite your existing save files before troubleshooting.
The most common error is Citra failing to recognize an existing save file when you launch a game. This usually happens if the save file name doesn’t match the game ID, or if you placed the save in the wrong folder. Double check that the save file is in the correct game ID folder in your Citra sdmc directory, and that you didn’t rename the file accidentally. Citra matches save files to games by their file name and ID, so even a small change to the file name can make the emulator unable to find it.
If you’re getting a “save file corrupted” error when you launch a game, first try loading the save on a different Citra build. Sometimes a specific nightly build has a bug that prevents it from reading valid save files, so switching to the latest stable build will often fix the issue right away. If that doesn’t work, replace the corrupted file with your backup copy, and you’ll be back to playing in no time.
Another common issue is save states failing to load after an update. I mentioned this earlier, but save states are version-specific, so you can usually fix this by downloading the older version of Citra that you used to create the save state, loading the state, saving through the game’s built-in menu, then moving that new .sav file to your newer Citra build. You don’t have to start your playthrough over if a save state stops working, as long as you follow that simple process.
At the end of the day, understanding what does the citra emulator save file extension use is one of the simplest ways to protect all the time you put into your 3DS playthroughs. You don’t have to be a tech expert to manage your save files properly, just follow the steps we covered, make regular backups, and you’ll never have to worry about losing your progress unexpectedly. If you run into any weird save file issues that aren’t covered here, the Citra community forums are a great resource to find fixes for less common errors, as other users have almost certainly run into the same problem before.
