Batocera Download 2026: 43.1 in 12 Steps, 30 Min

The phrase batocera download hides a small lie. There is no single download. There is an image, an architecture, a version string, and a destination drive — and getting any one of those four wrong lands you somewhere between "nothing boots" and "I have just reformatted the disk with my tax returns on it." Batocera itself is refreshingly honest about this: the project's own installation wiki warns, in as many words, that pointing the flasher at the wrong drive will corrupt it and that the action is irreversible. Most guides bury that line at the bottom. We are going to lead with it.

This is a full walkthrough of downloading and installing Batocera 43.1 — the 30 May 2026 point release of the "Glasswing" line — from the only URL that matters, onto a USB stick or SD card, in twelve numbered steps. Budget roughly thirty minutes, most of which is the image decompressing and writing while you make coffee. Every version number, filename, and menu path below is traceable to Batocera's own documentation, because the "batocera download" search results are thick with content-farm mirrors that will happily hand you a slower, older, or malware-adjacent copy of something the project gives away for nothing. When a mirror asks you to disable your ad-blocker to reach a "download button," you are not on the project site.

What Batocera Actually Is (And Why the Download Matters)

Before you download anything, understand what you are downloading. This is not a program. It is an operating system, and that changes every decision that follows.

A distribution, not an app

Batocera.linux is not something you install on top of Windows or macOS. It is the operating system. The project describes it as a retro-gaming distribution you copy to a USB stick or SD card to turn a computer or nano-computer into a game console, and that description is load-bearing. When you flash Batocera, you are writing a bootable Linux image — kernel and all — that seizes the machine at power-on and drops you straight into the EmulationStation front end. There is no Windows underneath to fall back to. There is no desktop to alt-tab into. The system partition is read-only by design, an immutable image built with Buildroot, so a crash mid-session cannot rot your configuration. Everything you change — ROMs, saves, settings — lives on a separate, writable userdata partition. This is the architectural opposite of a launcher. Unlike RetroPie, which is a bundle of packages layered on top of Raspberry Pi OS and inherits that OS's entire maintenance burden, Batocera ships as a single sealed image you either boot or you don't. That design gap is exactly why, as we covered in RetroPie's freeze at v4.8 while the Pi got more expensive, one project ships current images for the Pi 5 and 64-bit PCs and the other still points you at a 2022 build.

Free, open-source, and what that actually buys you

It costs nothing. Not "free tier," not "free with an account," not "free trial" — the entire distribution is released at no charge under a Creative Commons BY-NC-SA license, with the full source tree hosted on GitHub at batocera-linux/batocera.linux, copyright 2016–2026. There is no telemetry phoning home, no license key, no upsell nag. What the open-source posture buys you, beyond the zero on the invoice, is auditability: the repository that builds the official images is the same one you can read, fork, or compile yourself. What it does not buy you is games. Batocera ships zero copyrighted ROMs and zero proprietary BIOS files. The image is an empty console. Supplying the software is your problem, and the legal weather around that software is your problem too — the project stays scrupulously on the right side of the line by distributing nothing it lacks the right to distribute.

Version 43 "Glasswing" and the 43.1 patch

As of mid-2026 the current stable release is Batocera 43.1, published 30 May 2026. It is a point release — a stability patch — sitting on top of Batocera 43 "Glasswing," which landed 8 May 2026. Hold onto that distinction, because at least one widely-copied 2026 setup guide labels 43.1 itself "Glasswing" and dates the codename to 30 May. That is wrong. Glasswing is the 43 line. 43.1 is the fix that followed it three weeks later, cleaning up regressions that shipped in the .0: EmulationStation dropping systems and collections, broken LR-Dolphin options, a Steam/Flatpak issue, Microsoft controllers being misdetected as keyboards, and the storage manager ignoring some partitions. The 43 line's headline features are the reworked AMD and Intel graphics stack on the x86_64-v3 image, a move to Wayland with the LabWC compositor, and kernel 6.15.11 underneath. If you are downloading today, you want 43.1. If a guide tells you to grab anything below 43.0, close the tab.

Prerequisites: Hardware, Storage, and Software Versions

You need three things: a target machine, a card or stick to flash, and a second computer with a flashing tool. The details of each determine whether this goes smoothly or turns into an afternoon.

The hardware floor

Batocera runs on modest silicon. For a PC or mini-PC, any 64-bit x86 CPU from the last decade is fine; 1 GB of RAM is the practical floor and 2 GB is comfortable. The heavier a system you want to emulate, the more you need — 8-bit and 16-bit consoles run on a potato, while GameCube, PS2, and Dreamcast want a modern quad-core and a real GPU. You will also need a controller (wired or Bluetooth), an HDMI display, and, for the flashing step, a second working computer running Windows, macOS, or Linux. None of that is exotic. The table below is the honest minimum-versus-recommended split.

The 16 GB storage rule nobody reads

Batocera's installation guide sets the minimum at 8 GB and recommends 16 GB, and the reason for the gap is the single most important number in this article: automatic updates are not supported on an 8 GB target. Flash Batocera to an 8 GB stick and you get a console that works but can never update itself in place — a museum piece, frozen at whatever version you wrote. There is also a physical squeeze. The compressed .img.gz download is roughly 3 GB; it decompresses to about 8 GB written, and on first boot Batocera auto-expands the userdata partition to fill whatever card you gave it. On an 8 GB card there is essentially nothing left over for ROMs, saves, and box art. In practice, treat 16 GB as the recommended floor and 32 GB or larger as the comfortable one. A fast A2-rated microSD or a USB 3.0 stick is worth the few extra currency units; a bargain-bin Class 4 card will bottleneck EmulationStation's scraping and every save-state you write.

Software you need before you start

You need exactly one tool to flash: balenaEtcher, in its current release. Etcher is the path Batocera's own setup flow and nearly every 2026 walkthrough describes, and its one genuinely useful trick is that it reads the compressed .img.gz directly — you do not decompress the download by hand. Point it at the .img.gz, point it at the target, flash. On Linux and macOS you can skip Etcher and use dd if you enjoy living dangerously and reading man pages; we cover that in the flashing section. You do not need a partition editor, a "driver pack," or any of the paid "USB creator" utilities the ads will push at you. The official Batocera install wiki lists the same short toolchain.

Steps 1–2: Identify Your Architecture and Pick the Right Image

The download page offers you a menu of images, and choosing the wrong one is the most common way a first attempt dies before it even flashes. Two steps: know your architecture, then read the filename.

Step 1 — x86_64 vs x86_64-v3 vs device-specific

Batocera's install guide is blunt: the downloaded image must match the architecture you intend to run. For the overwhelming majority of PCs, laptops, NUCs, and mini-PCs, that image is x86_64. If your machine is genuinely modern — a Zen 3 or newer AMD chip, a 10th-gen-or-later Intel, or a Steam Deck — you can instead take the x86_64-v3 image, which is where the 43 line's improved AMD and Intel graphics stack lives. Single-board computers and ARM handhelds do not use either of those; they take device-specific images keyed to the exact board. A Raspberry Pi 5 image will not boot on a Pi 4, and neither will boot on a PC. Get this wrong and the symptom is unambiguous: a black screen, a kernel panic, or a machine that simply ignores the stick.

# Match the image to the board. Common Batocera architectures:
x86_64        # Most 64-bit PCs, laptops, mini-PCs, NUCs
x86_64-v3     # Zen3+/Intel 10th-gen+, Steam Deck (better GPU stack)
bcm2712       # Raspberry Pi 5
bcm2711       # Raspberry Pi 4 / 400
bcm2837       # Raspberry Pi 3
rk3588        # Rockchip RK3588 ARM boards / handhelds
h700          # Allwinner H700 (RG35XX-class handhelds)

# Already running Batocera and unsure which board you are on? Check:
cat /boot/boot/batocera.board

On a Pi 5 that last command prints bcm2712; on a 64-bit PC it prints x86_64. Write the answer down before you touch the download page.

Step 2 — Reading the filename convention

Batocera's image names are self-documenting once you know the grammar. The 2026 convention is batocera-[architecture]-[version]-[date].img.gz, and the canonical example for this release is batocera-x86_64-43.1-20260530.img.gz. Every field is a fact you can verify at a glance.

batocera-x86_64-43.1-20260530.img.gz
         |      |    |
         |      |    +--- build date (YYYYMMDD): 30 May 2026
         |      +-------- version: 43.1 point release
         +--------------- architecture: 64-bit PC

# Pattern:  batocera-[architecture]-[version]-[date].img.gz

If the file you downloaded reads batocera-bcm2711-43.1-... and you are on a PC, stop — that is a Pi 4 image. If the version field says 42 or 41, you are on an old mirror. The date field is your fastest sanity check that you have the 30 May 2026 build and not a stale re-upload.

Raspberry Pi, ARM boards, and handhelds

The device-specific list matters most for the Pi and the growing pile of ARM handhelds. Pi 5 takes bcm2712, Pi 4 and 400 take bcm2711, Pi 3 takes bcm2837. Rockchip's RK3588 boards use rk3588, and Allwinner H700 handhelds — the RG35XX class — use h700. This is the same architecture-matching discipline you apply to any custom firmware; if you have ever loaded OnionOS onto a Miyoo Mini Plus and its 6,041-ROM aggregation, the instinct is identical — the image is welded to the SoC. For a broader look at where these ARM images land, our rundown of the 2026 Retroid Pocket lineup maps which chips you are actually buying.

Steps 3–4: Downloading From batocera.org/download

With your architecture chosen and the filename grammar memorized, the actual download is two steps and one non-negotiable rule about where you get it.

Step 3 — The only URL that matters

Go to batocera.org/download. That is the entire instruction. The official download page — the one the community and every credible 2026 guide point to — lets you select your hardware and hands you the correct .img.gz as a direct download. There is no queue, no "premium" fast lane, no account. Pick your architecture from the on-page selector, confirm the filename matches the pattern from Step 2, and start the transfer. On a normal connection the roughly 3 GB file lands in a few minutes. Do not decompress it, do not rename it, and do not "just grab the torrent someone linked" — the project ships this directly and freely, so a torrent or a third-party mirror is, at best, slower and older and, at worst, tampered with.

Step 4 — Verifying the download you just pulled

Trust, then verify. Two quick checks catch a corrupt or wrong download before you waste a flash on it. First, confirm the file size is in the right ballpark — around 3 GB for the compressed image. Second, if the download page publishes a checksum, compare it. A truncated download will fail to boot in a way that looks exactly like a hardware problem, so spending fifteen seconds here saves you an hour of misdiagnosis later.

# The download is a COMPRESSED image, roughly 3 GB. Do not unzip it.
ls -lh batocera-x86_64-43.1-20260530.img.gz
# Expected, approximately:
# -rw-r--r-- 1 you you 3.0G May 30 2026 batocera-x86_64-43.1-20260530.img.gz

# Optional integrity check against the value published on batocera.org:
sha256sum batocera-x86_64-43.1-20260530.img.gz
# -> compare the printed hash to the site's; they must match character for character

What NOT to download

Search "batocera download" and a tier of parasite sites appears above or beside the real one: SEO farms with names engineered to look official, "review" pages that funnel you to a re-hosted image, and outright fake domains recycling the project's screenshots. Some of these — the tech-insider-and-shattered genre of content mill — fabricate version numbers and dates wholesale to farm clicks. Ignore them entirely. Batocera has exactly one home for images, and it is the domain in Step 3. The GitHub repository is the canonical code host, and the wiki is the canonical documentation; nothing else is authoritative. If a page's "download" button opens an ad interstitial, you are being monetized, not helped.

Steps 5–7: Flashing the Image With balenaEtcher

Now you write the image to the stick. This is the step Batocera's own docs flag as irreversible, so it gets three sub-steps and a warning in bold.

Step 5 — Why Etcher (and the dd alternative)

Install and open balenaEtcher. Its selling point for this job is that it flashes the compressed .img.gz directly — no manual decompression, no intermediate .img file cluttering your Downloads folder. It also refuses, by default, to write to your system drive, which is precisely the mistake that ends first attempts. If you are on Linux or macOS and prefer the command line, dd works, but dd gives you no guardrails whatsoever; the of= argument is a loaded weapon. Whichever you choose, the workflow the 2026 video and written guides all describe is the same three-move sequence: select the image, select the target, flash.

# balenaEtcher is the recommended tool and reads .img.gz directly.
# Linux/macOS purists can use dd instead. TRIPLE-CHECK the of= target:

# 1) Identify your USB stick (NOT your system disk):
lsblk

# 2) Decompress-and-write in one pipe (replace sdX with your stick):
gzip -dc batocera-x86_64-43.1-20260530.img.gz | sudo dd of=/dev/sdX bs=4M status=progress conv=fsync

# Choosing your system disk as 'of=' here destroys it. There is no undo.

Step 6 — The three-click flash workflow

In Etcher: click Flash from file and choose batocera-x86_64-43.1-20260530.img.gz. Click Select target and choose your USB stick or SD card. Click Flash. Etcher decompresses, writes, and then verifies what it wrote, which is why the progress bar makes two passes — do not pull the stick when the write bar hits 100%; wait for verification to finish and for Etcher to report success. Expected wall-clock is a few minutes on a USB 3.0 stick, longer on slow media. This is the coffee window.

Step 7 — The irreversible-drive warning (read this twice)

Here is the line the guides bury and we lead with. Batocera's install documentation warns explicitly that selecting the wrong destination drive can corrupt the USB stick — and, more to the point, whatever else you mistakenly select — and that the action is irreversible. Etcher's target picker shows the drive's size and label for a reason. Confirm the capacity matches your stick, not your 2 TB internal SSD. If two drives report the same size, physically unplug every removable drive except the one you are flashing before you touch Select target. There is no recycle bin for a raw disk write. The official install guide repeats this caution because it is the single most expensive mistake a first-timer makes.

Steps 8–9: First Boot, Auto-Expand, and Installing to Disk

The stick is written. Now you boot the target machine from it, let Batocera set itself up, and decide whether to run from the stick forever or move onto an internal disk.

Step 8 — Booting from the USB stick

Move the stick to the target machine and boot from it. On a PC that means opening the one-time boot menu — usually F12, F11, F8, or Esc depending on the vendor — and selecting the USB device, or setting USB first in the UEFI boot order. Two settings sabotage this more than any other: Secure Boot and Fast Boot. Disable both in the firmware. Secure Boot will reject Batocera's bootloader outright; Fast Boot skips USB enumeration entirely on some boards. Once it boots, you land in EmulationStation with no further prompts.

# What a healthy first boot looks like (abbreviated console output):
Batocera.linux 43.1
Expanding userdata partition to fill the device... done
Starting network... ok
Starting EmulationStation...

# You then arrive at the system-select carousel. No login. No installer wizard.

Step 9 — Userdata auto-expansion

On that first boot, Batocera automatically expands its userdata partition to consume all remaining free space on the card. This is why the 16 GB-versus-8 GB decision from the prerequisites section is permanent: the partition sizes itself to the medium you gave it. You do not run a resize tool; it simply happens. After it completes, the writable space — for ROMs, saves, and configuration — is whatever your card had beyond the ~8 GB the system image occupies. On a 32 GB card that is roughly 24 GB of headroom; on an 8 GB card it is a rounding error.

Step 9b — Optional: install to an internal disk

Running Batocera from a USB stick is entirely valid and popular — it leaves the machine's internal disk untouched. But if you have dedicated a mini-PC to this, you can install Batocera onto its internal drive for speed and to free the USB port. From inside the running system: START → SYSTEM SETTINGS → INSTALL BATOCERA ON A NEW DISK. This clones the system to the chosen disk and, again per the official guide, wipes the destination completely and irreversibly. Pick the correct target. There is no confirmation dialog generous enough to save you from selecting the wrong drive.

Steps 10–11: Adding ROMs and BIOS Over the Network

You now have an empty console. Filling it is a network operation, and Batocera makes it deliberately simple: it exposes a Samba share you drop files into from any other machine on the LAN.

Step 10 — The network share

With Batocera booted and on the network, its files are reachable as a Samba share named share. Open it from your desktop using whichever of these your OS prefers. Windows and macOS resolve the hostname; if name resolution is flaky, fall back to the machine's IP address, which Batocera shows in its network settings.

# Windows Explorer / macOS Finder (Go -> Connect to Server):
\\BATOCERA\share
smb://BATOCERA.local/share

# By IP, if hostname resolution fails:
\\192.168.1.50\share

# Linux file manager (GVFS/KIO):
smb://batocera.local/share

Step 11 — The /userdata folder structure

Everything you add lives under /userdata, which is what the share exposes. ROMs go into roms/ inside a subfolder named for the system's short name — snes, genesis, psx, nes, and so on. BIOS files go into bios/. Saves and states land in saves/, and system configuration lives in system/. Put a Super Nintendo ROM in roms/snes/, not roms/nintendo/; the folder names are fixed short-codes, not free text.

/userdata/
|-- roms/
|   |-- snes/        # place .sfc/.smc here
|   |-- genesis/
|   |-- psx/
|   +-- nes/
|-- bios/            # place required BIOS files here
|-- saves/           # save files and states
+-- system/
    +-- batocera.conf

BIOS placement and the _info.txt manifest

Some systems refuse to launch without the correct BIOS — PlayStation, Sega CD, and Neo Geo among them. Those files go directly in /userdata/bios/, and Batocera checks them by MD5 hash, so a renamed or wrong-region BIOS fails silently. Two references keep you sane here. Inside each roms/[system]/ folder, Batocera drops an _info.txt that lists the accepted file formats for that system — read it before you wonder why a .chd is being ignored. And the emulator project's own libretro BIOS reference, alongside Batocera's add games and BIOS wiki, lists the exact filenames and hashes each core expects. If you would rather sidestep the whole BIOS-and-ROM legal question by dumping your own carts, that is a different rabbit hole — and one where a hardware solution like the MiSTer Multisystem 2 or a cartridge dumper starts to make sense.

Step 12: Updating and the Content Downloader

The final step is keeping the thing current — and this is where the 16 GB storage rule pays off, because updates are the feature an 8 GB card silently forfeits.

Step 12 — In-place update from the menu

Updating Batocera is a menu operation. From EmulationStation: MAIN MENU → UPDATES & DOWNLOADS → START UPDATE. Batocera pulls the latest stable build for your architecture and applies it, preserving your userdata partition — your ROMs, saves, and config survive the update untouched, because they live on a separate partition from the system image. That separation is the entire point of the read-only design. Staying current is not optional hygiene; point releases like 43.1 exist specifically to fix boot and controller regressions, and skipping them is how you inherit bugs the project already patched. The discipline is the same one that makes firmware-tracking worthwhile on dedicated hardware — see how many revisions it took the Analogue 3D to reach a stable feature set across a dozen builds. Software distros move faster and cost nothing to update; there is no excuse to sit on a stale image.

The SSH / manual upgrade path

If the machine is headless or the menu update stalls, there is a command-line path. SSH into Batocera and run its upgrade command, which has existed since Batocera 5.23. For offline or mirror-pinned upgrades, you drop a boot.tar.xz into /userdata/system/upgrade and run the manual upgrade. The manual upgrade wiki documents both, including pointing the upgrade at a specific mirror when the default is slow.

# SSH in (default credentials: user 'root', password 'linux'):
ssh root@BATOCERA.local

# In-place upgrade to the latest stable build:
batocera-upgrade

# Offline/manual: place boot.tar.xz for your arch here first,
# then run the manual upgrade (mirror example shown for reference):
#   /userdata/system/upgrade/boot.tar.xz
#   mirror: https://mirrors.o2switch.fr/batocera/
batocera-upgrade

The content downloader (since 5.27)

The same UPDATES & DOWNLOADS frontend, reachable from the system list in EmulationStation, is also Batocera's content downloader. Available since Batocera 5.27, it offers freely distributed ROMs — homebrew and public-domain titles the project has the right to ship — plus bezels, music themes, and other cosmetic and functional enhancements, all pulled from inside the interface with no manual file wrangling. It is the sanctioned way to flesh out a fresh install with legitimately free content, and it is documented on the official Updates & Downloads wiki.

5 Common Pitfalls (And How to Fix Them)

Five mistakes account for most failed first installs. Every one of them is avoidable if you read this section before, not after.

Pitfalls 1–2: Wrong architecture, wrong drive

1. Downloaded the wrong architecture. Symptom: black screen, kernel panic, or the machine ignoring the stick. An x86_64 image will never boot a Raspberry Pi, a Pi image will never boot a PC, and x86_64-v3 will refuse to run on a pre-Zen-3 CPU. Fix: re-check cat /boot/boot/batocera.board or your hardware model, download the matching image from the download page, and re-flash. This is a two-minute fix disguised as a hardware failure.
2. Flashed to the wrong drive. Symptom: your data is gone and the wrong disk now claims to be an 8 GB Batocera volume. This is the irreversible one. Fix: there is no fix after the fact — only prevention. Verify the target by size and label in Etcher, and physically unplug every removable drive except the target before flashing.

Pitfall 3: The 8 GB freeze

1. Used an 8 GB card and lost updates. Symptom: no auto-update option, and almost no free space after the userdata partition expands. Fix: this is a storage-tier problem, not a bug. Reflash to a 16 GB card at minimum — 32 GB or larger if you want room for ROMs — and the update path returns. You cannot resize your way out of it after the fact without starting over.

Pitfalls 4–5: The image and the v43 emulator changes

1. Manually decompressed the .img.gz and then got confused. Symptom: Etcher or your flasher won't accept the file, or you flashed a partial archive. Fix: don't decompress it. Etcher and Batocera's flow read the .img.gz directly. If you already unzipped it, flash the resulting .img — that also works — but the compressed file is the intended input.
2. Games that ran on an older Batocera suddenly won't launch after upgrading to 43. Symptom: 3DS titles refuse to start; DS saves vanish. Fix: the 43 line requires 3DS ROMs to be decrypted (hardware shaders default off), and it removed the DraStic DS emulator in favor of melonDS — and saves do not transfer between the two cores. This is a breaking change, not a corruption. Decrypt your 3DS dumps and expect to re-establish DS saves.

Troubleshooting Table: Failure Modes and Fixes

When something breaks after a clean flash, the cause is almost always one of a short list. This table maps symptom to cause to fix so you can stop guessing.

Boot and flash failures

These strike before you ever reach EmulationStation, and they are the most alarming because the machine looks dead. It almost never is.

Input, video, and network

The system boots but misbehaves. Controllers, missing consoles, and invisible network shares dominate this category.

Reading the logs when the table runs out

If none of the above fits, Batocera keeps EmulationStation and per-emulator logs under /userdata/system/logs/, reachable over the same SSH connection or the network share. A launch that fails instantly usually leaves a one-line reason at the tail of the relevant emulator log — a missing BIOS, an unsupported format, a bad ROM. That line is faster than any forum thread.

Advanced Tips: batocera.conf, SSH, and Offline Upgrades

Once the basics work, Batocera is deeply configurable from a single text file and an SSH prompt. This is where a working install becomes a tuned one.

Editing batocera.conf

The master configuration lives at /userdata/system/batocera.conf. It is a flat key=value file — one setting per line, a leading ; comments a line out — and it controls Wi-Fi, language, video, retroachievements, and per-system emulator overrides. You can edit it over the network share or via SSH. The full key syntax is documented on the batocera.conf syntax wiki; the essentials look like this.

# /userdata/system/batocera.conf -- global system settings
# Syntax: key=value, one per line. ';' at line start = comment/disable.

## Wi-Fi
wifi.enabled=1
wifi.ssid=YourNetwork
wifi.key=YourPassword

## Language / region
system.language=en_US
system.timezone=Europe/London

## Video
global.videomode=default
global.bezel=thebezelproject

## Retroachievements (optional)
global.retroachievements=0

SSH access and the settings CLI

SSH is enabled by default. Connect as root with the password linux — and change that password immediately if the machine is on any network you do not control, because a default-credential box on a shared LAN is a liability. From the shell you can edit configs, read logs, run batocera-upgrade, and use the batocera-settings helper to read or write individual keys without hand-editing the file.

# Connect:
ssh root@BATOCERA.local          # password: linux (change it!)

# Read or write a single setting from the shell:
batocera-settings-get system.language
batocera-settings-set system.language en_US

# Apply changes and restart the front end:
batocera-es-swissknife --restart

Offline upgrades and the accuracy ceiling

For machines that can't reach the internet, the manual upgrade path — dropping the architecture's boot.tar.xz into /userdata/system/upgrade and running batocera-upgrade against a local copy or a mirror such as the o2switch mirror — keeps you current without a live connection. One honest caveat worth stating: Batocera is software emulation, and software emulation approximates original hardware rather than reproducing it cycle-for-cycle. For 99% of a library that is invisible. For the handful of titles that lean on exact timing, an FPGA implementation like the one in the MiSTer Multisystem 2 is the accuracy ceiling Batocera does not try to reach — and does not need to, for the price of nothing versus the price of a board.

A Complete Working Configuration

Here is the whole thing assembled — a reference batocera.conf, the folder layout it assumes, and a plain verdict — so you can copy, adapt, and stop reading.

A reference batocera.conf

This is a sane starting configuration for a PC install on a wired or wireless network, with retroachievements off by default and the Bezel Project overlays enabled. Drop it at /userdata/system/batocera.conf, adjust the Wi-Fi and locale lines, reboot.

# /userdata/system/batocera.conf
# Batocera 43.1 -- reference configuration
# Syntax: key=value; ';' comments a line out.

############ NETWORK ############
wifi.enabled=1
wifi.ssid=YourNetwork
wifi.key=YourPassword
; wired connections need no config -- DHCP is automatic

############ SYSTEM ############
system.language=en_US
system.timezone=Europe/London
system.hostname=BATOCERA
system.samba.enabled=1
ssh.enabled=1

############ VIDEO ############
global.videomode=default
global.bezel=thebezelproject
global.smooth=1
global.rewind=1
global.autosave=0

############ ACHIEVEMENTS (optional) ############
global.retroachievements=0
; global.retroachievements.username=
; global.retroachievements.password=

############ PER-SYSTEM OVERRIDE EXAMPLE ############
; force a specific core for the SNES:
; snes.core=snes9x
; n64.core=mupen64plus-next

The folder layout, recapped

Every file you add hangs off /userdata, exposed as the share Samba mount. Memorize this and the "why won't my game show up" questions disappear.

/userdata/
|-- roms/
|   |-- snes/        .sfc .smc
|   |-- nes/         .nes
|   |-- genesis/     .md .bin
|   |-- psx/         .chd .cue/.bin  (needs BIOS)
|   +-- n64/         .z64 .n64
|-- bios/            required BIOS, checked by MD5
|-- saves/           saves and save-states
+-- system/
    |-- batocera.conf   <- the file above
    +-- logs/           <- read these when a launch fails

The verdict

Batocera's "download" is really four correct choices in a row — right architecture, right version, right tool, right drive — followed by an OS that stays out of your way. Get 43.1 from batocera.org/download, match the image to your hardware, flash it with Etcher onto a 16 GB-or-larger card, and mind the one irreversible step where you pick the target. Do that and you have a free, open-source, no-telemetry console built from a project that has been shipping current images while its nearest rival sat frozen since 2022. For deeper reference beyond this walkthrough, keep four bookmarks: the download page, the install wiki, the GitHub repository, and, for the high-level context on the project's history and licensing, its Wikipedia entry. Everything else claiming to be a "batocera download" is somebody else's advertising.