Want a Raspberry Pi retro gaming setup that boots cleanly, finds the controller, plays the good stuff, and does not become a BIOS treasure hunt with HDMI cables? Start here.
A Raspberry Pi is still one of the nicest ways to build a compact retro gaming box. It is small enough to hide under a TV, cheap enough to experiment with, and flexible enough to become anything from a clean SNES-and-Genesis couch machine to a full-on tinkering station with shaders, scraping, controller profiles, save states, and a menu that looks like it was designed by someone who owned translucent plastic in 1999.
The trick is not to install the entire history of video games in one heroic sitting. Most messy Pi builds happen because people try to solve every system, every shader, every arcade ROMset, every wireless controller, and every BIOS file at the same time. A better approach is to pick one software lane, get five systems working well, and then expand only when the little box has earned your trust.
The Short Version
If you want the fastest path from blank microSD card to couch gaming, Batocera is usually the easiest appliance-like experience. If you want the classic Raspberry Pi emulation project with years of community answers around it, RetroPie is still the familiar route. If your Pi already runs Linux and you just want emulators added carefully, RetroArch on Raspberry Pi OS is the lighter, nerdier path.
Pick Batocera if...
You want a clean console-style interface, quick first boot, simple library management, and less time spelunking through Linux.
Pick RetroPie if...
You want the classic Pi project, tons of forum history, and enough tuning options to keep a rainy Saturday employed.
Pick RetroArch if...
Your Pi already has another job and you want emulation added as an app stack, not as the machine's whole personality.
Before Buying Anything, Pick the Job
The best Raspberry Pi emulation build is the one with a clear job. A kid-friendly TV box, a CRT experiment, a handheld test bench, and a "let me compare Super Nintendo cores at 1 a.m." device all want different choices. Decide whether this is a simple living-room console or a hobby project first.
What Hardware You Actually Need
You do not need a giant shopping list. You need a few boring parts that behave themselves. Boring is good here. Boring means you are playing Castlevania instead of reading power-supply forum threads.
- Raspberry Pi 4: the lowest-friction mainstream baseline if you want a snappy frontend, broad guide support, and strong 8-bit, 16-bit, handheld, arcade, and PlayStation 1 coverage.
- Raspberry Pi 5: more headroom and better hardware, but check your chosen image first. Support can differ by project and release.
- Raspberry Pi 3: still fine for NES, SNES, Genesis, Game Boy, Game Boy Advance, Neo Geo, and lighter arcade setups.
- A reliable microSD card: cheap cards create slow boots, failed writes, corruption, and mysterious "my emulator hates me" behavior.
- A correct power supply: undervoltage causes flaky USB behavior, controller disconnects, and instability.
- Cooling: even a modest heatsink-and-fan case helps if the Pi will live in a cabinet or run long sessions.
- One known-good controller: test with one wired pad first, then add Bluetooth controllers after the basics are stable.
A practical first target
For a first build, aim for five systems instead of fifty: NES, SNES, Genesis, Game Boy Advance, and PlayStation 1. That gives you a wide retro spread without immediately dragging you into the trickiest emulator edge cases.
Choose Your Software Lane
| Path | Best For | Work Level | Useful Links |
|---|---|---|---|
| RetroPie | The classic Raspberry Pi retro project experience | Medium | First installation, docs source, setup scripts |
| Batocera | A console-like setup that feels tidy from the couch | Low to medium | Getting started, add games and BIOS, downloads |
| Lakka | RetroArch-first builds with a lean interface | Medium | Raspberry Pi notes, downloads, Libretro docs |
| Raspberry Pi OS + RetroArch | A Pi that also does non-gaming things | Medium to high | Raspberry Pi Imager, Libretro Pi guide, RetroArch install docs |
If your goal is "I want a retro console under the TV," start with RetroPie or Batocera. If your goal is "I want emulators on a Pi I also use as a tiny Linux box," then RetroArch on Raspberry Pi OS makes more sense. If your goal is "I want to argue about shaders with myself," congratulations, you have discovered Lakka.
Step 1: Flash the Card Without Drama
The least annoying first move is Raspberry Pi Imager. Raspberry Pi's official software page describes Imager as the quick way to install Raspberry Pi OS and other operating systems to a microSD card. The official getting started docs also cover setup, networking, remote access, and troubleshooting.
- Pick the image that matches your Raspberry Pi model.
- Double-check the storage target before writing.
- Use OS customization where available so Wi-Fi, user settings, and remote access are ready on first boot.
- Label the microSD card after it works. Future you will not remember which tiny card is the good one.
RetroPie documents the SD image route as the easiest install path for most users in its first-installation guide, and Batocera's getting-started flow likewise begins by installing the image before adding games and BIOS files.
Step 2: First Boot Is for Stability
Your first boot is not the time for shaders, bezels, overlays, or importing a hard drive called "Definitely Organized ROMs Final Final 2." First boot is about making the machine act like an appliance.
Connect one controller
Map one pad, confirm hotkeys, and make sure menus are navigable before adding more devices.
Get networking working
Wi-Fi or Ethernet makes scraping, updates, SSH, and file transfer much easier.
Confirm audio and video
Fix display mode, aspect ratio, and audio output early. Many emulator problems are really TV output problems in costume.
Step 3: Add Games and BIOS Files the Legal, Organized Way
Important reality check
BIOS files and commercial game dumps are usually copyrighted. The clean rule is simple: use your own legally dumped media, public-domain software, freeware releases, or homebrew builds for testing.
Batocera's add games and BIOS guide lays out the basic pattern: BIOS files belong in the BIOS area, games belong in the correct per-system ROM folders, and some systems will not appear until suitable games are present. RetroPie has a similar mental model through its ROM transfer docs and per-system pages.
Good places to look for legal test material and community projects include itch.io homebrew games, PD Roms, PICO-8, Libretro's database project, and the Internet Archive software library where licensing and access vary by item. Read each page before downloading. A legal library is slower to assemble, but it is also less likely to come with broken files and weird mysteries.
- Keep ROMs sorted by system from the first import.
- Do not dump every file into one giant mystery folder.
- Use the frontend's BIOS checker or logs when something fails.
- For arcade, pay attention to ROMset version matching and shared BIOS files.
- Do not rename arcade ZIPs unless you know exactly why you are doing it.
Step 4: Start With Systems the Pi Handles Best
This is where a lot of Raspberry Pi guides drift into wishful thinking. A pretty menu does not magically make every N64, Saturn, Dreamcast, or PSP title behave. Build around systems the Pi handles confidently, then push upward later.
| Usually comfortable starting point | More setup-sensitive |
|---|---|
| NES, SNES, Genesis/Mega Drive, Master System, Game Boy, Game Boy Color, Game Boy Advance, PC Engine, Neo Geo, many 2D arcade boards | Nintendo 64, Dreamcast, PSP, Saturn, DOSBox configs, and arcade setups that depend heavily on exact emulator/core and ROMset choice |
| PlayStation 1 is often a good next step on stronger Pi hardware | Anything that tempts you into heavy shaders before the base setup is stable |
If what you really want is a smooth retro couch box, there is no shame in building an excellent 8-bit, 16-bit, handheld, and PS1 machine and stopping there. A setup that boots fast and plays well is better than a bloated setup that claims to run everything but makes you sigh before the title screen.
Step 5: Tune the Frontend Before Per-Game Tweaks
Once a few systems launch correctly, tune the shared experience before diving into per-title hacks.
- Set aspect ratio rules: decide whether you want original 4:3, integer scaling, or a more filled screen.
- Keep shaders off at first: add CRT effects later, after performance and latency feel good.
- Confirm hotkeys: menu, save state, load state, quit, and screenshot should be predictable.
- Scrape metadata after folder cleanup: it is nicer to scrape a clean library once than fix a messy one twice.
- Check audio latency: bad audio settings make everything feel worse even when frame rate looks fine.
If you are using RetroArch directly, Libretro's Raspberry Pi guide is worth reading because it calls out Pi-specific build and driver details. If you care about box art, manuals, videos, and metadata, also bookmark ScreenScraper, Skraper, and EmulationStation. Pretty libraries are optional, but they do make a tiny computer feel like a tiny arcade kiosk.
The Mistakes That Waste the Most Time
1. Treating power problems like emulator problems
A weak power supply creates random nonsense: controller disconnects, SD card corruption, stutters, and weird instability. Fix power first.
2. Importing a giant ROM collection before testing five games
Validate a few systems with a few known-good titles first. Scale comes later.
3. Chasing every best-settings video on day one
The clean setup is the one that matches your TV, controller, and Pi model. Copying random global settings often makes the machine worse.
4. Ignoring cooling
Thermals matter, especially once the Pi lives in a tight entertainment center next to other warm electronics.
5. Expecting perfect N64 and Dreamcast because the menu is smooth
The frontend being fast does not mean every heavier emulator target will be equally happy. Build expectations around the systems you most want to play.
If I Were Setting Up a Fresh Raspberry Pi Today
I would keep the first weekend intentionally boring, which is exactly how a fun little game box survives past Monday.
- Flash Batocera or RetroPie with Raspberry Pi Imager.
- Connect one wired controller and get the TV settings right.
- Add a tiny legal test library for NES, SNES, Genesis, GBA, and PS1.
- Confirm BIOS placement only for the systems that truly need it.
- Skip shaders until the base experience feels fast and consistent.
- Back up the working card image before getting adventurous.
- Add scraping, second controllers, and extra systems after that.
That approach is less dramatic than "install everything," but it is how you end up with a machine people actually leave plugged in.
Frequently Asked Questions
Is RetroPie still a good choice for Raspberry Pi?
Yes, especially if you like the traditional Raspberry Pi emulation project approach and want lots of community documentation around setup, controller mapping, and per-system behavior.
Should I buy a Raspberry Pi 4 or Raspberry Pi 5 for emulation?
Raspberry Pi 4 still has an easy setup path because guides and images commonly target it. Raspberry Pi 5 gives you more headroom, but confirm support in the exact frontend you plan to use before buying parts around it.
Is Batocera easier than RetroPie?
For many people, yes. Batocera tends to feel more appliance-like out of the box, which makes it attractive if your main goal is "plug it into the TV and play."
Do I need BIOS files for every retro system?
No. Some systems do, some do not, and arcade can get more complicated because specific boards or sets may rely on shared BIOS files. Check the documentation for the exact system and emulator you are using.
Should I build around RetroArch directly?
If you already run Raspberry Pi OS and want emulation added carefully, sure. If you want the simplest dedicated retro box, a full frontend stack like RetroPie, Batocera, or Lakka is usually easier to live with.
What is the biggest beginner mistake?
Trying to solve the entire emulation universe before making a handful of systems work well. Stable first, fancy second.
Useful starting links
Final Setup Checklist
- Choose the frontend before buying accessories or collecting files.
- Use a reliable power supply and microSD card before troubleshooting emulator settings.
- Start with systems that Raspberry Pi handles well.
- Keep BIOS files and ROM folders organized from the first import.
- Add shaders, scraping, wireless controllers, and heavier systems after the base build is stable.
- Back up the working card before changing major settings.
A clean Raspberry Pi retro gaming setup is not about having the longest menu. It is about a little box that turns on, recognizes the controller, launches the games you actually care about, and gets out of the way.