Emulation Done Properly — Accuracy, Input Lag and the Legal Position
Emulation is easy to do badly. Here's how to get accurate timing, low input lag and a setup that doesn't fight you.
The short answer
Good emulation depends far more on accuracy and input latency configuration than on raw hardware power, because a fast machine running a poorly configured emulator still feels wrong. The key settings are matching the emulator's internal frame pacing to your display, enabling run-ahead where supported to cancel inherent input lag, and using an accuracy-focused core rather than a speed-focused one for older systems. Legally, you must own the original media to dump your own copies; downloading ROMs you do not own is copyright infringement.
Verified and last updated August 12, 2026.
- Time needed
- 16 min
- Difficulty
- Intermediate
- Read time
- 4 min
Emulation has a reputation for being fiddly, and the reason is that the defaults in most emulators prioritise compatibility with weak hardware rather than feeling correct on a modern machine.
Configured properly, it can feel as immediate as original hardware. Configured with defaults, it feels subtly wrong in a way that is hard to name.
The legal position, stated plainly
The emulator is legal. The game files are the issue. Dumping from media you own is generally accepted in many jurisdictions; downloading games you do not own is copyright infringement whether or not the game is still sold. The "delete within 24 hours" rule people repeat is entirely fictional and has never been law anywhere.
The three settings that matter
Run-ahead is the big one
Emulation adds latency layers that the original hardware did not have — emulator buffering, the OS compositor, display processing, a wireless controller. Each adds a few milliseconds and together they are perceptible.
Run-ahead works by simulating frames ahead of what you see and discarding them, so that when you press a button the response is already computed. Setting it to one or two frames typically cancels the entire added latency.
Start at 1 frame of run-ahead 2 min
Test the game. Most systems tolerate one frame with no side effects and the difference in responsiveness is immediately obvious.
Try 2 frames if the machine can handle it 5 min
Run-ahead costs CPU because the emulator is effectively running multiple times per frame. Two frames is usually the practical ceiling for older systems on modern hardware.
Reduce it if audio glitches or performance drops 2 min
Those are the symptoms of asking for more than the machine can deliver. Back off one frame.
Frame pacing
Old consoles did not run at exactly 60 Hz. Many ran at 59.94, some at 50, and a few at genuinely odd rates. Forcing that onto a modern 60 Hz display produces a dropped or duplicated frame periodically, which shows as a hitch in smooth scrolling.
Options, in order of preference:
- A display supporting variable refresh rate. The cleanest solution — the display simply matches whatever the emulator outputs.
- The emulator's own frame pacing option, which resamples audio slightly to match your display exactly.
- Accepting the occasional dropped frame, which is genuinely fine for many games.
Accuracy versus performance cores
For anything up to the 32-bit era, use the accurate core. Modern hardware handles cycle-accurate emulation of those systems comfortably, and the compatibility benefit is real — the games that break on fast cores are exactly the ones doing clever hardware tricks, which is often the interesting software.
Performance cores exist for weak hardware and for newer systems where accuracy is genuinely expensive. If your machine can manage accuracy, use it.
Shaders: not just nostalgia
CRT shaders have a technical argument behind them. A great deal of pixel art was drawn assuming a CRT would blend adjacent pixels and soften dithering — artists used that blending deliberately to create colours and gradients that do not exist in the raw image data.
Displayed sharp on an LCD, that art shows the individual pixels the artist intended you to see blended. A CRT shader restores the intended appearance. Whether you prefer it is taste, but the case for it is not sentimental.
What works
What doesn't
Key takeaways
Frequently asked questions
Is emulation legal?
The emulator software itself is legal in most jurisdictions — it is clean-room software that reimplements hardware behaviour. The legal issue is the game files. Dumping a copy from media you own is generally accepted in many places, though the specifics vary by country, and downloading games you do not own is straightforward copyright infringement regardless of whether the game is still sold. The common claim that it becomes legal if you delete it within 24 hours is entirely fictional and has no legal basis anywhere.
Why does emulation feel laggier than the original console?
Because you have added several layers that did not exist: the emulator's internal buffering, your operating system's compositor, the display's processing, and often a wireless controller. Each adds a few milliseconds and they accumulate into something perceptible. Run-ahead, where supported, cancels most of it by simulating frames in advance, and it is the single most effective setting for making emulation feel like original hardware.
Should I use an accuracy core or a performance core?
Accuracy for older systems, because the hardware is simple enough that any modern machine can run a cycle-accurate emulator comfortably and the compatibility benefit is real. Performance cores exist for weaker hardware and for newer systems where accuracy is computationally expensive. If your machine can handle the accurate option, there is no reason to use anything else.
Do shaders and filters make old games look better?
They can, and CRT shaders in particular are doing something legitimate rather than merely nostalgic — a great deal of pixel art was drawn with the assumption that a CRT would blend and soften it, and sharp modern pixels can look wrong in ways the artists never intended. Whether you prefer it is taste, but the argument for CRT shaders is technical, not sentimental.
What hardware do I need?
For systems up to the 32-bit era, almost anything including a modest laptop or single-board computer. Later systems need considerably more, and the most demanding emulators require a strong CPU with high single-thread performance more than a powerful graphics card. Check the specific system's requirements rather than assuming a generally fast machine will handle everything.
About the author
PC Hardware & Performance Editor
Marcus has been building, breaking and repairing gaming PCs since 2011, first as a weekend favour for friends and then for eight years as a bench technician at an independent repair shop in Portland, where roughly a third of the job was diagnosing machines that "ran fine yesterday".
Found something wrong? Games patch and fixes go stale. If a step here no longer works, tell us at hello@spyld.com and we will retest it. Read how we test and our editorial policy.