Cache-type saves behave differently from normal game saves, and problems with them — saves created in an unexpected place, or not appearing where you look — can be confusing. In most reported cases the cause is misunderstanding where Cache data is created, between NAND and SD, combined with index behaviour, and this guide gives you three clarifications and checks. Handling of cache saves was improved in the 11/16/2025 release, so your JKSV version matters here.
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.