Switch Firmware Fields on a Dump Listing
Every entry carries a firmware line. It describes the system version the content was built against, and reading it as anything else causes most of the confusion.
What the line on the entry is actually claiming
Every catalog entry carries a switch firmware line, and it is read wrong more often than any other field on the page. It is not a status report about your console, not an instruction, and not a hint about how new the game is. It records the minimum system version the packaged content declares it requires, a value written into the dump when the content was built.
Read that way, the field is narrow and useful. It answers one question: what the content expects to find underneath it. It says nothing at all about what is underneath it in your hands, which is a separate number kept in a separate place.
How the version string is shaped
The value is three numbers separated by dots, ordered major, minor, patch. The launch version of the platform, 1.0.0, is the cleanest example of the shape, and it is used here for exactly that reason rather than as any suggestion about what you should be running.
Two habits help. First, compare the positions in order rather than reading the string as a decimal number, because the middle and last positions move independently and a jump in one does not scale against the others. Second, resist inferring size of change from position. A patch level increment can carry a change that matters to compatibility, and a minor increment can be quiet.
We deliberately do not print a current figure anywhere on this site. Numbers like that age within weeks and then circulate as if they were still true, which is worse than leaving the reader to check a live source.
Why content declares a requirement at all
A title is built against a set of system libraries and services. When those gain behavior a title relies on, the title records the version where that behavior appeared, so the system can refuse rather than fail in some unpredictable way further in.
This is also why the field varies within one game. A base title, a patch, and add-on content are separate objects with separate build dates, and each carries its own declaration. A patch shipped long after release commonly declares a higher value than the base it modifies. When they differ, the highest declaration in the set is the one that governs, not the one printed largest on a listing.
Where to read the number that belongs to your hardware
The console keeps its own version and reports it in System settings, under the system information screen. That figure is the only authoritative answer for your machine, and it is the one to compare a listing against. The relationship between the two numbers has enough nuance to deserve its own page, which is console version versus build target.
The practical rule is short. If the value declared by the content is higher than the value the console reports, the content is asking for something the console does not yet claim to provide. That is a mismatch to understand, not a defect in the dump.
When the numbers disagree with each other
Sometimes the disagreement is between the catalog line and the file itself. In that case the file wins: the declaration lives inside the content, and the listing is a transcription that can be wrong. Note the slug, note both values, and Report an issue so the entry gets corrected rather than quietly copied forward.
Sometimes the disagreement is between pieces you are assembling, and the fix is to check what you actually hold. The container types and how they carry metadata are covered in dumps versus cartridges, and if you need the entries themselves, Open the catalog.