SVI files are one of JKSV’s less understood features. An SVI file lets JKSV import or create save data for a title that is not currently installed in the normal way. This guide explains what SVI files are, the narrow situations where they are useful, and the developer’s explicit warning that comes with them.
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.