Importing Saves

If you already have ONScripter/NScripter save files — from a PC release, an emulator, or another device — you can bring them into Sakura for a specific game. There are two ways to do it: from within the app, or over Web Transfer.

Open the game’s Save Browser (see Save Management), tap the gear menu, and choose Import Saves.

Connect to Web Transfer, open the Saves tab, select the game, and tap ↑ Import save. A successful import shows a “Save imported” toast.

Both import paths accept the same formats:

.zip • save<N>.dat • envdata / envdata.utf • gloval.sav • kidoku.dat

You can select multiple files at once. A .zip archive is unzipped first — if its contents are wrapped in a single top-level folder, Sakura automatically descends into it rather than importing the wrapper folder itself.

Loose files are only accepted if they match a recognized save file — a slot file (save<N>.dat), or one of the sidecar files (envdata, envdata.utf, gloval.sav, kidoku.dat). Anything else is rejected with:

“{name}” is not a recognized save file. Supported: save{N}.dat, envdata, envdata.utf, gloval.sav, kidoku.dat, or a .zip archive.

An encrypted or corrupt zip is rejected with:

Could not read “{name}” — it is not a readable zip archive (encrypted archives are not supported).

Importing merges into the game’s current save folder: any file with the same name as an existing one is overwritten, and everything else already in the folder is left alone. If the destination folder already contains real saves (not just leftover soft-deleted files), Sakura takes a manual backup of it first — see Save Management for how backups and restores work.

Every imported file gets a freshly-stamped modification date. This is deliberate: if the game’s saves are synced to iCloud, the sync logic treats the newest modification date as authoritative per file, and without a fresh stamp an older cloud copy could silently overwrite your import on the next launch.

If an import silently doesn’t appear, or a save you expect to see is missing after a restore, see Save Issues.