What if the console you grew up with could come back, not as a software imitation, but as real hardware logic rebuilt inside a chip? That is the promise behind three very different retro gaming paths: MiSTer FPGA, the Analogue Pocket, and RetroArch. They all play old games. They get there in ways that barely resemble each other, and those differences show up in the places that matter most: which games run, how the controls feel, and whether your save file survives a switch. (Field-programmable gate array (FPGA))
This guide breaks down compatibility, controls, and save files for each option, with a practical eye on what actually works in 2027 and where the traps hide.
Three Approaches, One Goal
Before comparing details, it helps to know what each device actually is.
MiSTer FPGA is an open-source project built around a DE10-Nano board. Community developers write hardware “cores” that recreate consoles and computers at the circuit level. It is not a commercial product, and nobody sells it as a finished console; you assemble it. The project’s own documentation explains how cores, setup, and storage work.
Analogue Pocket is a commercial handheld from Analogue that runs FPGA cores on a pocket-sized screen. It shipped in December 2021, plays original Game Boy, Game Boy Color, and Game Boy Advance cartridges through its slot, and added third-party core support through openFPGA in 2022. The openFPGA developer documentation describes how those cores are packaged and loaded.
RetroArch is not an emulator at all. It is a frontend for the libretro API, hosting emulator “cores” such as Beetle, Genesis Plus GX, and Mesen. It runs on phones, PCs, handhelds, and even TVs. The official libretro documentation covers the core list and general operation.
So you have open hardware, a polished commercial handheld, and free software that runs almost anywhere. Each one wins a different argument.
Compatibility: Breadth vs Accuracy
Compatibility is where the three split most sharply, and it is not a simple “more is better” story.
| Platform | Compatibility model | Strength | Weakness |
|---|---|---|---|
| MiSTer FPGA | Community-written hardware cores | Cycle-accurate recreation on supported systems | Narrower coverage; depends on volunteer work |
| Analogue Pocket | openFPGA cores plus cartridge slot | Plays real cartridges; portable | Core library smaller than software emulation |
| RetroArch | Software emulator cores | Huge range of systems | Accuracy varies widely by core |
RetroArch covers the most ground by far. If a system existed and someone wrote a core for it, RetroArch probably runs it. The catch is that software emulation accuracy swings wildly. A well-maintained core can be excellent; a neglected one may stutter, glitch, or fail on specific titles. Two games on the same system can behave differently depending on which core you pick.
FPGA cores take the opposite trade. When a core exists, it aims to recreate the original hardware’s timing and behavior rather than approximate it in software. That usually means fewer surprises, fewer per-game hacks, and a picture that behaves like the real thing. But coverage is limited to systems someone has implemented. There is no core for everything, and some cores are far more mature than others.
The Pocket sits between the two. Its cartridge slot is a genuine advantage: original Game Boy and Game Boy Advance carts work directly, no ROM files required. Its openFPGA library keeps growing, but it remains smaller than what RetroArch offers.
Legal Reality Check
None of the three ships copyrighted game ROMs. You supply your own dumps, or in the Pocket’s case, your own cartridges for the supported slots. FPGA projects and RetroArch distribute core and frontend software only. This is general practice across the scene, not a feature any of them advertises.
The 2027 Caveat
Here is the honest part. There is no reliable information about 2027-specific features, releases, or compatibility changes for any of these three. Any claim about next year’s roadmap should be treated as a projection, not a fact. What is stable enough to plan around is the architecture: open-source cores keep arriving, commercial firmware keeps updating, and software emulation keeps improving. Buy for what works today, not for an announced future.
Controls: Three Philosophies of Input
Controls sound like a minor detail until you spend an evening fighting a menu instead of playing a game.
RetroArch offers the deepest remapping system of the three. It uses a RetroPad abstraction, a virtual controller layout that maps your physical gamepad onto a standard set of buttons. Once a controller is recognized, autoconfig profiles handle most of the setup. You can remap per core, per game, or globally, and save those profiles. The tradeoff is complexity. The settings menu is famously dense, and beginners routinely get lost in it.
MiSTer maps USB and Bluetooth controllers per core through its on-screen menu. Setup is more manual than RetroArch’s autoconfig, but it is also more transparent: you see exactly what each button does for the core you are running. Practical tip: map one controller fully, test it in a demanding game, then save the configuration before touching another core. Copying a working setup beats rebuilding from scratch every time.
Analogue Pocket has built-in controls plus USB-C and Bluetooth controller support added through firmware. That firmware detail matters. Pocket Bluetooth behavior has changed across firmware versions, so check the current firmware notes before assuming a specific controller will pair the way you expect. What worked on launch firmware may behave differently after an update.
The pattern is consistent: RetroArch gives you the most control with the steepest learning curve, MiSTer gives you clear per-core control, and the Pocket gives you the simplest path with the least flexibility. (Service mesh architecture explained control plane data plane)
Save Files: Where Dreams Go to Die
If there is one area where retro gamers lose the most sleep, it is save files. The rules differ by mechanism, and misunderstanding them is the most common mistake in this hobby.
RetroArch uses standard battery-save formats, typically `.srm` files, plus save states stored as `.state` files. Battery saves are the game’s own save data, the kind written to a cartridge’s memory. Save states are snapshots of the entire emulator at a moment in time. The libretro save-state documentation is clear that states are core-specific: a state made in one emulator core generally will not load in a different core, even for the same game.
FPGA cores on MiSTer and the Pocket typically write battery saves to an SD card. Those files often match original hardware formats or common emulator formats, which is good news for moving a battery save between devices. Save states, however, remain core-specific and are not cross-compatible. Exact compatibility between MiSTer and Pocket save files is not standardized and changes with core versions, so verify per core rather than assuming.
| Save type | RetroArch | MiSTer FPGA | Analogue Pocket |
|---|---|---|---|
| Battery save | `.srm`, widely portable | SD card, often standard formats | SD card, often standard formats |
| Save state | `.state`, core-specific | Core-specific | Core-specific |
| Cross-device portability | Good for battery saves | Varies by core | Varies by core |
Practical Save Hygiene
A few habits prevent most disasters:
- Treat battery saves as your long-term data and save states as temporary convenience.
- Back up your SD card or save folder before updating cores or firmware.
- Test a save transfer on a throwaway file before moving a 40-hour playthrough.
- Keep notes on which core version created each save state, because updates can break them.
The single biggest mistake is assuming a save state will travel. It usually will not. Battery saves are the portable currency of this hobby.
Performance and Feel
Raw compatibility lists miss something players notice immediately: how a game feels.
FPGA cores aim for cycle-accurate timing, which often means input latency and audio behavior that match original hardware closely. Software emulation can be tuned to reduce lag, but results depend on the core, the display, and the settings. A well-configured RetroArch setup on a low-latency display can feel excellent; a poorly configured one can feel mushy.
The Pocket’s appeal is that it feels like a handheld should: instant, portable, and cartridge-ready. MiSTer’s appeal is flexibility and community momentum. RetroArch’s appeal is that it runs on the hardware you already own.
This is also where a related concept helps: the same separation of concerns that makes modern infrastructure reliable shows up in retro setups. Understanding how a service mesh architecture separates control plane from data plane is a useful mental model for thinking about frontends and cores as distinct layers.
Which One Should You Choose?
The right answer depends on what you value.
Choose MiSTer FPGA if you want hardware-level accuracy, enjoy tinkering, and are comfortable assembling and configuring a system. It rewards patience with a growing core library and a passionate community.
Choose the Analogue Pocket if portability and original cartridges matter most. It is the simplest path to accurate play on the go, provided your favorite systems have cores.
Choose RetroArch if you want the widest compatibility and already own hardware to run it on. It is free, flexible, and runs nearly everywhere, at the cost of setup complexity and variable accuracy.
Many enthusiasts end up with more than one. A Pocket for travel, MiSTer for the living room, RetroArch on a laptop for quick tests. That is not indecision; it is matching the tool to the job.
Conclusion
MiSTer FPGA, the Analogue Pocket, and RetroArch are not really competitors so much as different answers to the same question: how faithful do you want your retro gaming to be, and how much work are you willing to put in? FPGA hardware delivers accuracy on the systems it covers. The Pocket delivers portability and real cartridges. RetroArch delivers range and convenience. Controls range from deeply configurable to refreshingly simple, and save files follow one rule above all: battery saves travel, save states usually do not. Plan around that, back up often, and verify per core rather than trusting assumptions.
Frequently Asked Questions
Can I move my save files between MiSTer, Analogue Pocket, and RetroArch?
Battery saves often can move, because many cores write standard formats to SD cards or `.srm` files. Save states generally cannot, since they are tied to a specific core and version. Always test with a throwaway file first. (Web application firewall explained beginners it blocks it)
Is RetroArch an emulator?
No. RetroArch is a frontend for the libretro API that hosts emulator cores. The actual emulation is done by the core you load, such as Beetle or Genesis Plus GX.
Does the Analogue Pocket play original cartridges?
Yes. It supports original Game Boy, Game Boy Color, and Game Boy Advance cartridges through its cartridge slot, and it also runs third-party cores through openFPGA.
Which option is most accurate?
FPGA cores on MiSTer and the Pocket aim for cycle-accurate hardware recreation, which usually means higher accuracy on supported systems. RetroArch accuracy depends heavily on which core you choose.
Do any of these include games?
No. None of the three ships copyrighted ROMs. You supply your own dumps or cartridges, and the projects distribute core and frontend software only.
Are there confirmed 2027 features for these platforms?
No reliable information exists about 2027-specific features or roadmaps. Treat any future claims as projections and base your decision on what works today.
Whichever path you take, start small: pick one system, one controller, and one game you know well, then confirm the whole chain works before expanding. A single verified setup teaches you more than a dozen half-configured cores. Communities around MiSTer, the Pocket, and RetroArch are active and generous with troubleshooting help, and core documentation usually lists known issues and save behavior. Read it before updating anything you care about. Above all, keep playing. The point of accuracy, controls, and save management is to get out of the way of the games themselves.
