One frontend, a shelf of cores

RetroArch is an open-source emulator frontend, and the description has to start with what it does not do: it emulates no machine at all. The work is done by cores, reached through an interface called libretro, and each core corresponds to one machine or one family of hardware. The advantage of that split is that the interface, the gamepad mapping, the save system and the picture settings are configured once and then shared. The disadvantage is that the first session requires understanding the structure itself, and installing the program does not install any core.

That is an honest trade, and it is worth naming before the surprise arrives. A tool that does one machine is understandable in a minute and must be reconfigured for the next machine; a tool that does all of them must explain itself first and then never be reconfigured again.

Cores and content

Cores come from a built-in updater that downloads them on request, and the list is arranged by machine name. A game is then started in two steps - load a core, load content - and a local folder can be scanned to build a library automatically, with cover images fetched for the entries. A gamepad goes through one mapping routine the first time it is connected, after which every core uses the same set of bindings.

The features that live in the frontend rather than in the cores are the ones people notice most: save states, multiple save slots, fast forward and rewind. Because they sit above the core, they behave identically whichever machine is being emulated, and that consistency is worth more over time than any single feature.

Picture quality and the advanced end

There is a lot to adjust on the picture side. Shaders and filters can imitate the scanlines of a CRT, sharpen an image, apply anti-aliasing, or overlay a border; resolution, aspect ratio and integer scaling are each adjustable separately. The latency options - running a frame ahead, vertical sync - visibly change how a game feels, especially on modest hardware. Network play is handled by a dedicated mode, and the achievements system requires an account and triggers while the game is running. Recording and streaming are also present, which is convenient for commentary or for keeping a replay of a run.

Versions and one caution

It supports Windows, macOS, Linux and a number of handheld and television platforms. The stable version 1.22.2 was published in August 2026, and daily test builds exist alongside it. The caution that belongs here is a legal one rather than a technical one: RetroArch supplies only the environment in which emulation runs. Game images and BIOS files have to be provided by the user, and they should be files the user legitimately owns.

Why the structure is worth the first ten minutes

The cost of this design is paid entirely at the beginning, and it is small compared with what it replaces: a separate program for each machine, each with its own idea of where saves live, its own gamepad dialog and its own update mechanism. The benefit is not that the emulation is better. It is that the surrounding work - the part nobody enjoys - happens once.

For playing a shelf of older console games on a computer or a handheld, this is the least troublesome arrangement going: install the frontend once, fetch the cores as needed, and the gamepad, the saves and the picture settings apply everywhere. Understanding what a core is takes a few minutes, and what it buys is never configuring the same things again for each machine separately.