- Top Pick: JSAUX 6-in-1 Docking Station (HB0609)
- Runner-up: KTC 15.6-inch Portable Monitor (H15F9)
- Also consider: SanDisk 1TB Extreme microSDXC Card
The Steam Deck should be the perfect Nintendo DS machine: a handheld with a touchscreen and a processor far stronger than anything the DS era imagined. melonDS, the accuracy-first DS emulator, runs natively on Linux, so the pairing looks obvious. The catch is the same one every DS emulator faces away from real hardware: the DS has two screens and the Deck has one 1280×800 panel to share between them.
As an Amazon Associate, we earn from qualifying purchases.
This walkthrough covers the Deck side of the setup: installing melonDS the way the project publishes it for Linux, adding games and system files dumped from your own DS, choosing a layout per game, handling touch input, and launching from Game Mode.
This article contains affiliate links, and purchases made through them may earn a commission at no extra cost to you.
Quick Answer
Install melonDS from Discover in Desktop Mode, using the Flatpak build published for Linux, then add game dumps from your own DS cartridges. Most games boot on the built-in replacement BIOS. Use the Hybrid layout so one screen stays large, tap the bottom screen directly on the touchscreen, and add melonDS to Steam for Game Mode play.
Step 1: Install melonDS the SteamOS Way
Switch to Desktop Mode and open Discover, the built-in software store, then search for melonDS and install it. This is the Flatpak build, published on Flathub under the application ID net.kuribo64.melonDS. It is the practical route on SteamOS because the system partition is read-only: conventional installs fight the OS and can vanish at a system update, while Flatpaks live in your home directory and update through Discover like any other app.
The project’s download page also offers a Linux AppImage, a single self-contained file you make executable and run. That works on a Deck too, and suits anyone who wants the newest build without waiting for the store package. Either way, take the file only from the project’s site or its Flathub page.
Step 2: Where Things Live on SteamOS
The Flatpak is sandboxed, so melonDS keeps its data in its own folder under .var/app/net.kuribo64.melonDS in your home directory, rather than the usual Linux config locations. That folder holds the configuration and the BIOS and firmware files once you add them. The AppImage instead uses the standard home-directory locations.
Keep your game library outside the app folder, in a directory you control, and point melonDS at it. Games on the internal drive or a microSD card both work, and a separate library means a reinstall or a switch between the Flatpak and AppImage builds never touches your dumps or the saves stored beside them.
Step 3: BIOS and Firmware From Your Own DS
Since version 0.9.4, melonDS ships with a built-in replacement BIOS and can generate firmware, so system files are optional for ordinary DS play: most games boot with nothing supplied. Start there and confirm your library runs before dumping anything.
Real files from your own DS still earn their place: authentic boot behaviour belongs to genuine dumps, and some features, such as GBA-slot connectivity, expect them. The files are bios9.bin at 4KB, bios7.bin at 16KB, and firmware.bin at 128, 256 or 512KB depending on the source machine, produced with the project’s flashcart dumper. One trap: firmware dumped from a DSi or 3DS carries no boot code, so it cannot start the system menu. DSi mode has no shortcut at all: it needs the full DSi set, including a NAND image, from your own console.
Step 4: Two Screens, One 800p Panel
Each DS screen is 256×192, so the pair is small next to the Deck’s panel, and layout decides how that space is shared. melonDS offers four arrangements. Natural stacks the screens as a real DS does. Vertical and Horizontal force a column or row. Hybrid, the handheld favourite, keeps one screen large and shrinks the other alongside it.
Screen sizing matters as much as arrangement. Set it to Auto and melonDS reads how the running game uses its displays and emphasises the right one, which matters because games swap the action between screens. Add the mid-screen gap for titles where objects travel between displays, and use 90-degree rotation for book-style games held sideways. Treat layout as a per-game decision: Hybrid for games that play on top and keep a map below, Natural for games that treat both screens as one tall playfield.
Step 5: Touch, Trackpads and the Microphone
The bottom screen is a touchscreen on real hardware, and on the Deck it still is: when it is visible in your layout, you can tap and draw on it directly with a finger. For finer work, set the right trackpad to act as a mouse in the Steam Input profile for melonDS; the emulator accepts mouse input as touch input, so the trackpad becomes a precision pointer. A passive capacitive stylus is the closest match to the original hardware for drawing-heavy games, and needs no pairing or charging.
Games that listen for blowing or speech use the microphone options. White noise, triggered with the microphone hotkey, satisfies titles that only listen for loud noise, and a WAV sample covers the rest. For voice-driven games, the Deck’s built-in microphone is the honest input.
Step 6: Settings for the Deck Hardware
Two settings do the heavy lifting. The JIT recompiler translates DS code into native code and caches it; the project treats it as the way to reach full speed on modest hardware, so leave it on. For the renderer, OpenGL hands 3D work to the Deck’s graphics unit and unlocks internal resolution scaling: 2x or 3x cleans up 3D games noticeably on an 800p panel. The scaling only redraws the 3D layer, though; 2D sprites and backgrounds are drawn at native resolution and softened by screen filtering.
Keep the threaded software renderer in mind as a fallback for a title with flickering polygons, and if a game crashes with the JIT on, disabling its fast memory option, then the JIT itself, is the documented first diagnostic step.
Step 7: Saves That Travel to Your Desktop
melonDS detects each game’s save type automatically and writes a raw save file beside the game file, in the same format a flashcart uses. That makes the save the bridge between devices: copy the game and its save to a desktop install of melonDS, or back again, and progress simply continues, with no conversion step.
Turn on the Separate savefiles option if you lean on savestates, so loading a state cannot overwrite your main save with an older one. Savestates themselves are a convenience for the moment, not an archive format: finish sessions on a real in-game save before moving files around.
Step 8: Docked Play and a True Second Screen
Docking the Deck unlocks the arrangement a desktop takes for granted. melonDS can place its two screens in separate windows, so with an external monitor connected through a dock, one screen can live on the big display while the other stays on the Deck’s own panel: the closest thing to holding a real DS in front of a television. A portable monitor beside the Deck achieves the same split at a desk. In handheld play, stick with the single-panel layouts from Step 4.
Step 9: Add melonDS to Game Mode
Still in Desktop Mode, open Steam, choose Add a Game, then Add a Non-Steam Game, and select melonDS. It now launches from Game Mode like any other title, with suspend, the performance overlay and per-game Steam Input profiles available. Build the profile once, with the trackpad-as-mouse mapping from Step 5, and every DS game opened through melonDS inherits it.
Gear That Suits DS Play on the Deck
JSAUX 6-in-1 Docking Station (HB0609)
A dock is what turns the Deck plus a spare display into a two-screen DS setup, with wired networking and charging included.
Specs:
- Model: HB0609
- HDMI output up to 4K at 120Hz
- Gigabit Ethernet, USB-C PD charging up to 100W
- USB-A and USB-C data ports
JSAUX 6-in-1 Docking Station on Amazon
KTC 15.6-inch Portable Monitor (H15F9)
A slim second display gives the top screen its own home in docked play, running from a single USB-C cable alongside the Deck.
Specs:
- Panel: 15.6-inch FHD 1920×1080 IPS
- Inputs: USB-C and Mini HDMI
- Built-in speakers, HDR support
- Model: H15F9
KTC 15.6-inch Portable Monitor on Amazon
SanDisk 1TB Extreme microSDXC Card
A full DS library is small by modern standards, but a fast card also holds the rest of your emulation collection.
Specs:
- Model: SDSQXAV-1T00-GN6MA
- Read speeds up to 190 MB/s as stated by the maker
- Speed classes: Class 10, U3, V30, A2
- SD adapter included
SanDisk 1TB Extreme microSDXC Card on Amazon
MEKO Universal Stylus (2-Pack)
A passive disc-tip stylus is the closest feel to the DS original for drawing and handwriting games, and it works on the Deck’s capacitive screen with no setup.
Specs:
- Disc tip for precision, fiber tip for tapping
- Two pens with six replacement tips included
- Passive capacitive design: no battery, no pairing
- Works on all capacitive touchscreens
MEKO Universal Stylus on Amazon
8BitDo Pro 2 Bluetooth Controller (Hall Effect)
For docked play, a proper pad with a strong D-pad covers the button-led half of the DS library while the screens sit on the big display.
Specs:
- Hall Effect joysticks, two Pro back paddle buttons
- Bluetooth 4.0 and USB-C wired connection
- Battery: 1000mAh, up to 20 play hours as stated by the maker
- SteamOS listed among supported platforms by 8BitDo
8BitDo Pro 2 Bluetooth Controller on Amazon
How to Choose
Choose by how you actually play. Handheld-only players need nothing beyond the Flatpak install, the JIT, OpenGL at 2x and the Hybrid layout. Stylus-heavy players should add a capacitive stylus and keep the bottom screen large and low in per-game layouts. Players who split time between Deck and desktop should organise around the .sav file: one library folder, saves beside games, copied both ways. Only docked players need extra hardware, and for them the dock comes first, the second display second.
Who Should Skip
Skip the Deck route if local multiplayer is your reason for playing DS games: melonDS’s wireless emulation is built around instances in a PC setup, and this handheld guide does not change that picture. Skip DSi mode unless a specific DSi title is the goal, since it demands the full dumped file set for a feature the project still labels work in progress. And skip melonDS entirely if your favourites are the rare save-type exceptions the project documents as unsupported.
FAQ
Does melonDS on the Deck need BIOS files?
No. Since version 0.9.4 the emulator includes a replacement BIOS and generated firmware that boot most DS games. Dumps from your own DS give authentic boot behaviour, and DSi mode still requires the full DSi file set.
What is the best screen layout on the Deck?
Hybrid, for most games: the action screen stays large while the second screen remains visible for maps and menus. Use the stacked Natural layout for games that treat both screens as one tall playfield, and set sizing to Auto either way.
Do my desktop melonDS saves work on the Deck?
Yes. melonDS writes the same raw save format on every platform and keeps it beside the game file, so copying the pair between a desktop install and the Deck carries your progress in both directions.
Flatpak or AppImage on Steam Deck?
The Flatpak from Discover is the simpler default: it installs cleanly on read-only SteamOS and updates with your other apps. The AppImage suits anyone who wants the newest build immediately.
Final Verdict
melonDS on the Steam Deck works because the hardware answers the emulator’s hardest questions: a touchscreen for the bottom screen, trackpads for precision, and a dock for a true second display. Install the Flatpak, turn on the JIT, pick Hybrid as your default layout and adjust per game, and the DS catalogue feels at home in your hands.










