Animal Crossing: New Horizons breaks the rule most players assume: there is no per-player island save to back up in the usual way. The island is a single piece of Device, or shared, save data belonging to the whole console. Back up the wrong thing and your ‘backup’ contains everything except the island. This guide explains what to capture in JKSV and how island moves really work. Get JKSV from our download page. Other game guides are on the game saves hub.
Why the island is a Device save
Every profile on a Switch shares one island, one museum and one landscape, so Nintendo stores that world as Device-Shared save data rather than as Account data for any one user. Your character’s personal progress and the island’s shared data are related but distinct. In JKSV’s save type list — Account, System, BCAT, Device, Temporary, Cache and System BCAT, explained in save data types explained — the island lives under the Device side, and that is the entry you must not miss.
This design is also why moving an island between consoles has always been a special operation rather than a normal save copy, and why whole-console thinking matters more for this game than for almost any other Switch title.
Backing up the island correctly
Launch JKSV with Title Override and back up Animal Crossing’s data including its Device save, not only your user entry. For a game this important, the belt-and-braces approach is a whole batch: use JKSV’s backup for the title and confirm the resulting backup in /JKSV/ actually contains the Device data before you rely on it. Then copy the backup off the card to a PC, and ideally into your cloud routine as well, because an island represents hundreds of shared hours.
Label the backup with the date and the island it belongs to. Months later, ‘New Horizons backup’ will not tell you which island or which season it holds, and restoring the wrong snapshot over a living island is a mistake no tool can undo for you.
Moving or restoring an island: cautions
Restoring a Device save is a bigger operation than restoring one player’s progress, because it replaces the shared world for everyone on that console. Tell anyone else who plays on the machine before you do it, double-check you have selected the intended snapshot, and keep the pre-restore backup JKSV offers to make. If you are moving to a different Switch 1, restore the Device data there with the same care, and verify by launching the game and walking around the island before wiping anything on the source console.
JKSV moves the data; it does not change Nintendo’s design or guarantees about how a moved island behaves with online services. Play it safe: verify first, delete last. The same export discipline powers exporting emuMMC saves to PC for a full archive.
Protecting the island long-term
Treat the island like the irreplaceable file it is. Back it up before big in-game events, terraforming projects or any console maintenance; keep one copy on the PC and one in the cloud using the setups in our cloud backup hub; and refresh the snapshots as the island changes, because a year-old island backup is a time capsule, not a safety net.
Do that, and the most fragile save on the Switch — the one stored unlike all the others — becomes one of the best protected. See also Minecraft world backups, the other shared-world case JKSV users ask about most.
One more island-specific habit is worth adopting: back up before you invite change, not after you regret it. That means a fresh JKSV snapshot before a visiting player gets building permissions, before a big terraforming weekend, and before any period where the console will be updated, repaired or lent out. Islands evolve socially as much as mechanically, and the snapshot timeline you build — dated, labelled, kept in more than one place — is what lets a community world survive accidents that would otherwise be permanent for every resident at once.