Batocera Download 2026: v38 to USB in 12 Steps, 30 Min

Two words: batocera download. They look like a transaction. They are not. There is no cart, no checkout, no "lifetime license," no email gate, no $39.99 microSD card mailed from a PO box stuffed with a thousand ROMs you never asked for. The download is free in the only sense that matters: the source is public, the binaries are public, and the price field reads $0.00 because nobody is legally permitted to put a number there.

What the two words hide is everything that happens after the file lands. Flashing it without corrupting the USB. Convincing a stubborn UEFI to boot from that USB. Feeding the thing BIOS files it legally cannot ship to you. Reading the cryptic checkmarks of a Missing-BIOS audit. This is a tutorial about all of it — the download, yes, but mostly the lore the word "download" politely omits. Budget thirty minutes if your hardware cooperates, an afternoon if it sulks.

The Price Is Zero, and That's the Point

What "Free" Actually Means Here

Batocera.linux is a Linux distribution whose entire job is to turn a computer into a games console and then get out of the way. It is licensed as free software, the source lives in the open at the batocera-linux GitHub repository, and the build artifacts — the actual images you flash — are handed out at no charge. When a guide tells you the download cost is $0.00, that is not a promotional rounding error. There is no paid tier, no premium image, no "pro" emulator pack. The project is maintained by a community of volunteers, unaffiliated with any commercial entity, which conveniently means there is nobody around to upsell you.

This matters because the retro space is rotten with people selling you free software. The $45 microSD card promising "10,000 games," the "custom firmware" that is RetroArch wearing a wallpaper, the eBay listing that is Batocera with the serial numbers filed off — all of it resells work the original authors gave away, frequently bundled with copyrighted material that is not theirs to bundle. What you are about to do is get the real thing, from the real source, for the real price, which is nothing.

Version 38, and Why the Number Hasn't Moved

The current stable release for PC (x86_64) is version 38, dated October 14, 2023. If you are reading this in 2026 and that date looks suspiciously geological, relax — that is how Batocera versioning works on the PC branch. The major number is a baseline, not a heartbeat. Through 2025 and 2026 the project has continued to ship theme updates, emulator bumps, and core fixes against that baseline without minting a new headline version for x86_64. Higher numbers (39 and up) tend to surface first as test builds for specific boards — Raspberry Pi 5, assorted Odroid units, handhelds — long before any of it becomes the recommended PC image.

So when the download page offers you "38," that is not a stale link somebody forgot to bump. It is the stable target, deliberately. If you would rather chase a bleeding-edge point release, we walked through that in our newer-build flashing guide; for a daily-driver console you want to stop thinking about, version 38 is the boring, correct choice. Boring is a feature.

What You're Actually Downloading

The PC image is named with Batocera's signature redundancy: batocera-x86_64-x86_64-38-20231014.img.gz. Yes, the architecture appears twice; no, it is not a typo, and complaining about it on the forums will not change it. The file is a gzip-compressed raw disk image, roughly 2.5 GB on the wire. Once written and expanded it occupies about 8 GB, which is why 8 GB is the floor for your USB drive and 16 GB is the number you should actually use. Inside that blob is a complete Linux userland, the EmulationStation front end, and over 50 emulators and game engines out of the box — RetroArch and its core army plus standalone heavyweights such as PCSX2, Dolphin, and PPSSPP. You are downloading a console. It just arrives as a 2.5 GB file with an absurd name.

Prerequisites: What You Need Before You Start

Hardware Requirements

Batocera for PC runs on x86_64 hardware — any 64-bit PC, laptop, NUC, mini-PC, or retired office desktop from roughly the last fifteen years. A 32-bit-only machine is out; this image will not boot it. Beyond that the requirements are modest, with the usual caveat that "runs" and "runs the system you actually want" are different sentences:

• CPU: any 64-bit x86 processor. 8-bit and 16-bit consoles run on a potato. PlayStation 2, GameCube, and Wii ask for real silicon and will humble a 2011 netbook.
• RAM: 2 GB is the technical floor. 4 GB makes EmulationStation and the heavier cores pleasant. 8 GB if your ambitions include sixth-generation consoles.
• USB drive: a USB 3.0 flash drive, 8 GB minimum, 16 GB recommended. This is not padding. With only 8 GB the system boots fine but cannot download updates or themes — there is no free space for them to land in. Use 16 GB and stop thinking about it.
• A second computer running Windows, macOS, or Linux to do the flashing. You cannot flash the drive you intend to boot from while you are booted from it. Physics, and also Etcher, forbid it.
• A controller (optional but sane). An Xbox-style USB or Bluetooth pad is recognized without ceremony. A keyboard works for menus and for swearing.

Software and Versions

The toolchain is two files and zero dollars. Pin the versions so you are not debugging a moving target:

• The image: batocera-x86_64-x86_64-38-20231014.img.gz from the official Batocera download page. Take it from there or from the GitHub releases — nowhere else.
• Balena Etcher, the flasher, free from balena.io/etcher. On Windows the installer is named balenaEtcher-Setup-1.xx.xx.exe (1.18 or newer is current). The single most important fact about Etcher: it reads .img.gz directly. Do not decompress the image first. Half the "my USB won't boot" threads on the internet are people who unzipped the file, flashed the raw .img, ran out of patience, or flashed the .gz to a tool that didn't understand it.

That is the entire software bill of materials. No paid utility appears anywhere in this pipeline. If a tutorial tries to sell you a "Batocera installer" as a product, close the tab.

What You Should NOT Bring (The Legal Part)

Batocera ships zero copyrighted BIOS files and zero ROMs, and this is the correct, lawful, adult decision. Emulators are legal software. Console BIOS dumps and commercial game images are not Batocera's to distribute, so it distributes none of them. What you supply yourself are BIOS files and game images dumped from hardware and media you own. The legality of format-shifting your own cartridges is its own thirty-year argument that varies by jurisdiction, and this guide is emphatically not your lawyer. What is not ambiguous is that the project made the right call by shipping an empty bios folder and pointing you at a checker — which is exactly what you would want from software that intends to still exist next year.

Picking the Right Image for Your Architecture

x86_64 Is Probably You

The Batocera download page is a wall of hardware targets, and the single most common installation failure is grabbing the wrong one. For the overwhelming majority of readers — anyone installing onto a PC, laptop, NUC, mini-PC, or that beige tower in the closet — the answer is x86_64. If your machine runs 64-bit Windows or 64-bit Linux today, x86_64 is your image. There is also a 32-bit "x86" build for genuinely ancient hardware, but if you are not certain you need it, you do not need it.

Select x86_64, download batocera-x86_64-x86_64-38-20231014.img.gz, and ignore everything else on the page. The other entries exist for completeness, not for you.

The Pi, the Handhelds, and the Rest

The same download page serves Raspberry Pi images, Odroid images, and builds for specific handhelds, each cut for a different SoC. These are not interchangeable with the PC image — a Pi build will not boot a PC, and the PC build will not boot a Pi, and trying either produces a black screen and a sense of betrayal. This is also where the higher version numbers live: Pi 5 and certain Odroid boards see test builds numbered 39 and beyond while the PC branch holds steady at 38.

If your actual goal is portable retro gaming rather than a living-room box, Batocera's PC build may be the wrong tool entirely. A purpose-made handheld saves you the entire boot-menu ritual below. We compared the leading options in our Retroid Pocket 6 launch coverage and in the Miyoo Mini Plus versus RG35XX breakdown — buy one of those and you are flashing nothing.

Compressed vs. Expanded Size — Plan Your Drive

The file you download is about 2.5 GB. The image it expands into is about 8 GB. That gap is the whole reason for the drive-size advice. An 8 GB USB stick technically fits the expanded system with almost nothing to spare, which means the over-the-air update mechanism and the theme downloader have no room to operate and silently do nothing. A 16 GB drive gives the system the headroom to update itself, pull themes from the built-in store, and hold a handful of save states without complaint. The compressed/expanded math is not a suggestion; it is the difference between a console that maintains itself and one that is frozen at install day.

The Install: 12 Steps From Download to Boot

Here is the whole procedure, start to finish. Each step states what to do and why, because a step without a reason is just a ritual, and rituals are how people end up flashing their Windows drive at 1 a.m.

1. Download the image from the official page. Go to batocera.org/download, choose x86_64, and pull batocera-x86_64-x86_64-38-20231014.img.gz. Why: mirrors and re-uploads are how malware and stale builds travel. The official page and the GitHub release are the only two sources you should trust.

2. Verify the file before you trust it. Confirm the size is roughly 2.5 GB and, if a checksum is published, match it.

   ls -lh batocera-x86_64-x86_64-38-20231014.img.gz
   # -rw-r--r--  1 you you  2.5G  Oct 14  2023  batocera-x86_64-x86_64-38-20231014.img.gz
   
   sha256sum batocera-x86_64-x86_64-38-20231014.img.gz
   # 9f1c...e4a2  batocera-x86_64-x86_64-38-20231014.img.gz
   # Compare this string to the checksum on the download page.
   # If they differ by a single character, delete it and download again.

   Why: a corrupt download produces a USB that boots to a black screen or a kernel panic, and you will blame your BIOS for an hour before realizing the image was truncated at byte 2.3 GB.

3. Get a 16 GB USB drive and accept that it will be erased. 8 GB is the documented minimum; 16 GB is the number that lets the system update and theme itself. Why: the expanded image is ~8 GB, so an 8 GB stick has no free space for the update and theme machinery. Flashing also wipes the drive completely — copy anything you care about off it first.

4. Install Balena Etcher. Download balenaEtcher-Setup-1.xx.xx.exe (or the macOS/Linux build) from balena.io/etcher and install it. Why: Etcher reads compressed images, validates the write automatically, and refuses to target your system disk by default. It exists specifically to stop the catastrophe in step 5.

5. Flash the .img.gz directly — do not extract it. In Etcher: Flash from file → select the .img.gz → Select target → pick the USB drive → Flash. Why: Etcher decompresses on the fly. Extracting first wastes 8 GB of disk and invites you to flash the wrong file. Selecting the target is the single most dangerous click in this entire guide — read the device name twice. Etcher hides your internal disks, but a second external drive can still get caught in the blast.

6. Let Etcher validate the write. Do not yank the drive when the progress bar hits 100%. Etcher then re-reads the drive to confirm. Why: validation catches a flaky USB stick or a failing port before you waste twenty minutes at the target machine discovering the image is half-written.

7. Move the drive to the target PC and open the boot menu. Plug the USB into the machine that will run Batocera, power on, and spam the one-time boot-menu key — most often F11, sometimes F8, F10, F12, or Esc depending on the manufacturer. Why: the one-time boot menu lets you boot the USB once without permanently reordering the BIOS, which is exactly what you want while testing. Select the USB drive, preferring a UEFI entry if both UEFI and Legacy appear.

8. Disable Secure Boot if the USB is rejected. If the drive refuses to boot or vanishes from the menu, enter the BIOS/UEFI setup and temporarily turn Secure Boot off. Why: Secure Boot only permits cryptographically signed bootloaders, and Batocera's is not on your firmware's approved list. Disabling it is a normal, reversible step for booting a non-Microsoft OS — not a hack, despite how the menu wording tries to scare you.

9. Boot Batocera and let it expand the filesystem. The first boot resizes the data partition to fill the drive, so the splash sits longer than later boots. Expect roughly this on a serial or verbose console:

   [  OK  ] Reached target Basic System.
   [batocera] No persistent partition found - expanding to fill device...
   [batocera] Resized USERDATA: /userdata now 8.0G (free 5.4G)
   [  OK  ] Started EmulationStation front-end.
   
     Welcome to Batocera 38 (x86_64)
     IP: 192.168.1.42   share: \\BATOCERA\share
     SSH: root@batocera.local  (default password: linux)

   Why: the resize is a one-time operation; interrupting it by cutting power mid-write is the classic way to corrupt a fresh install. Let it finish into EmulationStation.

10. Configure your controller. At the EmulationStation welcome screen, hold any button on your pad until the mapping wizard appears, then walk through the inputs. Why: EmulationStation will not assume your button layout, and an unmapped controller leaves you navigating a games console with arrow keys like an animal. Map it once and it persists.

11. Copy BIOS and ROMs into the share folder. Over the network or SSH, place files under the share root — BIOS dumps in bios/, games in roms/<system>/. Why: Batocera ships none of this on purpose (see the legal note above). The folders are pre-created and named for you; the next section covers the layout in detail.

12. Run the Missing BIOS Check, then update. From the menu open Game Settings → Missing BIOS Check to audit what you are still missing, then run the updater to pull current theme and emulator patches. Why: verifying BIOS before you launch a game converts a baffling "black screen on start" into a precise shopping list. Updating last ensures you are on the latest cores the 38 baseline supports — and it only works because you used a 16 GB drive.

Twelve steps. Roughly thirty minutes when the firmware behaves. The remainder of this guide is the part nobody tells you about until you are already stuck.

The Share Folder: Where BIOS and ROMs Live

The Layout of the Share

Everything you add to Batocera goes into one writable area. On the device it is mounted at /userdata; on the network it appears as a share named share, and many guides simply refer to it as the /batocera/share directory. Whatever you call it, the structure is fixed and the subfolders are created for you on first boot:

share/                      # network name; /userdata on the device
├── bios/                   # console BIOS dumps - exact filenames matter
│   ├── scph5501.bin        # PlayStation (US)
│   ├── gba_bios.bin        # Game Boy Advance
│   └── saturn_bios.bin     # Sega Saturn
├── roms/
│   ├── snes/
│   ├── psx/
│   ├── n64/
│   └── megadrive/
├── saves/                  # save states and battery saves (SRAM)
├── screenshots/
├── system/
│   └── batocera.conf       # the one config file that rules them all
└── themes/

The rule is mechanical: a BIOS file goes in bios/ under its exact expected filename, and a game goes in roms/ under the subfolder for its system. Drop a SNES ROM into roms/snes/ and it appears; drop it into roms/ root and it does not. Batocera is not guessing what console an arbitrary file belongs to, and it is right not to.

Getting Files In: Network, USB, SSH

You have three ways to fill the share, in ascending order of nerd:

# Linux / macOS - mount the SMB share in your file manager:
smb://BATOCERA/share

# Windows - paste into the Explorer address bar:
\\BATOCERA\share

# Or push a folder of ROMs over SSH (user root, default password linux):
scp -r ./snes root@batocera.local:/userdata/roms/

# Then change that default password at the first opportunity:
ssh root@batocera.local 'passwd'

The network share is the path of least resistance: Batocera advertises itself as BATOCERA on the local network and the share folder mounts like any other file server. SSH is faster for bulk transfers and lets you script things, but note the default credentials are root / linux — public knowledge, printed on the boot screen, and a genuinely terrible thing to leave unchanged on a box that holds your save files and sits on your home network.

ROM Naming and the No-Intro/Redump Lore

Batocera scrapes metadata and box art by matching your filenames against community databases. Files named the way the No-Intro (cartridge) and Redump (disc) preservation projects name them scrape cleanly and look like a polished console; files named game(1)final_REAL.zip scrape into a wall of placeholder boxes and broken titles. This is not Batocera being fussy — it is leaning on decades of cataloguing work so it does not have to ship a guessing engine. Name things sensibly and the front end rewards you; name things like a download folder from 2007 and you get exactly that energy back.

Verifying BIOS With the Missing-BIOS Check

Where the Check Lives

Buried in the menus is the single most useful diagnostic Batocera ships: the Missing BIOS Check, under Game Settings. It scans your bios/ folder, compares what is there against what your installed cores expect, and prints a verdict per file. Run it before you start blaming emulators. Nine times out of ten, a game that boots to a black screen or kicks straight back to the menu is not a broken core — it is a console BIOS that is absent, misnamed, or the wrong revision.

Reading the Output

The check produces a table you can read at a glance. A trimmed example of what it reports:

System              BIOS file          Status     MD5 check
------------------------------------------------------------------
Sony PlayStation    scph5501.bin       OK         490f666e...
Sega Saturn         saturn_bios.bin    MISSING    --
Nintendo DS         bios7.bin          OK         df692a80...
Nintendo DS         bios9.bin          MISSING    --
------------------------------------------------------------------
2 file(s) missing. Games for those systems will not start.

OK means present and the MD5 matches what the core wants. MISSING means the file is not there, or it is there under the wrong name. Some entries are flagged as needed only by particular cores, so a "missing" line for a system you do not play is safe to ignore. The point of the audit is that it converts a vague "why won't this run" into a precise filename to go find.

The BIOS Files That Trip Everyone

A handful of systems generate the bulk of the support threads: PlayStation (the SCPH BIOS set, region-specific), Sega Saturn and Sega CD, the Nintendo DS pair (bios7.bin and bios9.bin plus firmware), and the PlayStation 2 set if you are brave. The recurring mistake is a near-miss filename or a wrong-region dump that the MD5 check rejects. The authoritative reference for which file each libretro core expects, with checksums, is the libretro BIOS documentation; the Batocera wiki mirrors the same expectations per system. Match the filename and the MD5 exactly and the black screen evaporates.

Common Pitfalls and How to Fix Them

Flashing and Image Pitfalls

Pitfall 1 — extracting the .gz first. You unzip batocera-...-38.img.gz into a raw .img, flash that, and either it works by luck or your tool chokes on the extra step. Fix: feed Etcher the compressed .img.gz as-is. It decompresses during the write. The only reason to ever extract it is to use a different, dumber flasher — so use Etcher and don't.

Pitfall 2 — flashing the wrong target. Etcher hides internal disks, but a second USB stick or an external backup drive can sit in the target list looking innocent. Fix: unplug every external drive except the one you are flashing, and read the device name and size before clicking Flash. There is no undo on a finished flash.

Boot and BIOS Pitfalls

Pitfall 3 — Secure Boot silently eats the USB. The drive is flashed correctly, the boot menu either omits it or refuses it, and you conclude the image is bad. Fix: enter the UEFI setup and disable Secure Boot temporarily. This is the most common reason a perfectly good Batocera USB "won't boot."

Pitfall 4 — the 8 GB drive that can't grow. You bought the cheapest stick, the system runs, but the updater and theme store do nothing and you assume they're broken. Fix: they're not broken — there's no free space. Re-flash onto a 16 GB drive. The compressed-to-expanded jump from 2.5 GB to 8 GB leaves an 8 GB stick with no working room.

Post-Install Pitfalls

Pitfall 5 — games won't launch and you blame the emulator. A title boots to black and bounces back to the menu. Fix: run the Missing BIOS Check first. It is almost always an absent or misnamed BIOS, not a defective core. Match the filename and MD5 from the libretro docs.

Pitfall 6 — leaving root/linux as the password. The default credentials are printed on the boot screen and known to the entire internet. Fix: SSH in and run passwd on day one, especially before this box ever touches Wi-Fi. A retro console is still a Linux machine on your network, and treating it like a toy is how it becomes someone else's toy.

The Troubleshooting Table

How to Use This Table

Find the symptom in the left column, read the likely cause, apply the fix. These are ordered roughly by how often they bite a first-time installer, top to bottom. Most are firmware or filename problems wearing the costume of a software bug.

The Table

When the Table Doesn't Help

If the symptom isn't here, the wiki's per-system pages and the GitHub issue tracker are the next stops, in that order. Search before you post — the boot-menu and Secure Boot questions in particular have been answered several thousand times, and the people who maintain a free console in their spare time have earned the right not to answer them a thousand-and-first.

Advanced Tips: Persistence, Overlays, Updates

Installing to Internal Disk

Running from USB is the non-invasive default — it never touches your existing OS, which is the whole pitch. But USB sticks are slow and mortal. When you decide Batocera is staying, install it to an internal SSD via Main Menu → System Settings → Install Batocera on a new disk. This erases the target disk, so it is for a machine you are dedicating, not your daily Windows box. The payoff is faster boots, quicker scraping, and storage that will outlive the USB stick by years.

# Check the running version:
batocera-version
# 38

# Pull the latest stable patches (needs a 16 GB drive and a network):
batocera-upgrade

# Install to an internal disk instead of running off USB:
#   Main Menu -> System Settings -> Install Batocera on a new disk
# ...or inspect available disks from a shell first:
lsblk

Overclocking, Shaders, and Bezels

The visual layer is where Batocera stops being a utility and starts being a hobby. CRT shaders simulate scanlines and phosphor bloom so 240p content looks the way your memory insists it did; bezels (overlays) frame the smaller-aspect systems with artwork instead of black bars. Both are toggled globally and overridden per-system. Shaders are a feature of RetroArch underneath — the official RetroArch project documents the shader pipeline in depth if you want to understand what crt-royale is actually doing to your pixels rather than just clicking it on. Start subtle. Maxed-out CRT shaders on a weak GPU turn a buttery 60 fps into a slideshow.

Updates Without Breaking Things

The 2025-2026 value of the frozen-at-38 baseline is that updates patch cores and themes without rewriting the world underneath you. Run batocera-upgrade from a shell, or use the menu updater, on a 16 GB drive with a network connection. If you want a deeper, manual relationship with the emulation cores themselves — installing and tuning RetroArch's roster directly rather than letting Batocera manage them — our walkthrough on getting all 200 RetroArch cores running covers that territory, and the underlying machinery is the same libretro core system Batocera bundles. Treat updates the way you treat any system update: take them when stable, read what changed, and keep a backup of your batocera.conf before you experiment.

A Complete Working batocera.conf

The File and Where It Lives

Batocera's entire behavior is steered by a single text file: batocera.conf, living at /userdata/system/batocera.conf (i.e. share/system/batocera.conf). The menus you click write to this file; you can also edit it directly over SSH for surgical control. The format is flat key=value lines, with global keys prefixed global. and per-system keys prefixed by the system's short name. Back it up before you touch it — it is the one file whose corruption sends EmulationStation into a crash loop.

The Configuration

Here is a sane, complete starting configuration for a PC build — global defaults plus a few representative per-system overrides. Adjust to your hardware; the comments explain each choice:

## --------------------------------------------------------------
## /userdata/system/batocera.conf  -  Batocera 38 (x86_64)
## Flat key=value. Menus edit this file; so can you, carefully.
## --------------------------------------------------------------

## --- Global defaults ---
global.retroachievements=0        # toggle on and add login to use
global.smooth=1                   # bilinear smoothing on scaled output
global.shaders=none               # set per-system; global shaders cost fps
global.rewind=0                   # rewind is CPU-heavy; enable per-system
global.autosave=1                 # auto save-state on exit
global.integerscale=0             # crisp pixels per-system, not globally
audio.volume=90
wifi.enabled=0                    # set 1 and add wifi.key for wireless
system.power.timeout=0            # never auto-suspend a console

## --- Updates ---
updates.enabled=1
updates.type=stable               # never 'beta' on a daily driver

## --- SNES: snes9x, sharp integer scaling ---
snes.core=snes9x
snes.videomode=default
snes.integerscale=1

## --- PlayStation: swanstation, no filtering ---
psx.core=swanstation
psx.bilinear_filtering=0
psx.rewind=1

## --- Nintendo 64: mupen64plus-next, 4:3 lock ---
n64.core=mupen64plus_next
n64.video_43aspect=1

## --- Mega Drive: genesisplusgx, CRT shader on ---
megadrive.core=genesisplusgx
megadrive.shaders=scanlines

## --- PS2: standalone PCSX2 (only on capable CPUs) ---
ps2.core=pcsx2
ps2.videomode=default

## --- Controllers ---
controllers.bluetooth.enabled=1

Per-System and Per-Game Overrides

The hierarchy is global, then per-system, then per-game, each more specific winning over the last. Per-game tweaks live in RetroArch's own override files under the configs tree, so a single problem title — one that needs a different core, a slower frame pace, or a specific BIOS region — gets its own settings without disturbing the rest of that system's library. The discipline that keeps this maintainable: change one key, reboot or relaunch, confirm it did what you expected, then move on. Editing twenty keys at once and then wondering which one broke EmulationStation is a self-inflicted wound, and the fix is always the same — SSH in, revert batocera.conf, start smaller.

The Verdict: Free, Stable, and Slightly Smug

Who Should Run This

If you have a spare x86_64 machine and a pile of media you legally dumped, Batocera is the correct answer and it costs nothing. It is non-invasive by design — it runs entirely from the USB and changes nothing on your host disk unless you explicitly choose to install internally — so the downside of trying it is roughly zero. Version 38 being old is a feature, not a flaw: it means the thing is stable, documented to death, and unlikely to surprise you on a Saturday. You get 50-plus emulators, a coherent front end, and a config system that scales from "clicked some menus" to "hand-edited every key."

Who Should Buy a Handheld Instead

If your real desire is to play on the couch or the train rather than to tinker, the boot-menu ritual and BIOS scavenger hunt are overhead you can skip by buying purpose-built hardware. A modern handheld arrives configured. And if your goal is lag-free, cycle-accurate hardware emulation rather than software approximation, that is a different religion entirely — the FPGA path we covered in our MiSTer Multisystem 2 piece answers a question Batocera deliberately doesn't. Batocera is software emulation done well and given away. It is not pretending to be silicon.

The Bottom Line

The "batocera download" is free, the install is twelve honest steps, and everything that can go wrong is firmware refusing to boot a USB or a BIOS file named slightly wrong. None of it costs money, all of it is documented in the open on GitHub and the wiki, and the project's flat refusal to ship you a single copyrighted byte is the reason it will still be here next year. Flash it, feed it your own files, run the BIOS check, and stop paying strangers for software that was always free.