Batocera 43 Download 2026: USB in 12 Steps, 40 Min

There is a specific genre of regret reserved for the person who grabs a 2.5 GB disk image, flashes it onto whatever USB stick was rattling around a drawer, boots it, and then spends an evening discovering that the stick is a counterfeit advertised as 64 GB while physically holding about four. The image writes. The boot logo appears. The thing even runs a game — right up until the controller hiccups, the filesystem panics, and the drive eats every save you made. This guide is written to keep you out of that drawer.

The subject is the Batocera download: where the file actually lives, which file you want, how to verify it, how to write it to media that will not betray you, and how to get from a blank drive to a working EmulationStation desktop without summoning the support forum. As of mid-2026 the current release is Batocera 43, published on 8 May 2026, and it is free in both senses of the word. We will do it in twelve numbered steps, plus the parts the quick-start guides quietly skip because admitting them would make the screenshots longer.

What You're Actually Downloading

Before you click anything, it helps to know exactly what is arriving on your disk, because half the mistakes people make with Batocera come from misunderstanding what kind of thing it is. It is not a game collection. It is not an app you install alongside Windows. It is a whole operating system that you boot instead of your normal one, and that framing changes how you treat every step that follows.

Version 43, in one paragraph

Batocera 43 is the current stable build, released 8 May 2026, and it is the release these instructions target. Under the hood it is a buildroot-based Linux distribution whose entire job is to boot straight into EmulationStation and hand you a controller-driven menu of systems. Version 43 refreshes the heavy standalone emulators that do the actual work: Cemu (the Wii U emulator, on its 5 April 2026 build), BigPEmu v121 (Rich Whitehouse's Atari Jaguar emulator), and Azahar 2125.0.1 (the Citra-descended Nintendo 3DS emulator that exists because Nintendo's lawyers exist). The Amiga side rides Amiberry on its 5 March 2026 build, and the release ships the Glasswing engine among a roster of more than thirty emulators and game engines out of the box. The PC image you want is named batocera-x86_64-x86_64-43-20260508.img.gz — the trailing digits are the build date, which is how you will later tell at a glance whether a mirror is handing you the real thing or last quarter's leftovers.

Free as in $0.00, and free as in GPL

The price is $0.00. Not a trial, not a freemium tier, not a "donate to unlock" arrangement — Batocera is a non-commercial, community-driven project, and the entire source tree lives in the open on GitHub. That matters for two reasons. First, you can read exactly what you are about to run on your hardware, which is more than most operating systems will let you do. Second, it draws the legal boundary cleanly: what you are downloading is software. It contains no games and no console BIOS files, because shipping those would be copyright infringement and the maintainers are not interested in a cease-and-desist letter. The OS is legal. What you do with it afterward is your jurisdiction's problem, and we will come back to that when we talk about BIOS.

Why a USB stick or SSD, and not your SD card

Batocera is designed to run live from external media. You write the image to a USB 3.x stick or an SSD, boot from it, and your existing operating system on the internal disk is never touched unless you explicitly choose to install. This is the feature that makes the download worth doing: it turns any spare x86_64 box into a console for the length of a boot, and turns it back into an ordinary PC the moment you pull the drive. The catch is bandwidth. A blue USB 3.x port moves data fast enough for most 8- and 16-bit systems; an SSD is what you will want the instant you ask the machine to run PlayStation 2 or Wii U. A black USB 2.0 port and a bargain-bin thumb drive will technically work, and will technically make you regret it.

Prerequisites: Hardware and Software

Batocera advertises itself as a zero-configuration OS that auto-detects most controllers and consoles without manual setup, and that is largely true once it is running. Getting it running, however, still demands that you bring the right hardware and a small set of host-side tools. Skimp here and no amount of zero-config cleverness downstream will save you.

Hardware minimums, and what actually matters

Batocera x86_64 runs on effectively any 64-bit PC built in the last fifteen years, but "runs" and "runs the system you care about" are different claims. The realistic floor for a pleasant 8/16-bit and PlayStation 1 experience is a dual-core x86_64 CPU, 4 GB of RAM, and any GPU that speaks OpenGL without complaint. Push into PlayStation 2, GameCube, Wii, 3DS, and Wii U and you want a quad-core CPU, 8 GB of RAM or more, and a discrete or modern integrated GPU with working Vulkan drivers. The single most common misjudgment is rating a machine by its age rather than its graphics drivers; a ten-year-old desktop with a sensible GPU will out-emulate a fanless mini-PC whose chip throttles after ninety seconds. If you are building around a small fanless box, it is worth reading our notes on undervolting the CPU before you blame the emulator for thermal stutter.

The target drive: the part everyone cheaps out on

You need a drive of at least 8 GB to hold the image, but treat that as the minimum for a coaster, not a plan. The image expands to roughly 8 GB on write, and Batocera grows its data partition to fill whatever is left, so an 8 GB drive leaves you no room for a single ROM. Sixteen gigabytes is the smallest number that is not a punchline; 256 GB or more is where a real library lives. Buy a known-good USB 3.x stick, or better, a small SSD in a USB enclosure. And before you trust any new flash drive with your save files, validate its real capacity — counterfeit drives that report a huge size while physically holding a fraction of it are the single most common cause of "Batocera corrupted my files," and no operating system on earth can rescue you from media that lies about how big it is.

Software on the host machine

On the computer you will use to write the image, you need exactly three things: a web browser, a checksum tool, and a flasher. For flashing, the project points you at Balena Etcher; the Windows installer arrives as balenaEtcher-Setup-1.xx.xx.exe and requires no file extraction before use. Etcher reads the .img.gz directly, decompresses it in flight, and re-reads the drive afterward to confirm the write — three reasons it beats dragging files around by hand. The checksum tool is already on your system: sha256sum on Linux and macOS, or Get-FileHash and certutil on Windows. You do not need an archive utility, and if you find yourself reaching for one, stop — extracting the .gz first is a pitfall, not a step. Grab Etcher from balena.io/etcher and nowhere else.

Choosing the Right Image File

The download page lists more than one file, and the gap between picking right and picking wrong is the gap between a working desktop and a black screen that gives you no explanation. Three decisions matter: architecture, compression, and source. Get all three correct and the rest of this article is mechanical.

x86_64 vs the single-board builds

Open batocera.org/download and the first decision is architecture. The generic 64-bit PC build is the one whose filename doubles the architecture string — batocera-x86_64-x86_64-43-20260508.img.gz — and it is what you want for any normal desktop, laptop, mini-PC, or x86 handheld. If your target is a Raspberry Pi, an Odroid, or another single-board computer, you must instead pick the image that names that board specifically; an image built for ARM will not boot an x86 machine and vice versa, and the failure mode is a blank screen with no error, which burns an hour before you think to question the file. Match the image to the silicon. When in genuine doubt, x86_64 is the safe answer, because it is the most widely tested build the project ships.

Why .img.gz, and why you do not unzip it

The PC image is distributed gzip-compressed at roughly 2.5 GB, and it expands to about 8 GB when written. The compression is not an obstacle to engineer around; it is a convenience your flasher already understands. Balena Etcher, Raspberry Pi Imager, and a one-line dd pipeline all read the .gz and decompress on the fly. Manually extracting it first costs you 8 GB of disk you did not need to spend and, worse, sets up the classic blunder of pointing the flasher at the wrong file in a folder that now holds two of them. Leave it compressed. Between download and flash, the only number you should care about is the checksum, which we verify in Step 4.

Mirrors, the Reddit link, and basic hygiene

The official server is the canonical source and occasionally slow, because free hosting under load behaves the way free hosting under load behaves. The project's wiki keeps a record of current and previous releases, which is the right place to confirm a version or grab an older one. A community mirror posted to the r/batocera subreddit has reportedly sustained around 40 MB/s, which is tempting when the main server is crawling. Use mirrors if you must, but observe the one rule that keeps mirrors safe: a mirror is only ever allowed to host the clean official image. The moment a download advertises "preloaded with games" or "BIOS included," you are looking at someone else's copyright liability and quite possibly someone else's malware. Pull the bare image, then verify its checksum against the value on the official page before it goes anywhere near your hardware. If you want to see how the same process looked across earlier builds, our longer 14-step Batocera 43 walkthrough covers the variations in more detail.

The Install: 12 Steps to Desktop

Twelve steps, three acts: download and verify, flash, then boot and configure. Each step states why, because a step you understand is a step you can repair when it misbehaves, and a step you merely copied is a step that leaves you helpless when it does not. Budget roughly forty minutes end to end, most of which is the machine working while you do not.

Steps 1-4: Download and Verify

1. Go to the official download page. Open batocera.org/download directly rather than trusting a search-result advertisement. The canonical source is the only one whose checksum you can trust without further homework, and the only one that will not quietly fold copyrighted content into the file and turn your retro hobby into a legal exposure.
2. Select your architecture. For a PC, choose the x86_64 build. The architecture must match your hardware exactly; the wrong choice produces a black screen with no diagnostic, and you will suspect everything except the file you picked.
3. Download batocera-x86_64-x86_64-43-20260508.img.gz. Expect about 2.5 GB. If the official server crawls, the release page or the community mirror are options — but whatever the source, the next step is non-negotiable.
4. Verify the checksum. A truncated or corrupted image is the number-one cause of boot failures that masquerade as hardware problems. Compute the SHA-256 of the file you received and compare it to the value published on the download page. If they differ by a single character, delete the file and download it again; do not flash it "just to see."

$ sha256sum batocera-x86_64-x86_64-43-20260508.img.gz
9f1c0a...c0de  batocera-x86_64-x86_64-43-20260508.img.gz
# Compare that hash against the value printed on batocera.org/download.

# Windows (PowerShell):
PS> Get-FileHash .\batocera-x86_64-x86_64-43-20260508.img.gz -Algorithm SHA256

Steps 5-8: Flash the Drive

5. Install Balena Etcher. Run balenaEtcher-Setup-1.xx.xx.exe (no extraction required) on Windows, or install it from balena.io/etcher on macOS and Linux. Etcher validates the write after it finishes, which is the entire difference between "it flashed" and "it flashed correctly."
6. Insert the target drive into a USB 3.x port. Use the blue port. USB 3.x bandwidth is the difference between snappy menus and a slideshow, and an SSD in an enclosure is the difference between PS2 running and PS2 sulking. Everything currently on this drive is about to be erased; move anything you care about first.
7. Flash from file. In Etcher choose Flash from file, select the .img.gz while it is still compressed, select your target device, and start. Read the device name and size twice before committing — Etcher tries hard to hide your system disk, but the only real safeguard is your own eyes on the SIZE column.
8. Wait for the write and validation to finish. Etcher writes about 8 GB and then re-reads it to verify. This takes a few minutes; do not pull the drive the instant the progress bar fills, because the validation pass that follows is the part that actually matters. Wait for "Flash Complete."

# Identify the target FIRST. Read the SIZE column. Wrong target = a wiped disk.
$ lsblk -o NAME,SIZE,MODEL,TRAN
NAME   SIZE MODEL                  TRAN
sda  476.9G Samsung SSD 870        sata
sdb   28.7G SanDisk Ultra USB 3.0  usb     [<-- the target]

# The manual equivalent of Etcher, straight from the .gz, no extraction:
$ gunzip -c batocera-x86_64-x86_64-43-20260508.img.gz | sudo dd of=/dev/sdb bs=4M status=progress conv=fsync
2048+0 records in
2048+0 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 142 s, 60.5 MB/s
$ sync

Steps 9-12: Boot and Configure

9. Boot from the drive. Reboot the target machine and open its one-time boot menu — usually F12, F11, Esc, or Del depending on the vendor — then pick the USB device or SSD. If it does not appear, enter UEFI setup and disable Secure Boot and any "fast boot" option, then try again. Secure Boot blocks unsigned bootloaders, and Batocera's is unsigned by design.
10. Let the first boot finish. On its first run Batocera expands its data partition to fill the drive and then drops you into the EmulationStation carousel. This resize is precisely why you do not yank the drive early; interrupting it corrupts the partition you just created. Wait until you see the system menu before touching anything.
11. Set language, timezone, and pair a controller. Batocera auto-detects the overwhelming majority of controllers — Xbox, DualShock and DualSense, 8BitDo, generic XInput — with zero configuration. Map the Hotkey button when prompted; without it you cannot cleanly exit a game, and you will be reduced to cutting power, which is how save files die young.
12. Add your content and run the BIOS check. Copy ROMs and BIOS into the share (next section), then run Missing BIOS Check under Game Settings. Nothing on the PlayStation, Saturn, or Neo Geo end of the spectrum runs without the correct BIOS, and the checker tells you precisely which files are missing and the exact MD5 it expects. This step is the line between "it works" and "why is everything red."

Loading ROMs and BIOS into /share

You now have a working desktop with nothing to play, which is the most anticlimactic moment in the whole process. Fixing it means understanding where Batocera keeps your content, how to get files there, and why BIOS files are simultaneously the fussiest and the most legally loaded part of the entire exercise.

The /share map, and why it is also /userdata

Batocera keeps everything you add on a single writable partition. Over the network that partition appears as a share named share — reachable at \\BATOCERA\share from Windows or smb://batocera.local from macOS — while internally the same partition is mounted at /userdata. Same storage, two names; the network calls it share, the shell calls it userdata, and once you know that, the documentation stops appearing to contradict itself. Inside it, the layout is rigid and case-sensitive, and getting a folder name wrong is the single most common reason a game you definitely copied stubbornly refuses to appear.

/userdata/                (the network share \\BATOCERA\share points here)
  roms/
    snes/       Super Nintendo   formats: .sfc .smc .zip
    psx/        PlayStation      formats: .chd .pbp .cue
    ps2/        PlayStation 2    formats: .chd .iso
    wiiu/       Wii U            formats: .wua          (Cemu)
    n3ds/       Nintendo 3DS     formats: .3ds .cci     (Azahar)
    amiga1200/  Amiga 1200       formats: .lha .adf     (Amiberry)
  bios/         system BIOS and firmware (you supply these)
  saves/        save files and save states
  system/       batocera.conf and per-emulator configs
  screenshots/  in-game captures

Getting files onto the box

Three routes, in rough order of convenience. The first is the network share: with the machine on your LAN, browse to \\BATOCERA\share from another computer and drag folders in. The second is SSH and SCP for anyone comfortable at a terminal; the default credentials on a fresh image are user root, password linux, which you should change the moment the box is reachable from anywhere you do not personally control. The third is the built-in file manager, reached by pressing F1 on the system list, for when the machine is not networked and you are copying from a second USB stick. Pick whichever matches your setup — the destination folders are identical in all three.

# Default credentials on a fresh image: user "root", password "linux".
$ ssh root@batocera.local
root@batocera's password:

Welcome to Batocera.linux -- Version 43 (build 20260508)
SSH and Samba are enabled out of the box; change the root password now.

# Copy a folder of SNES ROMs straight in (/userdata == the "share"):
$ scp -r ~/snes-roms/* root@batocera.local:/userdata/roms/snes/
SuperMetroid.sfc       100%  3072KB   38.4MB/s   00:00
ChronoTrigger.sfc      100%  4096KB   40.1MB/s   00:00

BIOS, exact names, and the law

Here is where the lore meets the statute. Batocera ships no BIOS files because console BIOS images are copyrighted by their manufacturers — Sony, Sega, Nintendo, SNK — and redistributing them is infringement regardless of how freely they circulate on the wider internet. Dumping the BIOS from hardware you personally own occupies a friendlier legal position in many jurisdictions; downloading someone else's dump does not, and ROMs of games you do not own are simply piracy with extra steps. The technical requirement is unforgiving in a way that is actually useful: BIOS files must have the exact filename and frequently the exact MD5 the emulator expects, or they are treated as absent. Drop them in /share/bios, then run Missing BIOS Check under Game Settings; it lists every missing or mismatched file alongside the hash it wants, turning "it does not work" into a precise shopping list. For the granular question of which core wants which file, the libretro documentation is the authority worth bookmarking.

Five Pitfalls That Waste Your Afternoon

These are the failures that do not announce themselves as failures. The flash "succeeds," the boot "works," the copy "completes" — and then something downstream quietly does not, and you spend three hours debugging the wrong layer. Each pitfall below comes with the fix that actually addresses it rather than the one that merely feels productive.

Drive and flashing mistakes

• A counterfeit or dishonest-capacity flash drive. The drive reports 64 GB, holds 4, and silently overwrites the start of itself once you exceed the real size — which is to say, it eats your data. Fix: validate any new drive with h2testw on Windows or f3 on Linux and macOS before you trust it, buy from reputable sellers, and prefer an SSD, which largely sidesteps the entire category.
• Extracting the .img.gz before flashing. This wastes 8 GB and leaves two similarly named files in one folder, inviting you to flash the wrong one. Fix: feed Etcher the .gz directly; it decompresses on the fly. If you already extracted, you can flash the raw .img, but tidy the folder first.
• Pulling the drive too early. Yanking it the moment Etcher's bar fills skips the verification pass; yanking it during the first-boot partition resize corrupts the data partition outright. Fix: wait for "Flash Complete" in Etcher, and on first boot wait for the EmulationStation menu before you touch anything.

It boots, but nothing runs

• ROMs in the wrong folder or the wrong format. EmulationStation reads exact, case-sensitive folder names; a "Super Nintendo" folder is invisible where a "snes" folder is not, and a double-zipped or unsupported file is skipped silently. Fix: match the wiki's exact system names, prefer .chd for disc systems, avoid nesting archives, then choose UPDATE GAMELISTS so the frontend rescans.
• Missing or mis-named BIOS. A BIOS with the wrong region, wrong name, or wrong MD5 is treated as absent, and the system simply will not launch. Fix: run Missing BIOS Check under Game Settings, then place the precise files it names — correct region, correct hash — into /share/bios.

It will not boot at all

• Secure Boot or Fast Boot blocking the USB. The bootloader is unsigned by design, so Secure Boot refuses it, and Fast Boot can skip USB enumeration entirely. Fix: disable both in UEFI, and use the one-time boot menu to select the drive explicitly.
• The wrong architecture image. An ARM image will not boot an x86 PC, and the failure is a silent black screen. Fix: use the x86_64 image for PCs and the board-specific image for single-board computers — and re-verify which you actually downloaded.

Troubleshooting: 10 Failures and Fixes

Read the symptom column first, not the cause column. The "likely cause" is a hypothesis, and the discipline of matching what you actually see — rather than what you assume is wrong — is what keeps a ten-minute fix from becoming an afternoon. Work top to bottom; the cheaper fixes are listed first within each cell.

Boot, display, and input

Content, network, and performance

The nuclear option: reflash and verify

When a problem resists every targeted fix, stop debugging the symptom and re-establish the baseline: re-download from the official page, re-verify the SHA-256, reflash to a known-good drive, and boot it clean before adding anything back. Most "haunted" Batocera installs are a corrupt write or a dishonest drive wearing a costume, and a clean baseline exorcises both at once. The release page also lets you drop back to version 42 (15 March 2026) if a regression in 43 specifically bites your hardware — rare, but it happens, and rolling back is faster than arguing with it.

Advanced Tips: Beyond the Defaults

The defaults are genuinely good — that is the whole zero-configuration premise — but "good defaults" and "tuned for your hardware and your taste" are not the same thing. Once the basics work, these are the levers worth pulling, in roughly the order most people reach for them.

Install to an internal SSD

Running from USB is the point, but if Batocera is becoming the permanent personality of a dedicated machine, install it to an internal disk. Main Menu, then System Settings, then the install tool will write Batocera to a chosen internal drive and migrate your data partition onto it — faster load times, no dangling stick, and the same /userdata layout you already understand. Treat this as the deliberately destructive operation it is: it erases the target disk, so confirm twice that you are pointing it at the right one. Keep your USB image afterward; it doubles as a recovery tool when the internal install eventually needs one.

Tuning: latency, shaders, and clocks

The defaults are sane; the ceiling is higher. Run-ahead hides input latency by simulating frames in advance — transformative on twitchy 2D games, though it demands real CPU headroom. Shader stacks like CRT-Royale reproduce the look of a scanline display for people who consider pixel-perfect output a betrayal of the source material. On single-board computers, a modest overclock buys genuine frames if your cooling can pay for them. For the catalogue of cores and what each one supports, the libretro docs are the reference, and if you are assembling a core loadout from scratch our walkthrough on installing 200 RetroArch cores covers the libretro side in depth.

## Run-ahead: hide input latency on systems with CPU headroom
snes.runahead=1
snes.secondinstance=1

## A heavier shader stack for the CRT look (RetroArch/libretro)
global.shaders=crt/crt-royale

## Single-board overclock -- cool it FIRST, then edit /boot/config.txt:
## arm_freq=2600
## over_voltage_delta=25000

Scraping, updates, and backups

Three habits separate a maintained install from a fragile one. Scrape metadata and box art with a free ScreenScraper account entered in the scraper settings — anonymous scraping is rate-limited into uselessness. Update in place from Main Menu for point releases rather than reflashing; reflash only for major jumps or when something is genuinely broken, and consult the release history before you leap. And back up /share/system — your batocera.conf and per-emulator configs — somewhere off the drive, because the one thing a fresh flash cannot restore is the afternoon you spent tuning it. If you want to follow development or file a bug, the source lives on GitHub.

A Complete Working Configuration

What follows is a copy-paste starting point that produces a sane, tuned install on capable hardware. Keys do drift slightly between releases, so confirm anything exotic against the wiki — but the structure and the common keys below have been stable for a long time and will get you most of the way without guesswork.

A commented batocera.conf

## /userdata/system/batocera.conf
## Edit over the network at \\BATOCERA\share\system\  -- one key=value per line, no spaces around =.

## --- SYSTEM ---
system.language=en_US
system.kblayout=us
system.timezone=America/New_York
system.power.switch=PWRBTN
system.hostname=BATOCERA

## --- NETWORK (Ethernet is on by default; uncomment for Wi-Fi) ---
wifi.enabled=0
## wifi.enabled=1
## wifi.ssid=YourNetwork
## wifi.key=YourPassword

## --- GLOBAL EMULATOR DEFAULTS ---
global.videomode=default
global.ratio=auto
global.smooth=1
global.rewind=0
global.runahead=0
global.shaders=none
global.bezel=default
global.retroachievements=0

## --- PER-SYSTEM OVERRIDES ---
snes.core=snes9x
nes.core=mesen
megadrive.core=genesisplusgx
n64.core=mupen64plus-next
psx.core=swanstation
saturn.core=mednafen_saturn
ps2.emulator=pcsx2
gamecube.emulator=dolphin
wii.emulator=dolphin
wiiu.emulator=cemu
n3ds.emulator=azahar
amiga1200.emulator=amiberry
atarijaguar.emulator=bigpemu

## Heavy systems: raise internal resolution only on capable GPUs.
ps2.pcsx2.internalresolution=3
gamecube.dolphin.resolution=2

Read it top to bottom and it tells a story: identify the box, get it on the network, set conservative global defaults, then override per system where it matters. The per-system block pins specific emulators so a future update cannot silently switch you to a core you did not test — Cemu for Wii U, Azahar for 3DS, BigPEmu for Jaguar, all of them the version-43 choices from earlier in this guide.

A sane /share layout

The folder tree shown back in the ROMs section is the layout this config assumes, and it is worth re-stating the rules rather than the structure: disc-based systems want .chd to save space and stay sane, every BIOS lives flat in /share/bios under its exact name, and the system folder names are not suggestions. If a game does not appear, the layout is the first suspect, not the emulator. Keep a copy of /share/system off the drive and you can rebuild the rest from your ROM and BIOS archives in an afternoon.

Hotkeys you will actually use

The Hotkey button is usually the Guide or Home button on a modern pad, and holding it turns the face and shoulder buttons into a control panel. The defaults below are the common map; exact bindings vary by core, so the authoritative copy lives under Main Menu, then Controller Settings, and in the wiki.

Where to Go After First Boot

You have a verified image, a drive that does not lie, a desktop that boots, and a config that makes sense. The remaining work is maintenance and judgment — keeping the thing current, growing it without inviting a lawyer, and recognizing the point at which the PC route stops being worth the friction.

Keep the OS current

Batocera updates in place from Main Menu, which is the right tool for point releases and the wrong one for major jumps that are cleaner to reflash. Watch the release page so you know which category a given update is, and do not update on the eve of a gaming night — emulation regressions are real, if rare. For the blow-by-blow on a specific recent point release, the 43.1 point-release notes walk through what actually changed and whether it is worth your time.

Grow the library, stay on the right side of the line

The legal recap is short and worth repeating because people forget it the moment a game looks tempting: the OS is free and legal, BIOS and ROMs are not yours to download, and dumping from hardware you own is the defensible path. Beyond that, the homebrew scene is large, genuinely good, and entirely legitimate — original games and engine ports, including the kind of thing the Glasswing engine enables, are a growing share of what makes a Batocera box fun rather than merely nostalgic. Pull those from the in-OS content store, not from a stranger's "all-in-one" pack.

When to stop fighting your hardware

If the PC route is becoming more troubleshooting than playing — thermal throttling, driver fights, a mini-PC that wheezes at PS2 — the honest answer may be a dedicated handheld that ships tuned out of the box. Our Retroid Pocket 6 review covers what a purpose-built device buys you over a repurposed PC. Either way, Batocera asks for one afternoon and a drive that tells the truth about its own size. Give it both and it will outlast three of your gaming PCs. Give it a counterfeit USB stick, and you will be right back in the drawer.