roms not showing in steam fix

Last verified October 2026
Quick answer

Your ROMs don't show in Steam when the parser never ran or the ROM folder is wrong. Run the parser, point it at the right folder, then check Steam.

Frontend problems come in two shapes: the file is in the wrong place, or the tool that turns files into library entries never ran. These are the exact questions players ask when ROMs or BIOS files don’t appear — each answer names the folder, the extension rule, or the step that got skipped. Step-by-step walkthroughs live in the EmuDeck install guide and RetroArch BIOS not detected.

Why can't EmuDeck find my ROMs?

EmuDeck creates a specific folder structure for ROMs, per system, and only scans what's inside it. Files sitting in Downloads or the root of the SD card are invisible to it. Move your ROMs into the per-system subfolders EmuDeck created, then run the parser again. Folder names matter — the system subfolders are matched by name, so a game in the wrong subfolder won't appear in the right collection.

Why aren't my games showing up on Steam?

Adding files to a ROMs folder doesn't add anything to Steam — a parser has to run to create the Steam entries. In Steam ROM Manager, pick your emulators, press Parse, review the list it found, then click Add to Steam. If the parse finds nothing, the ROM folder path in the parser points somewhere other than where your files actually live.

Why are my installed games not showing up in Steam?

If these are Steam games rather than emulated ROMs, Steam's library may need a refresh or the install may have completed to a different library folder. Check Steam's storage manager for the library location, and use View → Refresh Library. For emulated ROMs, this question is really 'the parser hasn't run' — see the Steam ROM Manager questions below.

EmuDeck Parsers Not Showing in Steam ROM Manager?

EmuDeck installs preconfigured parsers, and they disappear from Steam ROM Manager's list when EmuDeck's configuration folder was moved or partially deleted — commonly after a big SteamOS update or a manual folder cleanup. Re-run EmuDeck's installer in repair mode rather than rebuilding parsers by hand; it restores the configuration it originally wrote.

Why isn't my game showing up in Steam Rom Manager?

Steam ROM Manager matches files by extension and folder. A ROM with a non-standard extension, or one stored loose in the parent folder instead of the system subfolder, won't match the parser's rules. Check the parser's preview list after parsing — anything missing there is a path or extension problem, not a Steam problem.

Why is Steam not finding my installed games?

For regular Steam installs, the library folder may be missing or on a disconnected drive — check Settings → Storage. For emulated ROMs, Steam never sees the files directly; the parser creates shortcut entries that point at them. If the shortcuts exist but games won't launch, the emulator path inside the parser is wrong, not the Steam library.

Why aren't games showing up in my Steam library?

Two different problems share this symptom. Installed Steam games missing from the library is usually a library-folder issue (Settings → Storage). Emulated ROMs missing is a parser issue — the entries only exist after a successful parse and add. Check which one you have before troubleshooting, because the fixes don't overlap.

Why won't my Steam ROM manager open?

It fails to launch most often because a previous parse left a lock or the configuration file was edited into invalid JSON. Close Steam entirely and retry; if it still won't open, rename the configuration folder (don't delete it) and let Steam ROM Manager rebuild defaults. Your ROMs are untouched — only the parser's settings reset.

How do I add BIOS to RetroArch?

Put the BIOS files as plain, unzipped files into RetroArch's system/ folder, whose location is listed under Settings → Directory. RetroArch won't go looking in your Downloads folder, and cores expect an exact filename — an archived copy or a renamed one is treated as missing. After copying, reload the core so it re-checks detection.

Why is RetroArch saying the PSx BIOS is missing?

The core looks for a specific filename in the system/ folder — typically an scph variant like scph5501.bin. Three things cause this message: the file is still zipped, it's in the wrong folder, or it's named differently. Extract it, place it loose in system/ with the exact expected name, and rescan.

Does RetroArch need a BIOS?

Some cores do and some don't. PlayStation, PlayStation 2, Sega CD and a few others expect BIOS files from the original hardware; most Nintendo and handheld cores emulate everything in software and need nothing. If a core launches without complaining, it doesn't need one — don't add BIOS files speculatively, since a wrong-named file in the system folder can confuse detection.

Retroarch not detecting bios folder on micro sd card?

RetroArch's system folder lives on whichever volume RetroArch is installed to. On a Steam Deck with RetroArch on the microSD, the system folder is on the card — a BIOS copied to internal storage won't be seen. Check Settings → Directory, note the actual path shown, and copy the BIOS there. The folder name must be exactly system, lowercase.

Retroarch bios detection issues?

Work through the same three checks every time: the file is loose (not inside an archive), it sits in the folder Settings → Directory actually points to, and its name matches the core's expectation. Then reload the core — one that already reported the file missing holds that state until it restarts, so a file copied after launch still looks absent.

PCSX-Rearmed won't recognize bios file - how do I fix this?

PCSX-Rearmed (the PS1 core) matches BIOS files by name and region. Rename your dump to one of the accepted names — scph5501.bin for NTSC-U, scph5502.bin for PAL — place it loose in the system/ folder, and rescan. A file that works in the standalone PCSX core but not in PCSX-Rearmed is almost always a naming mismatch.

Why is RetroArch not recognizing my ROM hacks?

Cores validate content against the original ROM's structure, and heavily modified files can fail the check. Patch the original ROM with your hack first, then load the patched file — don't expect the core to load a hack applied to a different region or version of the game. If the core still refuses, load the unpatched original to confirm the core itself works.

Last verifiedOctober 2026
CorrectionsSpotted an error? See our editorial guidelines