So in this guide I will use the words “emulators” and “cores” interchangeably. RetroArch consists of what they call “ cores“, which function as emulators embedded in the program. I have a habit of pronouncing it the latter way, which is what you’ll hear in my videos. Note that technically, “RetroArch” should be pronounced like “RetroARTCH” versus “RetroARK”, because it was first based on Arch Linux, but both pronunciations are considered acceptable. The frontend for RetroArch is often referred to as the “libretro frontend”. It can run on the usual platforms like Windows, MacOS and Linux, but it also runs on iOS and Android for tablets and phones, as well as on game consoles like PS2, PS3, PSP, PS Vita, Wii, Wii U, 2DS, 3DS, Switch, and more. RetroArch is a frontend for emulators, game engines and media players.

However, if you are using a system that relies primarily on RetroArch for emulation (like Xbox), or you have a beefy PC that can run well regardless of optimizations, you may find success in emulating higher-end systems in RetroArch, too. For more modern consoles, it is often more efficient to rely on standalone emulators, which are generally more optimized than RetroArch. RetroArch really shines on retro systems, particularly PlayStation 1 and below games. The video will primarily be done on Windows PC, but the same method will apply to MacOS, Linux, Android, iOS, Vita, and Xbox platforms, and more. This guide is meant to help you get set up with various RetroArch iterations. In this guide I’m going to demystify some of the more peculiar things about this emulation frontend, and show you how I set up RetroArch on my own gaming platforms. But it does have quite a steep learning curve. RetroArch is one of my favorite programs to use for retro game emulation, because it can emulate many systems. Last updated: 28FEB2022 (see Changelog for details)

Final burn alpha rom set retropie