Picture a Switch game as a locked building. Prod keys are the building master key — the " "keycard that opens every door in the structure. A title key opens one apartment: the single " "game it belongs to. Emulators always need the master key and only occasionally need the apartment key.
That one distinction answers most of the questions we receive. The rest is detail, and this page covers it in " "order.
What are prod keys?
Production keys are dumped from console hardware and stored as prod.keys. They carry the master "
"key generations, the titlekeks used to unwrap title keys, and the key area keys for the application, ocean and "
"system partitions — the layer that has to be cleared before an emulator can read a single game file.
When this file is missing or stale, nothing boots: no menu, no partial launch, just decryption errors. " "The full prod keys explainer traces where the keys come from and what each " "entry does.
What are title keys?
A title key is bound to one game and lives in title.keys. It is what makes a specific digital "
"title readable, so swapping games means swapping title keys. Modern emulators derive most of them on demand "
"from the master keys inside prod.keys — that is the part of the process that changed most over "
"the years, and the reason older tutorials overstate how often you need the second file.
How the three files relate
| File | Entity | What it unlocks | Do you need it? |
|---|---|---|---|
prod.keys | Production keys | System-level encryption — the root of the decryption chain | Always. No emulator works without it |
title.keys | Title keys | Individual digital titles and DLC | Sometimes — most are derived automatically from prod.keys |
| firmware files | System image | Runtime services a decrypted game calls while running | For most commercial games |
Feature-by-feature comparison
| Feature | Prod keys | Title keys |
|---|---|---|
| Purpose | Decrypt system-level encryption | Decrypt one individual game |
| File name | prod.keys | title.keys |
| Scope | Everything on the console | A single title or DLC pack |
| Required for | All encrypted content | Some digital titles and DLC |
| Updates with | Each firmware generation | Each game you add |
| Emulator support | Every emulator | Most modern emulators |
| Typical source | Console dump or the download table | Derived from prod.keys, or from a console dump |
Do you need both files?
Start with prod.keys alone. If one specific digital title or DLC pack refuses to launch while "
"everything else in your library works, drop a title.keys file beside it and retry — that "
"narrow failure pattern is the only reliable signal you ever needed one.
Keeping both files in the keys folder is harmless, but it is not the requirement older guides make it sound "
"like. What genuinely does matter is the version of prod.keys you hold: a stale master key set "
"fails no matter how many title keys sit next to it. "
"The version guide explains how to pick one.
Where does firmware fit?
Firmware is not a key file at all. It is the console operating system content — services, sysmodules, " "fonts and libraries — that an already-decrypted game calls while it runs. If a game starts and then hangs " "or crashes, keys have done their job and firmware is the missing piece. The " "Switch firmware guide covers the split, and " "prod keys not working maps each symptom to its cause.
Get the files
The current prod.keys file — and every version back to v16.1.0 — is in the "
"download table on the homepage, with firmware links beside it. Installing a dump from "
"your own console also produces title.keys in the same pass; see "
"how to dump prod keys, then follow the "
"install guide.