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.

The three locations at a glance

• Program: /switch/JKSV/JKSV.nro — the homebrew application itself.
• Backups: /JKSV/ at the SD card root — your exported saves, in a subfolder per game.
• Configuration: sd:/config/JKSV/ — settings and files such as webdav.json for cloud connections.

Keeping these roles separate in your mind prevents the most common file mistake: hunting for backups inside the program folder, or deleting configuration when you only meant to replace the program. Updating JKSV touches only the first location. Your backups and settings survive an update untouched.

The program folder: /switch/JKSV/

The switch folder at the root of the SD card holds homebrew applications, each typically in its own subfolder. JKSV’s subfolder contains JKSV.nro, the single file that is the current release. Its size for the 12/02/2025 build is 10,130,471 bytes, which is a quick sanity check if you are unsure which file you copied.

Do not store backups inside /switch/JKSV/. Nothing in the backup workflow writes there, and mixing your only backup copies into a folder you replace during updates is an unnecessary risk. The program folder should be treated as disposable and replaceable.

The backup folder: /JKSV/

Every backup JKSV creates is written under /JKSV/ at the root of the SD card, organised with a subfolder per game. Inside each game’s subfolder you will find the backups for that title, as unpacked folders or ZIP files depending on the export format you chose. Cloud backups must be ZIP files.

When you copy saves to a PC, copy from /JKSV/ and preserve its internal structure exactly. Restores and JKSV’s own browsing depend on that structure. A tidy habit is to copy the whole /JKSV/ folder into a dated folder on your PC after important sessions, so each archive is a complete snapshot.

The configuration folder: sd:/config/JKSV/

Settings live in sd:/config/JKSV/, separate from both the program and the backups. Cloud connection details are stored here — the WebDAV configuration is the webdav.json file in this folder. If you troubleshoot a cloud connection failure, this folder and that file are the first place to check for path or format mistakes.

Deleting the configuration folder is sometimes used as a reset when settings are suspected to be corrupted, as in black-screen troubleshooting. Be aware that doing so resets your JKSV settings, so you will need to set your preferences and cloud connections up again afterwards. Your backups in /JKSV/ are not affected by a configuration reset.

A practical SD card routine

Treat /JKSV/ as the folder you protect, /switch/JKSV/ as the folder you replace when updating, and /config/JKSV/ as the folder you touch only when changing settings or troubleshooting. With that routine, routine tasks — backing up, updating, copying to a PC — each have an obvious place, and accidents become much less likely.

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: file mode: edit single files and installation and file paths.

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.

The current version line

The current release is the date-based tag 12/02/2025. Before it, the 11/16/2025 release added compatibility with system 21.0.0 and introduced self-update checking and downloading. The rewrite era began on 08/25/2025, so any build older than that belongs to a different generation of the tool and should be replaced rather than updated in place conceptually — the file replacement itself is the same, but expectations about features should follow the new line.

Atmosphère is currently at 1.12.1 and Hekate at v6.5.4 in the surrounding ecosystem. JKSV updates and CFW updates are separate: updating one does not update the other, and a system update may require waiting for compatible releases of both before you update the console itself.

Update using JKSV self-update

• Launch JKSV as you normally would, preferably with Title Override.
• Use the update check inside JKSV and let it look for a newer release.
• If an update is offered, allow JKSV to download it and follow the on-screen prompts.
• Restart JKSV and confirm the displayed release matches the expected date tag.

Self-update requires a working network connection from the console. If your console is kept offline, self-update cannot reach the release, and the manual method below is the right choice. Neither method changes your backups in /JKSV/ or your configuration in sd:/config/JKSV/.

Update manually by replacing the .nro

Download the new JKSV.nro from the download page, preferring the GitHub channel at https://jksv.net/go/jksv-github . Verify the SHA-256 for the 12/02/2025 build — a2b7f6372a4b81f3c3194aa6f96f2824bdea853b9a8ebf8c4a008d0d865a0cbf — if you are installing that specific release. For a future release, use the hash published with that release instead.

Replace the file at /switch/JKSV/JKSV.nro on your SD card with the new file, keeping the same folder and file name. That single file replacement is the entire manual update. Boot back into Atmosphère, launch JKSV, and confirm it opens normally before you rely on it for a backup or restore.

After updating

Make a fresh backup of an important title after a major update and confirm it completes and is listed correctly. This validates the new build against your real library far better than simply seeing the menu open. Keep the previous .nro on your PC for a short while if you want a fallback, labelled by its date tag.

The 12/02/2025 release also re-enabled applet mode with a warning after it had been disabled in the previous release. Even on the current build, Title Override remains the recommended launch method, and applet mode should be treated as a convenience with known limits.

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: how to install JKSV and back up all saves at once.

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.

What an SVI file is

An SVI file carries the information JKSV needs to create save data for a title even when that title is not installed through the usual route. In practical terms, it bridges a gap: you have save-related data for a game, but the console does not currently present that game as an installed title with save data ready to manage.

For titles that are installed normally, you do not need SVI files at all. The standard create-save-data feature inside JKSV handles those titles directly, without any external file. SVI is a specialist tool for an unusual situation, not part of the everyday backup workflow.

When SVI files are used

The typical case discussed by users is preparing or importing save data connected to a title that is absent from the installed list — for example during an advanced reorganisation of a library, or when working from save information obtained before a title was removed. If that does not describe your situation, you almost certainly do not need SVI.

Because the title is not installed normally, anything created this way sits outside the path Nintendo and the game expect. That is precisely why the developer attaches a warning to the feature, covered in the next section. Understand the warning before you use an SVI file, not after.

The official warning — read this first

The developer’s position, as stated in JKSV’s official documentation, is that using SVI files for titles that are not properly installed is not a regular installation method and is done at your own risk. This site repeats that warning without softening it: SVI-based creation is unsupported territory, and results are not guaranteed.

In practical terms, that means you should expect no help if a game later misbehaves with SVI-created data, and you should never use SVI files on a profile or console state you cannot afford to rebuild. Always work from backups, and test any result thoroughly in an offline context first.

Safer alternatives to consider first

Before reaching for an SVI file, check whether the normal routes solve your problem. Installing the title properly and then using JKSV’s create-save-data feature is the supported path. Restoring a standard JKSV backup into a properly created save is likewise well-trodden and far easier to troubleshoot.

If you decide SVI is genuinely the only option, document what you did, keep the original files untouched in a separate folder, and keep the resulting save out of any online play until you understand how the game handles it. Modified or unusually created saves for online games carry ban risk, and SVI-created data deserves that same caution.

Summary

SVI files exist for edge cases involving uninstalled titles. They are not needed for normal backups, restores, or save creation, they come with an explicit developer warning, and they should be used rarely, carefully, and at your own risk. For everything else, the standard JKSV workflows in our other tutorials are the right tools.

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: create save data the standard way and how to back up 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.

What resizing save data means

Every save has an allocated size. If a game tries to store more data than the allocation allows, it can fail to save correctly even though your SD card has plenty of free space, because the limit is the container size, not the card. Resizing increases the allocated size for that title’s save data so the game has room to grow.

Minecraft is frequently mentioned for this feature because worlds can grow large over time. The principle is general, however: any title whose save data is constrained by its initial allocation can potentially benefit, provided the game itself can use the larger container.

Back up before you resize

Always back up the title before resizing. Resizing changes the save container itself, and if anything is interrupted the save can be left in a bad state. A fresh JKSV backup stored in /JKSV/, plus a copy on your PC, gives you a clean way back that takes only a minute to create.

Note the current state of the game before you start: confirm the save loads normally in the game. Resizing is not a repair tool for an already corrupted save. If the save is already unreadable, fix that problem first or restore a known-good backup, and only consider resizing a healthy save.

Resize step by step

• Launch JKSV with Title Override and select the user and title.
• Open the save options for the title and choose the resize function.
• Choose a larger allocation that gives the game comfortable headroom without being excessive.
• Confirm and wait for JKSV to finish; do not interrupt the operation.
• Launch the game and confirm the save loads and can be saved again.

Choose a sensible new size. Bigger is not automatically better: an allocation far beyond what the game will ever use simply reserves space. A moderate increase that solves the immediate pressure is usually the right call, and you can resize again later if a game genuinely outgrows it.

Test thoroughly after resizing

After resizing, play long enough to trigger a real save inside the game — for Minecraft, explore or modify the world and let it save — then quit and reload to confirm the data persisted. A save that loads once but fails on the next write has not been fixed, so the reload test matters.

Keep the pre-resize backup until you have played across several sessions without problems. Only when you are confident the resized save is stable should you treat the backup as archival rather than as an active safety net.

When resizing will not help

Resizing does not fix corrupted files inside a save, a mismatched user or title, or a failing SD card. If a game reports errors unrelated to space, work through the general troubleshooting steps first. Used for the right problem — a healthy save that needs more room — resizing is straightforward and effective.

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: back up saves before resizing and create save data without launching.

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.

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.

How the transfer works

There is no direct console-to-console wireless transfer inside JKSV. Instead, you back up on the source, copy the backup files from /JKSV/ on the source SD card to the same location on the destination SD card, usually via a PC, and then restore on the destination. The PC step also gives you a spare copy, which is valuable in its own right.

Both consoles need to be Switch 1 systems running Atmosphère with JKSV installed at /switch/JKSV/JKSV.nro. Keep both consoles on the current JKSV release, 12/02/2025, so backup formats and options match between source and destination.

Back up on the source console

On the source console, launch JKSV with Title Override and back up each title you want to move for the correct user. Use clear backup names and note which user each backup belongs to, especially if several profiles share the console. A batch backup for a single user is efficient when you are moving a whole profile’s library.

When the backups are done, shut down safely and copy the relevant subfolders from /JKSV/ to your PC. Keep the folder structure exactly as JKSV created it. Do not rename internal files or merge folders from different games by hand, because the structure is how JKSV and the restore process identify the data.

Prepare the destination

On the destination console, the game should be installed and the destination user should exist. If the title has never created save data on the destination, JKSV can create save data for a title without launching the game, which prepares a restore target. Creating the destination save first avoids a common class of restore failures.

• Copy the backup folders into /JKSV/ on the destination SD card, preserving structure.
• Boot the destination into Atmosphère and open JKSV with Title Override.
• Confirm the transferred backups appear under the expected titles.

Restore and verify on the destination

Restore each backup to the intended destination user. If you are moving saves between two different users rather than between consoles, the same principle applies: select the destination user deliberately at restore time and double-check the confirmation screen, because the user choice determines whose progress is replaced.

Launch each game after restoring and verify the progress in game. Only after you have confirmed the destination copies work should you consider cleaning up the source. Many users keep the PC copy permanently as an archive, which costs little space and preserves a recovery option.

Common problems

If a transferred save does not appear or is not recognised, the usual causes are a mismatched user, a mismatched title, or a folder structure altered during copying. Re-copy the original backup folders without modification and try again with one title. Version differences in the game itself can also matter for some titles, so keep game updates in mind when a single title misbehaves while others transfer cleanly.

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: transfer saves from emuMMC to sysNAND 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.

Why this transfer is sensitive

emuMMC and sysNAND are separate environments. Saves created or modified in emuMMC, especially while offline with homebrew, may not be considered clean by Nintendo if they later appear on a sysNAND that connects to online services. There is no method that guarantees a sysNAND will be treated as untouched after homebrew use, and JKSV does not promise ban protection.

In most reported cases, users who attempt this transfer do so entirely offline and accept that any sysNAND that has run CFW or received transferred homebrew-managed saves carries uncertainty. If keeping a pristine online sysNAND matters to you, the safest choice is not to perform this transfer at all. Read this whole section before you decide.

The general workflow

The basic idea is simple: back up the saves while booted into emuMMC, then restore those backups while booted into sysNAND with CFW, using the same JKSV backup files stored in /JKSV/ on the SD card. Because both environments can share the same SD card and the same /JKSV/ folder, the files themselves usually do not need to be moved by hand.

• Boot into emuMMC, launch JKSV with Title Override, and back up the titles you want to move.
• Copy the /JKSV/ folder to a PC as an extra safety copy.
• Reboot into sysNAND with Atmosphère, launch JKSV the same way, and confirm the backups are listed.
• Restore each backup to the matching user and title on sysNAND.

Match users and titles exactly

The user profile and title must correspond between the two environments. If the sysNAND profile is a different account or the game is not present in a compatible state, the restored save may not be recognised. Where needed, JKSV can create save data for a title without launching the game first, which can help prepare the destination before a restore.

Restore one title first and test it in the game before doing the rest. A single tested restore validates that your users, titles, and backup files line up. Batch-restoring everything and only then discovering a mismatch wastes time and makes diagnosis harder.

Reduce risk where you can

Work offline throughout the transfer. Do not connect the sysNAND to online services during the process, and think carefully before connecting afterwards with transferred saves present, particularly for online games. Saves for offline, single-player titles are generally discussed differently in the community from saves for competitive online titles, but neither category comes with a guarantee.

Keep your emuMMC backups untouched as the source of truth until you have confirmed the sysNAND copies work. If anything goes wrong, you can return to emuMMC and try again rather than having modified your only copy.

What this guide cannot promise

No guide can promise that a transfer is undetectable or ban-proof. Nintendo’s enforcement decisions are not published in detail, and community experience is anecdotal and changes over time. This guide describes the mechanics and the commonly discussed precautions with that uncertainty stated plainly, so you can make an informed decision rather than relying on a false assurance.

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: transfer saves between consoles and JKSV safety and ban risk guide.

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.

Whole-system vs single-user batch backup

A whole-system batch backup covers saves across users on the console, while a single-user batch focuses on one profile. Choose the whole-system option before a major change such as migrating to a new SD card or servicing the console. Choose the single-user option for routine protection of your own profile without copying everyone else’s data again.

Batch backup covers the save types JKSV supports, including Account, System, BCAT, Device-Shared, Temporary, Cache, and System BCAT data where present. Not every title uses every type, so an absence of a particular type for a particular game is normal.

Prepare space and power

Check free space on your microSD card before you start. A full library backup can be substantially larger than a single-game backup, and running out of space mid-batch can leave you with an incomplete set. If space is tight, copy older backups in /JKSV/ to a PC first and free room before starting.

Keep the console awake and powered for the duration. Do not remove the SD card, start a game, or let the battery run flat during a batch operation. Launch JKSV with Title Override so it has full memory access for the whole job.

Run the batch backup

• Open JKSV and navigate to the batch or backup-all function.
• Choose whole-system or single-user scope and confirm the selection.
• Wait for the progress to complete for all titles; larger libraries take longer.
• Review any titles JKSV reports as skipped or failed and note them for follow-up.

When the batch finishes, spot-check two or three titles in the list to confirm new backups with the current date are present. A quick spot-check catches a silent interruption far better than assuming success from the absence of an error message.

Store the batch result properly

Copy the entire /JKSV/ folder, or at least the newly created backups, to a PC or cloud location as soon as the batch completes. For cloud use, remember that JKSV cloud backups require ZIP format, and JKSV supports Google Drive and WebDAV uploads, including automatic upload when configured. Folder exports are fine for local PC storage.

Label the copied folder on your PC with the date and console it came from. If you own more than one Switch or maintain both emuMMC and sysNAND environments, an unlabelled backup folder becomes confusing within weeks. A simple dated folder name prevents restoring the wrong set later.

When to run a batch backup

Good moments for a full batch backup include before a firmware or Atmosphère update, before switching SD cards, before lending the console, and on a regular schedule if you play many games in rotation. Pair the habit with the single-game workflow for your most active title, which you can back up more frequently without repeating the whole library.

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: back up a single game save and how to update JKSV.

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.

Understand what a restore does

A restore overwrites the live save data for the selected user and title with the backup you choose. Any progress made after that backup was created will be lost unless you preserve it first. That is why naming backups clearly and keeping several dated copies matters, especially for long games.

JKSV offers an option to automatically back up the current save before a restore. Leave this option enabled unless you have a specific reason to disable it. If a restore turns out to be the wrong backup, the automatic pre-restore backup is often the only way back.

Prepare the backup file

If your backup is stored on a PC or in cloud storage, copy it back to the correct location first. Backups live under /JKSV/ on the SD card, in the subfolder for the game. Keep the folder structure exactly as JKSV created it. Manually reassembled folders are a common source of restore errors, including missing metadata problems covered in our troubleshooting section.

If you use cloud features, note that cloud backups must be in ZIP format. Google Drive and WebDAV uploads in JKSV require ZIP exports, so a folder export will need to be handled accordingly before it can be used as a cloud backup.

Restore step by step

• Launch JKSV with Title Override for full memory access.
• Select the same user profile that owns the save you want to replace.
• Select the title, open its backup list, and highlight the backup you want.
• Confirm the restore and wait for JKSV to report completion without interrupting it.

Double-check the user, title, and backup name on the confirmation screen. Restoring another user’s backup or an older backup than you intended are the two most common restore mistakes, and both are preventable with a five-second check.

After the restore

Close JKSV and launch the game normally. Load the save inside the game and confirm the progress, inventory, or settings match what you expect from that backup. Some games keep additional data in other save types, such as Device-Shared or BCAT data, so if only part of your progress looks wrong, consider whether a second save type is involved.

If the game does not recognise the restored save, do not immediately restore again at random. Work through the usual causes — wrong user, mismatched title, or a backup taken from a different context — which we cover in detail in the linked troubleshooting guide.

Safety habits for every restore

Never restore a save you downloaded from a stranger or a heavily modified save into a profile you use online without understanding the risk. Restoring other people’s saves or modified saves, especially for online games, carries a ban risk. JKSV itself does not promise protection from detection, and no honest guide can promise that either.

Keep your pre-restore automatic backup until you have played for a while and confirmed everything is correct. Deleting it immediately removes your safety net for no benefit, since backup files are small compared with most SD cards.

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: how to back up Switch saves and fix saves not appearing after restore.

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.