The short, honest answer

No tool can promise that homebrew use is undetectable or ban-proof, and JKSV makes no such promise. Running any CFW and homebrew involves modifying the environment Nintendo expects, and Nintendo’s enforcement criteria are not published. Anyone who guarantees safety is overstating what is known. What can be described honestly is how risk differs by activity, based on widely reported community experience — which is anecdotal and can change.

Lower-risk use: your own saves, offline

The use JKSV is built for — backing up your own saves from your own games, storing them, and restoring your own unmodified backups — is the activity most commonly regarded as lower risk, especially when done offline in emuMMC or with the console kept offline. Lower risk does not mean no risk: the presence of CFW itself is the underlying factor, and this category assumes saves are entirely your own and unedited.

Keeping backups is also simply prudent data care, independent of any online question. Many users run JKSV entirely offline for archival purposes and never take the managed saves online at all, which is the most conservative pattern available.

Higher-risk use: modified, borrowed, and online saves

Risk rises sharply in three situations. First, editing save files — changing items, currency, or progress — and then using those saves, particularly online. Second, restoring another person’s save, which may contain data inconsistent with your account’s history. Third, anything involving online or competitive games, where publishers actively check for manipulation and where the consequences affect other players as well as your account.

In most reported cases, enforcement stories in the community involve exactly these higher categories. This guide will not help you disguise modified saves, because that would be dishonest about both the risk and the purpose of the tool. If an online game matters to you, keep its saves entirely separate from any editing or borrowing.

Practical ways to keep risk down

• Back up and restore only your own, unmodified saves for any profile you use online.
• Do JKSV work offline where possible, and think before reconnecting a sysNAND that has run CFW.
• Never take edited or borrowed saves into online play.
• Keep a clean separation: an offline environment for experiments, a conservative one for online play.

Also keep perspective: a ban discussion is ultimately about Nintendo’s and publishers’ decisions, which neither JKSV nor this site controls. The layered picture above is the best available guide — use JKSV as the backup tool it is, avoid the high-risk categories, and do not rely on any claim, anywhere, that a method is completely safe.

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: emuMMC to sysNAND risk notes and back up your own 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.

Check 1: webdav.json path and format

WebDAV settings live in a file called webdav.json inside the configuration folder at sd:/config/JKSV/. If the file is in any other location — including the JKSV program folder or the backup folder — JKSV will not find it and the connection will fail as if no server were configured. Confirm the file is exactly there, with exactly that name.

Format matters just as much. The file must be valid JSON with the fields JKSV expects for your server. A single misplaced comma or quote makes the whole file unreadable. If you edited it by hand, re-check it carefully or recreate it following the field layout for WebDAV configuration, and avoid word processors that add formatting characters — use a plain text editor.

Check 2: The backup must be ZIP

Cloud backups in JKSV require ZIP format. A backup exported as an unpacked folder cannot be used for cloud upload in the same way, and attempting it can present as a connection or upload failure. Create a ZIP export of the title and retry the upload with that backup before changing any server settings. This check takes a minute and rules out a very common false trail.

Check 3: Network basics

Confirm the console is actually online in CFW and can reach the internet at all — for example by checking another network function you use. Then confirm the WebDAV server is reachable from another device with the same address and credentials. If the server is down, the address changed, or the password was rotated, JKSV will fail no matter how correct the file format is. Google Drive uses its Limited Input sign-in flow with authorisation on a phone or PC, so an expired or incomplete authorisation there produces a similar failure and is fixed by signing in again.

Check 4: Update and retest

The 11/16/2025 release included WebDAV fixes, so a connection bug on an older build may already be fixed. Update to the current 12/02/2025 build, relaunch with Title Override, and test with a small title’s ZIP backup first. A small test upload distinguishes a configuration problem, which fails immediately, from a size or timeout problem, which fails partway on large files only.

JKSV can also upload automatically when configured. Once manual upload works, automatic upload usually follows; if automatic upload alone fails while manual works, re-check the related settings in the configuration rather than the server details you already proved.

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: where config files live and create a ZIP backup.

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.

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.

Why Mac copies cause this

macOS sets an archive attribute on files it writes to removable media, and the Switch interprets that attribute on folders in a way that breaks normal handling — a folder flagged this way can be treated as a file. The result is confusing behaviour across homebrew that reads those folders, which is why the symptom often appears right after a Mac was used to copy JKSV, backups, or other content to the card.

Windows copies do not typically cause this problem, which is a useful diagnostic clue: if the trouble started immediately after the card was in a Mac, the archive bit should be your first suspect, ahead of reinstalling anything.

Step 1: Fix the archive bit in Hekate

Hekate, the bootloader commonly used with Atmosphère, includes a dedicated tool for exactly this problem. Boot into Hekate — the current release is v6.5.4 — open Tools, and run Fix Archive Bit. Hekate scans the SD card and clears the problematic attribute from the folders it finds.

• Boot into Hekate instead of directly into Atmosphère.
• Open the Tools section.
• Select Fix Archive Bit and let it complete its scan.
• Boot into Atmosphère and test JKSV and your other homebrew again.

This fix is non-destructive to your save data: it changes a file attribute, not file contents. Your JKSV backups in /JKSV/ remain exactly as they were, just correctly recognised again.

Step 2: Prevent it on future Mac copies

Knowing the cause makes prevention simple. After any session where a Mac writes to the SD card — copying a new JKSV.nro, moving backups, adding any content — run Hekate’s Fix Archive Bit once before judging whether anything is broken. Making it a habit after Mac copies turns a confusing class of problems into a ten-second routine.

Alternatively, transfer files using methods that do not involve the Mac writing directly to the card’s folders in the same way, if your setup offers one you trust. Whichever route you choose, test JKSV immediately after a copy session so any problem is linked to the copy in your mind, not discovered weeks later without context.

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: JKSV not showing in menu and install JKSV correctly.

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.

Step 1: Relaunch with Title Override

Before changing any files, try launching again with full memory: hold R while starting a game, open the Homebrew Menu, and start JKSV from there. Applet mode is known to behave abnormally at times per the developer’s warning, and a black screen under applet limits that vanishes under Title Override needs no further fixing — just change your launch habit.

Give the launch a little time on the first attempt after changes to your library. JKSV maintains a title cache that invalidates automatically, and rebuilding information for a large library can make a launch look stuck when it is actually working. A wait of a short while distinguishes a slow start from a true hang.

Step 2: Restart the console cleanly

A full reboot into Atmosphère clears transient states that a simple relaunch cannot. Reboot, launch JKSV once with Title Override, and observe. If the black screen happens only after the console has been in sleep for a long time or after other homebrew has run, a clean-boot test tells you whether the problem is state-related rather than file-related.

Step 3: Replace the program file

A corrupted JKSV.nro can fail before any menu appears. Re-download the current build from the download page, verify SHA-256 a2b7f6372a4b81f3c3194aa6f96f2824bdea853b9a8ebf8c4a008d0d865a0cbf for the 12/02/2025 release, and replace the file at /switch/JKSV/JKSV.nro. This does not touch your backups in /JKSV/ or your settings, so it is a safe step to take early.

Step 4: Reset the configuration (last resort)

If the black screen persists on a verified current build with Title Override, a corrupted configuration is the remaining common suspect. The community workaround is to delete the configuration folder at sd:/config/JKSV/, which forces JKSV to start with default settings. Be clear about the trade-off: this resets your settings, including cloud configuration such as WebDAV details, which you will need to enter again.

Your backups are not in the configuration folder and survive this reset. After deleting it, launch JKSV and confirm it reaches its menus, then re-enter your settings gradually. If even a fresh configuration black-screens, the problem lies outside JKSV’s own files — check your Atmosphère setup and SD card health next.

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: JKSV crashing and freezing fixes and where JKSV files live.

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 Cache saves differ

Most game progress is Account save data tied to your user. Cache save data is a separate type that titles use for cached content, and its storage behaviour differs: depending on the title and circumstances, cache data may be created on the system NAND or on the SD card. Looking for a cache save in only one of those places is a common reason it appears to be missing.

JKSV lists Cache among the types it supports, alongside Account, System, BCAT, Device-Shared, Temporary, and System BCAT. When you browse a title in JKSV, check which type you are actually viewing before concluding a save is absent — a title can have a normal save in one view and cache data in another.

Check 1: Update JKSV first

The 11/16/2025 compatibility update specifically included improvements for cache saves, alongside system 21.0.0 support. If you are troubleshooting cache behaviour on an older build, update to the current 12/02/2025 release before deeper investigation. Troubleshooting an already-improved area on an old build wastes effort and can lead to wrong conclusions.

Get the current build from the download page and, if you install manually, verify the file before replacing /switch/JKSV/JKSV.nro. Then re-check the cache save in the updated build, launched with Title Override.

Check 2: Verify the index and location

Cache saves can involve index selection, and selecting a different index from the one the title uses will show you an empty or unrelated slot. Step through the available indexes for the title’s cache data methodically and note which one holds data. Also consider both NAND and SD locations as described above, rather than assuming the cache must be on the card with your other backups.

Backups you export still live in /JKSV/ on the SD card regardless of where the live cache data resides. Do not confuse the live storage location with the backup location — JKSV unifies backups under /JKSV/ even when the source data came from NAND.

Check 3: Recreate and retest

If a cache save appears damaged or stuck, creating fresh cache save data for the title with JKSV, after backing up what exists, gives the title a clean container to work with. Then launch the title and let it rebuild its cache through normal use. Cache data is by nature regenerable for many titles, which makes this a lower-risk test than it would be for primary progress saves — but back up first regardless.

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: error creating save data fixes and update JKSV to current build.

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.

Check 1: Free space on the card and the system

Creating save data requires room where the save will live. A nearly full microSD card or nearly full system memory can cause creation to fail without a clear explanation. Check free space in the system settings, delete or offload something you do not need if either location is almost full, and try again. Leave comfortable headroom rather than freeing the bare minimum.

Check 2: The save type you are creating

JKSV supports Account, System, BCAT, Device-Shared, Temporary, Cache, and System BCAT save types, but not every type is appropriate for every title or creatable in every context. If creation fails for an unusual type, test with the standard Account save for your user and the title. If the standard save creates successfully, the problem is specific to the type or index you originally requested, not to JKSV generally.

Similarly, confirm the index or slot you selected is not already occupied in a conflicting way. Creating a second save where the title expects a single fixed location can fail. Review what already exists for the title in JKSV before retrying.

Check 3: The title’s state

Confirm the title is correctly installed and recognised. A title whose data is damaged, partially installed, or in the middle of an update may not accept new save data cleanly. Launching the game once, if it launches normally, and letting it initialise can also resolve a surprising number of creation failures — after which JKSV creation usually succeeds as well.

Also launch JKSV itself with Title Override for full memory. Creation under applet mode’s memory limits can fail in ways that look like data problems but disappear with a full-memory launch.

Check 4: Retry cleanly and note the pattern

Restart the console into Atmosphère, open JKSV with Title Override, and retry creating save data for a single title before attempting any bulk creation for all titles. If single creation works, the earlier failure may have been a transient state. If it fails identically every time for this one title while others succeed, the issue is title-specific and further general troubleshooting is unlikely to change it.

Keep notes on which title, user, and type failed. If you seek community help, those three details are what experienced users will ask for first, and having them ready gets you a useful answer faster.

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: create save data without launching and cache save problems 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.

What the message means in practice

JKSV backups are not just loose save files. A complete backup created by JKSV includes additional information that lets JKSV identify and validate the backup during a restore. When that accompanying information is missing, JKSV refuses the restore and reports that no meta file is present. The save files themselves may still exist — it is the backup as a package that is incomplete.

In most reported cases, this happens after a backup folder has been assembled or edited by hand: files copied from different backups into one folder, a folder copied partially to a PC and back, or files extracted and repacked without the rest of the original backup structure. It is much less common with a backup folder left exactly as JKSV created it.

Step 1: Stop editing the broken folder

Do not keep adding or renaming files inside the failing backup in the hope of satisfying the check. Each manual change moves the folder further from a state JKSV recognises and makes diagnosis harder. Leave the folder as it is — its save files may still be useful as raw material in the recovery below — and work in a new, clean backup instead.

Step 2: Make one clean backup in JKSV

Launch JKSV with Title Override, select the same user and title, and create a brand-new backup of the current live save. This fresh backup is guaranteed to have the complete structure JKSV expects, including the metadata whose absence caused the error. Confirm it appears in the backup list and, for certainty, that it can be selected without the error.

This clean backup is both your template and your safety net. It proves the restore path works for this title, and it preserves the current live save before you change anything else.

Step 3: Bring your files into the clean backup

If the goal was to restore save files from the broken folder, copy those files into the fresh backup’s structure as a replacement — using a duplicate of the fresh backup, and keeping file names and positions identical — rather than trying to repair the broken folder’s missing pieces. Work on a PC copy first so both originals remain untouched.

Then restore the prepared backup with JKSV and test in the game. If it still fails, the files themselves may not belong to this title or user, or may be incomplete in a different way. Fall back to the untouched clean backup to return the title to a working state, and reconsider the source of the loose files before trying again.

Prevent it next time

Keep backups exactly as JKSV creates them, copy whole folders rather than selected files, and when you edit individual files, edit a duplicate of a complete backup. ZIP exports, which are required for cloud backups anyway, are a good way to keep a backup sealed as a single file that cannot lose pieces during copying.

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: how to restore saves properly and file mode and single-file edits.

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.

Step 1: Switch to Title Override

Applet mode runs homebrew with restricted memory. JKSV can run in applet mode in the current 12/02/2025 build — it was re-enabled with a warning — but the developer warns it may behave abnormally. Crashes and freezes are exactly the kind of abnormal behaviour to expect when memory runs short, especially with large title lists or large saves.

Use Title Override instead: hold R while launching a game to open the Homebrew Menu with full memory, then start JKSV from there. For the majority of users reporting crashes, this single change resolves them. Make Title Override your default launch method for all backup and restore work.

Step 2: Update to the current build

If you are on an older build, update. The 11/16/2025 release improved compatibility with system 21.0.0 and fixed WebDAV and cache-save issues, and the 12/02/2025 release fixed a crash involving Keep Local Backups combined with the auto-backup option. A crash that matches a fixed bug will keep happening until you update, no matter what else you change.

Update via JKSV’s built-in self-update, available since 11/16/2025, or manually replace /switch/JKSV/JKSV.nro with the current file from the download page. After updating, test again with Title Override before moving to deeper steps.

Step 3: Isolate the trigger

Note exactly when the freeze happens. Crashing on launch for every title suggests a general problem — build, launch mode, or configuration. Crashing only for one title suggests that title’s data or cache is involved. Crashing during a cloud operation suggests a network or configuration issue instead. The pattern narrows the fix considerably.

If JKSV freezes on launch even with Title Override on the current build, a corrupted configuration is a possibility. Deleting sd:/config/JKSV/ resets settings to defaults and is a recognised community step, but it will reset your preferences and cloud setup, so note them first. Your backups in /JKSV/ are stored separately and are not deleted by this reset.

If it still crashes

Try a fresh SD card copy of the program file: re-download JKSV.nro, verify its hash, and replace the file, in case the copy on the card was corrupted. Also confirm your Atmosphère version is current for your system version — at the time of writing Atmosphère 1.12.1 is the current release — because a mismatched CFW and system combination can destabilise homebrew generally, not just JKSV.

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: JKSV not showing in the menu and fix JKSV black screen.

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.

Check 1: Confirm the exact path

The file must be at /switch/JKSV/JKSV.nro — a JKSV folder inside the switch folder at the SD card root, with JKSV.nro directly inside it. The two classic mistakes are placing the file at /switch/JKSV.nro with no subfolder, and nesting it one level too deep, such as /switch/JKSV/JKSV/JKSV.nro after unzipping carelessly. Both hide the app from the menu.

Connect the SD card to a PC and navigate the folders visually rather than trusting memory. Rename or move files until the path matches exactly. File and folder names are case-sensitive in effect here — JKSV.nro with that capitalisation is the name to use.

Check 2: Confirm you downloaded the right file

The current file is JKSV.nro, 10,130,471 bytes, from the 12/02/2025 release. Get it from the download page via the GitHub channel if your copy is in doubt, and verify SHA-256 a2b7f6372a4b81f3c3194aa6f96f2824bdea853b9a8ebf8c4a008d0d865a0cbf. A file still inside a ZIP archive, or a file renamed by a browser, will not be recognised as homebrew.

Check 3: Confirm you booted into CFW

Homebrew only appears when you are running Atmosphère. If you booted into the stock system by accident — for example after a full power-off without your usual payload step — the Homebrew Menu will show none of your homebrew, not just JKSV. Reboot into Atmosphère the way you normally do and check again before changing any files.

Check 4: Rule out SD card problems

If several homebrew apps vanished at once, suspect the SD card rather than JKSV. A card that was removed without safe ejection, or a card developing faults, can lose or corrupt folders. Copy the card’s contents to a PC as a precaution, check the /switch/ folder contents there, and consider the archive bit fix if the card was recently written by a Mac.

Once the path is correct and you are in CFW, JKSV should list alongside your other homebrew. Launch it with Title Override — hold R while starting a game — for full memory access, as applet mode carries a developer warning about abnormal behaviour.

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: fix JKSV crashing or freezing and full JKSV install 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.