# Goldleaf for Nintendo Switch: NSP installs, ticket cleanup and a PC remote browser > Goldleaf is a multipurpose homebrew tool for the Nintendo Switch, built on libnx. It installs NSP files, manages tickets and content, and can browse files on a PC over the network with Quark. **XorTroll/Goldleaf** — 🍂 Multipurpose homebrew tool for Nintendo Switch - Repository: https://github.com/XorTroll/Goldleaf - Stars: 3,044 · Forks: 359 - Language: C - License: GPL-3.0 - Published: 2026-09-24 · Updated: 2026-09-24 · Language: en - Canonical page: https://hysenlabs.com/projects/xortroll-goldleaf ## What Goldleaf does that a file manager does not A plain file browser on the Switch moves files. Goldleaf is built around Nintendo's own content model: titles, updates, DLC, tickets and savedata. The README describes the concept as similar to FBI on the Nintendo 3DS, and the feature list backs that up. The Explorer handles SD card, console memory partitions (SAVE, SYSTEM, USER and PRODINFOF), USB drives through libusbhsfs, game savedata read-only, NRO homebrew RomFs read-only, and a remote PC connection. Alongside it sits a content manager that lists each title's base game, update and DLC, shows the ticket, and lets you uninstall, export to NSP, remove a ticket or reset the launch version. That last operation exists for a specific situation: after an update has been removed, resetting the launch version lets the base game start again. The audience is narrow but real. You need a Switch that already runs homebrew, and you need to be comfortable with the fact that Goldleaf can delete tickets and uninstall content. The README repeats the warning "use this carefully, and make sure you know what you're doing!" for NSP installs, ticket removal and setting JPG icons. That repetition is not decoration. Several of these operations are not trivially reversible from inside the app. ## How the Explorer, content manager and Quark fit together Goldleaf is a C application built on libnx. The repository keeps its own submodules: Plutonium (the UI layer), a libnx extension in libnx-ext/libnx-ipcext, libusbhsfs for USB mass storage, and Quark, the PC-side companion. The Makefile shows the split clearly: the build target compiles Plutonium, the libnx IPC extension and Goldleaf itself, while a separate arc target runs Python scripts to generate resource headers from .rc.hpp files before the C++ resource file is produced. The data flow for remote browsing is the part worth understanding. Quark runs on the PC and serves the local filesystem; Goldleaf connects to it from the console and presents those files in the same Explorer used for the SD card. The README has separate Quark setup sections for Windows, Linux and Mac, which tells you the pairing is the intended path rather than an afterthought. USB drives go through libusbhsfs instead, so a USB stick and a Quark session are two different transports reaching the same file operations. Two constraints are documented and easy to miss. The web browser only works when Goldleaf is launched as an application, not as an applet, because of system memory limits. And every mounted location (SD, console memory, remote PC, USB, savedata, RomFs) is automatically unmounted when Goldleaf exits. If you are copying a large file, closing the app ends the mount. ## Installing Goldleaf and running a first NSP install The README does not give a step-by-step end-user installation guide. It points to the releases page for the latest build, and the repository is set up to be built from source. The Makefile states that the first build needs a setup step to install libusbhsfs packages, after which a plain make builds the project. ```bash make setup make ``` The first command installs the libusbhsfs packages. The second builds Plutonium, the libnx IPC extension and Goldleaf. If you only want the generated resource headers rebuilt, the arc target is separate. Once Goldleaf is running on the console, an NSP install starts in the Explorer. Navigate to the directory holding the NSP, open the directory options and choose the install-all-NSPs operation the README lists under directory operations. For a single file, the file operations include installing NSPs of games, updates and DLC. The README's warning applies here without qualification: it tells you to use this carefully and to know what you are doing. If the NSP is on a PC rather than the SD card, start Quark on that machine first and connect to it from Goldleaf's Explorer. The README documents Quark for Windows, Linux and Mac, so the PC side is not tied to one OS. With a USB drive, the libusbhsfs path is used instead and no PC is involved. ## Tickets, savedata and the operations you cannot undo Goldleaf's ticket browser checks tickets and can remove unused ones. The content manager can also remove a ticket for a specific title, and uninstall or completely remove content. The README notes that uninstalling content will not remove savedata, which is a deliberate separation: your game progress survives a content removal, but the ticket does not come back on its own. This is where Goldleaf stops being a convenience tool and becomes a tool you should read about before using. Ticket removal is flagged with the same careful-use warning as NSP installation. The README documents no rollback, and there is no undo for a removed ticket. The account manager has a comparable boundary: it can delete a user, but only if more than one user exists on the system, which prevents you from deleting the last account. That kind of guard rail is present for accounts and absent for tickets. Savedata handling is read-only in the Explorer, and mounting savedata is how you navigate it. If your goal is to edit savedata rather than inspect it, Goldleaf is not the tool for that job as documented. ## Where Goldleaf is the wrong tool Goldleaf assumes homebrew is already running on the console. Nothing in the README describes setting that up, and the installation path it gives is a releases page plus a source build. If you are not already in that world, Goldleaf is not your entry point. It is also a poor fit when you want a stable, predictable release channel. The README carries a notice at the top: if the last Goldleaf release is currently broken, the author points readers to a Discord server where dev builds of changes under test are shared before commits or releases. That is an honest statement about the release process, and it also tells you the latest release is not guaranteed to work. A user who wants a version with a support commitment should look elsewhere. The web browser is another limited case. Because it relies on the console's web applet and system memory, it is only usable when Goldleaf is launched as an application. If your launch method runs it as an applet, the browser is simply not available, and no setting changes that. Finally, the README lists known bugs as its own section, but that section is not reproduced here. Check it in the repository before relying on a specific operation. ## Goldleaf against FBI and against plain file managers The README itself makes the comparison: Goldleaf's concept is very similar to FBI, the well-known Nintendo 3DS homebrew tool. The difference is the platform, and with it the content model. FBI operates on the 3DS title and ticket system; Goldleaf operates on the Switch equivalent, where content is split into base game, update and DLC per title, and where the Explorer also reaches console memory partitions, USB drives through libusbhsfs and a remote PC through Quark. If you have used FBI, the mental model transfers, but the partition names, the NSP format and the Quark pairing do not. Against a plain file manager homebrew, the split is different. A file manager moves bytes between mounted locations. Goldleaf adds ticket inspection and removal, content export to NSP, launch version reset, NACP preview, amiibo dumping for emuiibo, and firmware and pending-update inspection under Settings. Those are system-level operations a file manager does not attempt. The cost is that Goldleaf carries the warnings that come with them. ## Licence, build requirements and what a fork inherits Goldleaf is GPL-3.0. The Makefile shows one concrete consequence: the setup target builds libusbhsfs with BUILD_TYPE=GPL install. If you build from source, that flag is part of the normal path, not an optional extra. The repository also bundles or references Plutonium, libusbhsfs, libnx-ext and Quark as submodules or directories, so a fork inherits those components and their terms along with Goldleaf's own. This is a description of what the repository shows, not legal advice; if you plan to redistribute a modified build, read the licence texts of every component you ship. Upgrade cost is low on the user side. The About screen checks for the latest Goldleaf update and can update to a new release if one exists, so you do not have to fetch files by hand each time. The release history shows a 1.2.0 in December 2025 and a 1.2.1 in September 2026, with the last push to the repository on 2026-09-22. For a source build, the recurring cost is the submodule set: Plutonium, the libnx IPC extension, libusbhsfs and Quark all need to be present and buildable. Translations are contributed separately, and the README lists 11 languages, including English, Spanish, German, French, Italian, Dutch, Japanese, Portuguese, Korean, traditional Chinese and simplified Chinese. ## Conclusion Goldleaf suits Switch owners who already run homebrew and want one tool for NSP installs, content and ticket management, and remote file browsing. It is the wrong choice if you are not willing to handle tickets carefully, or if you expect the author to guarantee a working release: the README points at a Discord server for dev builds when the latest release is broken. Before installing anything, verify your firmware version and key generation under Settings, and make sure Quark is running on the PC before you try the remote browser. ## FAQ ### How do I use Goldleaf to install an NSP? Open the Explorer, go to the directory holding the NSP, and use the install operation: the README lists installing all NSPs inside a directory, and installing NSPs of games, updates and DLC from the file operations. The README warns you to use this carefully and know what you are doing. ### How does Goldleaf work with a PC? Goldleaf connects to Quark, a PC-side tool that exposes the computer's filesystem, and shows those files in the same Explorer used for the SD card. The README documents Quark setup separately for Windows, Linux and Mac. ### What is Goldleaf Switch? It is a multipurpose homebrew tool for the Nintendo Switch, written in C and built on libnx. Its feature set covers a filesystem Explorer, a game, update and DLC content manager, a ticket browser, a web browser, an account manager, amiibo dumping and firmware settings. ### How do I use the Goldleaf remote PC browser? Run Quark on the PC first, then connect to it from Goldleaf's Explorer; the remote PC appears as one of the supported locations. The README notes that all mounted locations, including the remote PC, are automatically unmounted when Goldleaf exits. ### How do I use Goldleaf? Launch it as an application on a Switch that already runs homebrew, then pick a function from the main menu: Explorer for files and NSP installs, the content manager for titles, updates and DLC, the ticket browser, or Settings for firmware and memory information. The README notes that all mounted locations are unmounted when Goldleaf exits. ## Sources - [Issues](https://github.com/XorTroll/Goldleaf/issues) - [License: GPL-3.0](https://github.com/XorTroll/Goldleaf/blob/master/LICENSE) - [README](https://github.com/XorTroll/Goldleaf/blob/master/README.md) - [Releases](https://github.com/XorTroll/Goldleaf/releases) - [XorTroll/Goldleaf on GitHub](https://github.com/XorTroll/Goldleaf) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/xortroll-goldleaf