Normally a game creates its save data the first time you launch it. JKSV can create save data for a title without launching the game at all, for a single title or for all titles at once. This is especially useful when preparing a console for restores, setting up a fresh profile, or working with a large library. Here is how it works and when to use it.
Why create save data in advance
A restore needs a destination to restore into. If a title has never been launched under a user, there may be no save slot ready to receive a backup. Creating the save data in JKSV first solves that ordering problem without forcing you to start every game, skip its intros, and create a save manually.
The same feature helps when you set up a new user profile or rebuild a console. Creating saves for all titles at once gives every installed game a ready save container under that user, so later restores and backups proceed without per-game setup.
Create save data for a single title
- Launch JKSV with Title Override and select the user who should own the new save data.
- Find the title in JKSV’s title list and choose the option to create save data for it.
- Confirm the save type and details if JKSV prompts you, then wait for confirmation.
After creation, the title will behave as if it has save data for that user. You can immediately back it up, restore an existing backup into it, or launch the game and start playing. No game launch was required at any point in the process.
Create save data for all titles
JKSV can also create save data for all titles in one operation for the selected context. This is convenient for bulk setup, but it deserves a moment of thought: creating save containers for games you never play adds entries you may later need to sort through. For most users, creating for all titles makes sense during initial setup, while single-title creation is better for day-to-day use.
As with any bulk operation, keep the console powered and awake until it finishes, and spot-check a few titles afterwards to confirm their save data now exists. If a particular title fails, note it and handle it individually rather than repeating the whole batch blindly.
Save types to be aware of
JKSV handles Account, System, BCAT, Device-Shared, Temporary, Cache, and System BCAT save types. A normal game save for a user is typically an Account save. Other types serve system or shared purposes and should only be created or altered when you understand what the title uses them for. When in doubt, create the standard save for the user and title and test in the game.
Cache save data has its own placement behaviour between NAND and SD, which was improved in the 11/16/2025 release. If you work with Cache saves specifically, our troubleshooting guide on cache saves explains the background in more detail.
Limits and good practice
Creating save data is not the same as creating progress. The new save is an empty starting point provided by the system and title, not a completed game file. You still need to play the game or restore a real backup to have actual progress. Treat the feature as preparation, not as a shortcut to content you have not earned or backed up.
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: restore saves with JKSV and SVI files explained.
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.