There is no single “correct” way to play an old game. Original hardware, FPGA systems and software emulation solve different problems—and most serious retro setups eventually use more than one.
The three approaches in plain English
Original hardware
The real console, controllers and media. It delivers the physical ritual and behaviour the game was built around, together with ageing components and a growing cable problem.
FPGA
Programmable logic configured to reproduce a machine’s circuits. Projects such as MiSTer run “cores” developed for particular consoles, computers and arcade boards.
Software emulation
A program models the old hardware on a modern PC, handheld or console. It is the most flexible route and ranges from wonderfully accurate to hastily configured.
Original hardware: maximum character
A cartridge clicking into place, a memory card whirring, the feel of the original pad and the soft image of a CRT are part of the experience. Original accessories also matter for unusual games: light guns, link cables, dance mats and specialist controllers do not always translate neatly to modern substitutes.
The trade-offs are maintenance and complexity. Capacitors age, optical drives wear, batteries leak and analogue video needs help on a modern television. Region locks and 50Hz conversions can complicate a UK collection. Original hardware is best for collectors who enjoy the machine as much as the software.
FPGA: purpose-built digital hardware
An FPGA does not run a conventional emulator in the same way a PC does. Its programmable logic is configured so that operations can occur in parallel, closely matching the timing relationships of the original machine. That can make input and video behaviour exceptionally convincing.
It is important not to turn that into mythology. A core is still an implementation created by people; its accuracy depends on documentation, testing and continued development. Controllers, USB polling, scalers and displays can introduce delay elsewhere. FPGA is not magic, but a mature core on a well-configured system is an elegant way to place many machines behind one HDMI or analogue output.
Software emulation: flexibility wins
Software emulation supports huge libraries, save states, rewind, netplay, translation patches, shaders and portable devices. It can also make demanding systems practical before an FPGA implementation exists. Strong emulators prioritise correctness and expose useful latency controls.
The weak point is configuration. A fast PC does not automatically mean an authentic result: run-ahead, audio buffering, refresh-rate matching, controller mapping and display mode all matter. Front ends such as Batocera reduce the friction, but a curated library is more enjoyable than a drive full of files you never browse.
Quick comparison
| Priority | Best starting point |
|---|---|
| Physical collecting and original accessories | Original hardware |
| Accurate timing with one tidy setup | FPGA, using mature cores |
| Low cost, portability and convenience | Software emulation |
| Later 3D systems | Original hardware or software emulation |
| Local multiplayer with authentic pads | Any route, provided the controller setup is good |
Our honest recommendation
Start with the experience you actually want. If you miss one particular console, buy a reliable example and a small set of games. If you want a living-room museum with minimal fuss, investigate FPGA. If you want to explore broadly, build a carefully configured emulation system and add original controllers through quality adaptors.
Whichever route you choose, obtain game images lawfully and keep backups of media you are entitled to use. Preservation is not improved by a disorganised or legally dubious library.
Further reading: the community-maintained MiSTer FPGA documentation and our Batocera guide.