First, confirm you have the right build

The official file is Snes9x-1.63-Mac.zip from the Snes9x project’s GitHub releases. Two facts about it, verified from the app itself: it is a Universal binary — it runs natively on both Intel Macs and Apple Silicon, no Rosetta needed — and it requires macOS 10.12 or later. Extract the zip first and move Snes9x.app to your Applications folder; trying to run it from inside the zip preview or straight from Downloads is a common reason the first launch behaves oddly. If your Mac runs something older than macOS 10.12, this build genuinely cannot run on it — that is the one case where no launch trick helps.

The standard fix — right-click, then Open

Instead of double-clicking, right-click (or Control-click) Snes9x in the Applications folder and choose Open from the menu. macOS shows a confirmation dialog naming the app; click Open in that dialog. That is all. You only have to do this once — macOS remembers your choice for this app, and from then on Snes9x launches with a normal double-click like any other application. This right-click flow exists precisely for software obtained directly from a developer rather than the App Store; using it is the intended, Apple-supported way to say “yes, I meant to download this”.

If you already dismissed the warning — Open Anyway

If you double-clicked first and got the refusal, there is a second route. Open System Settings → Privacy & Security, scroll to the Security section, and you will see a note that Snes9x was blocked, with an “Open Anyway” button. Click it, confirm, and the app launches; as with the right-click method, macOS remembers the decision. On older macOS versions the same setting lives in System Preferences → Security & Privacy → General. Either route achieves the same one-time approval — use whichever you reach first.

What not to do

You may find old forum posts telling you to disable Gatekeeper entirely with a Terminal command. Do not. That switches off a system-wide protection for every app, just to launch one program — completely unnecessary when the right-click and Open Anyway routes above exist and are designed for exactly this situation. Likewise, if a site offers a “special” Snes9x build that opens without any prompt, treat it with suspicion and re-download from the official GitHub release instead; our download page links it directly and publishes the verified checksum of the Mac package. The prompt is a property of how the official app is distributed, not a defect to buy your way around.

Once it opens

Load a game with File → Open, and you are playing. If the app now opens but games misbehave, the fix depends on the symptom: a game file that will not load is covered by ROM won’t load, and if the window opens but stays blank on the Windows side of your setup, the black screen fix covers the output-method checks. For the full Mac picture — the current port, its features and its settings — see our Snes9x macOS guide.

“The file is damaged” and other scary wordings

Depending on the macOS version and how the file arrived on your Mac, the first-launch message may use stronger language — including claiming the app is damaged and should be moved to the Trash. For an app downloaded from outside the App Store, this wording most often appears when the download or extraction went wrong, or when the warning flow was interrupted. Before believing it: delete the extracted app, empty nothing else, re-download Snes9x-1.63-Mac.zip from the official GitHub release (our download page links it and publishes the verified checksum, so you can confirm the package arrived intact), extract it fresh, move the app to Applications, and use the right-click → Open route. A genuinely healthy copy approved through the standard flow will not keep re-warning you. If a work or school Mac refuses with a message about your administrator, that is a managed-device policy, not Gatekeeper — the fix there is your IT policy, not this guide.

When you update Snes9x later

Expect to repeat the one-time approval when you eventually replace Snes9x with a newer release: to macOS, the newly downloaded app is a new arrival from outside the App Store, so the right-click → Open step applies again. That is normal and quick the second time. Your games and progress are not inside the app bundle, so replacing the app does not endanger them — but as with any update, it is sensible to keep your ROM folder as it is and simply point the new app at it on first launch. Intel and Apple Silicon owners follow exactly the same steps, since the 1.63 Mac build is a single Universal app for both. And a final note for multi-platform players: none of this applies to the Windows build, which has its own first-run behaviours — those are covered in the Windows setup and troubleshooting guides linked from the hub.

Why this happens

Snes9x’s official system requirements, as printed in the readme bundled with version 1.63, are short: “Windows XP and up. DirectX 9.” Windows 10 and 11 ship with much newer DirectX versions built in, but the older DirectX 9-era helper libraries — the d3dx9 family of DLLs, of which d3dx9_43.dll is one — are an optional legacy component. If no older game or application has ever installed them on your PC, they simply are not there, and a program that expects them reports the file as missing. The same bundled documentation addresses this directly: the FAQ file in the 1.63 package asks “I get a dx9 dll error on startup. What to do?” and answers that Snes9x requires DirectX 9 to run correctly and that you can install it manually from Microsoft’s download site.

The fix — Microsoft’s DirectX End-User Runtime

Install the missing legacy components with Microsoft’s official DirectX End-User Runtime web installer (the small dxwebsetup download from microsoft.com — the very download the bundled Snes9x FAQ links to). Run it, let it detect and install the missing DirectX components, then launch Snes9x again. The installer only adds the legacy libraries your system lacks; it does not downgrade or replace the newer DirectX already in Windows, and it is safe to run alongside modern games. Afterwards, if the error persists, restart the PC once so every component registers cleanly, and re-extract a fresh copy of Snes9x from our download page in case the original extraction was incomplete.

Never download DLLs from “DLL download” sites

Searching the error message leads to sites offering d3dx9_43.dll as a standalone download to drop into a folder. Avoid them. A loose DLL from an unofficial site may be the wrong version, may be bundled with unwanted extras, and registers nothing — the runtime installer exists precisely so you never need to handle individual files. Microsoft’s installer is the only source this guide recommends, which is also why we follow the bundled FAQ’s pointer to Microsoft rather than mirroring any files ourselves.

The workaround — switch the output method

The missing component belongs to the Direct3D 9 path. Snes9x 1.63 for Windows can also render through OpenGL and Vulkan (and legacy DirectDraw), which do not rely on that DLL. So if Snes9x still opens on your system — for example the error appears only when a game loads — open the display settings and switch the output method to OpenGL or Vulkan as a workaround. If the error blocks Snes9x from opening at all, install the runtime first; the workaround needs a running emulator. Note what this fix does not involve: the bundled 1.63 documentation mentions no Visual C++ redistributable requirement for Snes9x, so there is no basis for chasing VC++ packages for this particular error — it is a DirectX issue, and the DirectX runtime is the documented remedy.

If the error names a different file

The same treatment covers the whole d3dx9 family — if Windows names a related legacy DirectX file, the End-User Runtime installs the set, not just one DLL. If the missing file is something else entirely, write down its exact name before searching: the fix depends on which library it is, and guessing wastes time. For other startup failures, the troubleshooting hub and the black screen fix (including the config-file reset) are the next stops.

Running the installer, step by step

• Close Snes9x and any other games or emulators.
• Download the DirectX End-User Runtime web installer (dxwebsetup) from Microsoft’s official site — the bundled Snes9x FAQ links the Microsoft download page for exactly this purpose.
• Run the installer and accept its offer to install the missing DirectX components; untick any optional extras bundled into the setup screens that you do not want.
• Let it finish — it checks which legacy components are absent and installs only those.
• Launch Snes9x and load a game to confirm the error is gone.

A few reassurances, because this error tends to send people down unhelpful paths. Running the installer on a brand-new gaming PC is normal: the legacy DirectX 9 components are simply not part of a default modern Windows installation, and many older games need them the same way Snes9x does. You do not need to reinstall Snes9x afterwards, and your ROMs, saves and settings are untouched by the process. If your copy of Snes9x was already running and only began showing this error after you switched its output method to Direct3D, the sequence still holds: install the runtime, then either keep Direct3D or return to OpenGL/Vulkan in the display settings — with the runtime installed, all four output methods are available to you again. And if a different Windows message appears after the DirectX error is fixed, deal with it on its own terms rather than reinstalling everything: one error message, one cause, one fix is the pattern throughout our troubleshooting hub.

Related guides: related guides: snes9x audio crackling fix.

Layer 1 — Pick an efficient output method

Snes9x for Windows renders through DirectDraw, Direct3D, OpenGL or Vulkan. The modern paths — Vulkan (added in 1.62) and OpenGL — are generally the leanest routes from emulator to screen on current hardware, while the legacy DirectDraw path exists for compatibility. If you are on an older output method, switching to Vulkan or OpenGL in the display settings is a reasonable first experiment: change one thing, play a timing-sensitive section you know well (a platformer jump or a rhythm of menu inputs), and judge by feel. Your mileage will vary with GPU and driver, so treat this as a test on your own machine, not a guaranteed number of milliseconds.

Layer 2 — The VSync trade-off

VSync prevents screen tearing by holding each finished frame until the monitor is ready for it — and that holding is itself a small delay. Turning VSync off can shave latency but may introduce tearing and can also uncouple the emulator’s pacing, so revisit the speed fixes if the game rate goes strange. A practical approach used by many players: keep the audio sync (“Synchronize with sound core”) as the pacing clock and experiment with VSync on and off to find the combination that feels responsive without tearing on your display. There is no universal winner — it depends on your monitor’s refresh rate and driver.

Layer 3 — Play fullscreen, and check the audio buffer

Running fullscreen (Alt+Enter) gives Snes9x a more direct path to the display than a window composited among other windows, and many players find it a touch more responsive. Separately, remember that a large sound buffer delays audio — and because your brain judges “responsiveness” partly by sound, an oversized buffer can make inputs feel late even when the picture is prompt. If you raised the buffer to cure crackling, trim it back down in small steps to the smallest value that stays crackle-free; the balance point is covered in the audio crackling fix.

Layer 4 — Your TV or monitor adds delay too

If you play on a television, its image processing is often the single biggest lag source in the chain — bigger than anything the emulator does. Switch the TV to its Game mode (the name varies by brand), which disables most of that processing for the input you are using. On a monitor, use its low-latency/game preset if it has one, and avoid daisy-chaining the signal through capture devices or receivers when you are testing. This is generic display advice rather than a Snes9x feature, but skipping it makes every emulator-side tweak feel pointless.

Layer 5 — Wired beats wireless, usually

Bluetooth controllers add a wireless hop between your hands and the PC, and that hop costs time — how much depends on the pad, the receiver and interference in the room. If lag is your priority, plug the controller in with a USB cable and compare; many players find wired play noticeably crisper, and it also sidesteps the Windows build’s no-hotplug behaviour (connect before launch, as explained in controller not detected). If you stay wireless, keep the receiver close and clear of obstructions, and keep the pad charged — some pads poll less eagerly on a low battery, though that varies by model.

What Snes9x does not have: run-ahead

Guides for other frontends often recommend run-ahead to claw back latency. Be clear about this: run-ahead is a RetroArch feature, not a feature of standalone Snes9x, and you will not find it in Snes9x’s menus. (Standalone Snes9x does have its own rewind — hold R — but rewind needs its buffer enabled in the emulation settings first, and it is a gameplay convenience, not a lag reducer.) If run-ahead is a must-have for you, the route is RetroArch with the Snes9x core; otherwise, the layers above are the honest levers available in the standalone app, and the best Snes9x settings guide collects the configuration we recommend as a baseline.

Measure before you tweak

“Feels laggy” bundles together several different delays, and each layer above fixes only its own. A rough but genuinely useful test: record your screen and your hands together with a phone camera — ideally its slow-motion mode — press a button with the pad visibly in frame, and count the frames between the press and the on-screen response. Repeat the count after each change. It will not give you laboratory numbers, but it will tell you whether a tweak actually helped your setup, which is the only verdict that matters. It also stops a common mistake: stacking five changes at once, feeling no difference, and concluding nothing works — when in fact one layer (usually the television) is contributing most of the delay and masking the gains from the rest.

Set expectations honestly

Some delay is structural: the emulated game itself reads input once per frame, the display takes time to show a finished image, and no setting removes those floors. What the steps in this guide do is strip away the avoidable additions stacked on top — compositor overhead, an oversized audio buffer, TV processing, a wireless hop. Players coming from real hardware on a CRT are chasing the most responsive setup there ever was; a well-configured Snes9x on a game-mode display gets respectably close for the vast majority of games, and the difference that remains is measured in single frames. If you have worked through every layer and a specific game still feels off, test the same game with a wired pad on a monitor rather than the TV: if it feels right there, you have found your bottleneck, and it was never the emulator.

Check the file extension against the supported list

Snes9x opens these cartridge formats directly: .smc, .sfc, .swc, .fig, .gd3 (and related copier formats), .bs (Satellaview) and .st (Sufami Turbo), plus compressed containers .zip, .gz and .jma. The .smc/.sfc pair are the standard dump formats; .swc and .fig come from Super Wild Card and Pro Fighter copier devices of the 1990s, and the .gd3 family from Game Doctor copiers — Snes9x still reads these legacy copier dumps, including the copier headers some of them carry. If your file has a double extension (something like .smc.zip is fine, but .zip.zip or a renamed archive is not), or an extension outside this list — for example a .7z or .rar archive — Snes9x cannot open it. Extract it first, or repackage the single ROM into a .zip.

One ROM per zip — no exceptions

The official readme states the rule plainly: Snes9x supports zipped ROMs as long as there is only 1 ROM per zip file. A “collection” zip containing dozens of games will not load — the emulator is not a ROM-set browser. Extract the archive and load the individual game file, or zip each game separately. The same applies to extra files riding along in the archive: if a zip holds a ROM plus text files or multiple regional dumps, pull out just the one ROM you want to play.

Corrupt or truncated dumps

A dump that was corrupted in transfer, or a download that never finished, can fail to load or crash shortly after starting. Symptoms that point here: the same file fails on a fresh Snes9x install, the file size looks suspiciously small or round (an interrupted download), or the game loads but glitches immediately in ways other players do not report. The remedy is to dump the cartridge again, or obtain a clean copy of your own dump — a different dump of the same cartridge is the standard fix, and the bundled FAQ makes the same point about patch files: if you are sure everything else is right, try the ROM from a different source (meaning your other dump of the game you own). If the game now loads but shows a black screen, switch to the black screen fix — that is a video problem, not a ROM problem.

Region is rarely the blocker

Players often assume a Japanese or European ROM fails because of region lockout. In practice, Snes9x is not a region-locked console: for most titles, a game from another region simply loads and plays, sometimes at its original television timing. If a specific foreign-region game misbehaves, that is more often a pacing or per-game quirk than a lockout — see the speed fixes if it runs at the wrong rate. Do not go hunting for “region-free patches” before you have checked the format and container rules above; they are far more common causes.

The honest exceptions: chips Snes9x does not emulate

A tiny number of games cannot work in Snes9x at all, because the cartridge chips they require are not emulated. The official readme names them directly: SD Gundam GX (needs the DSP-3 chip), Hayazashi Nidan Morita Shougi (Seta-11) and Hayazashi Nidan Morita Shougi 2 (Seta-18) “currently do not work with any version of Snes9x”. If your problem game is one of these three, no setting will fix it — that is a documented limitation, not your file. Two add-on formats have a different requirement: Sufami Turbo and Satellaview (BS-X) titles need their optional base files (STBIOS.bin / BS-X.bin) present, and BS-X support is only partial. Ordinary cartridge games need no BIOS file of any kind — Snes9x emulates the enhancement chips in code.

Last checks

Confirm the ROM is not still inside a nested archive, that the file is not zero bytes, and that you are loading it via File → Load Game rather than dragging an unsupported container onto the window. If a game loads but your progress will not save, that is a separate issue covered by saves not working. Nine times out of ten, though, a load failure is the one-ROM-per-zip rule or a bad dump — check those first.

Patched and translated ROMs

If your game loads but a translation or hack patch never applies — or the patched file itself will not open — check the patch mechanics before blaming the dump. Snes9x supports soft-patching with .ips files: per the bundled FAQ, the patch must sit in the same folder as the ROM and carry the exact same name apart from the extension (their example pairs “Pie.smc” with “Pie.ips”). Load the clean ROM and the patch applies on the fly. The FAQ adds the honest caveat that patches are written for one specific dump of a game: if the names match and the patch still misbehaves, a different dump of your own cartridge is the likely fix, because a patch applied to the wrong dump version can produce a file no emulator will run. Hard-patching a ROM with an external tool carries the same risk — keep your unpatched original, so a bad patch result never costs you the only copy.

A five-minute diagnostic routine

• Check the extension is on the supported list (.smc, .sfc, .swc, .fig, .gd3, .bs, .st, or a .zip/.gz/.jma containing one ROM).
• If it is zipped, open the archive yourself and confirm there is exactly one game file inside.
• Check the file size is sensible — a tiny or suspiciously round size suggests an interrupted download.
• Load a game you know works, to prove the emulator side is healthy.
• If only this title fails everywhere, check it against the three documented chip exceptions (DSP-3, Seta-11, Seta-18).

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.

The big one: connect the controller before you launch

Unlike the Linux (GTK) build, the Windows port of Snes9x does not hot-plug controllers. This is deliberate and documented in the official changelog: back in version 1.56, hotplugging on Windows was disabled in favour of a menu option to reconfigure joysticks. So if you launch Snes9x first and plug your pad in afterwards, the emulator may simply never notice it. Two ways around it: connect the controller first, then start Snes9x — or, with the pad connected, use the Input menu’s option to reconfigure joysticks so Snes9x re-scans your devices without a restart.

Map the pad in Input Configuration

Detection is only half the job — the pad also has to be mapped. Open Input → Input Configuration, click a SNES button field, and press the pad button you want for it. If Snes9x responds when you press buttons during mapping, the pad is detected and your only problem was an empty or stale mapping. If a second player pad is involved, make sure you are configuring the right controller slot. The bundled FAQ adds a useful D-pad tip: leave the diagonal fields blank when mapping — a real SNES D-pad only has four switches, and diagonals come from pressing two directions at once; filling the diagonal boxes in is a common cause of “my D-pad feels wrong”. Our full controller setup guide walks through mapping in detail.

XInput versus DirectInput

Windows gamepads speak one of two APIs. Xbox controllers and most modern PC pads use XInput; many retro-style USB pads, older controllers and some 8BitDo modes use DirectInput. Snes9x accepts both, so either kind should work — but a pad with a mode switch (some retro pads can present as either) sometimes shows up under one mode and not the other. If your pad has an X/D switch or a mode button combo, try the other mode, reconnect, and re-run the joystick reconfigure step. Also check the obvious: some pads enumerate differently over USB than over Bluetooth, so test wired if wireless is giving you trouble.

Bluetooth: pair with Windows first

Snes9x has no Bluetooth pairing of its own — it only sees controllers that Windows has already paired and connected. Pair the pad in Windows Bluetooth settings first, confirm it shows as connected (not merely paired), and only then launch Snes9x or use the Input menu to reconfigure joysticks. If the pad sleeps or disconnects mid-session, Windows drops the device and the no-hotplug behaviour means Snes9x will not pick it up again automatically when it wakes — reconnect it in Windows, then reconfigure joysticks from the Input menu. A wired USB connection remains the most reliable way to rule Bluetooth in or out, and it also removes wireless latency if you are chasing the lowest input lag.

Confirm Windows itself sees the controller

If Snes9x still shows nothing, step outside the emulator: open Windows’ own game controller panel (search for “Set up USB game controllers”) and check that your pad is listed and that its test screen responds to your button presses. The bundled FAQ’s advice is the same in spirit — most USB controllers work, and updating drivers and recalibrating the controller are the first remedies when one misbehaves. If the pad does not respond in Windows’ own panel, the problem is the pad, its cable, its receiver or its driver — not Snes9x — and no emulator setting will fix it.

Still stuck?

Try a different USB port (front-panel and hub ports are occasional culprits), close other software that grabs controllers exclusively, such as other emulators or game launchers, and restart Snes9x with the pad already connected. If the inputs register but feel delayed rather than absent, that is a different problem — see how to reduce input lag. And for choosing a pad that plays nicely with SNES games in the first place, our best controller for Snes9x guide compares the popular options.

Keyboard works but the pad doesn’t?

That split is itself a diagnosis. If keyboard controls respond in-game, Snes9x and the ROM are fine and the problem is confined to the pad path: device detection, mapping, or Windows’ view of the controller. Work the chain backwards — Windows game controller panel first (does the pad respond there?), then the Input menu’s joystick reconfigure (did you connect the pad after launching?), then Input Configuration (are the fields actually mapped to this pad, or to a controller you used last month?). A stale mapping is more common than people expect: mappings are stored per controller, and swapping between an Xbox pad and a retro USB pad can leave you pressing buttons on a device the current mapping was never written for. Re-mapping takes a minute and rules it out.

Second pad and player 2

For two-player games, each pad must be connected before launch (or picked up through the joystick reconfigure option) and mapped under its own controller configuration — player 2’s pad does nothing until its buttons are assigned in the second controller’s fields. If both pads are the same model, Windows and Snes9x distinguish them by connection order, so connect them one at a time and map each before connecting the next; otherwise it is easy to map player 1 twice and wonder why the second pad mirrors the first. Wireless receivers and dongles count as part of the device: a pad that is “on” but whose receiver is plugged into a sleeping USB hub is, to Snes9x, simply not there. Give receivers a direct motherboard port when you can, and wake everything up before you start the emulator rather than after.

Related guides: related guides: snes9x audio crackling fix.

Where Snes9x saves are supposed to go

By default, both save systems write to a folder called Saves in the same folder as snes9x.exe (the config defaults are literally .\Saves for both savestates and SRAM). Battery saves — the game’s own save feature — are stored as .srm files, written when the ROM is unloaded or you quit, and loaded automatically the next time you play that game. Save states (freeze files) live in the same folder, named .000 to .099: Snes9x 1.63 gives you 10 quick slots per bank (Shift+F1–F10 to save, F1–F10 to load) across 10 banks — up to 100 states per game. If you go looking for your saves anywhere else, you will not find them.

The Program Files trap

The classic failure: you extracted Snes9x into C:\Program Files or another protected location. Modern Windows blocks ordinary programs from writing there, so Snes9x cannot create or update the Saves folder — in-game saves appear to work during the session, then are missing next time, and state saves fail outright. The fix is simply to move the whole Snes9x folder somewhere your account owns: a folder on your desktop, in Documents, or something like C:\Games\Snes9x. Copy your existing Saves folder along with it so anything that did get written comes too.

Check the Saves path in settings

The Saves location is a setting, and it can be changed — which means it can also be changed by accident, or left pointing at a folder from an old setup. Open Snes9x’s settings and check the directories for savestates and SRAM: both should point at a folder that (a) exists and (b) you can write to. If the path names a drive or folder that no longer exists, browse to your real Saves folder and set it explicitly. After changing it, save a state and load it straight back as a smoke test.

States that exist but won’t load

If the state files are visibly present in Saves but refuse to load, check which slot and bank you are in — with 10 banks, the state you want may simply be in a different bank than the one you are browsing. Also keep in mind that save states are snapshots of a specific emulator build’s internal format; a state created by a very old Snes9x version may not load in 1.63 (the documented freeze format changed in the past and old formats were not kept compatible). Battery .srm saves are far more portable than states — another reason to use the game’s own saving for anything you care about long-term.

The .oops recovery file

One more resident of the Saves folder is worth knowing: if you quit Snes9x without saving after playing for a long time, it writes an .oops auto-recovery freeze file there. If you closed the emulator by accident mid-session, look for that file before assuming the session is lost — loading it can put you back where you were.

A reliable saving routine

To keep this from recurring: keep Snes9x in a writable folder, confirm the Saves path once, and use both systems for what they are good at — .srm battery saves as your durable progress, states as quick bookmarks. Our save states and .srm guide explains the two systems in full. If instead the game itself will not open at all, see ROM won’t load, and if the emulator opens to a black window, see the black screen fix.

Related files you will find in the Saves folder

While you are in there, two other file types belong to the same system. Games with a real-time clock use .rtc files alongside the .srm, and your cheat lists are stored as .cht files that Snes9x reloads automatically when the same game is loaded again. None of these should be deleted during troubleshooting unless you have a backup — “cleaning up” the Saves folder by removing unfamiliar extensions is a quiet way players lose clock data and cheat setups. It is also worth knowing that the save files are keyed to the game: if you replace a ROM with a differently named file — a re-dump with a new filename, for example — Snes9x will look for saves under the new name and your old .srm will sit unused in the folder. Renaming the save files to match the ROM’s new name is the standard way to reunite them.

Back the folder up

Once saving works, protect it: the entire Saves folder is small and self-contained, so copy it somewhere safe whenever you finish a long session in a game you care about. A copied folder also makes moving to a new PC painless — install Snes9x, drop your Saves folder next to the new executable (keeping the same game filenames), and your battery saves and states come with you. A dated backup copy also gives you an undo if a state ever gets saved over by accident: with banks and slots it is easy to overwrite the wrong slot, and the only real protection is a folder copy made before it happened. Treat the quick test as your routine after any settings change: save a state, load it back, save in-game, restart the game, and confirm both are exactly where you left them.

Step 1 — Switch the output method

Snes9x for Windows can render through DirectDraw, Direct3D, OpenGL or Vulkan — those are the four output methods the 1.63 build registers. Open the video/display settings and pick a different one, then load your game again. If Direct3D gives you a black screen, OpenGL or Vulkan will often work, and vice versa. Vulkan is a good test on newer systems because it arrived in Snes9x 1.62 and uses a completely separate code path from the older DirectDraw and Direct3D outputs. If Snes9x crashes before you can even reach the settings menu, skip to the config reset below — the output choice is stored in the config file, so resetting it returns you to the default.

Step 2 — Test without shaders

If the black screen only appears with a shader enabled, the shader and the output method are probably mismatched. Shader formats are tied to the renderer: Cg shaders work in both Direct3D and OpenGL, GLSL shaders are OpenGL-only, and slang shaders work with OpenGL (since 1.59) and Vulkan (since 1.62). Loading, say, a GLSL shader while rendering through Direct3D cannot work. Set the shader to none, confirm the game displays correctly, then re-enable a shader format that matches your chosen output.

Step 3 — Reset the config file

Settings in Snes9x live in a plain config file, snes9x.conf, in the same folder as the executable. The bundled FAQ’s official answer for messed-up options applies here too: you can safely delete snes9x.conf (with Snes9x closed) to reset every option to its defaults. Snes9x recreates a fresh file on the next launch. This clears a bad output method, a broken fullscreen resolution or any other half-remembered tweak in one move. Your ROMs and your Saves folder are untouched — but if saves are your actual problem, read the saves not working guide instead.

Step 4 — Update your graphics drivers

If several output methods fail, suspect the driver underneath them. Install the current graphics driver from your GPU maker’s official site (or your laptop maker’s support page) rather than relying on an old driver Windows installed years ago. This matters most for the OpenGL and Vulkan outputs, which depend directly on driver support; a stale driver is a common reason Vulkan in particular refuses to start. After updating, restart the PC before retesting — graphics drivers often do not fully swap in until then.

Step 5 — Confirm the game itself loads

A black screen after the game starts can also mean the ROM never loaded properly. Try a second game: if every game is black, the problem is video; if only one title is affected, work through our ROM won’t load checklist for that file. Also worth a quick check: if Windows reports a missing DirectX DLL when Snes9x starts, that is a separate, specific failure with its own fix — see the d3dx9_43.dll error guide.

Step 6 — Re-extract a fresh copy

If nothing above helps, eliminate the install itself. Download Snes9x 1.63 again from the official GitHub releases page (our download page links it and publishes the verified SHA-256 checksums), extract it to a fresh folder somewhere writable — not inside Program Files — and launch it before changing a single setting. A clean folder separates “my configuration is broken” from “this system has a deeper problem”, and in practice the fresh copy resolves most stubborn startup crashes. Once it runs, change one setting at a time so you learn exactly which option your system dislikes.

Two more checks: fullscreen and dual-GPU laptops

If the game displays in a window but goes black in fullscreen, the fullscreen resolution or refresh combination is the likely culprit — reset the config file (Step 3) to return fullscreen to its defaults, then re-enable it and note the exact moment it breaks. On laptops with both integrated and dedicated graphics, there is another possibility: Windows may be handing Snes9x to a different GPU than you expect, and the two GPUs’ drivers can behave differently with the same output method. Your graphics settings in Windows (or the GPU vendor’s control panel) let you assign which GPU an application uses; if one output method fails on one GPU, testing Snes9x on the other GPU is a legitimate diagnostic step. As with the output methods themselves, change one variable at a time and keep notes — a black screen that depends on three settings at once is only debuggable if you isolate them.

Quick recap

• Switch the output method among DirectDraw, Direct3D, OpenGL and Vulkan.
• Disable shaders, then re-enable only a format that matches your output method.
• Delete snes9x.conf (with Snes9x closed) to reset all options to defaults.
• Install the current GPU driver from the manufacturer, then restart the PC.
• Test a second game to separate a video problem from a single-ROM problem.
• Re-extract a fresh 1.63 copy into a writable folder and test before changing any setting.

First, rule out the simple causes

Before changing emulator settings, check the basics the official readme calls out. If you hear no sound at all, another Windows application may be holding exclusive access to your sound device — close media players, streaming apps and other emulators, then restart Snes9x. Check that the Windows volume mixer is not muting Snes9x specifically, and that your output device in Windows is the one you are actually listening to (a classic trap after plugging in a USB headset or an HDMI monitor). If sound plays but crackles, move on to the Sound Settings dialog.

Fix 1 — Enable “Synchronize with sound core”

Open the Sound Settings dialog and make sure “Synchronize with sound core” is enabled. On a real SNES, the audio processor runs in lockstep with the rest of the machine; enabling this option keeps Snes9x’s emulation paced by the sound hardware, which is the single most effective step against crackling for most users. If it is off, the emulator can drift ahead of or behind the audio stream, and the gaps are exactly what you hear as pops and stutters.

Fix 2 — Increase the sound buffer

Still in Sound Settings, raise the buffer size. A larger buffer gives the audio more headroom: brief hiccups in emulation speed get absorbed instead of turning into audible gaps. The trade-off is latency — a bigger buffer means sound reaches your ears slightly later, which matters if you are chasing the lowest possible input lag. Raise the buffer in small steps until the crackling stops, rather than jumping straight to the maximum, so you keep the delay as small as your system allows.

Fix 3 — Switch the sound driver (XAudio2 or WaveOut)

The readme’s next suggestion is to switch the sound driver — if you are on WaveOut, try XAudio2, and vice versa. Both are standard Windows sound output paths offered in the Sound Settings dialog, but they interact differently with your audio hardware and drivers. XAudio2 is the more modern path and is the better default on current Windows versions; WaveOut sometimes behaves better on older or unusual audio devices. There is no universally right answer here — if crackling appears with one, the other is worth a two-minute test.

Fix 4 — Adjust the input rate

Snes9x generates audio at a rate it negotiates with your system, and a mismatch shows up as persistent crackle. The readme’s advice: if the “Automatic Input Rate” option is disabled, enable it. If it is already enabled and you still hear crackling, disable it and lower the “Input Rate” value in steps of 10 until the crackling goes away. Small steps matter — overshooting can trade crackle for a subtle pitch or pacing problem.

Fix 5 — Enable Dynamic Rate Control and use 48000 Hz playback

Two more Sound Settings options round out the official checklist. Dynamic Rate Control lets Snes9x nudge the audio rate continuously to stay in sync, which smooths out the slow drift that causes periodic popping. And set the Playback Rate to 48000 Hz: since Windows Vista, the Windows sound server that mixes application audio typically runs at 48000 Hz, so matching it means Windows does not have to resample Snes9x’s output — resampling is another quiet source of artefacts. The readme is explicit that running at 32000 Hz provides no benefit, despite that advice circulating on old forum posts.

If the sound lags behind the action

Sound that is clean but noticeably late is usually the buffer working against you: lower the buffer size step by step until the delay feels right, accepting that too small a buffer brings the crackle back. Also check that your game is running at the correct speed — audio sync problems and speed problems often arrive together, and our guide to games running too fast or too slow covers the pacing side. For a full once-over of every relevant option, the best Snes9x settings guide ties the sound, video and input settings together. And if the picture itself is the problem — a black or frozen window — see the black screen fix instead.

Work through these in order — sync first, then buffer, driver, input rate, and finally dynamic rate control with 48000 Hz playback — and in most cases the crackling stops at one of the steps. None of these changes touch your games or saves, so you can experiment freely.

A sensible order to try the fixes in

• Enable “Synchronize with sound core” and test.
• Raise the buffer in small steps and test again.
• Switch the sound driver between WaveOut and XAudio2.
• Toggle “Automatic Input Rate”; if crackling persists, lower the input rate in steps of 10.
• Enable Dynamic Rate Control and set the Playback Rate to 48000 Hz.

Changing one thing at a time feels slow, but it is how you learn which control your system actually needed — and it stops you ending up with every option flipped and no idea which one helped. Two more patterns are worth recognising. If crackling affects one game only, especially a title that pushes the SNES sound hardware hard or uses an enhancement chip, the bottleneck may be raw emulation load rather than your sound settings: close other applications and test again before blaming the audio dialog. And if crackling appears only through a particular output — say, a Bluetooth speaker or a TV over HDMI — while headphones are clean, the output device and its own buffering are part of the chain; Snes9x can only hand audio to Windows, and what happens after that is the device’s business. Testing with plain wired headphones is the fastest way to separate “emulator audio problem” from “playback device problem”. Finally, keep your sound card or chipset drivers reasonably current: the readme lists up-to-date audio drivers among its first suggestions, and a driver from the Windows default set can behave very differently from the manufacturer’s own.