Snes9x 1.63 does not need much tuning to run well — the official readme’s own hardware recommendation is a semi-modern machine, and any current PC is far beyond that. The settings that genuinely change what you see and how a game feels are concentrated in one place: the video output method and the handful of display and timing options around it. This guide walks through those choices in the order we recommend setting them. If you have not installed Snes9x yet, start with the Windows setup guide and the setup hub, and grab the current release from the download page so you are tuning version 1.63 rather than an old build.
Start with the output method — it decides everything else
The Windows build of Snes9x 1.63 registers exactly four output methods: DirectDraw, Direct3D, OpenGL and Vulkan. This single choice controls which shader formats you can use, how the image is scaled, and how the emulator talks to your graphics hardware, so pick it first and leave the other menus alone until it is set. You will find the choice in the video/display settings, and you can switch freely — changing output method does not touch your saves, states or controller mapping.
For most readers the short answer is: use OpenGL or Vulkan. Both are modern paths, both support the current shader formats (Cg, GLSL and slang — see the shaders and filters guide), and both scale the SNES’s low-resolution output cleanly to a modern monitor. OpenGL is the long-established default-style choice and the safest pick if anything looks wrong. Vulkan, added in version 1.62 (not 1.63, despite what some sites claim), is the newer alternative and is equally valid — try it if OpenGL gives you trouble, or if you want to use slang shaders through the Vulkan path.
When Direct3D and DirectDraw make sense
Direct3D is the older DirectX path. Its main reason to exist today is Cg shader support: Cg shaders work in both Direct3D and OpenGL, so if you have a favourite old Cg preset, Direct3D remains a legitimate home for it. DirectDraw is the legacy option, kept for compatibility with very old hardware and drivers. On any machine built in the last decade it offers no advantage — it is the output method with the fewest modern features, and we only mention it so you know you can safely ignore it. If a guide tells you DirectDraw is the “fastest” option for a modern PC, it is repeating advice from another era.
Frame skip: what it does and when to touch it
Frame skipping exists for machines that cannot emulate every frame in real time: the emulator drops the rendering of some frames so gameplay keeps the correct speed. On hardware that meets the readme’s modest recommendation — which is to say, essentially every Windows 10 or 11 PC still in use — the correct setting is to leave frame skipping off or on its automatic behaviour and let every frame render. Deliberately skipping frames on a capable machine only makes motion look choppier. Treat frame skip as a troubleshooting tool for genuinely weak hardware, not a performance upgrade, and be suspicious of any settings guide that promises specific frame-rate gains from it: Snes9x’s publishers state no such figures, and neither do we.
Sync and timing options
The sync-related options govern how the emulator paces itself against your display and sound card. Left at their defaults, Snes9x targets the game’s own original timing, which is what you want: a game that runs noticeably too fast or too slow is almost never a “best settings” problem but a sync or configuration fault — our troubleshooting coverage works through that case specifically. Change one sync option at a time, test with the same game, and change it back if it does not help; stacking random timing tweaks is how settings files become a mess nobody can untangle later.
Picture quality beyond the output method
With OpenGL or Vulkan selected, picture quality is mostly about what you layer on top. Shader presets can reproduce a CRT look, smooth pixel edges, or leave the image untouched — the formats and trade-offs are covered in depth in the shaders and filters guide. Window size, fullscreen behaviour and aspect-ratio handling live in the same display area and are covered separately in the fullscreen and display settings guide. Our honest recommendation for a first session: OpenGL or Vulkan, no shader, correct aspect ratio, and play for an evening before changing anything. Most “bad picture” complaints turn out to be a stretched aspect ratio, not a missing filter.
A sane baseline to start from
- Output method: OpenGL first choice, Vulkan a close second (both support modern shaders)
- Direct3D: only if you specifically want Cg shaders through the DirectX path
- DirectDraw: legacy compatibility only — skip it on modern hardware
- Frame skip: off/automatic on any current PC; a rescue tool for weak hardware, not a boost
- Sync/timing: leave at defaults unless a game demonstrably runs at the wrong speed
- Shaders and scaling: add one change at a time, after a baseline session
How to test a change properly
Emulator settings interact, so change them like you would debug anything: one variable at a time, with the same game and the same scene as your test. Note what the default was before you touch it — a screenshot of the dialog is the quickest record — then play for a few minutes, not a few seconds, because timing and sync problems often appear in motion rather than on a title screen. If a change neither helps nor hurts, revert it: a settings file full of shrug-worthy tweaks becomes impossible to reason about the first time something genuinely breaks. The baseline below is deliberately boring, and that is the point — boring settings are the ones you never have to think about again.
Finally, remember that settings never affect your save data. Battery saves and save states live in the Saves folder regardless of display choices — the save states and .srm guide explains where they are and how to back them up, and the setup hub collects every other tutorial in this series.