You just spent 22 hours beating the Elite Four and catching a full team of shiny Pokemon on your Citra playthrough, and you want to back up your progress before updating the emulator. But first, you’re probably wondering what does the citra emulator save file look like, so you don’t accidentally delete the wrong folder when cleaning up your hard drive. I’ve been emulating 3DS games for over 6 years, and I’ve messed up enough save files in my early days to know exactly how these files are structured, where they hide, and how to handle them without breaking your progress. This guide breaks everything down in plain language, no confusing technical jargon included.
What Does the Citra Emulator Save File Look Like, Exactly?
Citra uses two distinct save file types, each with its own format and use case, so it’s important to know the difference between them. When you first open your Citra save folder, you might be confused by all the random ID folders, but once you know what does the citra emulator save file look like, you can pick them out instantly.
The first type is standard in-game saves, which are identical to the saves stored on a physical 3DS cartridge. These files use the .sav extension, are usually 512KB or 1MB in size, and are named to match your ROM file exactly. For example, if your ROM is named Animal Crossing New Leaf.3ds, your standard save will be Animal Crossing New Leaf.sav. Standard in-game Citra saves are fully compatible with real 3DS hardware, so you can transfer them between your emulator and a modded 3DS if you want to switch between platforms.
The second type is save states, which are snapshots of your game taken mid-playthrough using Citra’s built-in save state feature. These files use the .cst extension, include a number at the end to indicate which save slot they use (like Animal Crossing New Leaf.state2.cst), and are much larger than standard saves, usually between 10MB and 50MB depending on the game. Save states only work with the exact version of Citra you created them on, so you should never rely on them for long-term progress backups.
Both save types are stored inside a nested folder structure under your main Citra user directory, with separate folders for each game’s title ID and user profile. You won’t need to memorize the full folder path, as there’s a much faster way to find your saves directly through the emulator.
Where to Locate Your Citra Save Files on Your Device
The exact location of your Citra save folder changes based on your operating system and whether you installed Citra normally or used the portable build option. For most standard Windows installs, you’ll find your saves under C:\Users\[Your Username]\AppData\Roaming\Citra\user\sdmc\Nintendo 3DS\. For Mac users, the path is ~/Library/Application Support/Citra/, and for Linux users, it’s ~/.local/share/citra-emu/. If you used the portable build of Citra, all your save files are stored in the “user” folder in the same directory as your Citra executable, so you can move the entire folder between devices without losing progress.
The fastest way to find your save files is directly through the Citra interface, no digging through hidden system folders required. All you have to do is open Citra, right-click on the game you want to access saves for in your library, and select “Open Save Data Location” from the dropdown menu. This will pull up the exact folder with your standard in-game saves for that title, so you don’t have to sort through random title ID folders manually.
If you have multiple user profiles set up in Citra, each profile has its own separate save folder, so make sure you’re logged into the correct profile before accessing your saves if you share your emulator with family or roommates. You can switch between profiles through the Citra settings menu in 2 clicks, so it’s easy to confirm you’re looking at the right files.
Key Rules for Handling Citra Save Files Safely
A lot of people end up corrupting their saves because they don’t follow basic best practices when editing or moving them. I lost a 40-hour Animal Crossing: New Leaf save to a dumb mistake a few years back, so I always stick to these rules now to avoid losing progress:
- Always back up your save files before making any edits or moving them – even a small typo in a save editor can break your progress permanently if you don’t have a copy stored elsewhere, like a separate USB drive or cloud storage folder.
- Never close Citra while the game is saving, or while you’re copying save files from the active Citra folder – partial file transfers are one of the most common causes of corrupted saves, and they’re often impossible to repair without a backup.
- Don’t use save states from unofficial Citra builds, as they often have modified code that can cause compatibility issues with official versions of the emulator, and may even contain malware that corrupts your other files.
- If you’re transferring a save from a real 3DS, make sure you dump the save file correctly using a homebrew tool like Checkpoint, to avoid mismatched encryption that breaks the file when you try to load it in Citra.
You also want to avoid storing your active Citra save folder in a cloud sync folder like Dropbox or Google Drive while Citra is running, because the sync tool can lock the file mid-save and cause corruption. If you want to sync saves across devices, wait until you fully close Citra before allowing the sync to run, or set your cloud tool to only sync when Citra is not active.
How to Fix Corrupted Citra Save Files
If your save won’t load all of a sudden, don’t panic – most issues are fixable if you catch them early. The first step is to confirm what type of save you’re trying to load. If it’s a save state, the most common issue is that you’re trying to load it on a different version of Citra than the one you used to create it. To fix this, just download the exact build you used to make the save state, load the state, then save normally in-game, and that standard in-game save will work on any recent Citra version.
If your standard in-game save is corrupted, you can often repair it using a free 3DS save editor tool that checks for file structure errors and fixes common issues automatically. These tools also let you edit in-game items, currency, and progress if you want to customize your playthrough, as long as you have a backup of your original save in case something goes wrong.
Another common issue is that you might have placed the save file in the wrong folder, or renamed it so it doesn’t match your ROM file name exactly. Double check that the save file name matches your ROM name exactly, and that it’s in the correct title ID folder for your game. If you’re not sure what your game’s title ID is, you can look it up on public 3DS game databases in a few seconds. If all else fails, just replace the corrupted file with your backup – that’s why regular backups are non-negotiable for any emulator user.
Whether you’re looking to back up your progress, transfer saves to a real 3DS, or edit your in-game items, knowing what does the citra emulator save file look like makes the whole process way less stressful. You don’t have to be a tech expert to handle these files safely, as long as you stick to the basic rules we covered and always make a backup before you make any changes. I’ve transferred dozens of saves between Citra and my own modded 3DS over the years, and as long as you pay attention to file names and folder locations, you won’t run into any issues. Next time you finish a long gaming session on Citra, take 30 seconds to back up your save file – you’ll thank yourself if something goes wrong down the line.
