Skip to content
Go back

Steam Deck Emulation With EmuDeck + NAS

By KingPin 15 min read
Steam Deck Emulation With EmuDeck + NAS
Contents

Your Steam Deck Is Not the Hard Part

Installing emulators on a Steam Deck is a short job. Making the setup survive a second device, a full SD card, and a dead battery takes longer. EmuDeck solves the first problem. Your homelab solves the rest.

My thesis is simple. Let EmuDeck own the emulators and the folder layout, because it does that well. Then keep your ROM library and your saves on infrastructure you control, and let the Deck be a thin client. A handheld with limited internal storage is a bad place for a library you care about.

You will not find a games download source here. You dump your own games and your own BIOS files from hardware you own. EmuDeck’s own FAQ says the same thing: legally, ROMs and BIOS files must come from your own console, and the project will not discuss other methods.

If you want the general Deck-as-a-homelab-terminal angle, I covered that in Steam Deck Homelab Toolkit. If you want a browser-based library server instead of files on a handheld, read RomM vs EmulatorJS. This post sits between them.

What EmuDeck Actually Is

EmuDeck is a set of scripts. Its wiki describes it as a tool that auto-configures your Steam Deck, creates the ROM directory structure, and downloads the emulators with tuned settings. It is not an emulator itself. If it disappeared tomorrow, the emulators would keep running.

That matters for a homelab person, because it means there is no daemon and no server to babysit. You run an installer, it writes files, and it leaves.

The wiki lists what it installs on SteamOS. The wiki (its pages are dated January 2025, so the app may differ) lists these among the emulators it installs on SteamOS:

It also installs Steam ROM Manager and ES-DE, a front-end that browses your library inside one app. Optional extras are Decky Loader, Power Tools, and SteamDeckGyroDSU.

One more note on versions: the latest release I could see in the EmuDeck GitHub organization was v2.7.1, published on 29 September 2026. The wiki pages I read carry January 2025 dates, so some pages lag behind the app. When the wiki and the app disagree, trust the app.

Installing It

The wiki’s install steps for SteamOS are short.

  1. If you use an SD card, format it in Game Mode first. EmuDeck needs ext4 or btrfs.
  2. Switch to Desktop Mode: press the Steam button, choose Power, then Switch to Desktop.
  3. Download the EmuDeck installer from emudeck.com and run it.
  4. Pick an install location, internal SSD or SD card.
  5. Copy your games into the Emulation/roms folder the installer creates.
  6. Copy your BIOS files into Emulation/bios.
  7. Open Steam ROM Manager through EmuDeck, parse, save, then return to Game Mode.

The installer asks whether you want Easy or Custom mode. I only verified the Custom side in the docs: the wiki says Custom Mode gives you more granular options, including a prompt to choose which emulators to install. Pick Custom if you do not want a pile of emulators for systems you will never touch. Pick Easy if you want it done and do not care about the extra disk space.

The installer is also safe to re-run. The wiki says so explicitly when it describes moving an install between the SSD and an SD card, and states that re-running in Custom Mode does not delete your files.

The Emulation Folder

Everything you care about lives in one folder. The install location you chose holds the ROM directory, BIOS files, and storage files. EmuDeck installs the emulators themselves on the internal SSD no matter what you pick.

The paths:

/home/deck/Emulation/roms (internal SSD)
/run/media/SDCARDNAME/Emulation/roms (SD card)
Emulation/bios
Emulation/saves
Emulation/storage

The wiki lists the main subfolders as bios, hdpacks, roms, saves, storage, and tools. ROMs go into per-system folders, for example Emulation/roms/ps2 for PS2. The EmuDeck Cheat Sheet maps every folder name to a system and lists the BIOS files each emulator expects. Keep it open while you copy files.

Two gotchas from the wiki are worth repeating:

That second point decides how you sync saves later, so keep it in mind.

Steam ROM Manager: Getting Games Into Game Mode

Steam ROM Manager (SRM) adds ROMs, emulators, and tools to your Steam library as non-Steam shortcuts, with artwork pulled from SteamGridDB. It is how a PS2 game shows up next to your Steam games with a cover image.

The workflow from the wiki:

  1. Open SRM from the EmuDeck app in Desktop Mode.
  2. Enable the parsers you want. Each parser maps to an emulator or tool.
  3. Click Preview, then Parse.
  4. Wait for the artwork to download.
  5. Click Save apps to Steam.
  6. Close SRM and click Return to Game Mode.

Launching SRM from EmuDeck exits Steam and puts the Deck in Lizard Mode. In that mode, L2 is right click, R2 is left click, and the right trackpad moves the cursor. Do not panic when your controller stops acting like a controller.

Systems with several emulators get several parsers. The EmuDeck FAQ and Cheat Sheet give the example: PlayStation 1 can run through DuckStation (Standalone), SwanStation, or Beetle PSX. Enable the parser you want and disable the others, or you get duplicates.

You also do not have to use SRM at all. The EmuDeck FAQ says you can use SRM, ES-DE, both, or neither. My preference is SRM for the five or six games I actually play, and ES-DE for browsing everything else. Adding every ROM you own to Steam turns your library into a landfill.

The Homelab Part: ROMs on a NAS

Now the part EmuDeck does not do for you. A small SSD is a poor home for a library. A NAS is a better home, because it already has redundancy, snapshots, and a backup job.

I see three workable patterns.

Pattern 1: NAS is the source of truth, Deck gets a copy

Keep the master library on the NAS, sorted in the same folder names EmuDeck uses. Push only what you want on the Deck.

First enable SSH on the Deck. In Desktop Mode, set a password for the deck user with passwd, then start the SSH server.

Terminal window
passwd
sudo systemctl enable --now sshd

Then, run this on the NAS (or any machine that holds the library), one system folder at a time. Use the Deck’s IP address if the hostname does not resolve.

Terminal window
rsync -av /mnt/nas/roms/ps2/ deck@steamdeck:/home/deck/Emulation/roms/ps2/

The trailing slashes matter. Without them, rsync creates a nested ps2/ps2 folder, and SRM will not find your games.

This pattern works offline. That is why I like it for a handheld: a flight does not have a NAS.

If the Deck lives at home, mount your NAS share in Desktop Mode and point a system folder at it. Mount it under your home folder, not under /: SteamOS has a read-only root filesystem, and a system update wipes changes made there. The EmuDeck FAQ recommends symlinks for exactly this kind of linking, and links to a symlink guide.

Terminal window
mkdir -p /home/deck/nas
sudo mount -t nfs nas:/export/roms /home/deck/nas
mv /home/deck/Emulation/roms/gc /home/deck/Emulation/roms/gc.local
ln -s /home/deck/nas/gamecube /home/deck/Emulation/roms/gc

The symlink must keep the system folder name (gc), because SRM parsers and the EmuDeck launchers only scan the folder names from the Cheat Sheet. The original folder has to move aside first, and moving it is safer than deleting it. Swap the NFS line for a CIFS mount if your NAS speaks SMB.

This pattern saves disk space and breaks when the network does. SRM stores shortcuts to paths, so a game on an unmounted share will not launch. Decide whether you play on the couch or on a train, then pick.

Pattern 3: Skip files, serve a library

If you only want retro games on a browser tab, the answer might not be EmuDeck. A library server such as RomM serves files and metadata over HTTP. I compared the options in RomM vs EmulatorJS. EmuDeck still wins for anything heavy, like PS2 or GameCube, where you want a native emulator and controller mapping.

Do not move the whole Emulation folder to a share

Put ROMs on the NAS. Leave Emulation/bios, Emulation/storage, and the emulator configs on the Deck. Emulators write shader caches and settings constantly, and a flaky mount under them is a good way to corrupt a save. That last sentence is my engineering judgment, not a measured result, but I would not test it with a save I cared about.

Save Sync: Two Ways

Saves are the one thing you cannot re-download. They are also small. Treat them like a database, not like media.

Option A: EmuDeck’s CloudSync

EmuDeck ships a feature called CloudSync. Per the wiki, it syncs your saved games between EmuDeck installations. Under the hood it uses rclone: the wiki’s troubleshooting page points to Emulation/tools/rclone for the binary and Emulation/tools/rclone/rclone.conf for your settings.

The providers listed on the wiki’s CloudSync page for SteamOS are Google Drive, Dropbox, OneDrive, SFTP, Box, NextCloud, and SMB. For a homelab, SFTP, NextCloud, and SMB are the interesting ones, because they let you point CloudSync at your own server instead of a vendor.

Setup, per the wiki:

  1. Click the CloudSync link inside the EmuDeck app.
  2. Choose a provider and click Install.
  3. Log in when the browser window appears. You need Chrome or a Chromium-based browser such as Brave. The wiki says Firefox does not work.
  4. Choose whether to download your saves or upload them.

If you installed EmuDeck before enabling CloudSync, the wiki says to reset the Steam ROM Manager configuration and parse your entries again, so the shortcuts pick up the new launchers.

One caveat. The CloudSync page I read is marked “Under Construction” and “Early Access only”, with a January 2025 date. I did not test it, and I cannot tell you how it behaves in the current release. Try it with a throwaway save first.

Option B: Syncthing on Emulation/saves

If you already run Syncthing, you can skip CloudSync and sync the saves folder directly. I covered the mechanics in Game Save Sync Without Cloud, so I will stick to the EmuDeck-specific part here.

The EmuDeck-specific part is the symlink issue. Per the wiki’s save management page, these emulators keep their saves directly in Emulation/saves with no symlink listed: DuckStation, MAME, melonDS, mGBA, and PCSX2. Those are safe to point a sync tool at.

Others show a symlink in Emulation/saves. Syncthing does not follow symlinks by default, so a share on that folder would sync only the link. Dolphin, Citra, and PPSSPP point to a Target under /home/deck/.var/app/.... Cemu, RPCS3, and Yuzu point to folders inside Emulation, and Ryujinx points to /home/deck/.config/Ryujinx. For all of these, share the Target path instead. You can read the exact Target for each emulator on the wiki’s save management page, and I recommend you copy it from there rather than from me.

Whichever you pick, run a restore test before you trust it. Sync is not backup. If you delete a save on one device, both devices lose it. Put a snapshot or a nightly copy of the synced folder on the NAS.

Switch Emulation: Check Before You Plan

This section changes faster than the rest, so the date matters. As of November 2026:

I have not verified exactly what the installer offers a fresh user today, so I will not tell you to click anything. Read the current Switch page on the wiki and the emulator’s own site before you build a plan around it. The other emulators I checked (PCSX2, Dolphin, RPCS3, Cemu) are not archived and showed commits within a day of 21 November 2026.

Switch games also need prod.keys and firmware dumped from your own console. EmuDeck does not supply them.

Power Tools and Game Mode Tuning

EmuDeck can install Decky Loader and a plugin called Power Tools, which adds power controls to Game Mode. The wiki’s steps: open EmuDeck on the desktop, select Power Tools, enter your password, click Install Power Tools, and restart the Deck.

The wiki’s recommended settings for demanding emulators are SMT off in Power Tools and Manual GPU Clock Control set to 1200 in the performance menu. It also warns that some games will not run well regardless, and points you at each emulator’s compatibility list. I did not benchmark these settings, so treat them as the project’s advice, not mine.

I did not find OLED-versus-LCD guidance in the EmuDeck docs I read, so I will not claim one model runs emulators better than the other.

A Sane Setup, Start to Finish

Here is the order I would do it in.

  1. Dump your games and BIOS files from your own hardware onto the NAS, sorted by the folder names in the EmuDeck Cheat Sheet.
  2. Format the SD card in Game Mode if you use one.
  3. Run the EmuDeck installer in Custom Mode, and install only the emulators you will use.
  4. Copy BIOS files into Emulation/bios, following the Cheat Sheet.
  5. Sync the ROMs you want on the Deck with rsync.
  6. Run SRM, add only the games you play, and return to Game Mode.
  7. Turn on CloudSync or Syncthing for saves, then test a restore.
  8. Snapshot the saves folder on the NAS.

That setup takes an afternoon, mostly copying files. The reward is a Deck you can wipe and rebuild without losing anything that matters, which is the same standard you hold your servers to.

Common Questions

Can the Steam Deck run PS2 games?

Yes. EmuDeck installs PCSX2 for PS2 games. You supply a BIOS dumped from your own console and place the files directly in Emulation/bios, with no subfolder. Performance varies by game, so check the EmuDeck compatibility database before you commit to a long game.

Where do ROMs go in EmuDeck?

ROMs go in a per-system folder under Emulation/roms, such as Emulation/roms/ps2. On an SD card install, the path is /run/media/SDCARDNAME/Emulation/roms. The Cheat Sheet lists the exact folder name for each system.

Does EmuDeck sync saves between devices?

Yes, through CloudSync, which uses rclone. The wiki lists Google Drive, Dropbox, OneDrive, SFTP, Box, NextCloud, and SMB as providers, so you can target your own server. Setup opens a browser login, and the wiki says Chromium-based browsers work while Firefox does not. The wiki page is marked early access, so test with a throwaway save first.

Can I install EmuDeck on an SD card?

Yes. Format the card as ext4 or btrfs in Game Mode, then pick the SD card as the install location. The ROM, BIOS, and storage folders go on the card, but EmuDeck still installs the emulators on the internal SSD.

The emulators are legal software. The games and BIOS files are the issue. EmuDeck’s FAQ says you must obtain ROMs and BIOS files from your own console, and it treats every other method as piracy. Dump what you own, and keep the master copies on your NAS.


Share this post on:

Send a Webmention

Written about this post on your own site? Send a webmention and it'll show up above once verified.


Next Post
Immich External Libraries Without Moving

Discussion

Powered by Garrul . Sign in with GitHub or Google, or post anonymously.

Related Posts