How to Add a Save File to New Super Ultimate Injector (NSUI)

New Super Ultimate Injector — commonly called NSUI — is a Windows-based tool used to inject games into the Nintendo 3DS Virtual Console format, creating installable CIA files. While its primary function is ROM injection, NSUI also supports embedding save files directly into those CIA packages, which means your game launches with progress already loaded. Understanding how this process works, and what can affect it, helps you avoid common pitfalls before you start.

What Is a Save File in This Context?

When you play a Virtual Console game on a 3DS, save data is stored in a specific location on your SD card tied to that CIA's title ID. A save file in NSUI is typically a raw binary file — often with extensions like .sav, .srm, or .fla — that represents the game's saved state.

These files can come from:

• Emulator saves (e.g., from RetroArch, Snes9x, VisualBoyAdvance)
• Extracted saves from original cartridges using tools like Checkpoint or JKSM on a modded 3DS
• Pre-made saves shared online by other users

Not every save format is compatible with every injected game. The format must match what the Virtual Console core expects — and that varies by platform (Game Boy, SNES, NES, GBA, etc.).

Step-by-Step: Adding a Save File in NSUI 🎮

The general workflow in New Super Ultimate Injector follows a consistent pattern across supported platforms:

1. Open NSUI and Select Your Platform

Launch NSUI and choose the console platform you're injecting for — NES, SNES, Game Boy, GBA, and others are listed as separate injection options. Each platform tab has its own settings panel.

2. Load Your ROM

Click the ROM field and browse to your game file. NSUI will populate game metadata automatically where available. This step must happen before you configure the save file, as the save data format is linked to the specific game and platform.

3. Navigate to the Save File Option

Within the injection panel for your selected platform, look for a section labeled "Save File," "Save Data," or similar. The exact label depends on the NSUI version you're running — the interface has changed across updates.

Click the corresponding Browse or Import button and navigate to your .sav or equivalent file.

4. Verify the Save File Format

This is where most errors occur. NSUI expects save files in a specific size and format depending on the platform:

If your save file is the wrong size or format, the injection may succeed but the game will ignore the save or corrupt it on launch.

5. Build and Install the CIA

Once your ROM and save file are loaded, configure any remaining options (game title, banner, icon) and click Build CIA. NSUI will package everything into a single installable .cia file. Install this to your 3DS using FBI or a similar CIA installer.

Why Save File Compatibility Gets Complicated 🔍

Even when you follow every step correctly, save files don't always behave as expected. Several variables determine whether an injected save works:

Emulator save format differences — A save from one emulator core may not be byte-for-byte identical to what the 3DS Virtual Console core expects, even for the same game. Some emulators add headers; others don't.

Battery-backed vs. flash saves — GBA games in particular use different save types (SRAM, EEPROM, Flash 64K, Flash 128K). If your .sav file was created with the wrong save type assumed, the data won't map correctly.

Save file size mismatches — The 3DS VC core expects a save file of an exact size. A file that's too small or too large — even by a few bytes — can cause problems. Some users manually pad save files using a hex editor to reach the correct size.

Regional differences — A save from a Japanese ROM may not transfer cleanly to an injected US ROM, even if the games are nearly identical, because memory addresses for save data can differ between regional versions.

NSUI version — Older versions of NSUI had known bugs around save file handling for specific platforms. Running the most current release reduces exposure to those issues.

Profiles That Get Different Results

A user injecting a SNES game with a standard .srm from a well-known emulator will generally have a smoother experience — SNES save formats are well-documented and consistent. Someone working with a GBA save faces more variability because GBA save types differ significantly by game, and misidentifying the type is common.

A user who extracted their save directly from a physical cartridge using JKSM on a modded 3DS is working with the most compatible raw format — it's already in the format the 3DS hardware expects. Someone converting a save from a PC emulator has more variables to manage.

Technical comfort matters here too. Resolving a size mismatch or format issue involves using a hex editor, understanding binary file structure, and knowing what save type a specific game uses — none of which is immediately obvious if you're new to ROM management.

Your specific combination of game, platform, save source, and NSUI version is what ultimately determines how straightforward — or how involved — this process will be.