Who makes each one, and from what code

Desktop Snes9x comes from the snes9xgit project on GitHub — the current, upstream codebase, where 1.63 is the latest stable release. Snes9x EX+ is developed by Robert Broglia (of the EX / Imagine engine family of emulators) and distributed through his own channels: it is free on Google Play, where the listing shows it still being updated. The Play listing historically described EX+ as based on Snes9x 1.55 — the current listing no longer states a base version, so the honest statement is that EX+ grows from an older Snes9x codebase, maintained on Broglia’s own track, rather than tracking desktop 1.63 feature for feature. One more licensing note, because Play copy can mislead: the underlying Snes9x core is freeware for personal, non-commercial use with publicly available source — not OSI open source — whatever shorthand an app-store page uses.

The experience: desk versus pocket

Desktop Snes9x is a menu-driven program built for a keyboard, mouse and gamepad on a big screen: Direct3D, OpenGL and Vulkan output, Cg/GLSL/slang shaders, up to 100 save states across 10 banks, its own rewind (once you enable the buffer), cheats with a built-in search, and hotkeys for everything. EX+ is built for a phone in your hands: an on-screen touch control overlay for touchscreen play, support for physical Bluetooth and USB HID gamepads when you want real buttons, and Android-native file handling built on the Storage Access Framework, so it works with the scoped-storage rules of modern Android versions instead of expecting a desktop-style folder tree.

Neither experience is a lesser version of the other; they are shaped by their hardware. What you should not expect is parity of settings screens or behaviour. A desktop Snes9x guide — including most guides on this site — describes the desktop program. EX+ has its own menus and options, and where they differ, EX+ is not "wrong"; it is simply a different application by a different developer.

Moving your games and saves between them

Your ROM files are the same files on both — EX+ and desktop Snes9x read the same common SNES formats. Saves need one distinction. Battery saves (.srm) are your portable progress: the Snes9x readme notes that .srm files are compatible with all SNES emulators, and EX+ uses the same convention, so a game’s in-cart saves can move between your phone and your PC — copy the .srm alongside the ROM, keep the base filename matched to the ROM’s, and load the game on the other device.

• Do move: ROMs, and the matching .srm battery save for each game — that is where RPG progress and unlocks actually live.
• Do not rely on moving: save states. State formats are tied to the emulator and build that created them — Snes9x’s own snapshot format has changed across its history — so treat states as a convenience on the device where you made them, not as portable saves.
• Expect to reconfigure: controls, video options and folders do not travel; each app keeps its own settings, and on Android your ROM and save locations are governed by the file access you grant EX+ through the Storage Access Framework.

Which one should you install?

• You play at a desk, on Windows, Mac or Linux: desktop Snes9x 1.63 — the current upstream release, from the project’s official GitHub releases page.
• You play on an Android phone or tablet: Snes9x EX+ from Google Play — free, touch-first, gamepad-friendly, and honest about being Broglia’s separate app. It is also the main channel our Android download link points to.
• You play in both places: install both, standardise on .srm saves as your transfer format, and accept save states as per-device. Many players in this cluster also weigh the alternative Android route — the Snes9x core inside RetroArch — which standalone vs libretro core and the field guide cover.

Verdict

Desktop Snes9x is the original and the most current; Snes9x EX+ is a separate, respected Android adaptation by Robert Broglia, based on older Snes9x code and built around touch and Android storage rules. Pick by where you play, not by which name sounds more official — and be wary of any site that blurs the two, especially one offering a "Snes9x Android APK from the Snes9x team," because no such mainline product exists. For the rest of the landscape, see Snes9x vs RetroArch and Snes9x vs bsnes.

What each one costs, and what neither costs

Money settles nothing here, in a good way. Desktop Snes9x is freeware for personal, non-commercial use, downloaded at no cost from the project’s GitHub releases — any site charging you for the emulator itself is selling you something the project gives away. Snes9x EX+ is likewise free on Google Play, as its listing states, so the Android choice costs nothing either. What each asks of you instead is different in kind: the desktop program asks for a computer and a few minutes with a ZIP file, while EX+ asks for an Android device and your comfort with granting a phone app access to the folders holding your games and saves. Judge sites accordingly — the trustworthy ones for both programs are the ones that send desktop users to the project’s own releases and Android users to Broglia’s Play listing, rather than to an unofficial APK mirror.

The contenders, in one paragraph each

Snes9x is the long-running all-rounder: in development since the late 1990s, currently at version 1.63 (July 2024), with official Windows, macOS and Linux builds plus a libretro core. Emulation Gametech Wiki rates its accuracy High with 5 known issues and marks it recommended, noting it is less accurate than bsnes or ares but runs at full speed on weaker hardware. It needs no BIOS for normal games. bsnes (and its relatives higan and ares) is the accuracy-first line, built on low-level emulation, with extras such as true Super Game Boy emulation, at the cost of demanding much stronger hardware. Mesen-S, by Sour — author of the NES emulator Mesen — is the modern accuracy-minded contender for Windows and Linux, with Super Game Boy support. RetroArch is not an emulator but a frontend that can run Snes9x, bsnes and Mesen-S cores inside one multi-system shell. And the forks — Snes9x EX+ on Android, Snes9x GX on Wii, ports for 3DS and PSP — are how Snes9x code reaches devices the mainline project does not target.

Pick by use case

• Weakest PC, oldest laptop, mini PC: standalone Snes9x. Its only official spec is "Windows XP and up, DirectX 9" with a 1 GHz-class CPU recommended — in practice, if the machine still runs, Snes9x runs on it.
• Accuracy purist, developer, preservation-minded: bsnes or ares. You are choosing the projects that treat hardware fidelity as the goal, and accepting their hardware demands and, for some chip games in the higan tradition, firmware-dump housekeeping. See Snes9x vs bsnes.
• Android phone or tablet: there is no mainline Snes9x app. Use Snes9x EX+, Robert Broglia’s separate, free Google Play app in the Snes9x family, or the Snes9x core inside RetroArch. Our flagship Snes9x for Android page and Snes9x vs Snes9x EX+ explain the distinction honestly.
• CRT-shader fan: either shell works — standalone Snes9x supports Cg, GLSL and slang shaders, including CRT presets from the libretro shader collections — but RetroArch’s frontend shader system is the deeper rabbit hole, with per-core and per-game presets. See Snes9x vs RetroArch.
• Online play with friends: RetroArch with the Snes9x core. Standalone Snes9x netplay exists (up to five players, TCP port 6096) but the project’s own readme warns it has not been maintained in a long time and might be broken; the libretro documentation recommends the Snes9x core for netplay because RetroArch’s system is the maintained one.
• Super Game Boy games: not Snes9x — it has no SGB support at all. bsnes and Mesen-S both cover Super Game Boy; a dedicated Game Boy emulator is the other honest route.
• Mac user: Snes9x’s official macOS build is a Universal binary for Intel and Apple Silicon (macOS 10.12 or later), which keeps it the simplest native answer; RetroArch is the alternative if you want one app for everything.
• Just want to play, tonight, with no fuss: standalone Snes9x on desktop. Extract, load a game, play — no installer, no firmware files, no frontend to learn.

The known-issue honesty box

No emulator in this guide is flawless, and pretending otherwise helps no one. Snes9x’s readme states that games on the unemulated DSP-3 and Seta-11/18 chips — it names SD Gundam GX and the two Hayazashi Nidan Morita Shougi titles — do not work in any version of Snes9x, and that its Satellaview/BS-X support is only partial. The accuracy-first projects exist to close exactly those kinds of gaps. What you should distrust is any site that converts this into a tidy percentage: no official compatibility percentage exists for Snes9x, and a short named list of problem titles is more useful information than a fabricated decimal ever was.

So, the short answer

For most people, on most computers, asking most questions, the answer is Snes9x — standalone for simplicity, or as a RetroArch core for frontend features and netplay. Accuracy specialists should run bsnes or ares alongside it; Mesen-S deserves a look from Windows and Linux users who want a modern, accuracy-minded alternative (Snes9x vs Mesen); Android players should install EX+ knowing exactly what it is (desktop vs EX+). And ZSNES, beloved as it is, belongs to history — here is why. The remaining comparison in this cluster, standalone vs the libretro core, settles the last shell question. Whichever you choose, keep your games’ .srm saves backed up — that format travels between all of these emulators, so your progress is never hostage to one program.

How to decide in sixty seconds

If the use-case list above still feels like a lot, compress it to three questions. First: where will you play? A desktop points to Snes9x or bsnes, a phone points to Snes9x EX+ or RetroArch, a modded console points to its Snes9x fork. Second: how old is the hardware? Anything modest points to Snes9x, whose official recommendation is only a 1 GHz-class CPU; only a comfortably modern PC unlocks the accuracy-first projects at their best. Third: is there one special thing you need — Super Game Boy games, online play, CRT shader tinkering, a specific known-issue title? That single need, if you have one, usually settles the choice on its own, and the detailed comparisons linked throughout this guide explain each of those branches. If you have no special need, you have your answer too: Snes9x, and get playing.

What is actually the same

The SNES emulation itself comes from the one Snes9x codebase in both cases. The games, the enhancement-chip handling, the broad compatibility — including its known limits, such as the unemulated DSP-3 and Seta-11/18 titles named in the readme — do not change because the window around them changed. Both forms read the same ROM formats (.smc, .sfc, .swc, .fig, .bs, .st, and single-ROM .zip, .gz or .jma archives), both use .srm files for battery saves — a format the readme notes is compatible with all SNES emulators — and both work with .cht cheat files. Your library and your in-game saves are portable between the two; it is everything around the game that differs.

What the standalone apps give you

The standalone route gives you Snes9x as its authors present it: a menu-driven Windows program (with native Mac and Linux counterparts), its own settings dialogs, its own hotkeys, and its own feature implementations. Save states are Snes9x’s own system — 10 quick slots per bank across 10 banks, files .000–.099, written with your .srm saves to a Saves folder beside the executable. Rewind is Snes9x’s own implementation too, present since 1.54 on the R key — but remember it is disabled until you set a non-zero rewind buffer, because the default buffer size is 0. Shaders are built in and capable: Cg under Direct3D and OpenGL, GLSL under OpenGL, and slang under OpenGL and Vulkan. Netplay exists in standalone form — up to five players over TCP port 6096 — but carries the project’s own warning that it has not been maintained in a long time and might be broken.

In short: in the standalone apps, what you see is what Snes9x itself does. When a guide shows a Snes9x menu, it is showing you this program, and troubleshooting has exactly one layer to consider.

What changes inside RetroArch

Load the same code as a libretro core and the frontend takes over the surrounding jobs. RetroArch owns the video and audio settings, the controller profiles, the library, the screenshots — and the headline features. Rewind becomes a RetroArch feature applied to the core (the libretro documentation lists rewind as supported for the Snes9x core, provided by the frontend), netplay becomes RetroArch’s maintained netplay — the libretro docs describe the Snes9x core as recommended for netplay for exactly this reason — and shaders come from RetroArch’s own preset system rather than Snes9x’s dialogs. Run-ahead, achievements and other frontend-level systems, where you use them, are likewise RetroArch’s contribution, not the core’s.

That division of labour is the whole point, and also the whole learning curve. Settings that standalone users find in Snes9x’s menus are now split between RetroArch’s menus and the core’s own options list, and your saves and states live in RetroArch’s folder structure instead of beside an executable. In exchange, every other core you run behaves the same way — which is why our broader Snes9x vs RetroArch comparison frames this as a lifestyle choice, not a quality ranking. The Platforms cluster covers the same ground from the installation side in the Snes9x RetroArch core guide linked from our platforms hub.

Who should pick which

• Pick the standalone apps if SNES is your only system, you want the official Snes9x interface and documentation to match your screen exactly, or you are on a modest PC and want the lightest possible setup — the readme’s recommendation is only a 1 GHz-class CPU.
• Pick the libretro core if you already live in RetroArch, you want its netplay or frontend features such as run-ahead, or you want one consistent setup across many consoles and devices — the core is also how Snes9x reaches platforms with no standalone app.
• Switch freely: keep your ROMs and .srm saves somewhere both can reach, treat save states as per-build and disposable, and you can change your mind at any time without losing real progress.

Verdict

Same heart, different shell. The standalone apps are Snes9x unmediated — simpler, self-contained, and the reference experience. The libretro core is Snes9x as a citizen of a larger frontend — more powerful for multi-system and online players, at the cost of learning RetroArch’s layer as well. Neither is the "real" Snes9x; the 1.63 release ships both because both audiences are real. See also Snes9x vs RetroArch and the best SNES emulator field guide.

Where the core travels that the apps do not

One last asymmetry is worth knowing. The standalone apps cover the desktop — Windows, macOS and Linux — and stop there. The libretro core travels further: because frontends exist for so many systems, the Snes9x core is how Snes9x emulation reaches places the mainline project ships nothing for, including Android phones (through RetroArch; the project’s own build system also compiles the libretro core for Android) and a long tail of handhelds, single-board computers and console homebrew frontends. That reach is a real argument for learning the core’s way of doing things if your playing is spread across gadgets. It does not make the standalone apps redundant — on a desktop they remain the simpler, reference experience — but it does mean the core is the more future-flexible of the two shells, and the one most new devices will meet first.

The dates tell the story

ZSNES first appeared in 1997, built for DOS and later ported to Windows and Linux, and its last official release is version 1.51, from January 2007. Development was then discontinued. That means the ZSNES most sites still offer for download predates modern Windows as most people know it, predates current display, audio and controller stacks, and has had no maintainer to adapt it to any of them. When you read about "Super ZSNES" in 2026 headlines, that is a separate, from-scratch new project by the original creators — not an update that revives the classic 1.51 build.

Snes9x, ZSNES’s great contemporary rival, never stopped. Its current stable release is 1.63, published on 9 July 2024 on the project’s GitHub releases page, with the codebase still maintained in the open. The Windows build in that release registers modern output methods — DirectDraw, Direct3D, OpenGL and Vulkan — and supports libretro slang shaders, a feature set that belongs to a living program, not a preserved one.

Security and the modern-PC problem

An unmaintained emulator is not just missing features; it is missing fixes. ZSNES has a publicly known security issue from 2015 in which a specially crafted ROM file could cause code hidden in the ROM to run on the user’s computer when the game was loaded — and with development discontinued, there is no maintenance channel through which such issues get repaired. The practical guidance writes itself: never load untrusted ROM files in ZSNES, and do not make an unpatched 2007 program your everyday emulator in the first place.

There are quieter, everyday problems too. ZSNES was written around assumptions from its era — its interface, its save and cheat handling, and its netplay (disabled from version 1.50 onward, so online play requires hunting down far older builds) all belong to another period of PC gaming. None of this diminishes what ZSNES achieved in 1997 or 2001. It does mean that in 2026 every practical question a new player asks — will it run well on my current PC, is it safe, is it still looked after — has the same answer, and the answer is not ZSNES.

What Snes9x gives you instead

• A maintained release: Snes9x 1.63 (2024), with official Windows 32-bit and 64-bit, macOS and Linux builds and libretro core packages from the project’s own GitHub releases — not a mirror of a 2007 file.
• Modern video: Direct3D, OpenGL and Vulkan output, with Cg, GLSL and slang shader support depending on the driver.
• Current conveniences: up to 100 save states (10 slots across 10 banks, files .000–.099), its own rewind feature (enable the rewind buffer first — it is off by default), Game Genie and Pro Action Replay cheats with a built-in cheat search, and .srm battery saves that are compatible across SNES emulators, so progress you made in ZSNES-era saves is not stranded.
• Low demands: the official readme asks only for Windows XP or later with DirectX 9 and recommends a 1 GHz-class CPU — the classic-PC friendliness ZSNES was loved for, kept alive.
• No firmware chores: normal SNES games need no BIOS file; Snes9x emulates the enhancement chips in code.

Accuracy has moved on as well. Emulation Gametech Wiki rates Snes9x’s accuracy as High with a small, enumerated set of known-issue titles, and notes it is less accurate than bsnes or ares — the current accuracy leaders — while running at full speed on hardware those projects cannot. ZSNES, by contrast, was famous even in its prime for speed-first shortcuts; its own era’s compromises are frozen into the 1.51 build forever.

Verdict: visit the museum, live elsewhere

Keep ZSNES the way you keep a childhood console: with affection, and for the occasional nostalgia session with ROMs from your own collection that you trust. For actually playing — safely, on a modern PC, with current features and a maintainer — use Snes9x or one of the other living emulators in this cluster. Start with the best SNES emulator field guide for the full landscape, compare the accuracy-first option in Snes9x vs bsnes, and see the modern challenger in Snes9x vs Mesen.

Should you keep a copy of ZSNES at all?

There is a fair case for keeping ZSNES installed, as long as it stays in its museum role. If you have save files, replays or muscle memory from its era, or you simply want to show a younger player what PC emulation felt like in the early 2000s, the 1.51 build is a genuine piece of computing history — the falling snow and all. The rules for keeping it safely are simple. Only ever load ROMs from your own collection that you trust, because of the known crafted-ROM security issue and the absence of any maintainer to patch it. Do not download "ZSNES" builds from random modern sites claiming to be new versions; the last official release is 1.51 from January 2007, and anything dressed up as a newer classic ZSNES deserves suspicion. And do your real playing — the long RPG, the saves you would hate to lose — in a maintained emulator such as Snes9x, where your .srm progress stays portable and your emulator is still looked after.

Origins and where each project stands

According to the libretro documentation, the Mesen-S core was authored by M. Bibaud (Sour), is built in C++ and C#, and runs on Windows and Linux. Emulation Gametech Wiki records that Mesen-S launched in April 2019 as the SNES sibling of Sour’s NES emulator Mesen. That NES heritage matters: Mesen earned its reputation on accuracy and on polished debugging and development tools, and Mesen-S was built in that image. The wider Mesen line has since continued to evolve — Sour’s work moved on into Mesen 2, and the project now also continues as a community edition — so anyone choosing Mesen-S today should check which current Mesen build is the actively developed one for their platform.

Snes9x’s story is continuity. It has been developed, ported and re-ported for more than two decades, its file formats are shared across the emulation scene — its cheat .cht files are also used by higan/bsnes, for example — and its current release still ships first-party builds for Windows (32-bit and 64-bit), macOS and Linux, plus libretro core packages. When a guide, forum answer or front-end preset mentions Snes9x, it is usually still accurate, because the project changes steadily rather than in revolutions.

Scope: what each one plays

Mesen-S was designed as more than a bare SNES emulator: its libretro core documentation lists SNES and Super Famicom support alongside Game Boy and Game Boy Color, with complete Super Game Boy support. That last point is a genuine differentiator — Snes9x has no Super Game Boy emulation at all. If playing Game Boy games through the SGB, or in the same app as your SNES library, appeals to you, Mesen-S (like bsnes) covers ground Snes9x simply does not.

Snes9x counters with breadth of a different kind: breadth of places. Beyond the desktop builds, the Snes9x family includes the libretro core for RetroArch, Snes9x EX+ on Android, Snes9x GX on Wii and GameCube, and long-lived ports for 3DS and PSP — separate projects by separate maintainers, all growing from Snes9x code. If your SNES playing happens across a phone, a modded console and a PC, there is probably a Snes9x-shaped option on each of them, and the standard .srm battery-save format lets your progress travel between SNES emulators.

Accuracy, in honest terms

Mesen-S set out to be as accurate as possible, and its documentation says so directly. Snes9x’s honest position is the one Emulation Gametech Wiki gives it: accuracy rated High, a small set of known-issue titles (the readme names SD Gundam GX and the two Hayazashi Nidan Morita Shougi games, on unemulated DSP-3 and Seta chips, as not working), and a note that it is less accurate than bsnes or ares while running at full speed on weaker hardware. There is no official compatibility percentage for Snes9x, and we will not invent one for Mesen-S either. In everyday terms: both will play the mainstream SNES library very well; the differences appear at the edges, and at the edges an accuracy-focused design like Mesen-S or bsnes is the safer bet.

Day-to-day fit

• Setup: Snes9x needs no BIOS or firmware for normal SNES games — it emulates the enhancement chips in code — and on Windows it is extract-and-run with no installer. Mesen-S is a conventional modern application on Windows and Linux.
• Platforms: Snes9x offers official Windows, macOS (a Universal build for Intel and Apple Silicon, macOS 10.12 or later) and Linux AppImage builds, plus the fork ecosystem above. Mesen-S’s documented home is Windows and Linux, including as a libretro core.
• Longevity risk: Snes9x’s latest stable is 1.63 (2024) from a project active since the 1990s. Mesen-S is newer, and its lineage now runs through Mesen 2 and the community edition, so check you are downloading the maintained branch.
• Debugging and tinkering: the Mesen family is known for developer-friendly tooling; Snes9x counters with a built-in cheat search, Game Genie and Pro Action Replay code support, and decades of community knowledge.

Verdict

Choose Mesen-S if you like modern, accuracy-focused design, want Super Game Boy support in the same program, and are on Windows or Linux. Choose Snes9x if you value a still-releasing emulator with the widest port and fork ecosystem, a native Mac build, and the lowest-friction setup on modest hardware. Many players will honestly be happy with either for the mainstream library — the deciding factors are platform and the edge cases above. For the accuracy benchmark see Snes9x vs bsnes, for the frontend question see Snes9x vs RetroArch, and for the full decision walk-through see the best SNES emulator field guide.

A note on momentum and support

One practical factor rarely shows up in feature lists: where you will find help in two years’ time. Snes9x’s long history means its behaviour is documented in an enormous trail of guides, forum threads and front-end presets, and most answers you find will still apply to 1.63 because the program evolves gradually. The Mesen family’s world is smaller but more concentrated, with its development now carried forward through Mesen 2 and the community edition, so the smart move for a new Mesen-S user is to start from the current Mesen builds and their documentation rather than from an old standalone Mesen-S download a mirror may still be offering. Neither community will leave you stranded — but they reward slightly different habits: Snes9x rewards searching the accumulated record, while the Mesen line rewards following the current project.

What "accuracy-first" actually means

Emulation Gametech Wiki’s SNES comparison table is a useful, sober anchor here. It rates Snes9x’s accuracy as High, lists 5 known issues for it, and marks it as recommended — while its Snes9x summary notes plainly that Snes9x "might not be as accurate as bsnes or ares" but "is still a good choice for systems that can’t run either at full speed." That single sentence is this whole comparison in miniature: bsnes and ares chase the last edge cases; Snes9x keeps almost everything running well on hardware the accuracy-first projects struggle with.

Those edge cases are real, but they are also specific. Accuracy-first emulation matters most for games that exploit unusual hardware timing, for homebrew and ROM-hack developers testing against real-hardware behaviour, and for preservation-minded players who want a glitch to be the game’s fault, never the emulator’s. For the mainstream SNES library played casually, Snes9x’s High rating is not marketing language — it reflects a mature emulator whose remaining issues are a short, named list rather than a pattern.

The honesty section: what Snes9x does not run

We will name that list, because a comparison that hides it is worthless. The readme bundled with Snes9x 1.63 states that some add-on chips are not emulated — it gives DSP-3, Seta-11 and Seta-18 as examples — and that three games "currently do not work with any version of Snes9x": SD Gundam GX (DSP-3), Hayazashi Nidan Morita Shougi (Seta-11) and Hayazashi Nidan Morita Shougi 2 (Seta-18). Satellaview / BS-X support in Snes9x is also only partial. There is no official compatibility percentage for Snes9x — anyone quoting you one is inventing it — but a handful of known-issue titles against the whole library is the honest framing. If one of those specific games is the reason you emulate, bsnes is your answer; if none of them are, this gap may never touch you.

Firmware files and Super Game Boy: two practical contrasts

Low-level emulation has a housekeeping consequence. The bsnes/higan approach emulates some enhancement chips at a level that can require DSP firmware dumps — files extracted from real hardware — for certain chip games. Snes9x takes the other route: it emulates the enhancement chips in code, and normal SNES games need no BIOS or firmware file at all. Its only firmware-adjacent exceptions are optional base files for two add-on systems — STBIOS.bin for Sufami Turbo and the BS-X base cartridge for Satellaview. For most players, setup in Snes9x is simply: extract, load a ROM, play.

Super Game Boy cuts the other way. bsnes offers true Super Game Boy emulation, so Game Boy cartridges played through the SGB accessory are within its scope. Snes9x has no Super Game Boy support at all — there is no SGB code in the project, and no BIOS file you can add to change that. If SGB play matters to you, that is a clean, decisive point for bsnes (or for a dedicated Game Boy emulator), and no amount of Snes9x settings will substitute.

Hardware demands: the convenience half of the title

Snes9x’s only official system specification is the one printed in its readme: "Windows XP and up. DirectX 9," with a recommendation of an 800 MHz CPU for good results and 1 GHz for a near-perfect experience, noting that certain add-on-chip games want a faster machine. In modern terms, that means essentially any PC still in service — old laptops, office machines, low-power mini PCs — runs Snes9x at full speed. bsnes makes no apology for demanding significantly more powerful hardware in exchange for its accuracy, and on a weak machine that trade can mean the difference between playing and not playing.

• Pick bsnes if you want the accuracy-first reference, are developing or testing homebrew, need Super Game Boy emulation, or specifically want one of the titles Snes9x cannot run.
• Pick Snes9x if your PC is modest, you want zero firmware housekeeping for normal games, or you simply want a mature emulator that starts fast and stays out of the way.
• Pick both if you play widely: Snes9x as the everyday default, bsnes for the edge cases — they coexist happily, and .srm battery saves are compatible across SNES emulators.

Verdict

bsnes is the more accurate emulator; Snes9x is the more convenient one, and for most players on most hardware convenience is what they will actually feel. The honest summary is the Gametech Wiki one: Snes9x is less accurate than bsnes or ares, highly compatible, recommended, and able to run at full speed where the accuracy-first projects cannot. Compare the frontend route in Snes9x vs RetroArch and the other modern contender in Snes9x vs Mesen, or use the field guide to pick by use case.

One more bsnes draw: presentation and reference value

Accuracy is bsnes’s headline, but it is not its only draw. The bsnes line is also known for presentation work built on top of that accuracy — most visibly its HD Mode 7 graphics, which render the SNES’s famous rotation-and-scaling mode at higher resolution with optional supersampling — and for acting as a reference that other projects measure themselves against. That reference role is easy to underrate: when developers, ROM hackers or even other emulator authors need to know what the hardware really does, the accuracy-first projects are where the answer gets settled. None of that changes the trade at the heart of this page — you pay for it in hardware demands and, for some chip games, in firmware housekeeping — but if your interest in SNES emulation goes beyond playing the hits, bsnes gives you something Snes9x deliberately does not try to be: a microscope as well as a console.

The standalone experience: one program, one job

Standalone Snes9x — currently version 1.63, released on 9 July 2024 — is about as direct as emulation gets. There is no installer and no account: you extract the ZIP, run the executable, use File → Load Game, and play. The menus are a conventional Windows, Mac or Linux menu bar, the settings live in dialogs labelled for SNES hardware, and your battery saves (.srm) and save states are written to a Saves folder next to the program. Everything you see belongs to SNES emulation, and nothing else competes for your attention.

That focus has a cost. Standalone Snes9x only plays SNES games. If you also want NES, Genesis, arcade or PlayStation games in the same library, with the same controller mappings and the same screen treatment, you will be installing and learning several separate programs. RetroArch exists precisely to remove that duplication — at the price of a bigger, more abstract interface you have to learn once.

The RetroArch experience: one shell, many systems

In RetroArch you install the frontend, download the Snes9x core from its built-in core downloader, point it at the same ROM files, and play — but the game is now running inside RetroArch’s world. Your video settings, controller profiles, save locations, screenshots and library scanning are RetroArch’s, shared across every core you use. Players who emulate many systems often love this consistency: learn the menus once, and every console behaves the same way.

The same layering confuses newcomers. When something does not work, you have to work out whether the setting belongs to RetroArch, to the Snes9x core’s own options, or to the game — and guides for standalone Snes9x will not always map onto what you see on screen. If SNES is the only system you care about, that extra layer buys you little.

Rewind, shaders and netplay: whose feature is it anyway?

This is where the two genuinely diverge, because several headline features exist in both places but are implemented by different layers. Rewind is a good example. Standalone Snes9x has its own rewind, added in version 1.54: hold the R key and the game runs backwards. It is, however, switched off by default — the rewind buffer is set to 0 MB on a fresh install, and you must give it a non-zero size in the emulation settings before the key does anything. In RetroArch, rewind is a frontend feature applied to whichever core is loaded; the Snes9x core supports it, but RetroArch owns the setting. Same button, different owner — and a different place to fix it when it does not work.

Shaders split the same way. Standalone Snes9x 1.63 supports Cg shaders in its Direct3D and OpenGL drivers, GLSL shaders under OpenGL, and libretro .slang shaders under OpenGL (since 1.59) and Vulkan (since 1.62) — a genuinely capable built-in stack for CRT-style looks. RetroArch adds its own, larger shader system on top, with preset browsing and per-game or per-core overrides managed by the frontend. If you like endlessly auditioning CRT presets, RetroArch’s stack is the richer playground; if you want to pick one good preset and forget it, standalone Snes9x already has what you need.

Netplay is the clearest split of all. Standalone Snes9x does contain netplay — up to five players, one machine acting as server over TCP port 6096 — but the readme that ships with 1.63 still carries the maintainer’s 2017 note that netplay "has not been maintained and tested in a long time, so it might be broken." The libretro documentation describes the Snes9x core as recommended for netplay precisely because RetroArch’s own netplay system is the maintained path. If playing online with friends is a priority, that is a strong, practical reason to run Snes9x inside RetroArch rather than on its own. We compare that arrangement in more depth in standalone Snes9x vs the libretro core.

Saves, settings and moving between the two

The good news is that you are not locked in. Battery saves use the standard .srm format — the Snes9x readme notes that .srm files are compatible with all SNES emulators — so your in-game saves can move between standalone Snes9x and the RetroArch core. Cheat files (.cht) are likewise shared with other emulators. Save states are the fragile part: state formats are tied to the emulator build that made them, so treat states as disposable and .srm saves as your real progress.

• Choose standalone Snes9x if you only play SNES, want the shortest path from download to game, or are putting an emulator on a modest or older PC — the official readme only asks for Windows XP or later with DirectX 9 and recommends a 1 GHz-class CPU for a near-perfect experience.
• Choose RetroArch with the Snes9x core if you emulate several systems, want RetroArch’s netplay, or want its frontend-wide shader, library and controller systems applied uniformly to everything.
• Choose both if you like experimenting: they can sit side by side on the same machine and share the same ROMs and .srm saves.

Verdict

Neither option makes the other obsolete, because they solve different problems. Standalone Snes9x is the simpler, lighter, more predictable choice for SNES-only play, and its built-in rewind and slang shader support are better than many people expect. RetroArch earns its complexity when SNES is one system among many, or when its maintained netplay is the feature you actually need. For the accuracy-first alternative to both, see Snes9x vs bsnes, and for a guided pick by player type, see our best SNES emulator field guide.