Screenshot of higan , a video game console emulator Image by byuu, via Wikimedia Commons (GPLv2).

higan

MULTI SYSTEM EMULATOR

higan

higan is a multi-system accuracy-focused emulator (originally bsnes) that emphasizes low-level, cycle-accurate emulation and preservation. It is developed in the open on GitHub and targets exact hardware behavior over performance or convenience.

Jump to download ↓Jump to setup guide ↓

Screenshot of higan , a video game console emulator Image by byuu, via Wikimedia Commons (GPLv2).

Multiple systemsPRIMARY SYSTEM

2004PROJECT BEGAN

Open sourcePROJECT MODEL

WHY IT MATTERS

Why higan exists

higan (originally developed as bsnes) was created to pursue extremely accurate emulation of classic consoles — reproducing hardware timing and behaviour rather than relying on hacks. Over time the project broadened from SNES-only to a multi-system framework focused on preservation, readability, and correctness.

BEST FOR

What higan is best for

Research-grade, low-level emulation and hardware preservation. It is appropriate when you need high-accuracy results for debugging, archival dumps, or to study how original console hardware behaved. It is not optimized for low-power systems or maximum speed; accuracy may require a relatively fast modern CPU.

Gameplay from Super Mario World on SNES.

The people behind higan

History and status

Work began in 2004 under the name bsnes to produce highly-accurate SNES emulation. The project was renamed higan in 2012 as it expanded to support multiple systems and a generalized emulator framework. The original author (known as byuu / Near) led development for many years; the project later moved to an open GitHub-hosted development model with community contributions. In 2018 the bsnes name was revived for a SNES-focused fork aimed at usability and performance, while higan continued as the accuracy- and preservation-focused multi-system project. The higan source and releases are maintained on GitHub and documentation is published online. Current development and releases are available from the project's official GitHub repository and its documentation site (see sources).

What higan supports

Multi-system (focus includes the Super Nintendo / SNES family)
Game Boy-family and other classic handhelds (project documentation lists multiple handheld cores)
Several other 8/16-bit systems (project documentation describes multiple classic console cores)
CD-based systems supported via the project’s CD/BIOS handling (see docs)

Download and availability

OFFICIAL DOWNLOADS

Get higan

Official builds and release archives are published on the higan GitHub releases page. For source builds, clone the official repository and follow the project's build instructions in the documentation. Do not expect commercial game ROMs, console firmware, or BIOS to be included — these must be acquired separately and legally if required.

Get higan ↗

DOCUMENTATION

Official documentation

Read the official configuration, compatibility, and troubleshooting material before changing advanced options.

Read official documentation ↗

Broken or missing download? Emulator projects move and official links sometimes change. Please contact Retro Replay so the source can be verified and updated.

higan setup guide

Setup note: Verified setup steps — use the project repository and documentation as authoritative sources. The steps below summarize the practical setup path and common options; follow the linked docs for platform-specific build flags or prebuilt binaries.

Get the official software: Download prebuilt binaries or source from the official GitHub repository's Releases page (higan-emu/higan). For source compilation, clone the repository and use the documented build procedure in the project's documentation (higan Read the Docs and README in the repo).
Check platform support and dependencies: Consult the repository README and documentation for current platform support and required libraries. The project targets desktop platforms; building from source typically requires a recent C++ toolchain and any platform-specific libraries listed in the docs. Use the release notes for details about prebuilt binaries for Windows, macOS, or Linux.
Provide your own game files and firmware where required: higan does not include commercial games, console firmware, BIOS, or encrypted copyrighted files. If a core requires BIOS or firmware files, obtain and install them separately and legally into the path expected by higan (see documentation for filename and location expectations).
Configure cores and accuracy/performance tradeoffs: higan's design emphasizes accuracy; it exposes configuration options for emulation modes. Read the documentation to understand options (for example, different timing models, CD handling, and peripheral support) and adjust based on your CPU capability. If you need a more user-friendly or higher-performance SNES-focused experience, consider the revived bsnes project instead.
Running and verifying games: Use the GUI or command-line (per current releases) to load game images. For archival or debugging work, consult the project's documentation for recommended verification steps and any checksums/dump formats the project prefers. If you encounter issues, consult the GitHub issue tracker and documentation for guidance and known limitations.
Building from source — practical notes: Follow the README/build instructions in the repository. Ensure your toolchain matches the project's stated requirements in the docs. If the build produces optional plugins or extras, read the docs to enable them explicitly. When in doubt, use an official release binary that matches your OS to avoid build-tool differences.

Software reminder: Always use official project downloads and documentation for builds. Do not distribute or use copyrighted game images, firmware, or BIOS unless you own them or have legal permission.