Abdessamad Derraz
801af113b7
The rom folders files kept the default core of each folder only, so a core the user picks in the frontend's menu was not known to read its sets there. Each folder now lists its offers: every <core> of every <emulator> in AmberELEC's es_systems.cfg (arcade: packages/ui/emulationstation/config/es_systems.cfg:116-150), every core of EmuELEC's es_systems.json, every add_emu_core of ROCKNIX's emulators package.mk with the device case it is written under (arcade: 218-229), and the emulator of every ES-DE <command>. A core written under every branch of a case is offered unconditionally. The ES-XML, ES-JSON, ELEC-conf and ES-DE setups are rescraped at their pins: archr, arkos, chaos, darkos, jelos, kolos, pan4elec, retrobat and unofficialos gain the same records and nothing else. A libretro core offered for a folder reads the sets it loads beside the game there, as the default one does. Manifests, roms folders gaining sets read beside the game: - AmberELEC: +215 (293.1 MB) in fbneo, arcade and mame, for MAME 2010, 2015, 2016 and 2003-Plus. 1 omission leaves. - EmuELEC: +291 (232.0 MB) in cps1, cps2, cps3, mame, fbneo and arcade, for MAME 2010 and 2003-Plus. 47 omissions leave. - ROCKNIX: +501 (538.7 MB) in fbneo, neogeo, cps1, cps2, cps3, arcade and mame, for MAME 2010, 2015 and 2003-Plus. 120 omissions leave. - EmuDeck: +306 (251.2 MB) in cps, cps1, cps2, cps3, arcade and mame, for MAME 2000, 2003, 2003-Plus and 2010. 92 omissions leave. Each omission that leaves was a set named as read outside the BIOS folder. RetroDECK and the other platforms do not change. No file leaves, and verify --all keeps its severity and status counts.
The BIOS files emulators need, put in the right folder and checked.
Website · Get the files · A game does not start · Questions
Some consoles need a small program, the BIOS, to start their games: PlayStation 1 and 2, Saturn, Neo Geo, Dreamcast and more. RetroBIOS installs the BIOS and firmware files for AmberELEC, Batocera, BizHawk, EmuDeck, EmuELEC, KNULLI, Lakka, MiSTer FPGA, MinUI, MyMinUI, NextUI, ROCKNIX, Recalbox, RetroArch, RetroBat, RetroDECK, RetroPie, and RomM, checked the way each one checks them.
Install in one line
Windows: open the Start menu, type PowerShell and open it. Paste this line (Ctrl+V or right-click in the window) and press Enter.
irm https://abdess.github.io/retrobios/i.ps1 | iex
Linux, macOS, Steam Deck, Android (Termux): open a terminal, paste this line and press Enter.
curl -fsSL https://abdess.github.io/retrobios/i | sh
With Python 3.8 or newer: uvx retrobios runs the same installer, and so does pipx run retrobios.
A handheld, an SD card, or not sure? Pick the device: its page gives the folder and the command. A muOS, Onion, spruceOS, MinUI, KNULLI, ROCKNIX, Lakka or MiSTer SD card plugged into the computer is found by itself.
The installer finds the setup and its BIOS folder, installs the files it needs (only what the games need when it finds them on the card) and checks each one. Its screen installs everything, or fewer under Choose systems. Arrow keys and Enter drive it, or a controller on a handheld. It sends no report of its own (what is counted). Options go after the line in the form the installer page gives.
First time? The first install, step by step. A game does not start: what to check. Other questions: FAQ.
Or download a ZIP
The Files column counts what a pack holds once unzipped.
| Setup | Files | Size | Unzip into | Download |
|---|---|---|---|---|
| Batocera | 19,125 | 10.1 GB | /userdata/bios/ |
Download |
| EmuDeck | 14,651 | 8.0 GB | ~/Emulation/bios/ |
Download |
| MiSTer FPGA | 90 | 29 MB | /media/fat/games/ |
Download |
| RetroArch | 15,005 | 7.6 GB | system/ |
Download |
| RetroBat | 8,882 | 8.2 GB | bios/ |
Download |
| RomM | 468 | 831 MB | library/bios/ |
Download |
ZIPs are made for the setups most people download. The others install with the line above, and each page gives the command: AmberELEC, BizHawk, EmuELEC, KNULLI, Lakka, MinUI, MyMinUI, NextUI, ROCKNIX, Recalbox, RetroDECK, RetroPie.
Unzip into the BIOS folder, files straight in it. A big pack comes in parts (Pack.part1of2.zip): download every part (why some setups have no ZIP). Each release lists its files' SHA-256 with a signature (verifying a release).
Help
- "BIOS missing" or a game does not start: what to check
- Have a file? Check it by its hash
- Every console and the files it needs: systems
- Asking an AI assistant: it reads the site best from llms.txt
How it is built
- 648 emulators profiled, 614 from their source code and 34 closed-source builds from their binaries: 94% of the files they load cite the file and line that reads them
- 18 setups, each checked its own way: MD5 for Batocera and Recalbox, the file name for RetroArch, as their own code does
- 522 systems, 21,936 files in the collection, what is still missing named file by file
- 2,229 archives, each with a recipe that rebuilds it from the ROMs the collection holds: 1,794 byte for byte, 435 with the same files inside (rebuilding an archive)
- Public data: JSON, CSV and SQLite, the metadata under MIT
For developers: build a pack
Packs are built from a clone, and the clone carries the collection: its checkout alone is over 7.8 GB. git clone --depth 1 https://github.com/Abdess/retrobios.git leaves the history out. Files kept as release assets are downloaded when a pack needs them. Then generate packs for any platform, emulator, or system:
python scripts/generate_pack.py --platform retroarch --output-dir dist/
python scripts/generate_pack.py --emulator dolphin
python scripts/generate_pack.py --platform batocera --required-only
python scripts/verify.py --platform batocera
Requires Python 3.9 or newer and pyyaml. The one-line installer alone runs on Python 3.8. Every tool and option: tools. How the lists are built: architecture.
Contributors
Community tools
- BIOS Preservation Tool by monster-penguin - scans, verifies and stages a BIOS collection using RetroBIOS hash metadata
Contributing
See CONTRIBUTING.md for guidelines.
License
The scripts and tooling are released under the MIT License. The BIOS and firmware files are not covered by that license: they are third-party system software, preserved and provided for personal backup, archival, and interoperability with emulation software. NOTICE sets out their status and how to ask for a file to be removed. The reasoning, and where it is weakest, is in the project's legal position.
Auto-generated on 2026-11-10T08:51:40Z