nesicide

NES EMULATOR

nesicide

NESICIDE (NES Integrated Development Environment) is an open-source IDE that includes an integrated NES hardware emulator for development and testing of NES/Famicom code and homebrew. It is primarily an assembly/C development environment with a built-in emulator and debugging tools rather than a consumer-focused game player.

Jump to download ↓Jump to setup guide ↓

nesicide emulator screenshot.

nesPRIMARY SYSTEM

History documentedPROJECT BEGAN

Open sourcePROJECT MODEL

WHY IT MATTERS

Why NESICIDE exists

NESICIDE was created to give homebrew and hobbyist developers an integrated workflow: edit source, assemble/compile, run in an integrated NES hardware emulation environment, inspect CPU and PPU state, and debug. It focuses on development features rather than being a high-compatibility general-purpose NES player.

BEST FOR

Best use cases

Writing and debugging NES/Famicom homebrew (6502 assembly/C), stepping through CPU/PPU state, testing mappers and small demos within an integrated toolchain, and learning NES internals using an IDE-centric workflow.

The people behind nesicide

History and status

The project is hosted on GitHub and has a history on NES development discussion sites. Upstream sources and discussions show NESICIDE has long been an IDE with an included emulator component; over time the project moved to GitHub where sources, issues, and releases are maintained. The project is open-source; activity levels vary and should be checked on the repository and its releases page for the most recent updates. Community discussion threads on nesdev.org document usage, packaging attempts, and historical updates. Because project activity can change, confirm current development status on the repository and the releases page before relying on recent-binary availability.

What nesicide supports

Nintendo Entertainment System (NES) / Famicom (development and testing)
Included emulator component for running NES code within the IDE
Debugging and inspection of CPU/PPU state, assembler integration
Cross-platform builds (Windows, Linux, macOS) reported in upstream documentation

Download and availability

OFFICIAL DOWNLOADS

Get nesicide

Official binaries and source are distributed from the project's GitHub repository releases page. If prebuilt binaries are not available for your platform, the source can be built from the repository; building requires a C++ toolchain and Qt (see guide steps).

Get nesicide ↗

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.

nesicide setup guide

Setup note: Practical setup steps below are based on the project's official repository and community documentation. Confirm exact package names and version numbers on the repository and releases page before beginning.

1) Get the official sources or releases: Open the project's GitHub repository and check the Releases section for prebuilt binaries for your platform. If a release binary is available for your OS, download that package and extract/install following any bundled README. If no suitable binary exists, download the source (zip or git clone) from the repository.
2) Check requirements: NESICIDE is implemented in C++ using Qt. To build from source you will need: a supported Qt development stack (Qt libraries and qmake/CMake as used by the repo), a compatible C++ compiler (MSVC on Windows or gcc/clang on Linux/macOS), and standard build tools. Confirm the repository's README or BUILD documentation for the exact Qt major version and any additional library requirements before installing.
3) Building (when no binary available): Clone the official repository, install the Qt development packages matching the repo's supported Qt version, then run the project's build instructions (qmake or CMake as provided). Use your platform's preferred compiler toolchain (Visual Studio on Windows, gcc/clang on Linux/macOS). Watch the repo's README for any platform-specific flags and for documentation of optional components (for example, extra libraries for audio or graphics backends).
4) Running the IDE and emulator: After installation or when running a release binary, open NESICIDE and create or open a project. Use the IDE's assembler/compile step to build your ROM image; then run it in the integrated emulator window. The IDE provides debugging tools (CPU/PPU viewers, memory viewers, breakpoints). Consult the repository README or in-app help for exact menu locations and debugger usage.
5) ROMs, BIOS and legality: NESICIDE does not include commercial game ROMs, copyrighted BIOS, or other proprietary firmware. Use only code and ROM images you have legal right to use. For development, assemble your own test ROMs or use public-domain/homebrew test ROMs and NES test suites as permitted by their licenses.
6) Troubleshooting and packaging: If you encounter missing libraries or runtime problems, confirm the Qt runtime matches the build and that runtime dependencies (DLLs/so/dylib) are available on your PATH or bundled with the executable. For Linux distributions, check community packaging threads for distribution-specific packages if you prefer not to build from source.

Software reminder: Confirm exact Qt and toolchain versions from the project's README before building. Do not expect commercial game ROMs or BIOS to be bundled with the software.