Lichii & Fritchii Firmware & Keys Setup

Setting up Lichii (build 316) or Fritchii (Fritchii v5.8.4) requires configuring your own legally dumped console decryption keys (prod.keys) and system firmware (.nca system archives) in the right directories. Because Lichii build 150+ moved to %APPDATA%\lichii and ~/.local/share/lichii while Fritchii v5.8+ moved to %APPDATA%\fritchii, placing files into old legacy folders is the #1 cause of blank game lists and startup errors. Every menu path, XDG folder and initialization error below is verified directly against zortos293/Lichii’s docs/user/QuickStart.md, Storage.md, src/common/fs/path_util.cpp and release notes on November 17, 2026.

Advertisement

Lichii Emulator Guide / Firmware & keys setup

A Nintendo Switch 2 console standing in its dock with both Joy-Con controllers attached

Strict legal & safety policy: Neither Lichii nor Fritchii ships keys, firmware or games, and this site hosts zero files and provides zero links to download prod.keys, firmware packs, BIOS archives or ROMs. Only use system files legally dumped from your own console. Websites advertising a “Lichii firmware + keys pack” are unauthorized and a frequent source of malware (see Is Lichii safe?).

Official setup via the Tools menu

Upstream’s docs/user/QuickStart.md recommends installing both keys and firmware through the built-in Qt interface rather than copying files manually, because the GUI validates filenames, clears stale registered NCAs, and initializes NAND directories cleanly:

Advertisement
  1. Launch the desktop GUI first: open lichii.exe on Windows, the .AppImage / lichii binary on Linux, or lichii.app on macOS (upstream’s README notes that command-line eden-cli should only be used after you have initialized keys and folders once in the GUI).
  2. Install decryption keys: in the top menu bar, click Tools > Install Decryption Keys and select your legally dumped prod.keys file. (If you also have an optional title.keys file, click File > Open Lichii Folder — or Open Fritchii Folder — and drop title.keys into the keys subfolder alongside prod.keys.)
  3. Install system firmware: click Tools > Install Firmware and choose either:
    • Install from a ZIP — points directly at a standard .zip archive containing your dumped firmware .nca files.
    • Install from Folder — points at an unpacked directory containing those .nca files.
    The emulator copies and registers the system content archives into nand/system/Contents/registered/ automatically.
  4. Add your game directory: double-click the central prompt on the home screen (or open Emulation > Configure... > General) to add the folder holding your legally dumped game packages (.nsp, .xci, .nup, or compressed single-file .nx archives supported since Lichii build 130 #923 and Fritchii v5.7).

Exact firmware and prod.keys folder paths by OS

Verified from src/common/fs/path_util.cpp and fs_paths.h in zortos293/Lichii, here is where each emulator and operating system reads keys, registered firmware, saves, shader caches and logs:

Emulator & OSDecryption keys (prod.keys)Registered firmware (.nca files)Saves, config & log paths
Lichii (Windows)
build 150+
%APPDATA%\lichii\keys\prod.keys%APPDATA%\lichii\nand\system\Contents\registered\Saves: %APPDATA%\lichii\nand\user\save\
Config: %APPDATA%\lichii\config\
Log: %APPDATA%\lichii\log\eden_log.txt
Fritchii (Windows)
v5.8 – v5.8.4
%APPDATA%\fritchii\keys\prod.keys%APPDATA%\fritchii\nand\system\Contents\registered\Saves: %APPDATA%\fritchii\nand\user\save\
Save backups: nand\user\save-backups\
Lichii (Linux & macOS)
XDG layout
~/.local/share/lichii/keys/prod.keys~/.local/share/lichii/nand/system/Contents/registered/Saves: ~/.local/share/lichii/nand/user/save/
Config: ~/.config/lichii/
Cache: ~/.cache/lichii/
Fritchii via Steam Proton
(Linux / Steam Deck)
.../compatdata/<AppID>/pfx/drive_c/users/steamuser/AppData/Roaming/fritchii/keys/prod.keys.../Roaming/fritchii/nand/system/Contents/registered/Full prefix root under ~/.local/share/Steam/steamapps/compatdata/<AppID>/ (Linux & Proton guide)
CheezyEmu / Eden
(legacy shared folder)
%APPDATA%\eden\keys\prod.keys
(Linux: ~/.local/share/eden/keys/)
%APPDATA%\eden\nand\system\Contents\registered\Used by CheezyEmu, Eden, and Lichii builds prior to build 150

macOS path heads-up: unlike native Cocoa apps that use ~/Library/Application Support/, Lichii’s path_util.cpp uses XDG directories on macOS too (~/.local/share/lichii, ~/.config/lichii, and ~/.cache/lichii, unless overridden by XDG_DATA_HOME / XDG_CONFIG_HOME). Using File > Open Lichii Folder inside the app always opens the active directory in Finder or Explorer.

Portable user folder and safe migration

  • Portable user/ directory mode: if you want to keep keys, firmware, saves and shaders on an external SSD or separate per-build test folder without touching %APPDATA%, create an empty folder named user in the exact same folder as lichii.exe (Windows) or your launch working directory (Linux/macOS) before opening the app. Both Lichii and Fritchii switch automatically to user/keys/, user/nand/system/Contents/registered/, user/config/ and user/cache/.
  • Automatic migration from Eden / Lichii:
    • Lichii build 150+ (#1253): imports your existing keys, NAND and saves from %APPDATA%\eden / ~/.local/share/eden into lichii on first launch when safe.
    • Fritchii v5.8 – v5.8.4: checks both %APPDATA%\eden and %APPDATA%\lichii on first run, picks whichever has your newest saves, and asks which items to copy (Saves, keys & profiles and Settings ticked by default; Mods & updates unticked so broken mods stay behind). You can re-run this anytime from Help > Copy Data from Eden or Lichii..., or copy saves two-way via the home-screen Saves button (v5.8.3+) and repair mismatched profile IDs with Saves > Fix (v5.8.4).

Firmware vs keys and version matching

  • What prod.keys handles vs what Firmware handles: prod.keys supplies console-derived AES/NCA header and master keys needed to parse and decrypt game containers (.nsp, .xci, .nup, .nx) and updates. Registered system firmware in nand/system/Contents/registered/ supplies shared system archives, Mii/profile data, time-zone data and Switch/Switch 2 font glyphs (for instance, controller face-button icons in Mario Tennis Fever showed “?” without firmware fonts until Lichii build 125 added a synthesized glyph fallback alongside firmware font loading, #691 & #821).
  • Matching firmware and key generations: use prod.keys and firmware dumped from the same updated console generation required by your game updates. Always install or upgrade firmware through Tools > Install Firmware rather than dragging new .nca files on top of old ones in File Explorer — manually mixing two firmware versions inside Contents/registered/ leaves duplicate system NCAs and causes startup aborts.

Fixing common initialization and missing-key errors

Symptom or error messageRoot causeVerified fix
“Decryption keys missing” badge in game listAdded in Lichii build 316 (#1503) so games are no longer hidden when keys are missing or incomplete.Click Tools > Install Decryption Keys and select a valid prod.keys. Build 316 also derives missing key generations automatically when the underlying master keys are present in prod.keys.
Missing specific key slot error
(formerly “bad header, please redump”)
Before build 316 (#1457), a missing newer key generation falsely blamed a corrupt game dump.Check the exact key name shown in the dialog or log/eden_log.txt; re-dump prod.keys from your updated console so the required master-key generation is present.
prod.keys placed in keys/ is ignored on WindowsWindows File Explorer’s “Hide extensions for known file types” saved the file as prod.keys.txt.Enable View > Show > File name extensions in Explorer and rename prod.keys.txt to prod.keys, or install it through Tools > Install Decryption Keys.
Game crashes or hangs when an older game update is installedIncompatible or stale update NCA registered in NAND alongside a base dump.Update to Lichii build 316 (#1504 ignores incompatible older updates cleanly, noted in Hyrule Warriors: Age of Imprisonment), or right-click the title > Remove > Remove Installed Update and reinstall the matching update.
Corrupted NAND after manual .nca drag-and-dropLeftover mixed firmware NCAs inside nand/system/Contents/registered/.Close the emulator, empty nand/system/Contents/registered/ (never delete nand/user/save/!), reopen the GUI, and run Tools > Install Firmware cleanly.

Recommended SDL3 controllers

Lichii reads gamepads through SDL3 (including HID command 300 motion). Standard Xbox pads have no gyroscope, so games that use motion aiming or tilt steering (such as Mario Kart World or Ocarina of Time) need a DualSense or aSwitch-style pad, while TMR/Hall sticks prevent drift:

ControllerGyro in Lichii (SDL3)Why pick itAmazon
Sony DualSenseYes (USB-C & Bluetooth)Confirmed working in Mario Kart World (#523); full SDL3 gyro on Windows, macOS & LinuxView on Amazon →
GameSir Cyclone 2Switch mode / PCTMR electromagnetic sticks (no drift) + Hall/micro-switch triggers for PC & Switch 2View on Amazon →
8BitDo Ultimate 2 BluetoothSwitch modeNintendo ABXY layout, TMR sticks and charging dock for Switch 2 & WindowsView on Amazon →
Xbox Wireless ControllerNo gyroPlug-and-play XInput on Windows & Steam Deck (named in upstream Deck notes)View on Amazon →

As an Amazon Associate, this site earns from qualifying purchases. Full button profiles and Linux udev rules: controller setup guide.

Advertisement
A heap of fresh lychees with their pink, bumpy shells, on a white ground
Lychees (Litchi chinensis).

Common questions

Does Lichii or Fritchii include firmware or prod.keys?

No. Both zortos293/Lichii and Frizti/Fritchii distribute open-source GPL-3.0 emulator code only. Neither project — and nothing on this site — hosts, bundles or links to Switch / Switch 2 decryption keys, system firmware or game ROMs. Only use files legally dumped from your own console.

How do I install prod.keys and firmware in Lichii or Fritchii?

Open the emulator GUI (lichii.exe or lichii), click Tools > Install Decryption Keys to select your legally dumped prod.keys file, then click Tools > Install Firmware and pick either Install from a ZIP or Install from Folder to register your dumped firmware .nca archives into the NAND system folder.

Where is the Lichii firmware and keys folder on Windows, Linux and macOS?

Starting in Lichii build 150 (#1253), Windows uses %APPDATA%\lichii\keys\prod.keys and %APPDATA%\lichii\nand\system\Contents\registered\. On both Linux and macOS, Lichii uses XDG paths: ~/.local/share/lichii/keys/prod.keys and ~/.local/share/lichii/nand/system/Contents/registered/ (macOS does not use ~/Library/Application Support/). Fritchii v5.8+ uses %APPDATA%\fritchii\keys\ and %APPDATA%\fritchii\nand\system\Contents\registered\ on Windows.

How do I make Lichii or Fritchii portable on a USB or second SSD?

Create an empty folder named user right next to lichii.exe on Windows (or inside the working directory on Linux/macOS) before launching the emulator. Upstream’s path_util.cpp detects user/ automatically and stores user/keys/, user/nand/, user/config/ and user/cache/ inside that local folder instead of %APPDATA% or ~/.local/share.

What does “Decryption keys missing” or a named missing key error mean in recent Lichii builds?

Since Lichii build 177 (and in build 316), games still appear in your game list with a “Decryption keys missing” badge and tooltip when keys are absent, and Lichii derives missing key slots automatically when the required master keys are present in prod.keys (#1503). If a newer key slot is missing, Lichii names the exact missing key instead of showing a misleading “bad header, please redump” message (#1457), and build 316 also plays solid .nsz files directly (#1734) and fixes Install Decryption Keys crashing when picking keys already inside keys/ (#891).

Do I need system firmware for every game, or are keys enough?

Decryption keys (prod.keys) are required to read encrypted game packages (.nsp, .xci, .nup, .nx), while installed system firmware (nand/system/Contents/registered/) provides system archives, Mii data and shared controller glyph fonts (for example, Mario Tennis Fever rendered “?” in place of controller icons without firmware fonts before build 125’s fallback, #691/#821). Installing matching console firmware via Tools > Install Firmware avoids missing-applet and font errors.