/// FIELD NOTES FROM A SELF-AWARE GAME SITE
Batocera Download 2026: 43.1 in 12 Steps, 30 Min
Type batocera download into a search bar and the internet will assure you it is a one-click affair: grab a file, click a button, play Sonic. That is technically true and practically a trap. Batocera is not installed in the sense a Windows user means the word. It is flashed — written byte-for-byte onto a drive as a raw disk image — and the single most reliable way to ruin an afternoon is to treat that image like an application you double-click.
As of 22 July 2026, the current stable release is Batocera 43.1, a point update pushed on 30 May 2026 on top of Batocera 43 "Glasswing," which landed on 8 May 2026. It is free — genuinely, permanently, with no "pro tier" — licensed CC-BY-NC-SA, and it emulates north of 200 systems out of the box. The download itself is a roughly 3 GB compressed image that expands to about 8 GB once written. That is the entire product. Everything else is a matter of knowing which 3 GB file to grab and, more importantly, where not to point the flasher.
This guide walks the full path: choosing an architecture, downloading and verifying the image, flashing it without unzipping it, booting, optionally installing to an internal disk (the step that irreversibly erases whatever was there), loading ROMs and BIOS files, and updating without ever reflashing again. Twelve steps, roughly thirty minutes of hands-on time, and a short, unglamorous list of the ways people torch their own data along the way.
What You're Actually Downloading
Before you touch a download button, it helps to understand that the file you are about to fetch is not a program. It is a complete operating system frozen into a single compressed blob. That distinction dictates every step that follows.
A disk image, not an installer
The file you download follows the pattern batocera-(architecture)-(version)-(date).img.gz. For a PC in the 43.1 cycle that meant batocera-x86_64-43.1-20260529.img.gz — the x86_64 build carried the date stamp 20260529, while the point release was announced on 30 May 2026 and individual architectures were stamped anywhere from 29 May to 1 June depending on when each build finished. The .img.gz extension tells you exactly what it is: a raw disk image (.img) that has been gzip-compressed. Inside the compression is a bit-for-bit picture of a bootable drive — a boot partition, a Linux root, and a data partition — that a flasher lays down onto your USB stick or SD card unchanged. You do not merge it with an existing OS. You do not run a setup wizard. You overwrite a drive with it.
This is why so much of the advice below is about which drive and which flasher rather than "how to install." The install is trivial; the aiming is where people miss.
Glasswing, and why 43.1 followed so fast
Batocera 43 shipped under the codename "Glasswing" with a genuinely consequential change under the hood: the x86_64 build moved to an x86_64-v3 baseline and the desktop stack shifted to Wayland with the LabWC compositor, with AMD and Intel graphics as the well-supported path and Nvidia still flagged experimental. It runs on kernel 6.15.11 with LLVM 19.1.7. Barely three weeks later, 43.1 arrived as a pure stability patch — no new headline features, just repairs. It fixed EmulationStation dropping systems and making collections vanish, broken LR-Dolphin options, a Steam and Flatpak launch issue, LR-MAME light-gun regressions, some Microsoft controllers being detected as keyboards, and the storage manager ignoring certain partitions. If you are downloading Batocera in 2026, you want 43.1 specifically, because 43.0 shipped with exactly the kind of paper-cut bugs that make a newcomer assume they did something wrong.
Free, open-source, and 200-plus systems
There is no upsell here and no telemetry-funded free tier. Batocera is 100% open-source, developed in the open at the batocera-linux GitHub repository, and it costs exactly zero dollars. That matters because the search term "batocera download" is a favorite of content farms that wrap the free image in a fake installer or a survey wall. The only canonical source is the project's own download page; anything charging you money is a scam wearing Batocera's name. If your goal is broad, low-fuss coverage of everything from the NES to relatively modern consoles on hardware you already own, this is the appeal — and it is a different proposition from the frozen, Pi-centric world of RetroPie, whose official image has been stuck at v4.8, or from the deterministic, hardware-accurate approach of an FPGA box like the MiSTer Multisystem 2. Batocera's bet is breadth via software emulation, and the 200-plus number is the whole thesis.
Prerequisites: Hardware & Software
Gather these before you download anything. Half of all failed Batocera installs are traceable to a drive that was too small, a flasher that was too old, or a target disk the user did not actually intend to erase.
The hardware floor
Batocera's published minimums are modest but real. You need at least 1 GB of RAM (2 GB recommended) and a storage device of at least 16 GB (32 GB recommended). The 16 GB figure is not arbitrary: below it, Batocera disables its own auto-update mechanism because there is not enough headroom to stage a new build, which means you would be back to manually reflashing every time you wanted a point release. A cheap, name-brand 32 GB USB 3.0 stick or a decent A1-rated microSD card is the sweet spot for a first run; a small SATA or NVMe SSD is better still if you intend to install permanently. CPU-wise, anything from a Raspberry Pi 4 upward, or roughly any x86 machine built in the last decade, will boot the menu; how well a given system emulates is a separate question entirely and depends heavily on the machine.
The flashing tools (and versions)
You need exactly one imaging tool, and it must be able to read a gzip-compressed image. Three do this reliably: Raspberry Pi Imager (use 1.8 or newer and its "Use custom" option), USBImager (a tiny, no-nonsense cross-platform writer), or Balena Etcher (1.18+). All three accept the .img.gz directly. What will not work is copying the file onto a drive in your file manager, "burning" it as a data disc, or extracting it and dragging the .img onto a FAT32 stick — none of those write the raw bytes to the boot sectors, and the machine simply will not boot. Pick one of the three, install it, and move on.
A drive you can afford to erase
Every step from here treats your target media as disposable. Flashing overwrites the entire device — not a partition, the whole disk — and the later in-system installer does the same to whatever internal drive you point it at. Before you continue, physically identify the stick or disk you intend to use and, if it is anything other than a blank stick, back up its contents now. The number of people who have flashed Batocera onto their photo-archive drive because it happened to be "Disk 2" is not small. Treat the destination selection as the single highest-stakes click in this entire process, because it is.
Which Image to Download
Batocera compiles a separate image for each CPU family it supports. Download the wrong one and it will not boot — there is no graceful fallback, no compatibility mode, just a black screen. Getting this right is the first real decision.
x86_64 for PCs and mini PCs
For the overwhelming majority of desktops, laptops, NUCs, and Intel/AMD mini PCs, the answer is the x86_64 image. This is the build that received Glasswing's x86_64-v3 and Wayland work, and it is the most capable Batocera target by a wide margin because it can lean on real GPU horsepower. If you are repurposing an old office PC, a Beelink or similar mini PC, or a home-built emulation box, download x86_64 and do not overthink it. The only caveat worth internalizing: Nvidia graphics remain experimental on the v43 stack, so a machine with an AMD or Intel GPU will give you the smoothest first boot. An Nvidia card is not a dealbreaker, but it is the most likely source of a black screen after the splash, and there are boot-time driver options to fall back on if it misbehaves.
Raspberry Pi and the bcm codes
Raspberry Pi boards each get a dedicated image keyed to their Broadcom SoC. In 2026 the mapping is: bcm2712 for the Raspberry Pi 5, bcm2711 for the Pi 4 and Pi 400, bcm2837 for the Pi 3, and bcm2836 for the Pi 2. Batocera — alongside Recalbox — ships an official Pi 5 image, which is one of the practical reasons to prefer it over RetroPie on newer Pi hardware. Download the image that matches your exact board; a Pi 4 image will not boot a Pi 5 and vice versa. The download page groups these clearly, so you are picking from a labeled list rather than guessing.
Handhelds, SBCs, and checking an existing board
Beyond PCs and Pis, Batocera publishes images for a sprawling set of single-board computers and handhelds — Rockchip rk3588 boards, the Allwinner h700 used by the Anbernic RG35XX line, Odroid and Orange Pi boards, and dedicated builds for devices like the Steam Deck, the Odin 2, and the Retroid Pocket 6 (all three of the latter were added device targets in the v42/v43 cycle). If you are choosing between a handheld's stock firmware and Batocera, or comparing something like the Miyoo Mini Plus and its curated ROM sets against a Batocera-class device, that is a hardware decision this guide will not make for you. If you already have Batocera running on a board and cannot remember which architecture it is, ask it directly over SSH:
[root@BATOCERA]# cat /boot/boot/batocera.board
x86_64That single line is the authoritative answer, and it is the string you match when you later update via the mirror. On a Pi 5 it would print bcm2712; on an RG35XX, h700. Write it down.
The 12-Step Download & Install
Here is the entire process as a numbered checklist, each step paired with the reason it exists. The detailed sections that follow expand the three or four steps that actually bite. If you read nothing else, read this list.
- Identify your hardware and pick the matching architecture. Rationale: the image is compiled per-CPU-family; the wrong architecture does not degrade gracefully, it simply refuses to boot.
- Download the .img.gz from the official download page. Rationale: the project's own download section is the only trustworthy source — third-party "mirrors" that outrank it in search are frequently stale, re-wrapped, or monetized.
- Download the matching MD5 file and verify the checksum. Rationale: a truncated 3 GB download flashes without complaint and then fails to boot in ways that look exactly like a hardware fault, costing you an hour of misdiagnosis.
- Do not unzip the .img.gz. Rationale: every recommended flasher reads gzip natively; decompressing first burns an extra ~5 GB of disk and accomplishes nothing.
- Insert the target USB stick or SD card — 16 GB minimum, 32 GB recommended. Rationale: under 16 GB, Batocera disables auto-update, condemning you to manual reflashes forever.
- Open Raspberry Pi Imager, USBImager, or Balena Etcher and select the .img.gz as a custom image. Rationale: these three write raw bytes and read compression; a file-manager copy does not produce a bootable drive.
- Triple-check the destination device, then flash. Rationale: the flasher overwrites the whole device — choose the wrong disk and its contents are gone with no undo.
- Move the media to the target machine and set it to boot from USB with Secure Boot off. Rationale: PCs default to their internal OS; Batocera will not appear until the firmware is told to look at the stick.
- Boot once and let first-boot auto-expand the data partition. Rationale: the image writes ~8 GB, then the userdata partition grows to fill the drive on that first boot — interrupting it leaves you with a fraction of your storage.
- Decide: run from USB, or install to an internal disk via SYSTEM SETTINGS then INSTALL BATOCERA ON A NEW DISK. Rationale: installing is faster and roomier but erases the entire target disk irreversibly, and you must choose the same architecture you downloaded.
- Copy ROMs into share/roms/[system] and BIOS files into share/bios/. Rationale: Batocera ships with zero games; a console only appears in the menu once its folder contains a recognized ROM.
- Update in place via MAIN MENU then UPDATES & DOWNLOADS then START UPDATE, or over SSH with batocera-upgrade. Rationale: you never reflash to move between point releases — the updater pulls only what changed.
Why the order matters
The sequence is not decorative. Verifying the checksum (step 3) before flashing (step 7) saves you from chasing phantom hardware faults. Letting first-boot finish (step 9) before installing to disk (step 10) ensures the installer copies a fully-expanded, healthy system rather than a half-initialized one. And adding ROMs (step 11) after you have settled on run-from-USB versus install-to-disk (step 10) means you are not copying gigabytes of games onto media you are about to abandon. Skip ahead and you will usually end up repeating a step.
Expected output at each gate
Three checkpoints tell you the process is on track. After step 3, your checksum tool prints OK. After a successful flash in step 7, the tool reports "Write successful" or verifies the written image against the source. And after step 9, the storage manager inside Batocera reports a data partition that matches your drive's full size — a 32 GB stick shows roughly 24 GB free, not 3 GB. If any of those three is wrong, stop and fix it before continuing; every one of them is a leading indicator of a later failure.
How long it really takes
The honest breakdown: the download is bandwidth-bound (a few minutes on a fast line, longer on a slow one), the checksum takes under a minute, the flash runs five to fifteen minutes depending on your media's write speed, and first boot plus partition expansion is another minute or two. Installing to an internal SSD adds perhaps five minutes. The thirty-minute estimate assumes you already have ROMs staged; hunting down and organizing a game library is a separate, open-ended project that no tutorial can time.
Downloading & Verifying the Image
This is the step everyone thinks is trivial and half the failures start here — either from grabbing a bad file or from skipping the thirty seconds of verification that would have caught it.
The download page and the filename pattern
Go to the official Batocera download page and nowhere else. The page groups builds by category — desktop PCs and laptops, the various Raspberry Pi models, handhelds like the Steam Deck and Odin 2, and a long tail of SBCs — and each entry gives you the image plus a torrent and an MD5 checksum. Confirm the filename matches the batocera-(arch)-(version)-(date).img.gz pattern and that the architecture segment is the one you chose in the previous section. For a 43.1 PC install you are downloading batocera-x86_64-43.1-20260529.img.gz, roughly 3 GB. If a site offers you a ".exe installer" or asks you to complete a survey to "unlock" the download, close the tab; that is not Batocera.
Torrent vs direct, and the MD5
The direct HTTP download is simplest. The torrent is worth using if your connection is flaky, because BitTorrent verifies each piece as it arrives and will re-fetch corrupt chunks automatically — which, conveniently, sidesteps the exact failure mode that makes manual verification necessary. Either way, once the file lands, verify it against the published MD5 before you flash. On Linux or macOS, drop the image and its .md5 in the same folder and run the check; on Windows, PowerShell has a built-in hasher:
# Linux / macOS
$ md5sum -c batocera-x86_64-43.1-20260529.img.gz.md5
batocera-x86_64-43.1-20260529.img.gz: OK
# Windows (PowerShell)
> Get-FileHash .\batocera-x86_64-43.1-20260529.img.gz -Algorithm MD5
Algorithm Hash
--------- ----
MD5 7F3A...compare this to the .md5 file...The word you are looking for is OK. If the hashes do not match, the download is corrupt — delete it and fetch it again. Do not flash a file that failed verification "just to see;" you will see a black screen and waste an hour blaming your USB port.
Expected output: what a good download looks like
A healthy download directory contains three files that share a base name — the image, its checksum, and optionally the torrent metadata — with the image itself sitting at roughly 3 GB:
batocera-x86_64-43.1-20260529.img.gz 3.0G
batocera-x86_64-43.1-20260529.img.gz.md5 64 bytes
batocera-x86_64-43.1-20260529.img.gz.torrent ~40 KBIf your image is only a few hundred megabytes, the download was interrupted and truncated — a truncated gzip often still opens far enough to fool a flasher, which is precisely why the checksum step is not optional. A 3 GB file that verifies clean is your green light.
Flashing Without Unzipping
Flashing is mechanically simple and conceptually the most dangerous step, because the tool you are about to use will happily overwrite any disk you point it at, with no recycle bin.
Raspberry Pi Imager
Despite the name, Raspberry Pi Imager writes to any drive and is the friendliest option for PC users too. Launch it, click CHOOSE OS, scroll to the bottom and pick Use custom, then select your batocera-x86_64-43.1-20260529.img.gz — it reads the gzip directly, no extraction required. Click CHOOSE STORAGE and here is where you slow down: the list shows every removable device, and you must select the exact stick or card you intend to erase. Then WRITE. Imager will typically re-read the written data to verify it, which is worth letting finish. This is the tool the project itself points to, and the official Batocera install guide walks the same flow.
USBImager and Balena Etcher
If you want something even more minimal, USBImager is a sub-megabyte utility with a single window: pick the image, pick the device, hit Write. It has no telemetry and no cloud anything. Balena Etcher is the third common choice — some 2026 mini PC walkthroughs point users to balena.io/etcher specifically — and its three-panel "Flash from file, Select target, Flash!" layout is deliberately hard to get wrong. Any of the three produces an identical result because all they do is decompress the gzip on the fly and write raw sectors. The tool does not matter; the target selection does.
Why you never gunzip first
New users routinely right-click the .img.gz, extract it to an 8 GB .img, and then look for a way to "install" that. Do not. The compression exists so you download 3 GB instead of 8, and every recommended flasher reads it compressed. Unzipping first wastes disk, wastes time, and — because a bare .img looks like something you could drag onto a drive — actively tempts people into the file-copy mistake that produces a non-booting stick. The Batocera wiki is explicit that the archive does not need to be unzipped before flashing. Leave it as .img.gz and let the tool do its job.
First Boot & Installing to Disk
You now have a flashed stick. What happens next depends on whether you want Batocera to live on that removable media or to move onto an internal disk — and the second option carries the same irreversible-erase warning as flashing did.
Run-from-USB vs install-to-disk
Batocera is fully usable straight from the USB stick or SD card you just flashed — this is the intended way to try it, and for a lot of people it is the permanent setup. Move the media to your target machine, power on, and enter the firmware boot menu (commonly F12, F11, F8, ESC, or DEL depending on the vendor). Set the Batocera media as the boot device, and if the machine has Secure Boot enabled, disable it — Batocera is not signed for it. On first boot, Batocera automatically expands its data partition (the SHARE partition, mounted as /userdata) to fill the drive, so a 32 GB stick becomes a 32 GB Batocera rather than staying an 8 GB one. Let that finish; it is quick, but interrupting it leaves your storage stunted.
SYSTEM SETTINGS then INSTALL BATOCERA ON A NEW DISK
If you would rather run from an internal SSD or hard drive — faster load times, more room, no dangling stick — Batocera includes an in-system installer. From the main menu, open START then SYSTEM SETTINGS then INSTALL BATOCERA ON A NEW DISK. Choose the target disk, and critically, choose the same architecture you originally downloaded — the installer asks, and picking a mismatched architecture produces a system that will not boot. Batocera can install to a USB drive, SD card, hard drive, or SSD, including external SSDs connected through a SATA/M.2-to-USB cable, which is a genuinely convenient way to prep a drive on one machine and move it to another. The official install documentation covers the disk-target options in detail.
The irreversible-wipe warning
This bears repeating because it is the most expensive mistake in the entire guide: the in-system installer overwrites the selected disk in its entirety, irreversibly. It does not resize your Windows partition or dual-boot politely alongside your existing OS. If you select the disk that holds your other operating system or your files, they are gone. The Batocera documentation warns about this explicitly, and it is not boilerplate — verify the target disk by its size and model before you confirm. When in doubt, pull every drive from the machine except the one you intend to install to. There is no recovery step in this tutorial for "I installed over my main drive," because there isn't one.
Moving ROMs & BIOS Files
A freshly installed Batocera is an empty jukebox: the software is there, the games are not. Systems only appear in the menu once their folders contain recognized content, so this step is what turns a booting menu into a usable library.
The network share
The cleanest way to load content is over the network. Batocera exposes its /userdata tree as an SMB share the moment it is on your LAN. From Windows or macOS, browse to \\BATOCERA\share; from Linux, use smb://BATOCERA.local/share; and if hostname resolution is being difficult, address it by IP with \\192.168.1.X\share. Inside you will find the folders that matter: roms/, bios/, saves/, and system/. Drop games into roms/[shortname] — where the shortname is the system's folder, like snes, nes, or psx — and place BIOS files into bios/. The layout looks like this:
/userdata
├── bios/
│ └── dc/dc_boot.bin # Dreamcast BIOS, since v42
├── roms/
│ ├── snes/
│ │ ├── _info.txt # lists accepted formats for THIS system
│ │ └── SuperMarioWorld.sfc
│ ├── nes/
│ └── psx/
├── saves/
└── system/
└── batocera.conf # your main config fileThe F1 file manager and USB transfer
If you would rather not touch the network, Batocera has a built-in file manager. Press F1 on a connected keyboard from the main menu to open it, then copy ROMs and BIOS files from an external USB drive straight into the /userdata tree. This is the workflow the project expects for offline transfers, and it is how most people move a large, pre-organized collection onto a fresh install without waiting on Wi-Fi. Whether your ROMs come from a handheld's bundled set, a personal archive, or from dumping your own cartridges to ROM files — the legally cleanest source, and a project in its own right — they all land in the same roms/[system] folders.
_info.txt, shortnames, and the bios folder
Two things trip people up here. First, every system folder under roms/ contains an _info.txt that lists exactly which file formats and extensions that emulator accepts — read it before assuming a ROM "doesn't work," because the fix is often just the wrong container. Second, BIOS files are unforgiving about names and checksums: a PlayStation or Dreamcast BIOS must be the exact file the emulator expects, in the exact location. The Batocera add games and BIOS guide and the libretro BIOS reference are the two documents to keep open while you do this — they list the required filenames and hashes per system. Note also that v43 changed some emulator paths: DS games moved from the removed DraStic to melonDS (and DraStic saves do not transfer), and 3DS ROMs must now be decrypted, with hardware shaders off by default. If a system that worked in v42 is silent in v43, an emulator change is the usual reason.
Updating: GUI, SSH & the Mirror
Once Batocera is installed, you never download a fresh image to move between releases again. The system updates itself in place, and there are three ways to do it depending on how much control you want.
The in-menu updater
The path of least resistance is built into EmulationStation. Open MAIN MENU then UPDATES & DOWNLOADS then START UPDATE, and Batocera checks the release channel, downloads only what changed, and reboots into the new build. This is the correct tool for going from 43.0 to 43.1, or from 43.1 to whatever ships next. Two prerequisites: your storage must be at least 16 GB (below that, auto-update is disabled, which is the single best reason not to cheap out on a tiny stick), and you need a working network connection. The channel — stable or beta — is set by the updates.type key in your config, which we will get to.
batocera-upgrade over SSH
For anyone comfortable at a command line — or running a headless box — the same job is done over SSH. Batocera's default credentials are user root, password linux. The wiki notes that for version 5.23 and higher, upgrading (or downgrading) via batocera-upgrade over SSH is the preferred method, because it is URL-driven and lets you target a specific channel or an archived release directly. A full session looks like this:
$ ssh root@192.168.1.50
root@192.168.1.50's password: linux
[root@BATOCERA]# cat /boot/boot/batocera.board
x86_64
[root@BATOCERA]# batocera-upgrade https://mirrors.o2switch.fr/batocera/x86_64/stable/last
>>> Downloading boot files...
>>> Verifying...
>>> Update staged. Reboot to apply.
[root@BATOCERA]# rebootThe reboot at the end is what actually applies the staged update. If you ever need to roll back, the same command pointed at an archived path — for example the architecture's /stable/last/archives/ directory — lets you install an older build the same way.
The o2switch mirror URL (and the missing slash)
Here is a trap that circulates in copied-and-pasted tutorials and quietly 404s for everyone who follows them. The correct mirror base is https://mirrors.o2switch.fr/batocera/, and the x86_64 stable example command is:
batocera-upgrade https://mirrors.o2switch.fr/batocera/x86_64/stable/lastNote the /batocera/ path segment. A widely-repeated version of this command drops it — writing mirrors.o2switch.fr/x86_64/stable/last — which points at nothing and fails. If batocera-upgrade returns a not-found error, check that segment first; nine times out of ten the URL lost its /batocera/ in transit. Swap x86_64 for your own architecture code (the string batocera.board printed earlier) to target a Pi or handheld. The full procedure, including manual boot-file upgrades via boot.tar.xz for edge cases, is documented in the manual upgrade guide.
Five Pitfalls That Eat Beginners
These are the failures that generate the most forum threads, ranked roughly by how much time they cost. None are hard to avoid once you know they exist; all are easy to walk straight into.
Flashing and boot pitfalls
- Copying the .img.gz onto the drive instead of flashing it. Dragging the file onto a stick in your file manager produces a drive with a file on it, not a bootable Batocera. Fix: use Raspberry Pi Imager, USBImager, or Balena Etcher and select the image as a custom OS — these write raw sectors, a copy does not.
- The PC boots its old OS and Batocera never appears. The firmware is still booting the internal drive. Fix: enter the boot menu (F12/F11/ESC/DEL), select the Batocera media, and disable Secure Boot — Batocera is unsigned and Secure Boot will block it.
The disk-wipe pitfall
- Selecting the wrong destination — in the flasher or the installer. Both the flasher and the in-system "Install Batocera on a new disk" overwrite the entire selected disk with no undo. Fix: identify the target by its size and model, back it up first, and when installing internally, physically disconnect every other drive if you have any doubt. This is the only pitfall on the list that destroys data you can't get back.
Content and upgrade pitfalls
- Empty menu / "no systems" after a clean install. This is expected — Batocera ships with zero games, and a system only shows once its folder holds a recognized ROM. Fix: add ROMs to roms/[system]; if systems genuinely vanish or collections disappear, that was a 43.0 EmulationStation bug fixed in 43.1, so update.
- Games that worked in v42 are silent in v43. The v43 release changed emulators: DraStic was removed (DS now runs on melonDS, and DraStic saves do not carry over), and 3DS ROMs must be decrypted with hardware shaders off. Fix: re-add affected ROMs in the new emulator's expected format and back up old saves before upgrading a v42 machine. For finer control over which core runs each system, the libretro cores available in Batocera can be pinned per-system in the config.
Troubleshooting Table
A quick-reference matrix for the symptoms that show up most often, from flash to first game. Match the symptom, apply the fix, and if it involves a bug listed as fixed, the underlying answer is almost always "update to 43.1."
Boot and flash failures
The first cluster is everything between a downloaded file and a working menu — the flasher, the firmware, and the GPU. These are the failures that look scariest and are usually the most mechanical to fix.
Emulation and controller issues
The second cluster is post-boot: empty menus, silent systems, controllers behaving strangely, and network shares that won't appear. Several of these are named 43.0 regressions with a one-word fix.
The table
| Symptom | Likely cause | Fix |
|---|---|---|
| Imaging tool won't open the .img.gz | Tool too old or expects a bare .img | Use Raspberry Pi Imager 1.8+, USBImager, or Balena Etcher 1.18+ — all read gzip. Do not unzip. |
| PC boots its old OS, not Batocera | Boot order or Secure Boot | Enter the firmware boot menu (F12/DEL), disable Secure Boot, set the Batocera media first. |
| Black screen after the splash on a PC | GPU/driver mismatch, usually Nvidia | Prefer AMD/Intel graphics on the v43 Wayland stack; Nvidia is experimental — try a driver boot option or another machine. |
| Menu shows "no systems / no games" | Empty roms folders (expected) or 43.0 ES bug | Add ROMs to roms/[system]; if systems vanish outright, update to 43.1 (fixed there). |
| Only ~3 GB usable on a big drive | First-boot expansion interrupted | Reboot and let the SHARE/userdata partition finish auto-expanding; needs 16 GB+ media. |
| Update greyed out or fails | Storage under 16 GB, or no free space | Use 16 GB+ (32 GB rec) media, or update over SSH with batocera-upgrade. |
| batocera-upgrade returns "not found" | Mirror URL missing the /batocera/ segment | Use https://mirrors.o2switch.fr/batocera/x86_64/stable/last — note /batocera/. |
| DS games gone after a v42 to v43 upgrade | DraStic removed; DS moved to melonDS | Re-add DS ROMs; DraStic saves do not transfer, so back them up first. |
| 3DS games won't launch | v43 requires decrypted ROMs | Decrypt the .3ds/.cia; leave hardware shaders at the default (off). |
| Controller behaves like a keyboard | 43.0 bug with some Microsoft controllers | Update to 43.1, which fixed MS controllers being detected as keyboards. |
| Dolphin options missing or broken | 43.0 LR-Dolphin regression | Update to 43.1, which restored LR-Dolphin options. |
| Can't reach \\BATOCERA on the network | SMB hostname resolution | Address it by IP (\\192.168.1.X\share) or use smb://BATOCERA.local/share; confirm networking is enabled. |
Advanced Tips & a Complete Config
Once the basics work, most of Batocera's power lives in a single text file. The GUI is a friendly front-end for it, but editing it directly is faster and — for headless or repeatable setups — the only sane way.
SSH, headless, and autoconfig
Batocera runs an SSH server by default (root/linux), documented in the wiki's SSH access guide, which means you can administer a fanless box that lives behind the TV with no keyboard attached. Over SSH you can trigger updates, inspect /userdata, tail logs, and edit configuration — everything this guide has covered from the couch. For a truly hands-off first boot, you can pre-stage settings so the machine joins Wi-Fi and applies your preferences before you ever plug in a controller, which is the autoconfig trick below.
Editing batocera.conf on the boot partition
The master configuration file is /userdata/system/batocera.conf. It is a plain key=value file, and its full syntax is documented in the batocera.conf syntax reference. The clever part: immediately after flashing — before the first boot — the boot partition is a FAT volume readable on Windows, macOS, and Linux, so you can drop in a pre-written config and have Batocera come up already on your network. One security note worth knowing: when you set wifi.key in plaintext, Batocera encrypts it in place on the next reboot, rewriting the value as enc:xxxx so your password is not sitting in cleartext forever. Special characters in the key need to be escaped with a backslash.
The complete working batocera.conf
Here is an annotated, working configuration using only keys verified against the wiki. Treat the per-system block at the bottom as a template — swap in your own systems and the core names Batocera lists in its per-emulator menu. This is a sane starting point for a networked, controller-friendly, auto-updating install:
## /userdata/system/batocera.conf — annotated working example
## Full syntax: https://wiki.batocera.org/batocera_conf_syntax
## --- Identity & locale ---
system.hostname=BATOCERA
system.language=en_US
system.timezone=America/New_York
## --- Networking (Wi-Fi) ---
wifi.enabled=1
wifi.ssid=YourNetworkName
wifi.key=YourWifiPassword ## rewritten as enc:xxxx after first reboot
## --- Update channel ---
updates.type=stable ## stable | beta
## --- Audio ---
audio.volume=90
## --- Global emulator defaults (apply to every system) ---
global.smooth=1 ## bilinear smoothing on
global.rewind=0 ## rewind buffer off (saves CPU/RAM)
global.integerscale=0
global.shaderset=none ## e.g. scanlines, retro, none
global.bezel=none
global.retroachievements=0
global.retroachievements.username=
## --- Controllers ---
controllers.bluetooth.enabled=1
## --- Per-system overrides (shortname = the roms/ folder name) ---
## Pattern: .core and .emulator
snes.core=snes9x
snes.emulator=libretro
n64.core=parallel_n64
n64.emulator=libretro
psx.core=swanstation
psx.emulator=libretro Save that as /userdata/system/batocera.conf, reboot, and the machine comes up on your network, with Bluetooth controllers enabled, on the stable channel, with sensible emulator defaults and three systems pinned to specific cores. From here, everything else is adding games and tuning per-system settings — and none of it ever requires downloading a fresh image again. That is the entire point of the update path: you download Batocera exactly once, and after that the 3 GB file has done its job.
Questions the search bar asks me
- Is the Batocera download free?
- Yes — Batocera is 100% free and open-source, licensed CC-BY-NC-SA, with no paid tier and no upsell. The only official source is batocera.org/download, and the code lives at github.com/batocera-linux/batocera.linux. Any site charging money or gating the file behind a survey is a scam using Batocera's name.
- Do I need to unzip the .img.gz before flashing?
- No. Raspberry Pi Imager, USBImager, and Balena Etcher all read the gzip-compressed .img.gz directly, and the Batocera wiki explicitly says not to unzip it. The download is roughly 3 GB compressed and expands to about 8 GB when written — unzipping first just wastes ~5 GB and a step.
- Which Batocera image do I download for a PC?
- For nearly all desktops, laptops and mini PCs, download the x86_64 image — in the 43.1 cycle that was batocera-x86_64-43.1-20260529.img.gz. Raspberry Pis use board-specific images instead (bcm2712 for the Pi 5, bcm2711 for the Pi 4). If a machine already runs Batocera, 'cat /boot/boot/batocera.board' prints its exact architecture.
- How do I update Batocera without reflashing?
- Use MAIN MENU → UPDATES & DOWNLOADS → START UPDATE in the menu, or SSH in (root/linux) and run batocera-upgrade against the mirror. The correct x86_64 URL is https://mirrors.o2switch.fr/batocera/x86_64/stable/last — note the /batocera/ segment, which copied tutorials frequently drop, causing a 404. Updates need 16 GB+ storage.
- Will installing Batocera erase my drive?
- The in-system installer (SYSTEM SETTINGS → INSTALL BATOCERA ON A NEW DISK) overwrites the entire selected disk irreversibly — it does not dual-boot or resize partitions. Running Batocera from the flashed USB stick does not touch your internal drive. Verify the target disk by size and model before confirming, and disconnect other drives if unsure.
Ben covers the hardware end of retro gaming: FPGA cores, real-cartridge dumping, capture setups, CRT vs scaler workflows, and the legal and physical preservation infrastructure that keeps old games playable. Every post under this byline is reviewed pre-publish by Sam P., Editor & Operator — corrections to info@instalinkoteam.com. Published 2026-07-22 · Last updated 2026-07-22. Full bios on the author page.