RetroArch is the most powerful retro gaming application ever written, and the most intimidating to configure. It is a frontend that turns your PC, phone or console into a machine that plays almost every retro system ever released, using small plugins called cores. The trade-off is that RetroArch was built for people who love settings, and its menu can feel like a control panel for an aircraft. This guide is the honest walkthrough you need: what RetroArch actually is, how to install it without breaking anything, which cores to choose, the settings that matter and the ones to ignore, and how to make your games look and sound the way they were meant to.
What RetroArch Actually Is
RetroArch is not an emulator. It is a frontend that loads emulators, and understanding that one sentence saves you hours of confusion. The emulators themselves are called cores, and they are the same engines used by many standalone emulators, rewritten or wrapped to run inside RetroArch. The frontend gives every core the same menu, the same input system, the same save system and the same video and audio pipeline, which is why one app can play a NES game and a PlayStation 1 game with identical controls and identical save menus.
The other thing to know is that RetroArch is free software, distributed under the GNU GPL license. It runs on Windows, macOS, Linux, Android, iOS, Raspberry Pi, and on consoles that allow homebrew. The versions differ in small ways, but the core concepts and the menu structure are the same everywhere, so learning it once transfers to every device you own.
How to Install RetroArch Safely
The download page is the first trap for new users, because RetroArch is offered in stable, nightly and development builds, and the differences matter. The stable release is the version that has been tested and frozen; it is the right choice for almost everyone. Nightly builds are updated every day and can fix bugs, but they can also introduce new ones, and they are for people who want to test. The development builds are exactly what they sound like, and you should not use them unless you know what you are doing.
Download RetroArch only from the official site, retroarch.com, or from your platform official app store. A quick warning: search results are full of fake RetroArch downloads that bundle adware and malware, and the official project itself warns users about this every year. Verify the domain, verify the checksum if the site provides one, and never install RetroArch from a random YouTube description or a forum attachment.
On Windows the installer is straightforward, and the default options are fine. On Android, the official build is on the Google Play Store, plus older builds on the official site. On Raspberry Pi, RetroArch comes as part of RetroPie, which I covered in my Raspberry Pi retro gaming guide, so you get it as part of a larger setup rather than alone. On macOS, use the official .dmg and check the security prompt, because macOS will flag unsigned apps the first time.
Choosing the Right Cores
Your library of games is only worth anything if the cores you load are good, and the honest rule is that one core per system is enough. Here are the cores I recommend for the most popular retro systems, based on accuracy, speed and compatibility.
Nintendo Systems
For the NES, the core to use is Mesen, the gold standard for NES emulation, or FCEUmm if you need something lighter on an old machine. For the SNES, use Snes9x, which balances speed and accuracy, or bsnes if you have a powerful PC and want cycle-accurate emulation. For the Game Boy, Game Boy Color and Game Boy Advance, use Gambatte and mGBA, both excellent. For the N64, use ParaLLEl or Mupen64Plus-Next; N64 emulation is still imperfect, and on some games you will need to try both to find the better result.
Sega and Other Systems
For the Sega Genesis and the Game Gear, use Genesis Plus GX, which is accurate and light. For Sega CD, Genesis Plus GX also works well. For the Master System, the same core covers you. For arcade games, use FinalBurn Neo or MAME; FinalBurn Neo is easier to set up for a curated set of games, and MAME is the encyclopedic option, which I explain in my article on retro arcade games.
PlayStation and Modern Systems
For the PlayStation 1, use the Beetle PSX core, which is accurate and well maintained. For the Sega Saturn and Dreamcast, use Beetle Saturn and Flycast; Saturn emulation remains demanding, and Flycast is the best way to play Dreamcast on modest hardware. For newer systems like the Nintendo 64 and the PlayStation 2, the situation is different, and I cover the full legal and technical picture of emulation and ROMs in my dedicated guide.
The Settings That Matter
RetroArch has hundreds of settings, and most of them you will never touch. The settings that actually matter are these four: video, audio, input and saves. Getting them right once will make every game you play work correctly.
Video: Run-Ahead, VSync and Shaders
The video settings control how the games look and how responsive they feel. VSync prevents screen tearing and should stay on. Run-ahead is a unique RetroArch feature that reduces input lag by predicting frames; it can make old games feel significantly snappier, and it is worth experimenting with if you play fast action games. Shaders are the effects that emulate a CRT screen, scanlines and other display characteristics, and they are the single biggest visual upgrade you can make, which is exactly the topic I covered in my CRT and upscaler guides.
Audio: The Setting Nobody Checks
The audio settings matter more than people think, and the default is not always the best for every core. The audio driver should be set according to your platform default; on most computers the default works fine. The important detail is to check that audio and video are synchronized, otherwise you get crackling or stuttering. Some cores also have their own audio options, like the PlayStation cores with their interpolation settings, which can subtly change the sound quality.
Input: Controllers and Hotkeys
The input settings are where RetroArch shines and where most new users get lost. RetroArch has its own controller mapping system, and you can remap buttons per core, per game or globally. The honest advice is to set the global mapping once and let each core use it. Hotkeys are a separate system: they let you use your controller to save, load, open the menu and exit, and they are the difference between a setup that feels like software and one that feels like a console.
Saves: Save States and In-Game Saves
RetroArch separates save states from in-game saves, and understanding the difference saves you lost progress. Save states are snapshots of the entire console state; they are created and loaded instantly, and they are the emulator equivalent of a rewind button. In-game saves are the normal saves the games themselves write, and they are stored in per-core folders. The practical advice is to rely on in-game saves for long games and use save states for quick sessions, because over-relying on save states can leave you with progress that does not work anywhere else.
The Honest Performance Guide
How well a game runs depends far less on the hardware than people expect. A Raspberry Pi 4 runs the 16-bit and older systems comfortably, a mid-range PC handles PlayStation 1 and most N64 games, and only the newest systems, like the Saturn at full accuracy, demand a strong machine. This table shows the honest expectations for common hardware.
| Hardware | Plays comfortably | Struggles | Best for |
|---|---|---|---|
| Raspberry Pi 3/4 | NES, SNES, Game Boy, Genesis, GBA | N64, PS1 at full speed | RetroPie, low budget builds |
| Old office PC | All 16-bit, PS1, most N64 | Saturn, demanding arcade | Cheap emulation box |
| Mid-range PC | Everything up to PS1, N64, Dreamcast | Full-accuracy Saturn | The all-round RetroArch machine |
| Gaming PC | Everything RetroArch supports | Nothing practical | Shaders, run-ahead, heavy cores |
| Android phone | All 16-bit, GBA, most PS1 | N64 at full speed | Portable retro gaming |
| Nintendo Switch (payload) | Up to PS1, most N64 | Runs in homebrew mode only | Handheld all-in-one |
The single most useful hardware upgrade is not a faster CPU; it is a CRT or a good upscaler, because how the picture is displayed changes the experience more than any core setting. That is the exact topic I explored in my CRT guide and my guide to playing retro games on a modern TV.
The Legal Picture
RetroArch itself is completely legal: it is open-source software, and it does not come with games. The legal question is always about the games, and the answer is the same one I gave in my emulation and ROMs guide: owning the game, legally, is the only safe way to play it. Emulation is not stealing, and owning the hardware does not automatically give you the right to download every ROM. The honest rule is simple: dump your own games, keep the files you have the right to, and use the legal services I listed in my guide to playing retro games online.
Frequently Asked Questions
Is RetroArch safe to download?
Yes, if you download it from the official site or your platform store, and no, if you get it from random sites that fake the RetroArch name. Check the domain, check the checksum, and never run a downloaded emulator from an untrusted source.
Which retro systems can RetroArch play?
Virtually all classic systems: NES, SNES, Game Boy, Game Boy Color, Game Boy Advance, N64, Sega Genesis, Sega CD, Game Gear, Master System, PlayStation 1, Saturn, Dreamcast, arcade games and many more. The list depends on the cores you install.
Why is my game running slow?
Usually because the core, the video settings or the hardware are mismatched. Try a lighter core, turn off heavy shaders, enable VSync, and check that the audio and video drivers are synchronized. On older hardware, dropping to a lighter core like FCEUmm or Snes9x fixes most slowdowns.
Do I need a powerful PC for RetroArch?
No. A Raspberry Pi handles most 8-bit and 16-bit systems, and a modest office PC handles PlayStation 1 and most Nintendo 64 games. Only the newest and heaviest cores demand a gaming machine.
Can I use my original consoles controllers?
Yes. Original controllers can be used with USB adapters, and wireless versions exist for many classic systems. RetroArch treats them as normal controllers, and the input mapping system lets you assign every combination.
Make the Setup Yours
The magic of RetroArch is that after the initial configuration, every system you play has the same menu, the same saves and the same controls, which no other emulator setup offers. The honest conclusion is that the first hour is the hardest and the rest is pure payoff: install the stable build, pick the right cores, set the four settings that matter, and enjoy the single best way to play the games you own.
