Batocera 43 Download 2026: 14 Steps to USB, 40 Min

There is a particular flavor of optimism that says you can take the dead office Dell under your desk, write a single file to a USB stick, and walk away forty minutes later with a console that plays everything from Pong to Gran Turismo 4. For once, the optimism is mostly justified. Batocera is the Linux distribution that makes it true, and unlike most projects that promise to resurrect old hardware, it actually boots, the first time, on a stunning range of junk.

This is a download-and-install tutorial, not a brochure. By the end you will have fetched the correct image for your specific board, confirmed it is not a corrupt 2.5 GB lie, written it to a stick, booted it, and put your first ROMs and BIOS files in the folders Batocera expects. Note the word your. Batocera ships exactly zero games and exactly zero copyrighted firmware, and it is refreshingly honest about that. The current release is version 43, codenamed Glasswing, which landed on May 8, 2026. We will use it. We will also be candid about where it breaks, because the comment sections of every tutorial on Earth are full of people who skipped the boring parts.

What Batocera Actually Is

Before you download anything, understand what you are downloading. People install Batocera, hit a wall, and blame the project for behaving exactly as documented. A few paragraphs of theory will save you an evening.

A read-only Linux that boots straight into games

Batocera is a self-contained, immutable Linux distribution built for a single purpose: front-loading an emulation stack and then getting out of the way. It uses EmulationStation as its frontend — the scrolling, box-art carousel you have seen in a thousand YouTube thumbnails — and underneath it sits the entire libretro and RetroArch ecosystem plus a pile of standalone emulators for the systems RetroArch handles poorly. You do not install Batocera onto an existing operating system. It is the operating system. It takes the whole disk, or the whole USB stick, and it boots into games with no desktop, no login screen, and no telemetry asking how your day went.

The architecture detail that trips up newcomers: the system itself is read-only. The boot image contains a compressed, signed root filesystem that Batocera never writes to during normal use. Everything you change — ROMs, saves, screenshots, controller mappings, the main configuration file — lives on a separate writable partition mounted at /userdata, which the network exposes as a share folder. This is why upgrades are painless and why a yanked power cable rarely corrupts anything: the part that matters is mounted read-only, and the part you touch is isolated. It is also why editing the wrong file accomplishes nothing. Remember that; it returns in the troubleshooting table.

What "Glasswing" (version 43) actually changed

Version 43 shipped on May 8, 2026 and is an emulator-refresh release more than a frontend overhaul. The headline updates: Amiberry — the Amiga emulator — was bumped to the March 5, 2026 build, and Cemu, the Wii U emulator, to the April 5, 2026 build. The Nintendo 3DS path moved to Azahar 2125.0.1, and Atari Jaguar support advanced to BigPEmu v121. None of that changes how you download or flash the image; it changes whether your specific games run well once you are inside. If you are coming from an older release, you do not need a different procedure — the steps below are version-agnostic — but you do want the current image so you inherit those emulator builds rather than chasing them later. If you want the granular point-release history, we logged the 43.1 download notes separately.

Free as in price, and free as in source

Batocera costs nothing. There is no license fee, no subscription, no "pro" tier that unlocks the systems you actually wanted, and version 43 continues that mission without an asterisk. It is also genuinely open source: the entire build system and every recipe lives on GitHub at batocera-linux/batocera.linux, which means you can read precisely how the image is assembled, file bugs against real maintainers, and — if you are the kind of person who does this — compile your own. The practical upshot for a downloader is trust: you are not pulling a mystery binary off a file-locker. You are pulling a reproducible artifact whose source you can audit. That matters when the thing is about to take over an entire disk.

Prerequisites You Can't Skip

Half of all "Batocera doesn't work" complaints are prerequisite failures wearing a costume. Get these right and the install is boring, which is the goal.

Hardware requirements

For the PC build — the x86_64 image — you need a 64-bit Intel or AMD machine. That is essentially anything made in the last fifteen years, including the Beelink Mini S12 and similar mini PCs that a 2026 mini-PC tutorial demonstrated running Batocera without a gaming rig in sight. A blunt capability ladder:

• 8-bit and 16-bit (NES, SNES, Genesis, Game Boy): any 64-bit CPU, 2 GB RAM, integrated graphics. A potato runs these.
• PlayStation 1, N64, Dreamcast: a dual-core from the last decade and 2–4 GB RAM.
• PlayStation 2, GameCube, Wii (PCSX2, Dolphin): a real quad-core, 4 GB+ RAM, and an actual GPU with Vulkan or solid OpenGL. A 2010 netbook will boot Batocera and then humiliate you at 9 FPS.

On the storage side, the single hard number you must respect comes from the image itself. The compressed download is roughly 2.5 GB, and after decompression it expands to about 8 GB. Your target USB flash drive or SSD must therefore be at least 8 GB, and in practice you want 16 GB or more so the userdata partition has room for ROMs, saves, and box art. Use a name-brand stick. Counterfeit "128 GB" drives that are physically 8 GB are a real and common failure that surfaces as a flash that succeeds and a boot that corrupts.

Software requirements and versions

You need exactly two downloads and one optional verification tool:

• The Batocera 43 image for your board, from batocera.org/download. Nowhere else. Mirrors on random forums are how you acquire someone else's idea of a good time.
• balenaEtcher, the flashing utility, from balena.io/etcher. On Windows the installer is named balenaEtcher-Setup-1.x.x.exe and it is free. Etcher runs on Windows, macOS, and Linux, and it is the recommended route because it validates the write automatically.
• Optionally, a SHA-256 tool. Windows 10/11 has CertUtil built in; macOS and Linux have shasum / sha256sum. You already own this.

Do not substitute Rufus, UNetbootin, or the Windows "format and copy the file" ritual. Batocera is a raw disk image, not an ISO you drag onto a stick. It must be written block-for-block. Etcher (or dd) does that; a file copy does not, and the result will not boot.

The BIOS and ROM question, answered honestly

This is the part most tutorials mumble through. Batocera includes no game ROMs and no console BIOS files, because both are copyrighted. A BIOS image is the console manufacturer's firmware; a ROM is a publisher's game. The legally defensible position is supplying files you dumped from cartridges and discs you physically own. "Abandonware" is a community sentiment, not a legal category, and a downloaded ROM set is copyright infringement regardless of whether the original is still sold. The Machine is not your lawyer, but the Machine can read a statute. Batocera ships clean specifically so the project stays on the right side of that line; what you put in the folders afterward is your jurisdiction, your risk. Plan to supply your own BIOS — many systems (PS1, PS2, Sega CD, Neo Geo) will not boot a single game without the correct one, and Batocera's built-in Missing BIOS Check will tell you precisely which files it wants.

Choosing the Right Image

The download page is not a single button. It is a menu, and picking the wrong entry is the single most common way people waste a download.

x86_64 for PCs, mini PCs, and laptops

If you are installing onto a desktop, a laptop, a NUC, or a mini PC like the Beelink S12, you want the x86_64 (also written x86-64 or PC) image. There is also an older 32-bit x86 build for genuinely ancient machines; ignore it unless your CPU predates 64-bit, which for anything you would actually want to game on, it does not. The x86_64 image is the one this tutorial assumes, and it is the most capable: it carries the full standalone-emulator roster, including the PCSX2 and Dolphin builds you need for sixth-generation consoles.

Raspberry Pi, Odroid, and handhelds

The same download page serves images for Raspberry Pi boards, Odroid devices, and a growing list of ARM handhelds. These are not interchangeable with the PC image or with each other — a Raspberry Pi 4 image will not boot a Pi 5, and neither will boot a PC. ARM builds are leaner and, on the smaller boards, top out around the PS1/Dreamcast tier. If your goal is PS2-class emulation in your hands rather than under your TV, a dedicated handheld is the saner buy; we walk through one in the Retroid Pocket 6 review, and it will outrun a Pi for that workload. Match the image to the silicon. The page labels each clearly; read the label.

Reading the filename convention

Batocera's image names are self-documenting once you know the grammar. The PC image for version 38, released October 14, 2023, was named:

batocera-x86_64-x86_64-38-20231014.img.gz
        \______/ \____/ \/ \______/ \___/
        platform  arch  ver  date   gzip

Decoded: batocera (the project), x86_64 (the platform family), x86_64 (the architecture), 38 (the version), 20231014 (the build date, YYYYMMDD), and .img.gz (a raw disk image, gzip-compressed). The version 43 file you download in 2026 follows the identical pattern with 43 and a 2026 build date in those slots. Knowing this grammar means you can glance at a filename and confirm you grabbed the right version, the right architecture, and a complete .img.gz rather than a half-downloaded fragment. If you want the long-form walkthrough on an earlier release for comparison, the version 38 download guide covers the same ground with the older image.

The 14-Step Install

Here is the whole procedure, start to finish, with the reasoning attached to each step so you understand why, not just what. Budget about forty minutes the first time, most of which is the download and the flash running unattended.

1. Open the official download page. Go to batocera.org/download in a browser. Rationale: this is the only source that guarantees an unmodified image and a matching checksum. Every third-party mirror is an unaudited variable.
2. Select your architecture. Choose the x86_64 / PC entry (or your specific Pi/Odroid/handheld). Rationale: the wrong architecture produces a file that flashes perfectly and boots to nothing, costing you a full download and a full flash to discover.
3. Download the .img.gz and its checksum. Grab the image and, if offered, the SHA-256 file beside it. Rationale: the checksum is the only way to prove the ~2.5 GB you received equals the ~2.5 GB they sent. Skipping it is how silent corruption becomes a two-hour debugging session.
4. Verify the checksum. Run the SHA-256 comparison (commands below). Rationale: a single flipped bit in a disk image can pass the flash and fail the boot. Thirty seconds here saves an evening.
5. Decide whether to decompress. Etcher can flash a .img.gz directly. If you use dd instead, decompress first with gunzip. Rationale: 2.5 GB compressed becomes about 8 GB extracted; dd needs the raw .img, Etcher does not.
6. Install and launch balenaEtcher. Download from balena.io/etcher, run balenaEtcher-Setup-1.x.x.exe (or the Mac/Linux equivalent), and open it. Rationale: Etcher validates the write after flashing, catching bad sticks before you waste a boot attempt.
7. Insert the target USB drive or SSD. Use a drive of at least 8 GB; 16 GB+ preferred. Rationale: the image expands to ~8 GB, and anything smaller cannot hold it, never mind your future ROMs.
8. In Etcher, choose "Flash from file" and select the Batocera image (the .img.gz or extracted .img). Rationale: selecting the wrong file — say, the Etcher installer — is a real mistake people make at 1 a.m.
9. Select the correct target drive. Confirm the size and label match your USB stick, not your system disk. Rationale: Etcher hides system drives by default, but verify anyway. Flashing the wrong disk erases an operating system.
10. Click Flash and wait. Etcher writes, then verifies, then ejects. Rationale: the verify pass is the whole point of using Etcher; let it finish rather than yanking the stick at "100%."
11. Boot the target machine from the USB drive. Insert the stick into the machine that will run Batocera, power on, and invoke the boot menu (commonly F12, F10, F9, or Esc — it varies by vendor). Select the USB device. Rationale: if the machine boots its own OS instead, the boot order or Secure Boot is the culprit; fix it in UEFI before blaming Batocera.
12. Let the first boot complete. Batocera expands its userdata partition and lands on the EmulationStation carousel. Rationale: the first boot does one-time setup; interrupting it is how you get a half-initialized userdata partition.
13. Add your ROMs and BIOS. Press F1 to open the built-in file manager, or copy over the network share, and place files under /userdata/roms/<system> and /userdata/bios. Rationale: Batocera only scans those exact paths. Files anywhere else are invisible. (Folder map is in the next section.)
14. Run the Missing BIOS Check and configure your controller. Open Game Settings > Missing BIOS Check, supply whatever it flags, then plug in a gamepad — Xbox, PlayStation, and generic USB pads are recognized out of the box. Rationale: systems like PS1 and PS2 refuse to launch without their BIOS, and confirming controller mapping now beats discovering a dead stick mid-game.

Verify and decompress (Linux / macOS)

Run these from wherever your browser dropped the file. The sha256sum -c line assumes the project's checksum file sits beside the image.

# Move into the download directory
cd ~/Downloads

# Confirm the file isn't a truncated 0-byte lie
ls -lh batocera-x86_64-x86_64-43-2026*.img.gz

# Verify the published SHA-256 checksum
sha256sum -c batocera-x86_64-x86_64-43-2026*.img.gz.sha256

# Decompress only if you plan to use dd (~2.5 GB in, ~8 GB out)
gunzip -k batocera-x86_64-x86_64-43-2026*.img.gz

Flashing with dd (the Linux power-user route)

Etcher is the recommended path. If you prefer dd, it is faster and entirely unforgiving — there is no "are you sure," only consequences. Identify the disk twice before you write.

# List disks. Identify the USB stick by SIZE and MODEL, not by guessing.
lsblk -dpo NAME,SIZE,MODEL

# Unmount any auto-mounted partitions on the stick (example device: /dev/sdb)
sudo umount /dev/sdb*

# Write the raw image block-for-block. Wrong 'of=' erases the wrong drive.
sudo dd if=batocera-x86_64-x86_64-43-2026.img of=/dev/sdb bs=4M conv=fsync status=progress

# Flush write buffers so "done" actually means done
sync

Expected Output

You should know what success looks like so you can recognize failure early. Here is what each stage prints when it is working.

A clean checksum and a clean flash

The verification step, when the download is intact, says exactly one thing:

batocera-x86_64-x86_64-43-2026.img.gz: OK

If it says FAILED, stop. Re-download. Do not flash a corrupt image and then spend an evening debugging a problem that does not exist on disk. A successful dd run, meanwhile, ends with matched record counts and a byte total near 8.0 GiB:

2048+0 records in
2048+0 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 561 s, 15.3 MB/s

The first-boot console and the EmulationStation carousel

On first power-on, Batocera flashes a brief boot log, resizes userdata, and lands on the EmulationStation theme. You will see only the systems for which you have placed at least one ROM — an empty Batocera shows a near-empty carousel, which is correct, not broken. Controllers announce themselves; plug in an Xbox or PlayStation pad and Batocera maps it without a single menu visit, then prompts you to confirm. If you want to understand what is running underneath each of those system entries, our breakdown of the RetroArch core library maps the libretro cores Batocera bundles to the systems they power.

The share folder layout

Once booted, your writable storage — reachable via the F1 file manager or over the network as \\BATOCERA\share — looks like this. Commit it to memory, because every "my games don't show up" problem is a violation of it:

/userdata
├── bios/                <- BIOS and firmware files go here
├── roms/
│   ├── snes/            <- one folder per system, exact short names
│   ├── psx/
│   ├── ps2/
│   ├── megadrive/
│   └── ...
├── saves/              <- in-game and save states
├── screenshots/
├── system/
│   └── batocera.conf   <- the master config file
└── music/

Common Pitfalls and Fixes

These are the failures that fill forum threads. None is exotic; all are avoidable.

Download and flashing mistakes

Pitfall 1 — skipping the checksum. A download that drops a few bytes flashes happily and boots to a black screen or a kernel panic. Fix: always run the SHA-256 verification in Step 4. If it fails, re-download from the official page; do not flash.

Pitfall 2 — copying the image instead of flashing it. Formatting a stick and dragging the .img onto it produces a stick with a file on it, not a bootable disk. Fix: use Etcher's "Flash from file" or dd. Block-for-block writing is mandatory.

Pitfall 3 — the counterfeit USB drive. A fake-capacity stick flashes "successfully" and then corrupts on first write past its real size. Fix: buy name-brand storage; if a cheap high-capacity drive misbehaves, test its true size with f3 or h2testw before trusting it.

Boot and BIOS mistakes

Pitfall 4 — Secure Boot left enabled. Many machines refuse to boot the USB while Secure Boot is on, silently falling through to the internal OS. Fix: enter UEFI setup, disable Secure Boot, and set the USB device first in the boot order (or use the one-time boot menu).

Pitfall 5 — wrong-named or wrong-region BIOS. Batocera matches BIOS files by exact filename and often by hash. SCPH1001.BIN in uppercase when it wants scph1001.bin, or a European BIOS for a US game, both read as "missing." Fix: run Game Settings > Missing BIOS Check, which lists the precise names it expects, and match them exactly into /userdata/bios. The official Batocera wiki documents the per-system requirements.

Storage and persistence mistakes

Pitfall 6 — putting ROMs on the read-only system partition. The boot partition is immutable; nothing you place there survives or is scanned. Fix: everything you add goes under /userdata — ROMs in /userdata/roms/<system>, BIOS in /userdata/bios. If changes vanish after a reboot, you edited the wrong partition.

Troubleshooting Table

Symptom on the left, the actual cause in the middle, the fix on the right. This table resolves the overwhelming majority of first-install problems.

Advanced Tips

Once the thing boots, these are the moves that separate a working install from a good one.

Network copy, SSH, and the F1 file manager

Copying ROMs by physically shuttling a second USB stick is the slow path. Batocera runs an SMB share and an SSH server, both toggleable from the config. Over the network you can drop entire ROM sets straight into the right folders, and over SSH you can do real maintenance. The default credentials are root / linux — change them if this box lives on an untrusted network.

# SSH in from another machine on the LAN (default password: linux)
ssh root@batocera.local

# Copy a whole SNES set over the network into the correct folder
scp -r ~/snes-romset/ root@batocera.local:/userdata/roms/snes/

# Mount the share directly instead of clicking through EmulationStation
# Linux:
sudo mount -t cifs //batocera.local/share /mnt/bato -o guest,vers=3.0
# Windows (paste into File Explorer's address bar):
#   \\BATOCERA\share

For quick, on-device file moves — say, pulling a BIOS off a plugged-in USB drive — press F1 at the EmulationStation carousel to open the built-in file manager. It is a full graphical file browser, and it is the fastest way to relocate a handful of files without leaving the couch.

Shaders, bezels, and integer scaling

Default Batocera is functional but visually plain. The interesting settings live in batocera.conf and in the per-game menu. Integer scaling (integerscale=1) keeps pixels square instead of smeared; a scanline or CRT shader (shaderset=scanlines) makes 240p content look the way it did on a Trinitron rather than the way it looks on a clinical 4K panel; bezels frame the non-16:9 systems so you are not staring at black voids. These are taste decisions, set globally and overridden per system. The libretro documentation covers the underlying shader pipeline if you want to go deep rather than pick from presets.

Updating without reinstalling, and reading the release notes

You rarely need to reflash to upgrade. Batocera updates in place from the Updates & Downloads menu, preserving your userdata partition — your ROMs, saves, and config survive the version bump. Before any major upgrade, skim the project's release history wiki, which documents what each version changed and, occasionally, what it broke. Version 43's emulator bumps — Amiberry, Cemu, Azahar, BigPEmu — are exactly the kind of detail that determines whether an in-place update helps or hurts your particular library.

A Complete Configuration

Here is a working batocera.conf you can adapt — a sane global baseline with a couple of per-system overrides to show the syntax. It lives at /userdata/system/batocera.conf.

The batocera.conf baseline

# /userdata/system/batocera.conf
# ----------------------------------------------------------
# Global defaults; any line can be overridden per system.

## Language / region
system.language=en_US
system.kblayout=us

## Video
global.videomode=auto
global.bezel=thinbezel
global.smooth=1            # bilinear smoothing; set 0 for sharp pixels
global.shaderset=none      # try "scanlines" for CRT cosplay
global.integerscale=0
global.rewind=1            # RetroArch rewind buffer
global.ai_service_enabled=0

## Audio
audio.volume=90
audio.bgmusic=1

## Network shares + remote access
system.samba.enabled=1
system.ssh.enabled=1

## Bluetooth controllers
controllers.bluetooth.enabled=1

## Per-system override: keep PS2 on the standalone PCSX2
ps2.videomode=auto
ps2.emulator=pcsx2
ps2.core=pcsx2

## Per-system override: SNES with scanlines, integer scale, no rewind
snes.shaderset=scanlines
snes.integerscale=1
snes.rewind=0

A folder layout that just works

Pair that config with this discipline on the userdata partition. The short system names (snes, psx, ps2, megadrive, n64) are fixed by Batocera; do not invent your own.

/userdata/roms/snes/      *.sfc, *.smc, *.zip
/userdata/roms/psx/       *.chd, *.pbp, *.cue+*.bin
/userdata/roms/ps2/       *.iso, *.chd
/userdata/roms/megadrive/ *.md, *.bin, *.zip
/userdata/roms/n64/       *.z64, *.n64
/userdata/bios/           scph1001.bin, scph5501.bin, ps2 bios, etc.

What the Missing BIOS Check should print

After populating /userdata/bios, the Missing BIOS Check should look like this — every required file present, nothing flagged red:

System     BIOS file              Status
psx        scph1001.bin           PRESENT
psx        scph5501.bin           PRESENT
ps2        ps2 bios (per region)  PRESENT
segacd     bios_CD_U.bin          PRESENT
dreamcast  dc_boot.bin            PRESENT

If anything reads MISSING, that system will not run until you supply the named file. There is no workaround inside Batocera, because the workaround would be shipping someone else's copyrighted firmware, which the project will not do and you now understand why.

The Bottom Line

Batocera is the rare free thing that over-delivers. The download is honest, the install is forty unglamorous minutes, and the result is a console that asks nothing of you afterward.

Who should run Batocera on a PC

If you have a spare 64-bit machine — a retired desktop, a cheap mini PC, an old laptop with a working GPU — and a TV, Batocera on x86_64 is close to the optimal answer for living-room retro gaming. It scales from NES to PS2 depending on your silicon, it costs nothing, and version 43's current emulator builds mean you are not fighting last year's bugs. The forty minutes you spend doing it correctly — checksum included — buy you years of it simply working.

Who should buy hardware instead

If you want retro gaming in your hands rather than under your TV, a tuned handheld beats babysitting a Raspberry Pi image; the Retroid Pocket 6 handles the PS2-class load Batocera-on-Pi cannot. And if your interest is accuracy and zero input lag rather than breadth, FPGA is a different religion entirely — we covered it in the MiSTer Multisystem 2 piece. Batocera is the generalist; those are the specialists.

What to read next

Once you are booted, the next rabbit hole is the emulator layer underneath EmulationStation. Start with our guide to the RetroArch cores that power most of Batocera's systems, keep the release-history wiki bookmarked for upgrades, and remember the one rule that survives every version: the project ships the machine, you supply the games, and the folders do not move. Build accordingly.