How to Transfer Modded 3DS Data to a New SD Card

Upgrading your SD card is one of the most common tasks for modded 3DS owners — whether you're running out of space for CIA-installed games, homebrew apps, or custom firmware files. The good news is that the transfer process is straightforward, but there are a few details that trip people up if they're not prepared. Here's what you need to know.

What's Actually on a Modded 3DS SD Card?

Before moving anything, it helps to understand what you're working with. A modded 3DS SD card typically contains a mix of:

• CFW (Custom Firmware) files — most commonly Luma3DS files including boot.firm and the luma folder
• Boot9strap or similar payload files stored in a boot9strap folder
• Homebrew applications in the 3ds folder
• CIA-installed game data stored in the Nintendo 3DS folder (this is the big one)
• Checkpoint save backups, themes, and other user data

All of these live directly on the SD card. Unlike a stock 3DS setup, modded systems depend heavily on the SD card being present and correctly populated at boot.

The Core Transfer Process 🗂️

The fundamental method is a direct copy — not a format, not a sync tool, just a file-level copy from old card to new card.

What you'll need:

• Your current SD card
• Your new SD card (formatted as FAT32)
• A computer with an SD card reader (or a USB adapter)
• Enough free space on your computer to temporarily hold the data, if copying card-to-card isn't possible directly

Step-by-step:

1. Power off your 3DS completely before removing the SD card. Never pull it while the system is running.
2. Insert your old SD card into your computer.
3. Copy everything — select all files and folders, including hidden ones. On Windows, enable "Show hidden items" in File Explorer. On macOS, use Cmd + Shift + . to reveal hidden files.
4. Paste everything onto your new SD card, which should already be formatted as FAT32.
5. Once the transfer is complete, eject the new card safely and insert it into your 3DS.
6. Power on and verify your CFW loads correctly (Luma's boot screen should appear if it's configured to show, or your home menu should load normally with homebrew access intact).

FAT32 Formatting: Why It Matters

The 3DS hardware only reads FAT32. If your new card is larger than 32GB — common sizes like 64GB, 128GB, or 256GB ship formatted as exFAT by default — you must reformat it to FAT32 before use.

Windows' built-in formatter caps FAT32 at 32GB, so for larger cards you'll need a third-party tool. FAT32 Format (guiformat.exe) and SD Card Formatter from the SD Association are widely used options that handle larger capacities correctly.

Skipping this step is the most common reason a modded 3DS fails to boot after a card swap.

The Hidden Files Problem

This is where many transfers go wrong. The Nintendo 3DS folder — which contains your installed game data, saves, and system-linked content — is often hidden at the OS level. If you copy your SD card without enabling hidden file visibility, you may transfer everything except the data you most care about.

Always double-check that hidden files are visible before you start copying. Some users have also reported that on macOS, . prefixed system files are omitted in certain copy operations, so verifying the file count or folder sizes between source and destination is a good habit.

What Varies by Setup 🔧

Not every modded 3DS transfer is identical. A few factors that affect your experience:

Console model and firmware version — A New 3DS XL with a recent Luma3DS version may have slightly different folder structures than an older O3DS setup. The process is the same, but file locations can differ.

SD card size jump — Moving from 32GB to 128GB is painless. Moving from a nearly full 128GB card introduces longer copy times and more opportunity for transfer errors. Verifying file integrity after a large transfer is worth the time.

Encrypted Nintendo 3DS folder — This folder is tied to your specific console's unique ID. It is not portable between consoles. If you're replacing a broken 3DS and copying your old card to a new one, your installed game data will likely appear as corrupted or inaccessible on the new hardware. Saves backed up via Checkpoint before the console swap are a different story — those can sometimes be restored through homebrew tools.

Homebrew and third-party app configs — Apps like FBI, Checkpoint, or custom themes store their settings within the SD card structure. These typically transfer cleanly, but some apps may prompt for reconfiguration on first launch.

After the Transfer

Once your new card is in and the system boots, run a quick sanity check:

• Open the Homebrew Launcher and confirm your apps appear
• Launch a CIA-installed game and verify save data is intact
• Check that Luma3DS settings (if customized) are preserved

If something seems off — a game is missing, a save is gone — the culprit is almost always the hidden files issue or an incomplete copy rather than anything more serious.

The right approach for your specific setup depends on what you have installed, the size of the cards involved, and whether you're doing a simple upgrade or moving data between different consoles — each of those scenarios plays out differently once you get into the details.