A game running at double speed, or crawling in slow motion, is a pacing problem: something is stopping Snes9x from holding the emulated SNES at its proper rate. The causes range from a key you are leaning on without realising, to a sync option switched off, to a display refresh mismatch. Work through the checks below in order — the first one fixes an embarrassing number of cases. Everything here assumes the current 1.63 build from our download page; the troubleshooting hub collects the rest of our fixes.
Check 1 — Are you holding the turbo key?
Snes9x’s fast-forward is the Tab key, and it is momentary: the game speeds up for exactly as long as Tab is held. If your game suddenly races every time you lean on the keyboard, rest a controller on the desk, or use a keyboard layout where something sits on Tab, that is your answer. There is also a separate fast-forward toggle in the hotkey list (unassigned by default) — if you ever bound it to a key and pressed it, the game stays fast until you press it again. Open Input → Customize Hotkeys and check what fast-forward and turbo are bound to before changing anything else.
Check 2 — Frame limiting and VSync
Left to itself, a modern PC can emulate a SNES far faster than real time, so Snes9x relies on its frame-limiting options to hold the correct pace. In the display/emulation settings, make sure frame skipping is set sensibly and that the option to limit the frame rate (tied to VSync on the video side) is enabled rather than disabled. With limiting off, games run as fast as your hardware allows — fun for grinding, wrong for everything else. With VSync driving the pace, the emulator syncs to your monitor’s refresh cycle, which is also why the next check matters.
Check 3 — Refresh-rate mismatch
SNES games were built for the television timing of their era. If your monitor runs at a much higher refresh rate and the emulator is syncing to the display, pacing can feel off — subtly uneven, or slightly fast or slow depending on how the sync lands. If you use a high-refresh monitor and speed feels wrong with VSync on, try the combination the other way: let the sound sync govern pacing (next check) with VSync off, and compare. There is no single correct pairing for every monitor and GPU driver, so treat this as an A/B test on your own machine rather than a universal rule.
Check 4 — Sync to sound
Snes9x can pace emulation from the audio side instead: the Sound Settings option “Synchronize with sound core” keeps the whole machine locked to the sound stream. If it is disabled and your frame limiting is also loose, speed can wander. Enabling it gives the emulator a steady clock, and it is the same option the official readme recommends first for audio crackling — pacing and sound quality are two sides of the same coin in Snes9x. If enabling sound sync makes audio worse on your system, work through that crackling guide’s buffer and input-rate steps alongside this one.
Check 5 — Slow games: is it the game or your PC?
Persistent slowdown in every game suggests the PC is struggling — check that nothing heavy is running alongside, and that laptop power settings are not in a battery-saver mode that throttles the CPU. Slowdown in one game is different: some original SNES titles slowed down on real hardware too, especially ones using enhancement chips — the official readme notes that games using added hardware require a faster machine, and faithful emulation reproduces some of the original slowdown rather than fixing it. If a chip-heavy game dips exactly where it dipped on a real SNES, your emulator is behaving correctly.
Pulling it together
Rule out the Tab key first, then confirm frame limiting/VSync and sound sync are actually enabled, then A/B test the sync combination against your monitor’s refresh rate. If controls feel unresponsive rather than the game feeling fast or slow, the issue may be latency instead — see how to reduce input lag in Snes9x. And for a known-good starting configuration across video, sound and input, copy the values in our best Snes9x settings guide, then deviate one setting at a time.
Check 6 — You might be paused, or frame-stepping
Two defaults from Snes9x’s hotkey list can look exactly like a speed fault. The Pause key (the Pause/Break key by default) halts emulation entirely — if your game appears frozen rather than slow, tap it once and see if play resumes. And while paused, the backslash key advances the game one frame at a time: a game that moves in tiny jerks when you touch the keyboard may not be slow at all, just paused and being stepped. Both keys are remappable in Input → Customize Hotkeys, and the same dialog holds the screenshot key (F12), the save/load state keys (Shift+F1–F10 and F1–F10) and the turbo controls from Check 1 — it is worth one slow read through that list whenever Snes9x seems to be doing something you did not ask for, because most “the emulator is misbehaving” reports turn out to be a hotkey doing precisely its job.
What “correct speed” actually means
One last expectation check: a faithfully emulated SNES does not promise a locked, perfectly smooth frame rate in every scene. Busy scenes in chip-heavy games dipped on real hardware, and Snes9x reproducing that dip is accuracy, not a fault — the readme’s note that add-on-chip games need a faster machine cuts both ways. Judge your fixes on ordinary gameplay: menus, early levels, and the games that felt wrong before. If ordinary scenes hold a steady pace after the checks above, the emulator is doing its job, and remaining dips in the most demanding scenes belong to the original hardware’s limits rather than to your settings.
