This is a screenshot of the public domain game for Nintendo DS , Diamond Trust of London , being played in the GNU GPL 2.0 -licensed emulator DeSmuME version 0.9.11 on macOS High Sierra . As the game is public domain, the emulator is free and open-source softw Image by Yetisyny, via Wikimedia Commons (CC0).

melonDS DS

NINTENDO DS/DSI EMULATOR CORE

melonDS DS

melonDS (libretro melonds_ds core) — a libretro core that runs Nintendo DS and DSi software using the melonDS emulator codebase. Intended for use inside RetroArch and other libretro frontends.

Jump to download ↓Jump to setup guide ↓

Nintendo DS/DSiPRIMARY SYSTEM

History documentedPROJECT BEGAN

Open sourcePROJECT MODEL

WHY IT MATTERS

Why use melonDS DS (libretro core)?

Provides a current melonDS-based core for libretro frontends with DSi support, a focus on compatibility and usability inside RetroArch, and cross-platform core builds distributed through libretro and the melonDS project.

BEST FOR

Best for

Users who run RetroArch (or another libretro-based frontend) and want an up-to-date melonDS implementation with DSi features and integration with libretro features (cores, input mapping, saves, and frontend-managed updates).

Gameplay from New Super Mario Bros. on Nintendo DS.

The people behind melonDS DS

History and status

melonDS is an actively maintained Nintendo DS / DSi emulator project; the melonDS codebase is maintained upstream (melonDS-emu on GitHub) and a libretro core (melonds_ds, sometimes packaged as melondsds_libretro) provides a libretro-compatible build for RetroArch and other frontends. Libretro maintains documentation pages for the melonDS DS core and the libretro core-info repository lists a melonDS DS entry describing the core. Both the upstream melonDS project and libretro-hosted melonDS core repositories have activity and releases; official melonDS binaries and source are available from the melonDS website and the project's GitHub, while the libretro core lives in libretro's repositories. The core requires user-supplied BIOS/firmware dumps for full DS/DSi system emulation (the project documents this requirement), though melonDS historically includes a FreeBIOS fallback for direct-boot modes in some builds. Project status (active/maintenance) should be confirmed against the upstream GitHub and libretro repositories for the current date before taking action.

What melonDS DS supports

Nintendo DS (ROM .nds)
Nintendo DSi (requires DSi BIOS/firmware/NAND image for full DSi emulation)
RetroArch and other libretro frontends (melondsds_libretro core)
Windows
Linux
macOS (where libretro cores are supported and a build exists / can be built for the platform)

Download and availability

OFFICIAL DOWNLOADS

Get melonDS DS

Official melonDS standalone binaries and source are provided by the melonDS project (melonDS website and GitHub). Libretro/distribution builds of the melonds_ds core are documented on the Libretro docs core page and libretro's core-list; RetroArch users can install the melonds_ds core through RetroArch's Online Updater or by placing the core binary (melondsds_libretro.dll / .so / .dylib) into RetroArch's cores directory as documented by libretro.

Get melonDS DS ↗

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.

melonDS DS setup guide

Setup note: Setup checklist: obtain the correct libretro melonDS core build for your platform, place it in your frontend's cores directory or install via the frontend's core manager, and configure system/BIOS paths and input. The guide below focuses on practical, emulator-specific steps for RetroArch/libretro users.

1) Get the correct core or standalone build: For RetroArch: use RetroArch's Online Updater to download the 'MelonDS DS' (melonds_ds / melondsds_libretro) core, or download a prebuilt core binary for your platform from libretro or a trusted buildbot. Alternatively, download the official melonDS standalone binaries or build from the upstream melonDS GitHub if you prefer the standalone app. Confirm the core filename for your OS (melondsds_libretro.dll on Windows, .so on Linux, .dylib on macOS) and put it in RetroArch's 'cores' directory if installing manually. Confirm core/version from libretro docs or the core-info repository.
2) Prepare BIOS / firmware / NAND (required for full emulation): melonDS requires user-supplied Nintendo DS BIOS and firmware dumps for full correctness; for DSi emulation you also need the DSi BIOS, firmware, and a NAND image. Consult melonDS / libretro documentation for exact filenames and how to name/place them. Some builds may include or enable a FreeBIOS fallback for direct-booted ROMs, but encrypted games, system menu, and full DSi features generally require the real files. Do not download BIOS/firmware/NAND from untrusted sources; these are copyrighted files you must obtain from hardware you own.
3) Configure RetroArch core and system paths: In RetroArch, after the melonds_ds core is loaded, open the core options or RetroArch settings to point the core to the directory containing your BIOS/firmware/NAND files (commonly retroarch/system/melonDS DS or an equivalent path). If placing the core manually, ensure the core filename matches expected naming in your frontend and restart RetroArch to let it detect the new core.
4) Load games and choose boot mode: melonDS supports 'boot firmware' (to run the DS/DSi system menu) or 'boot ROM directly' modes. If you want system-menu features (DSi menu, PictoChat, DSiware), boot through firmware and ensure the required files/NAND are present. For many ROMs you can load the .nds file directly if you accept the direct-boot behavior; encrypted/region-protected titles and DSi-specific features require firmware and/or NAND images.
5) Input, touchscreen, and peripherals: Map touchscreen input to mouse or touch input in your frontend; pin or map the virtual stylus to a mouse button or touch interface. Configure microphone input (if needed) in the core options; some frontends require explicit microphone device selection and permission. Save and test input mappings with a simple game that exercises touchscreen and microphone features.
6) Saves, save types, and compatibility: melonDS determines save type from the save file size and may require correctly sized external save files when migrating saves from other emulators. Use the frontend's save-state feature for quick saves, but keep battery/flash saves separate for compatibility with other emulators or hardware. Verify game save type if importing saves from other sources.
7) Networking and advanced features: The libretro core may expose network-related options; for Wi‑Fi/Download Play and multiplayer features, consult the melonDS and libretro documentation for whether those features are available/enabled in the core build you are using. Netplay behavior and availability can differ between the standalone melonDS and the libretro core.
8) Building from source (optional): If you need a custom build, get the upstream melonDS source from the project's GitHub, follow its BUILD.md for platform-specific build steps, and (if building a libretro core) follow the libretro core build instructions for producing melondsds_libretro. Building requires typical developer tools for your platform and following the project's documented build steps.

Software reminder: melonDS/libretro cores do not include commercial games, firmware, BIOS, or NAND images. You must supply those files yourself where required and ensure you have legal rights to use them.