Abdess/retrobios: source-verified BIOS packs for RetroArch, Batocera and RetroPie
Source-verified BIOS and firmware packs for RetroArch, Batocera, Recalbox, Lakka, RetroPie, EmuDeck, RetroBat, RetroDECK, RomM, BizHawk, ROCKNIX, and MiSTer FPGA. Platform-native verification, with emulator source code as the deciding authority.
At a glance
- What is it?
- RetroBIOS builds per-platform BIOS and firmware packs by reading emulator source code, then verifies each file the way the target platform does. It is a packaging and verification project, not a legal shortcut.
- Who is it for?
- Adopt RetroBIOS if you run one of the eighteen supported platforms and want a checksum-verified BIOS set instead of a folder of files from a forum thread. Do not adopt it if you need files it explicitly lists as unsourceable, such as per-user keys and user-filled slots, or if you expect the pack to satisfy a licence you do not hold.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly HTML, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 13, 2026, and from our analysis. They are not legal advice.
Star history
- Abdess/retrobios7,667 ★ · +482
| Repository | 2026-09-23 | 2026-11-13 |
|---|---|---|
| Abdess/retrobios | 7.2k | 7.7k |
482 Stars in the last 51 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The problem RetroBIOS solves: BIOS files scattered across forum threads
Emulators do not ship the firmware they load. A PlayStation core needs a BIOS image, a Saturn emulator needs firmware, an arcade set needs its parent ROM. Those files live on the user's disk, and the emulator documentation rarely lists all of them, because the list is buried in the source code that calls the file loader. RetroBIOS exists to close that gap. It reads emulator source, extracts the filenames, sizes and hashes each emulator actually checks, and packages the result per platform.
The audience is narrow and specific. It is people running AmberELEC, Batocera, BizHawk, EmuDeck, EmuELEC, KNULLI, Lakka, MiSTer FPGA, MinUI, MyMinUI, NextUI, ROCKNIX, Recalbox, RetroArch, RetroBat, RetroDECK, RetroPie or RomM who want the BIOS folder populated without hand-collecting files. The README states the scope plainly: 18 platforms, 623 emulators profiled from source, 541 systems, and 19,916 files with five fingerprints each.
How the verification works, and why the platform decides the test
The mechanism is a build pipeline, not a runtime tool. The repository holds a bios/ directory, a platforms/ directory, an emulators/ directory, a provenance/ directory, a recipes/ directory and a schemas/ directory, plus database.json at the top level. pyproject.toml notes that install.py accepts Python 3.8, the build scripts under scripts/ need 3.9, and CI runs the test suite on 3.12. The site is built by Astro Starlight from website/package.json.
The verification rule is the part worth understanding. Each file is checked the way the target platform checks it, and the Coverage table names that test per platform. Most compare a checksum of the file's contents. RetroArch, Lakka and RetroPie only look for the filename, because that is all their code does. Independently, the collection records SHA1, MD5, SHA256, CRC32 and Adler-32 for every file. Where an emulator's source states an expected size or hash, that value is read from source and rechecked.
That distinction matters more than it looks. A pack verified by filename presence will hand you a file that boots the emulator and may still be the wrong dump. RetroBIOS does not hide this: the Coverage table publishes which platforms get the weaker test.
Installing on Linux, macOS, Steam Deck or Windows
The README gives a one-line installer per operating system. On Linux, macOS and the Steam Deck, the command is a curl pipe into sh. The script auto-detects the platform, downloads only missing files, and verifies checksums.
curl -fsSL https://abdess.github.io/retrobios/i | shOn Windows the equivalent is a PowerShell download-and-execute, which the README shows as irm piped into iex.
irm https://abdess.github.io/retrobios/i.ps1 | iexAndroid runs the same shell script under Termux, after installing Python and setting up storage access with pkg install python and termux-setup-storage. For a handheld whose SD card is mounted on a PC, the README shows the script taking a platform and a destination path, which is how you target one machine rather than the host.
curl -fsSL https://abdess.github.io/retrobios/i | sh -s -- --platform retroarch --dest /path/to/sdcardIf you prefer the ZIP route, download the pack for your platform from its Download link in the README's table and extract it to the path in the table. Batocera expects /userdata/bios/, RetroArch expects system/, RetroPie expects ~/RetroPie/BIOS/, RomM expects library/bios/. RetroDECK, RetroPie and several other setups have no ZIP; for them the README says to use the installer command. A pack over 2 GB comes in several parts (Pack.part1of2.zip, Pack.part2of2.zip); each part is an ordinary ZIP, and you extract them all into the same folder. Every release ships SHA256SUMS.txt and a detached signature checkable against allowed_signers in the repository.
What the packs cannot contain
The README is unusually direct about its own holes, and they are the reason to read before downloading. 1,086 files that the platforms' emulators load are still to be found, and 138 more cannot be sourced at all. The gap analysis page names them. The unsourceable category is structural: per-user keys, user-filled slots, and dumps nobody has made. No amount of scraping fixes a key that is unique to your console.
Licence status is the third limit. The repository's LICENSE file exists, but the metadata reports the licence as NOASSERTION, which means GitHub could not classify it. The project packages and verifies files; it does not resolve the legal position of the dumps themselves.
RetroBIOS against scraping a BIOS list yourself
The obvious alternative is doing what most people do: find a platform's published BIOS list, download the files from wherever they are offered, and drop them in the folder. That approach is faster for a single missing file and requires no tooling. It also fails in a specific way that RetroBIOS was built to address.
The published list is incomplete by construction. It is maintained by hand and covers the files someone remembered to add. The README says a pack holds the platform's own BIOS list plus every file its emulator cores load. A user following the published list alone will have a working setup for the common cores and silent failures for the rest, and silent is the operative word, because a missing file often produces a core that will not start rather than an error naming the file.
The second difference is the verification test. A hand-collected folder has no checksums at all. RetroBIOS records five fingerprints per file and applies the platform's own test, whether that is MD5, SHA1 or filename presence. If your platform is RetroArch, Lakka or RetroPie, be aware that the pack's verification is no stronger than the emulator's own, which is filename presence only. The five recorded fingerprints are still there for you to check manually, but the automatic test is the weak one.
The third difference is update mechanics. The installer downloads only missing files and verifies checksums, so re-running it after a release is cheap. A hand-maintained folder has no such path.
Maintenance status, release cadence and what a contributor needs
The repository is not archived, and the last push was on 2026-10-28. The most recent release is v2026.10.10, dated 2026-10-10, with a separate large-files release from 2026-03-17 for firmware over 100 MB. That cadence matters for the upgrade cost: re-running the installer picks up only missing files, so the marginal cost of staying current is a checksum pass over your existing BIOS folder rather than a fresh download of several gigabytes.
The RetroPie row carries an asterisk worth reading. The README marks it archived in the sense that the configuration is kept and the installer serves it, but upstream is no longer scraped on a schedule. If RetroPie is your platform, its coverage numbers will drift from upstream over time while the installer continues to serve it.
For anyone modifying the project rather than consuming it, pyproject.toml splits the dependencies cleanly. Runtime needs pyyaml only. The dev extra pulls jsonschema for the schema validation scripts and the CI contract check. There is no docs extra: the site is built by Astro Starlight from website/package.json. The Python floor is 3.8 for install.py, the build scripts under scripts/ need 3.9, and CI runs the test suite on 3.12.
Editorial conclusion
Adopt RetroBIOS if you run one of the eighteen supported platforms and want a checksum-verified BIOS set instead of a folder of files from a forum thread. Do not adopt it if you need files it explicitly lists as unsourceable, such as per-user keys and user-filled slots, or if you expect the pack to satisfy a licence you do not hold. Before extracting anything, read the Coverage table for your platform and the gap analysis page, because the gap analysis names the files that are still missing.
Frequently asked questions
Do I need a BIOS for RetroArch?
It depends on the core. RetroBIOS's RetroArch pack holds 8,504 files, 6.0 GB once extracted, covering RetroArch's own BIOS list plus every file its emulator cores load. The Coverage table shows RetroArch checks files by filename presence only.
Where can I get RetroArch BIOS files?
The README's download table links a page for each platform's pack that extracts to the platform's BIOS path. For RetroArch that path is system/. The installer script does the same file by file and downloads only what is missing.
How do I use RetroBIOS?
Either run the one-line installer for your operating system, which auto-detects the platform and verifies checksums, or download the ZIP for your platform from the README's download table, where one is offered, and extract it to the path listed in the README's platform table. The handheld case takes --platform and --dest arguments to target an SD card.
Is RetroBIOS safe?
Every release ships SHA256SUMS.txt and a detached signature checkable against allowed_signers in the repository, and the installer verifies checksums. The project's own coverage data still lists 1,086 files that are to be found and 138 that cannot be sourced at all, which is a completeness limit rather than a safety one.
Where are RetroArch BIOS files located on iOS?
The README's quick install section gives no iOS route. It lists Linux, macOS, Steam Deck, Windows, Android under Termux, and handhelds with an SD card mounted on a PC.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/abdess-retrobios)Star history chart for your README
[](https://hysenlabs.com/projects/abdess-retrobios)Was this useful?