Few things are more frustrating than adding your ROMs to Batocera and seeing… nothing.
Luckily, the cause is almost always simple. Let’s walk through the most common reasons and how to fix them.
1. Check Whether the File Extensions Are Supported
Batocera only recognizes certain extensions for each console.
For example, PlayStation games must be .bin/.cue or .chd, while SNES games should be .sfc or .smc.
If your files use odd or proprietary extensions, Batocera will ignore them.
2. Make Sure ROMs Are Placed in the Correct Folders
Batocera relies on a very strict folder structure. Putting a PS2 game into the PSP directory means Batocera simply won’t display it.
Correct examples:
/roms/snes
/roms/megadrive
/roms/ps1
/roms/ps2
Double-check your directories — most issues come from one misplaced folder.
3. Verify That Required BIOS Files Are Installed
Several systems will not load games unless the correct BIOS files are present. For example, PS1, PS2, Sega CD, Neo Geo, and others require BIOS files. If the BIOS is missing, Batocera may hide the system entirely or prevent games from loading.
You can check missing BIOS files under:
4. Enable Hidden Systems in the Settings
Batocera can hide systems that don’t yet have ROMs or required BIOS files.
Go to:
Main Menu → UI Settings → Show Hidden Systems → ON
Now systems appear even if incomplete, which helps troubleshooting.
5. Refresh the Game List After Adding New Files
Batocera does not automatically detect new games if you add them while it’s running.
Go to:
Main Menu → Game Settings → Update Games Lists
This forces Batocera to rescan all folders.
6. Check for Corrupted ROMs
If a ROM is damaged or incomplete, Batocera will silently ignore it.
Try verifying the file, re-dumping it, or converting it to CHD format.
Still stuck?
Post your folder structure and file formats — the community can usually spot the issue quickly.
