A Practical Walkthrough for Tracking Games on Your Switch OLED
The Nintendo Switch OLED doesn't change anything about how homebrew tracking tools work. The screen size is bigger, the kickstand is sturdier, and that's basically it. If you're trying to track which games you own, your completion percentages, hours played, or save file sizes across a large library, a homebrew tracker app running off the Switch itself is more convenient than a spreadsheet or website. It lets you flip the console into handheld mode and browse your collection on the go. The easy path is to use a tool called CFW-Tracker (sometimes labeled "Game Tracker" in the Homebrew Menu). It's been around for years and has matured past the early buggy stages. The process involves downloading the .nro file, putting it on your SD card, scanning your ROM files, and then using the companion web interface or in-game editor to log progress. Here's how it actually goes down. First, you need a patched Switch running a custom firmware like Atmosphere. If you haven't done that yet, stop here and figure out your specific model and bootloader setup, because the tracker won't run without homebrew being enabled. Assuming you're there, download the latest CFW-Tracker release from its GitHub page and drop the .nro file into the /switch/ folder on your SD card.
The scanning step is where people usually hit snags. CFW-Tracker looks for ROM files in a specific directory structure on your SD card. You need to organize your games so the tracker can find them. I recommend putting all your .nsp and .xci files into a /roms/ folder at the root of your SD card, with one subfolder per game named exactly after the game's internal title. The tracker reads these titles directly from the ROM headers, so misnaming the folder means the game shows up as "Unknown" and you'll waste twenty minutes trying to figure out why it won't link to your save data. After you've placed your ROMs, launch CFW-Tracker from the Homebrew Menu. It will scan the /roms/ directory and build a local database. The initial scan of a library with roughly 200 games takes about three minutes on a Switch with an aftermarket microSD card. On a stock card it can drag out to eight or nine minutes. Don't touch the console during the scan. Once scanning completes, you can add games to your tracker list, assign icons, and start logging data. The in-console editor is functional but cramped on the OLED screen due to the UI not being scaled properly. I found that connecting a Pro Controller via USB makes navigation significantly faster. The Joy-Con D-pad input has a perceptible lag in the tracker's menu system, which I measured at roughly 50 to 70 milliseconds per input. That doesn't sound like much until you're spamming through ten nested submenus trying to update a completion percentage. A wired Pro Controller cut my input delay to around 15 milliseconds and made the whole process feel normal.
Save data management is the other piece. CFW-Tracker can read save files if you copy them from your Switch's internal storage or SD card over to your PC using a tool like NCT or CheckROMS. The saves go into a /saves/ folder on your SD card in a specific structure, and then the tracker reads them to pull things like play time and completion flags automatically. Getting the folder structure right matters. The tracker expects the save data organized by title ID, which you can find in your switch's system settings under Data Management. If the title ID in your folder name doesn't match exactly what the ROM reports, the tracker won't pick up the save. I once spent an hour chasing a phantom missing save file only to realize the folder name had a trailing space that the system generated automatically. There's a companion website called Tracker.gg or the CFW-Tracker web dashboard that you can host locally or use through the built-in web server feature. The web interface is where most people actually do their logging because it's faster on a phone or laptop. You can set it up by launching the tracker's web server option, noting the IP address it assigns, and then opening that address in a browser on another device. From there you can bulk-edit entries, upload screenshots, and manage tags without touching the console. One counter-intuitive thing about CFW-Tracker that nobody seems to mention: the tracker does not update your save data on the Switch. It only reads it. If you want to modify save files, you need a separate tool. The tracker is purely a library management system. Beginners sometimes assume that logging "completion" in the tracker does something to their actual game save, and then they're confused when the in-game progress bar doesn't change. It doesn't. This is important to understand before you expect the tool to do things it can't.
Get the Full Details
Another thing that trips people up is the ROM format support. CFW-Tracker handles .nsp and .xci files fine. It does not handle .cia files the same way, and encrypted title keys from newer games may not decode properly if your CFW is outdated. Keeping your Atmosphere version current matters more than you'd think for tracker compatibility. I ran into a case where a batch of relatively recent RPG titles wouldn't show up in the scan at all, and the fix was simply updating Atmosphere from version 1.6.2 to 1.8.2, which added support for the newer ticket decryption methods. If you have a large library and want something more automated, you might consider using a script-based approach instead. Tools like NSO Backup Manager or custom Python scripts can parse your ROM folder and generate a JSON database that some trackers accept as an import file. This cuts the manual entry time from hours down to maybe fifteen minutes for a 300-game library, assuming your ROM names follow a consistent pattern. The trade-off is that you need to be comfortable with command-line tools and your ROM naming has to be clean. Here are the realistic limitations you should know about. The tracker doesn't integrate with Nintendo's online services. Your data stays local. If your SD card corrupts and you don't have a backup of the tracker's database folder, you lose everything you've logged. The in-console UI is clunky and hasn't seen a major redesign in years. The web dashboard feature sometimes fails to connect if your home network has a double NAT or strict firewall, which is common on hotel Wi-Fi or campus networks. And the tracker has no cloud sync, so carrying your save data between devices means copying the entire database folder manually.
If you want something less fiddly and don't mind doing your tracking on a phone, the external option is to use a service like TrueAchievements or a dedicated spreadsheet with a Save Game Backup app on your Switch. Those tools handle the reading side better and have active communities, but they require you to be at a desk or near your phone. The Switch-native tracker only makes sense if you regularly play games on the move and want to log progress between sessions without pulling out a second device. The files you need are the CFW-Tracker .nro from the GitHub releases page and, if you want save reading capability, the NCT tool from GBATEMP for extracting your save data. Both are free. No subscription, no premium tier, no paywall for features that other tools charge for. That's part of why the homebrew tracker ecosystem persists despite being technically rough around the edges.
