NSP vs XCI in 2026: The Ultimate Guide for Ryujinx, Eden, and Yuzu Forks (Plus Updates and DLC)

Your download finished at 3 AM. The file is 15 GB. You open the Eden emulator on your phone, tap the file, and get a black screen.

Sound familiar?

That single moment is the entire NSP vs XCI debate in one sentence. The format you pick decides how a game installs, how updates attach, and how much space your SD card loses. It does not decide your frame rate. We will prove that below, and the proof surprises most people.

An NSP is a Nintendo Submission Package. It is the eShop format. It holds NCA content files, metadata, and a Ticket.

An XCI is an NX Card Image. It is a raw dump of a physical game card. It carries a cartridge header and a Certificate.

Here is the 2026 reality you must accept first. Yuzu died in March 2024 after the Nintendo lawsuit. Ryujinx carries the PC scene now. Citron, Sudachi, Suyu, and Torzu keep the Yuzu code alive. Eden and Skyline rule Android. This guide covers every one of them.

Also Read: NSP File Not Showing Up in Ryujinx

TL;DR Quick Verdict

Question	Short Answer
Best format for Ryujinx	XCI for mounting, NSP for clean NAND installs
Best format for Eden on Android	NSZ or XCZ to save SD space
Best format for Citron and Sudachi	Either one; the code reads both the same
Best format for updates and DLC	Always NSP
Best format for archiving carts	XCI
Best format for small SD cards	NSZ or XCZ

Bookmark this table. You will come back to it.

NSP vs XCI at the File Level: Packaging, Not Performance

Open any Switch dump, and you will find the same core. That core is a set of NCA files. NCA stands for Nintendo Content Archive. It holds the actual game code and assets.

The difference between NSP and XCI is the wrapper around those NCA files. Think of it like shipping. The product inside is identical. The box and the paperwork change.

Format Anatomy Table

Inside the File	NSP	XCI
NCA game content	Yes	Yes
Metadata and Title ID	Yes	Yes
Ticket	Yes	No
Cartridge header	No	Yes
Certificate	No	Yes
Empty cart padding	No	Yes

The Ticket proves a digital purchase on real hardware. The Certificate proves a physical cart on real hardware. Emulators ignore both in most setups. They matter mostly on modded Switch consoles, and we cover that in Section 7.

The Performance Myth, Killed for Good

Here is the myth. People say NSP runs faster. Other people say XCI runs smoother. Both camps are wrong.

Once the emulator loads the NCA data into RAM, the wrapper is gone. Decryption, CPU calls, and GPU draws are identical. Ryujinx does not check your file extension before rendering a frame. Neither does Citron, Sudachi, Suyu, Torzu, or Eden.

The only real speed difference is the first load. An NSP installed to emulated NAND reads from your SSD. A mounted XCI also reads from your SSD. If both sit on the same drive, the gap is a second or less.

Storage and Load Times: Where XCI Gets Fat

Physical carts come in fixed sizes. A cart is 4 GB, 8 GB, 16 GB, or 32 GB. A full XCI dump keeps that whole shell, including empty padding.

An eShop NSP contains only real data. That is why NSP files usually look smaller.

Example Game	NSP Size	Full XCI Size	Trimmed XCI Size
13.1 GB eShop title	13.1 GB	16 GB	13.2 GB
3.5 GB indie title	3.5 GB	4 GB	3.6 GB
28 GB large title	28 GB	32 GB	28.3 GB

Tools like NSC Builder and 4NXCI can trim the padding off an XCI. A trimmed XCI is nearly the same size as the NSP. So size alone is a weak argument, and compression changes the whole game. More on that in Section 5.

How Every 2026 Emulator Handles NSP vs XCI

Each emulator family treats the two formats a little differently. The differences are about file management, not speed. Pick your workflow around these behaviors.

Emulator Handling Table

Emulator	NSP Behavior	XCI Behavior	Updates and DLC
Ryujinx	Installs to emulated NAND	Mounts as virtual game card	Separate NSP installs
Citron	Reads from game folder	Reads from game folder	Right-click install
Sudachi	Reads from game folder	Reads from game folder	Right click install
Suyu	Reads from game folder	Reads from game folder	Right click install
Torzu	Reads from game folder	Reads from game folder	Right click install
Eden (Android)	Loads from file picker	Loads from file picker	Separate NSP loads
Skyline (Android)	Loads from file picker	Loads from file picker	Limited support

Ryujinx: The Strict Purist

Ryujinx models the real Switch closely. It treats an XCI as a game card you inserted. The game runs without touching the emulated NAND.

An NSP is different. Ryujinx wants you to install it. You right-click the title and choose Install to NAND. The file then lives inside the emulated system storage.

Ryujinx is also strict about Title IDs. An update whose Title ID does not match the base game simply will not attach. This strictness is annoying, but it catches bad dumps early. We cover the fix in Section 4.

Saves behave differently per format too. A mounted XCI keeps its save in the user profile, just like an installed NSP. The location on your disk changes, so back up the right folder before switching formats.

Also Read: Tomodachi Life NSP

Yuzu Forks: Citron, Sudachi, Suyu, and Torzu

The Yuzu codebase is the most relaxed of the group. Citron, Sudachi, Suyu, and Torzu all scan a game directory. Every NSP and XCI in that directory shows up in one list.

There is no install step for base games. The emulator reads the file directly. Updates and DLC still install through a right-click menu into the emulated NAND.

Modding is where the forks shine. Each title gets a mod folder named after its Title ID, like load/0100F2C0115B6000/mods. The format of your base file does not change this path. Keep your Title ID handy, because the mod folder always uses it.

Eden and Skyline: The Android Reality

Eden is the name to know on Android in 2026. Skyline is its retired ancestor. Both use a plain file picker, and both treat NSP and XCI the same way.

That means the format debate on mobile is really a storage debate. Your enemy is the SD card, not the emulator. Two things decide your experience on Eden.

The first is file size. Compressed formats win here, and Section 5 is your friend.

The second is SD card formatting. Most Android SD cards ship as exFAT or FAT32. FAT32 cannot hold a file bigger than 4 GB, so large dumps get split.

Split File Codes Table

Extension	Parent Format	Meaning
.xc0	XCI	First split part of a cart dump
.xc1	XCI	Second split part
.ns0	NSP	First split part of a package
.ns1	NSP	Second split part

Eden and most 2026 emulators read split parts as one file. Keep all parts in the same folder and keep the names exact. Rename one part and the whole game dies.

Warning: Do not format your Switch or Android SD card to exFAT for the space gain. exFAT corrupts Nintendo file systems far more often than FAT32. The community consensus on this has not changed since 2019.

Updates, DLC, and Title IDs: The Real NSP vs XCI Nightmare

Here is the number one pain point behind this keyword. Someone downloads an XCI base game. Then they download an NSP update. The update refuses to attach.

The format is rarely the problem. The Title ID is the problem.

Every Switch title has a 16-character hex Title ID. The base game, its update, and its DLC share a family ID, but the last characters differ.

Title ID Suffix Codes Table

Content Type	Suffix Pattern	Example
Base game	ends in 000	0100F2C0115B6000
Update	ends in 800	0100F2C0115B6800
DLC pack 1	ends in 001	0100F2C0115B6001
DLC pack 2	ends in 002	0100F2C0115B6002

Now look at regions. A US cart and a JP eShop update have different Title ID families. They will never link, in any emulator, forever.

Version Codes Table

Version Code	Common Name
v0	Base game, no patches
v65536	First update
v131072	Second update
v196608	Third update

A v65536 update expects a matching base family. It does not care if the base is XCI or NSP. It cares about the ID family and the region.

The Fix: Check Your IDs Before You Rage

You can read any dump’s Title ID in under a minute. Three tools do this well.

SAK (Switch Army Knife) is the GUI option. Drag the file into SAK and the header panel shows the Title ID and version. It is the friendly path.

NSC Builder prints the same data in a terminal. It also validates the whole package.

hactool is the raw option for command-line people.

hactool -t xci "game.xci"

python NSCB.py -i "game.xci"

Compare the first 13 characters of your base game and your update. If they match, the pair belongs together. If they differ, you downloaded mismatched regions, and no emulator on Earth will fix that.

Pro Tip: Keep a plain text library sheet. One line per game, with base ID, update version, and DLC IDs. It turns future troubleshooting into a ten-second lookup.

NSZ and XCZ: The 2026 Standard That Ends the NSP vs XCI Storage Fight

Raw NSP and XCI files are becoming obsolete for one reason. Storage is expensive on handhelds. A Steam Deck with a 256 GB drive and an Android phone with a 512 GB SD card cannot host a raw library.

The answer is Zstandard compression. It produces NSZ from NSP and XCZ from XCI. The compression is lossless, and the game plays identically.

Compression Codes Table

Code	Parent	Compression
.nsz	NSP	Zstandard
.xcz	XCI	Zstandard

Real World Size Table

Format	Size for a 13.1 GB Game	Reads Natively In
NSP	13.1 GB	All emulators
NSZ	7.9 GB	Ryujinx, Citron, Sudachi, Suyu, Torzu, Eden
XCI	16 GB	All emulators
XCZ	8.2 GB	Most 2026 builds

You save 40 to 80 percent of the space. You lose zero performance. The emulator decompresses on the fly, and your SSD is usually faster than the game can read anyway.

Modern Ryujinx reads NSZ without a conversion step. The Yuzu forks inherited that support. Eden on Android handles NSZ well, which is why it is the default recommendation for mobile libraries.

Pro Tip: Archive the master dump as a trimmed XCI, and keep a playable NSZ copy for daily use. You get preservation and space savings at the same time.

Conversion Masterclass: Merging and Converting with NSC Builder and SAK

Sometimes you need one clean file. Maybe your update is NSP and your base is XCI. Maybe you want DLC baked in. This is the job for NSC Builder.

NSC Builder is a Python tool built on hactool. It converts, trims, merges, and compresses Switch packages. SAK wraps much of the same power in a GUI.

Tool Codes Table

Tool	Type	Best For
NSC Builder	Command line	Merging and batch conversion
SAK	GUI	Header reading and quick jobs
4NXCI	GUI	Extracting XCI contents
hactool	Command line	Raw header and NCA work

Convert XCI to NSP

python NSCB.py -o "C:\Switch\Out" --C_nsp "C:\Switch\game.xci"

The output is an installable NSP. The cartridge header and Certificate are dropped. Emulators never miss them.

Merge Base, Update, and DLC Into One File

This is the tutorial most guides skip. Feed every piece to one command, and NSC Builder stitches them in order.

python NSCB.py -o "C:\Switch\Out" --C_nsp "C:\Switch\game.xci" "C:\Switch\update.nsp" "C:\Switch\dlc.nsp"

The result is a single NSP at the latest version, with DLC attached. Install it once in Ryujinx and everything is live. No separate update step, no mismatched folders.

Compress to NSZ in the Same Breath

python NSCB.py -o "C:\Switch\Out" --C_nsp_zst "C:\Switch\game.xci" "C:\Switch\update.nsp"

You now have one small, complete, versioned file. This is the endgame of Switch file management.

Warning: Only download ROM files from places you trust, and never run a ROM that arrives as an .exe file. Real dumps are NSP, XCI, NSZ, or XCZ. An executable is malware, every single time.

Hardware Modders vs Emulator Users: Two Different Worlds

This keyword hides two different audiences, and mixing them up causes endless confusion. Know which side you are on.

Emulator Users

You need prod.keys to decrypt games. You may need title.keys for some dumps. You do not need sigpatches. You do not need a hacked console. You dump your own carts with NxDumpTool or your own eShop purchases, and you play on Ryujinx, a fork, or Eden.

Modded Switch Owners (Atmosphère)

You run Atmosphère with the Hekate bootloader. You extract keys with Lockpick_RCM. Here the format rules flip.

An NSP installs to your real NAND or SD card, and it needs sigpatches unless it is properly signed. Installers like Tinfoil, DBI, Goldleaf, and Awoo Installer handle the NSP side. DBI with its MTP responder is the community favorite in 2026.

An XCI is the archival format on hardware. Legacy SX OS mounts XCI straight from the SD card. Modern setups usually convert XCI to NSP for installation, or keep the XCI as a backup of the physical cart.

Audience Comparison Table

Item	Emulator User	Modded Switch Owner
Keys needed	prod.keys, title.keys	Lockpick_RCM output
Sigpatches	Not needed	Needed for NSP installs
Installer	Emulator itself	Tinfoil, DBI, Goldleaf, Awoo
Best archive format	Trimmed XCI	XCI
Best daily format	NSZ	Installed NSP

Warning: Nintendo’s legal stance has not softened. The 2024 Yuzu settlement and the Ryujinx takedown notices show where the company stands. Dump your own games, keep them private, and treat preservation as a personal archive, not a distribution hobby.

NSP vs XCI FAQ: Straight Answers for 2026

1. Does NSP run faster than XCI on Ryujinx?

No. Once data is in RAM, both formats perform the same. Only the first load can differ, and only by a second or less.

2. Can I install an NSP update to an XCI base game?

Yes. Updates are always NSP, and they attach to any base format. The Title ID family must match, or the install fails.

3. Why is my XCI file split into .xc0 and .xc1?

Your drive or SD card uses FAT32, which caps files at 4 GB. The dump was split to fit. Keep all parts together and emulators read them as one file.

4. How do I convert XCI to NSZ to save space on my Steam Deck?

Run NSC Builder with the zst flag, or use SAK’s compress option. Then copy the NSZ to your Deck. EmuDeck and Ryujinx read it natively.

5. Does Eden emulator prefer NSP or XCI?

Eden treats both the same. Choose by storage, not format. NSZ or XCZ is the smart pick on Android.

6. What is the difference between NSP, XCI, NSZ, and XCZ?

NSP is the eShop package and XCI is the cart dump. NSZ and XCZ are the same files compressed with Zstandard. Gameplay is identical across all four.

7. Do I need sigpatches for XCI files on a modded Switch?

Not for mounting or archiving. You need sigpatches when installing unsigned NSP content to the system. Emulator users never need them.

8. How do I check the Title ID of my Switch dumps?

Drag the file into SAK, or run NSC Builder’s info command, or use hactool. All three print the Title ID and version in seconds.

9. Is it legal to download NSP or XCI files if I own the game?

Ownership does not make downloading legal in most regions. The safe path is dumping your own cart or eShop purchase. This guide supports preservation of your own library only.

10. How do I merge DLC into my XCI file using NSC Builder?

Pass the XCI and the DLC NSP to one NSC Builder command with the merge flag. The output is a single file with the DLC baked in. Verify the Title IDs match first.

Final Verdict: Format Does Not Dictate Performance

Remember the golden rule. Format does not dictate performance. File management does.

Pick XCI when you archive a physical cart. Pick NSP when you want clean installs and tidy update handling. Pick NSZ or XCZ when storage is tight, which is most of us on Steam Deck and Android.

Match your Title IDs. Keep your parts together. Trim your dumps. Compress your daily library.

Do those four things and the NSP vs XCI question stops being a debate. It becomes a simple choice in your workflow.

Now tell us your setup. Which emulator runs your library in 2026, and which format sits on your drive? Drop it in the comments, because the scene moves fast and your answer helps the next reader.