Where Does Panda3DS Store Saves and Config?
Panda3DS keeps saves and sysdata under its app data folder, with portable mode beside the executable.
Last updated
Panda3DS stores per game save data, System save files, and the sysdata folder with aes_keys.txt under its app data root. The exact parent follows each OS app data convention. A config.toml beside that data controls paths, audio, and renderer picks.
Enable portable mode with usePortableBuild to keep everything next to Alber or Panda3DS executable. That helps on USB sticks and Deck setups. Back up saves before updating nightly builds, since formats still shift.
Where Panda3DS stores this, by platform
%AppData%\Panda3DS (saves and sysdata)
App data root with saves and sysdata/aes_keys.txt. Portable mode keeps the same tree beside the exe. config.toml here controls folders and DSP mode.
~/Library/Application Support/Panda3DS (saves and sysdata)
Same layout as Windows. Encrypted ROMs need sysdata/aes_keys.txt and seeddb.bin for newer titles. Keep that folder out of cloud sync while playing.
~/.local/share/Panda3DS (saves and sysdata)
Config at ~/.config/Panda3DS or beside saves depending on build. Libretro core instead uses the frontend save directory. Check config.toml for the active root.
Frequently asked questions
Where do I put AES keys for Panda3DS?
Create sysdata inside the app data root and add aes_keys.txt there, plus seeddb.bin for seed encrypted titles. Encrypted dumps refuse to boot without them. Decrypted dumps need no keys.
How do I make Panda3DS portable?
Flip usePortableBuild in config.toml so saves and sysdata sit beside the executable. Move the whole folder together. This suits USB drives and multi PC sync.
Notice an outdated path? Let us know.