Many Switch 1 owners run their CFW world inside emuMMC, an emulated copy of the console’s internal storage living on the SD card. The saves in there are real saves, and getting them out to a PC — for backup, editing or migration — is a standard JKSV job once you understand what emuMMC means for where data lives. This guide covers the export cleanly. JKSV is on our download page. Related guides are on the game saves hub.
What emuMMC changes, and what it does not
emuMMC means the system JKSV runs in is reading and writing save data inside the emulated storage on your SD card, rather than the console’s internal sysMMC storage. From JKSV’s point of view, almost nothing changes: you launch it the same way, it lists the same users and titles, and it writes backups to the same /JKSV/ folder. The data it sees, however, is the emuMMC world’s data. A save that exists only in sysMMC will not appear, and vice versa, which explains most ‘my save is missing’ moments in this workflow.
Decide which storage holds the saves you want before you start. If the answer is emuMMC, boot into that environment, run JKSV there, and everything you export is emuMMC data by definition.
Exporting to the PC
Inside emuMMC, launch JKSV with Title Override and back up the titles you want, per user or as a batch — JKSV can back up all saves for the system or for a single user in one operation, which suits a full emuMMC harvest. Choose unpacked folders if the PC is where editing will happen, since editors work on the files directly. Then shut down cleanly, put the SD card in the PC, and copy the backup folders out of /JKSV/ into a dated archive folder on the computer.
Copy, do not move, so the SD card keeps its own set. Then treat the PC archive as the master: it is the copy you feed to editors, emulators and cloud storage, while the card copy remains the console-side spare.
Editing, emulators and next steps on PC
Once on the PC, emuMMC-exported saves behave like any JKSV export. Pokémon saves can go through the PKHeX loop in the Pokémon workflow; saves for games you also emulate can move into Ryujinx using the Ryujinx transfer guide, with the same-game, same-version rule in force. Keep the untouched export separate from any edited working copy, with folder names that say which is which, because a month later nobody remembers which folder was the experiment.
If a save will eventually return to the console, it goes back through JKSV restore inside the matching storage environment — emuMMC exports restore into emuMMC — under the same user it was exported from.
Archiving the whole emuMMC library
For long-term safety, mirror the PC archive into your cloud setup from the cloud backup hub, or simply include the dated archive folder in your normal PC backups. emuMMC setups get rebuilt, cards get replaced and partitions get resized; a PC archive taken today is what makes those operations calm instead of risky. Refresh it after major play milestones, not just once.
Do this and emuMMC stops being a place saves can get trapped. They become files you own, on hardware you control, ready for editing, emulation or a future console. See also island backups for the Device-save case that needs special care in any environment.
It is also worth deciding, once, how you will name and store these archives over years rather than weeks. A simple pattern — game name, user, storage source and date — makes an emuMMC harvest searchable long after the card it came from has been repurposed. Saves exported in a hurry with default names tend to become a pile nobody dares delete or trust. The export itself takes minutes; the naming discipline is what turns those minutes into a library you can actually use when a console, card or partition is gone.