What Nintendo Switch Oled Journal Quick Actually Is
This is a homebrew tool that parses your Switch's save data and system logs to give you a readable timeline of activity. It pulls timestamped events from the journal entries on the console and formats them into something that doesn't require reading raw JSON files. If you have a jailbroken Switch OLED model, this saves you the headache of manually digging through /save/ directories or trying to parse binary log files. It only works on firmware versions 3.0 through 11.0.x, and even then, only on consoles that have SigMemes or KSuspend applied. If your console is on 11.0.0 or higher without any title signature patches, you are not going to get clean output. The tool simply cannot read the journal entries without them.
Nintendo Switch Oled Journal Quick Usage
Place the .nro file in atmoo/contents/externals on your microSD card, or however you normally run homebrew. Launch it from Homebrew Menu. You will see a tree view of your data. Navigate with the D-pad and L/R shoulder buttons. X opens a category, Y exports it, and the minus button takes you back. Simple enough. The export function writes a text file to /atmosphere/contents/externals/export/ on the card. You can then mount the card on a PC and copy the files wherever you need them. It also has a basic CSV option if you want to throw the data into a spreadsheet for analysis. The CSV output includes timestamp, title ID, event type, and a short description field.
How to Set It Up Correctly
First, make sure your payload is loaded and you are in hekate or Atmosphere. The tool reads directly from the console's NAND, so you need to be running it off the SD card while the system is booted into atmosphere. It will not function from the stock environment. That should be obvious but I have seen people try anyway. Your console must be in developer mode with sysmodule patches enabled. Without those patches, the journal entries come back garbled or empty. This means either a full custom firmware install or at minimum ksuspended state with the right boot arguments in your hekate config.txt. Specifically, you need the line "emummc_force_enable=1" only if you are using EmuMMC. If you are on sysNAND, skip that line. One thing that trips people up: the tool needs write access to the /atmosphere/contents/externals/export/ folder. If you created that folder manually on Windows, sometimes the permissions get set weirdly depending on your tool. Use a Mac or Linux machine, or the Switch itself via hbmenu, to create the folder. This took me two hours to figure out once on a project where I was trying to match play sessions against Joy-Con drift reports.
Get the Full Details
Practical Applications
The main use case is tracking down when something happened on your console. Did a game corrupt a save? The journal will show you the last few minutes of activity before the corruption event. Did your friend's console get banned? You can cross-reference the eShop login timestamps against your own activity to see if there was any overlap that might explain why your account got flagged too. This happened to me last year. I had shared my console with a friend who was running cracked games through a different account, and my account got a temporary suspension. The journal data showed exactly what he was doing and when, which helped me appeal effectively with Nintendo. It is also useful for documenting playtime for Speedrun.com or community verification. The timestamps are system-level, so they are harder to fake than in-game counters. Not foolproof but better than nothing.
What It Cannot Do
This tool does not recover deleted saves. It does not decrypt save data for you. It reads the journal entries, which are separate from the actual save files. If you are looking for a way to pull your game progress back after an accidental delete, this is not the right tool. You would need a proper save extractor like Goldite or a NAND backup instead. It also does not work on emulated console dumps. The journal is tied to the live system's hardware clock and NAND state. Trying to run it against a backup image just gives you empty results. Don't waste time on that. On firmware 11.0.0 and above, even with SigMes patches, the journal format changed slightly. The tool handles the transition but some older entries may not parse correctly. You will get gaps in the timeline around the firmware update window. This is a known limitation and there is no workaround other than accepting the missing data for that period.
Where to Get It
The tool is available on GitHub under the username generally associated with the hbmenu externals collection. The repository is typically listed alongside other Atmosphere homebrew utilities. Look for the latest release tag, not the main branch, because the main branch often has breaking changes before they are sorted out. The release .nro file is what you actually want. Download link: Check the official GitHub releases page for the Nintendo Switch Oled Journal Quick repository. The direct link changes occasionally when the maintainer reorganizes the repo, so searching the repository name directly is more reliable than following an old URL.
A Few Things to Keep in Mind
The output files can get large quickly. A week of normal play on multiple titles will produce around 40 to 60 megabytes of raw journal data. If you are exporting everything and not filtering by title, plan for that. I once exported three weeks of data without realizing it and nearly ran out of space on a small card. Filtering by title ID before exporting keeps the file manageable. The CSV export includes some redundant metadata in the description field that you will probably want to clean up with a simple find-and-replace in whatever text editor you use. The timestamps are in UTC. If you live in a timezone that is not UTC, do the conversion yourself. The tool does not do it for you. If your console uses EmuMMC and you are trying to journal the emulation environment, you need to make sure you are actually running the tool from the EmuMMC environment and not the sysNAND one. They have separate journal entries. I made that mistake once and spent an hour wondering why my sysNAND data showed nothing while the EmuMMC side was full. Checking which environment you were booted into fixed it immediately.
