Is there one minimum specification for every game?
The current project README says that compatibility and performance vary by game, hardware and driver and makes no universal frame-rate guarantee. The sources reviewed for this guide do not establish a single reliable minimum CPU, RAM and GPU combination for all Switch 2 games.
The repository includes an inherited Basics guide, which discusses Eden and older API requirements. Those inherited requirements should not be republished as proven Lichii Switch 2 specifications. Game-specific renderer features and current release changes can matter more.
First, check whether the package can run
| Platform | Checked build 125 package details |
|---|---|
| Windows | x86-64 ZIP, standard and PGO |
| Linux | x86-64 or ARM64; AppImage requires glibc 2.39+; tar.gz uses system libraries |
| macOS | Apple Silicon ARM64, macOS 15+ |
Check the official release notes for newer requirements before downloading. See Windows, Linux or macOS setup for installation steps.
Next, identify your hardware accurately
Write down your exact CPU, graphics card, RAM, operating system and graphics driver. On a laptop, note whether the emulator uses the integrated GPU or discrete GPU. On Linux, include the driver and Mesa version where relevant. On Mac, include the Apple chip and macOS version.
Avoid broad statements such as “I have an AMD PC.” The CPU vendor does not tell a reader which GPU or driver is involved.
Find a report for your actual game
Use the compatibility page to compare reports. Match the game version and build before looking at a performance number. A result should explain what was tested: a title screen, short gameplay, a particular area, or a longer session with saving and loading.
A stronger GPU alone does not prove a driver issue is resolved. For example, the Ocarina AMD crash tracker contains reports across several AMD GPU families. Read the matching problem rather than treating hardware price as compatibility evidence.
What if there is no matching report?
Use the nearest report as a starting hypothesis. If you decide to test, back up data and record the conditions. Do not advertise your result until you have distinguished startup, gameplay, rendering, input, audio and save/load behavior.
For stutter or a low frame rate after successful startup, follow the FPS guide. For progress preservation before experimenting, use update and backup.