Retro gaming has exploded in popularity over the past decade. Collectors and casual players alike are no longer satisfied with just playing the games—they want the closest possible experience to the original hardware. This has created two dominant approaches: software emulators and FPGA-based recreations.

If you’ve spent any time in the retro community, you’ve probably heard people claim that FPGA systems have “zero latency” while emulators are laggy by nature. But is that actually true? Let’s break down the real differences between emulators and FPGA, and take a closer look at the latency question.

What Is a Software Emulator?

A software emulator is a program that runs on a modern computer, phone, or handheld and simulates the behavior of an old game console’s hardware. Popular examples include RetroArch, DuckStation, PCSX2, Dolphin, and Mesen.

Emulators work by interpreting or translating the original console’s instructions into something a modern CPU can understand. The better the emulator, the more accurately it recreates the original system’s timing, graphics quirks, and sound behavior.

Pros of emulators:

• Extremely convenient and inexpensive (or free)
• Easy access to save states, rewind, upscaling, and shaders
• Can run on almost any modern device
• Constantly improving accuracy through community development

Cons of emulators:

• Input lag can vary depending on the host system, display, and settings
• High-accuracy (especially cycle-accurate) emulation is very demanding on hardware
• Some systems are still not perfectly emulated

What Is FPGA Recreation?

FPGA stands for Field-Programmable Gate Array. Instead of simulating the original hardware with software, an FPGA is a reconfigurable chip that can be programmed to behave like the original console’s custom chips at a hardware level.

Projects like the MiSTer FPGA, Analogue Pocket, Analogue Nt Mini, and Analogue Super Nt use this approach. Rather than “pretending” to be a console, the FPGA is wired to function as a near-clone of the original silicon.

Pros of FPGA:

• Extremely high hardware accuracy
• Consistent, predictable performance
• Very low input lag when properly configured
• No reliance on a powerful host CPU

Cons of FPGA:

• More expensive than running emulators
• Limited to the cores that have been developed
• Less convenience features (save states, rewind, etc. are often limited or absent)
• Requires more technical knowledge to set up (especially MiSTer)

Key Differences at a Glance

Does FPGA Really Have Zero Latency?

This is the claim that gets repeated the most—and it’s also the most misunderstood.

The short answer is: No, FPGA does not have true zero latency. But it comes much closer to the original hardware experience than most people realize.

Here’s why the “zero latency” claim exists:

1. No software buffering layers Emulators run on top of an operating system. Even well-optimized ones have to deal with the host OS’s input polling, frame buffering, and display pipeline. FPGA cores talk more directly to the video output and controllers.
2. Cycle-accurate timing High-quality FPGA cores recreate the original console’s timing down to the clock cycle. This means the relationship between controller input and on-screen response is extremely close to the original hardware.
3. Lower display lag in practice When paired with a low-lag display (or a CRT), FPGA systems often measure under 1–2 frames of total lag from button press to pixel response. Many software emulators, even with run-ahead and frame delay enabled, struggle to match this consistency across different systems.

However, “zero latency” is marketing language. Every digital system has some delay:

• Controller polling still takes time
• HDMI signal processing adds a small amount of lag
• Modern LCD/OLED panels have their own response times
• Even original hardware on a CRT was never truly “zero lag”

What FPGA actually delivers is latency that is consistently very close to original hardware, and often lower than the average software emulator setup in the real world.

It’s also worth noting that modern emulators have closed the gap significantly. Features like run-ahead, frame delay, and rollback netplay mean that a well-tuned emulator on a powerful PC can feel extremely responsive—sometimes even better than original hardware in certain cases. The difference is that FPGA achieves this consistency with far less tuning and system load.

Which One Should You Choose?

There’s no universal winner. It depends on what you value most.

Choose FPGA if:

• You want the closest possible experience to original hardware
• Low and consistent latency is a top priority
• You’re willing to invest more money and time into setup
• You mainly play systems that have mature FPGA cores (NES, SNES, Genesis, Neo Geo, etc.)

Choose emulators if:

• You want convenience, portability, and features
• You play a wide variety of systems (including more modern ones)
• Budget is a concern
• You enjoy tweaking settings and shaders

Many serious retro enthusiasts end up using both. FPGA for the systems they care about most, and emulators for everything else.

Final Thoughts

The emulator vs FPGA debate often gets oversimplified into “FPGA is perfect, emulators are laggy.” Reality is more nuanced. FPGA offers outstanding accuracy and very low, consistent latency that closely matches original hardware. Emulators continue to improve rapidly and remain the most accessible way to play classic games.

If your goal is the purest possible experience with minimal lag, a well-set-up FPGA system is currently the closest thing we have to owning the original console—without the reliability issues of 30- to 40-year-old hardware. But for most players, a carefully configured emulator will still deliver an excellent experience.

The best approach is simply to try both and decide based on how it feels to you.