Sometimes you do not need to replace a whole save — you need to inspect or swap a single file inside it. JKSV’s file mode lets you browse the contents of save data and backups at file level, which pairs with external save editors in a common workflow. This guide explains the workflow and the precautions that keep single-file edits from becoming whole-save losses.
What file mode is for
A JKSV backup exported as an unpacked folder contains the individual files that make up the save. File mode gives you a way to browse that structure and work with single files — viewing what is present, copying a file out, or replacing one file — instead of treating the save as an all-or-nothing block.
The typical reason is an external editor or tool that operates on one specific file within the save. Rather than extracting and rebuilding everything by hand on a PC alone, file-level access keeps the surrounding save structure intact while you change only the piece the tool needs.
The standard workflow
- Back up the title normally first and copy the backup to your PC — this untouched copy is your fallback.
- Work on a separate copy of the backup, never on your only copy.
- Use file mode or your PC to replace the single target file in the working copy, keeping names and locations identical.
- Restore the working copy with JKSV and test it in the game.
Keeping file names and folder positions exactly the same is essential. Many restore problems, including backups reported as incomplete, trace back to a file that was renamed, moved, or added during manual editing. Change the contents of the file if needed, but not its identity within the structure unless the tool explicitly requires it.
Work on copies, keep originals pristine
The single most important habit in file-level work is separation of copies. Your original JKSV backup, made cleanly inside the console, should remain untouched on the SD card and on your PC. All editing happens on a duplicate. If the edited version fails, you restore the pristine original and start over with no loss.
A related habit: make one change at a time. If you replace several files and the save then fails, you cannot tell which change caused it. Single, tested changes keep troubleshooting simple and are faster in the end than batch edits followed by guesswork.
Restore and test carefully
Restore the edited backup to the same user and title it came from, with the pre-restore automatic backup option enabled so your current live save is also preserved. Then launch the game and check not just that the save loads, but that the specific change you intended is present and that normal saving still works afterwards.
Be honest about risk if the edited file belongs to an online game. Editing save files and then playing online is exactly the category of use that carries ban risk. JKSV provides file access as a tool; how a game’s publisher treats edited saves online is outside JKSV’s control and no tool can promise safety there.
When to use whole-save restore instead
If you are not working with a tool that specifically needs one file, prefer the ordinary whole-save backup and restore workflow. It is simpler, better understood, and less prone to structural mistakes. File mode is a precision instrument for a specific job, not a replacement for the standard workflow.
Next steps and related guides
This guide is part of our hub collection. Before you start, get the current build from the download page. You may also find these guides useful: where JKSV saves files and how to restore saves.
JKSV is JK’s Save Manager by developer J-D-K, released under GPL-3.0 for Nintendo Switch 1 with Atmosphère. The current release is the date-based tag 12/02/2025. Always keep a second copy of important backups on your PC or in cloud storage, and test a restore on a non-critical save before you rely on a backup for a game you care about.