Pi 5 support, built on evidence.

An important distinction

On September 26, 2026 UTC, the directory listed Bookworm 4.8.12 Pi 5 images dated August 25, 2026, in both 32-bit and 64-bit variants. This corrects the incomplete picture from looking only at the main download page.

The comparison image

The upstream 64-bit Bookworm Pi 5 development image is a useful comparison candidate. Read its development-build notice first. It is an upstream file, not a verified download from this project.

The accompanying metadata describes an 881,463,784-byte compressed download and a 4,120,903,680-byte extracted image. Its published SHA-256 applies to the extracted image, not the .xz file:

5df55bf53cfada6c40cd102ed9cf65eed9d109f051c7a67578e659d0034b792d

The metadata’s embedded GitHub URL differs from the weekly-directory URL. Verify the actual endpoint, byte count, and extracted hash before relying on it. We have inspected the metadata, not downloaded or booted this Pi 5 candidate.

Choose a base before changing code

Use Raspberry Pi OS Lite 64-bit. First reproduce the Bookworm baseline supported by upstream’s image builder, then evaluate current Trixie on a separate installation for the forward-looking recipe. Older-than-Bookworm images are not an appropriate Pi 5 base. Keep the same hardware, display mode, controller, and test content for comparisons.

The setup code already recognizes Pi 5 and configures Cortex-A76 platform flags. Existing code paths are not proof that every emulator, video backend, or controller works.

Prove the smallest useful system

1. Boot a clean, verified OS image and record hardware, kernel and firmware.
2. Install a pinned RetroPie-Setup revision with a small package set.
3. Launch EmulationStation, then RetroArch and one rights-cleared test program.
4. Verify wired controls, HDMI sound, save persistence, menu return and shutdown.
5. Repeat the installation from the written instructions on a freshly flashed spare card.

Start at stock clocks. Investigate graphics, input, audio and thermal problems separately. Do not promise every console or game based on one successful launch.

Turn the recipe into an image

Start with RetroPie’s existing image builder: its Bookworm ARM64 configuration already lists Pi 5. Evaluate Raspberry Pi’s rpi-image-gen if that path cannot meet our needs. Use a controlled Linux build environment and pin the base, APT packages, setup commit, emulator source revisions, patches and toolchain. A setup-script pin alone does not pin the dependencies it downloads.

Create clean first-boot identity, avoid shared credentials, and strip builder history, network secrets and private game files. Export the image with a package manifest, component licenses, corresponding source, checksums, signature, and release notes. Demonstrate a repeatable build before claiming reproducibility.

Test before offering a release

Our first matrix covers clean flash, account setup, repeated boot, 1080p display, HDMI audio, wired input, saves, networking, shutdown, a sustained run, reinstallation, backup restoration, update recovery and identity checks. All results are currently untested.

GPIO, Bluetooth, NVMe, extra displays and demanding systems are separate later tests. Community reports should retain their hardware and settings rather than becoming universal support claims.

What would make an alpha ready?

A reproducible installation path, a deliberately small working feature set, redistribution review, recovery instructions, and recorded physical tests. Website readiness alone does not make an image ready. Our local research pack contains the detailed hardware matrix and build investigation plan.

Download the expanded Pi 5 build research