misshexa66/OunceCake

OunceCake is a narrow-purpose utility for people who want the raw, unencrypted contents of Switch 2 game partitions on their own machine. It assumes you already have a working exploit chain and a specific fork of ns2jb; without those, the tool does nothing.

The problem

You own a Switch 2 game, update or DLC and want to look inside its romFS and exeFS rather than only play it. Normally the console keeps those files encrypted, and pulling them off the device requires more than an FTP connection: something has to run on the system while the game is mounted, and something has to serve the extracted files. OunceCake connects over RPC to that running exploit environment, lets you choose a title from a prompt, and then exposes the dumped files through an FTP server on port 2121. You finish with plain files on your computer, ready to browse or archive.

What's different

The README describes the approach plainly: files are loaded normally by the system and then pulled over FTP. That means no separate decryption keys or key-derivation workflow are involved, and the tool explicitly says it does not supply system keys or a method to decrypt files. The work is split between an exploit environment that provides an RPC connection and OunceCake, which drives the dump and stands up the file server. Because the transfer is FTP over the local network, you use an ordinary client with no credentials. The trade-off is dependence on a specific external setup: the tool is launched against the path of an ns2jb run folder, and the README points to kurumuz's fork rather than the upstream project.

The license is GPLv2, and the author notes that a small amount of code is borrowed from Atmosphere. The scope is limited to dumping; there is no built-in viewer, comparison tool or re-packaging step, so any inspection happens after the files land on your disk.

Who should try it

A good fit is a owner who already has the ns2jb exploit running and wants the contents of their own digital games, game cards or Switch 2 Editions, including updates and DLC, in a plain folder. For someone already comfortable with that environment, the flow is short: start the RPC connection, point OunceCake at the run folder, choose a title, then pull files over FTP.

A poor fit is anyone who has not set up the exploit chain, or who expects a turnkey ripper. The README's first real step is obtaining an RPC connection through an external project, so without that path the rest cannot start. It is also a poor choice for anyone looking for a general game-file browser: it produces dumps, not tools to explore or modify them.

Requirements and limitations

The hard requirement is a working ns2jb RPC connection from a supported fork of the exploit exploit setup. You also need Node.js, since the tool and the exploit's launcher are both invoked with node, plus a clone of this repository project instructions. The console and your computer must be on the same local network so you can reach the Switch 2's IP on port 2121. Finally, the dump depends on the system loading the title normally; the README states that no keys are provided and encryption is not bypassed by this tool.

Ongoing care is mostly about the external chain: the exploit fork, the exact run-folder path and the console firmware situation are outside OunceCake's control, so a change there can break the launch flow. The README also carries a blunt usage warning: do not share ripped files, and use the tool only with your own games on your own system readme.

HotRepo's take

HotRepo's only dated observation is the NEW-REPOSITORY board for JavaScript on 2026-10-25, where the repo appears with 239 total stars at #3; that is a board placement, not a daily growth figure project page. With a one-day sample and no comparably recorded daily history, persistence cannot yet be judged. Before investing setup time, the specific point to check is whether kurumuz's ns2jb fork matches your console and how the run-folder path is reported, because that dependency sits before anything OunceCake does.