You restored a save with JKSV, the restore reported success, but the game shows old progress, an empty slot, or no save at all. In most reported cases the cause is a mismatch of user, title, or save context between backup and destination, and this guide gives you five checks in the order experienced users try them.
Check 1: User profile mismatch
Saves belong to a specific user. If you restored under a different profile from the one you play with — easy to do on a shared console — the game will correctly show that playing profile’s own untouched save, and the restored data sits unused under the other user. Open JKSV, note which user holds the restored backup, and compare it with the profile you launch the game with.
Check 2: Title mismatch
Confirm the backup and the installed game are truly the same title. Similar names, regional variants, or a backup taken from a different release of the game can all produce a backup that restores without error into a place the installed game never reads. Compare the title shown in JKSV for the backup with the installed game you are launching.
Check 3: Did the restore target exist?
If the destination title had never created save data for that user, a restore may have had no proper container to land in. Use JKSV to create save data for the title for the correct user first, then restore again. This ordering fix resolves a large share of ‘restore did nothing’ reports, particularly on fresh profiles or freshly set up consoles.
Check 4: Game version and additional save types
Some games store data across more than one save type — for example Account data plus Device-Shared or BCAT data. Restoring only one type can leave the game showing a mixture that looks like the restore failed. Consider whether the title uses additional types and whether your backup included them. Similarly, a backup from a substantially different game version may be ignored or only partly applied by the game; that behaviour is title-specific and cannot be diagnosed with certainty from JKSV alone.
Check 5: Verify inside JKSV before retrying
Browse the title in JKSV after the restore and confirm the live save now reflects the backup — then launch the game once more, making sure you fully closed it before the restore if it was suspended. A game that was left running can overwrite a restored save with its in-memory state on exit. Close software completely before restoring, every time.
If all five checks pass and the game still ignores the save, restore your pre-restore automatic backup to return to a known state, and treat the problematic backup itself as suspect — it may be incomplete or from a context that cannot be reproduced on this console.
Next steps and related guides
This guide is part of our troubleshooting hub collection. Before you start, get the current build from the download page. You may also find these guides useful: the correct restore workflow and transfer saves between consoles.
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.