Amiberry 8.1.6 released with better JIT stability, Android fixes and WinUAE sync

Amiberry has never been the loudest name in emulation, but it has become one of the most useful. Built on the WinUAE core, it brings broad Amiga compatibility to modern machines, from Linux boxes and Macs to Windows PCs, Android devices, FreeBSD and Haiku systems. With version 8.1.6, released on GitHub on 9 May 2026, Amiberry takes another step toward becoming a more mature cross-platform emulator. This is not a flashy release full of showpiece features. It is a maintenance-heavy, platform-aware update that makes the emulator feel more dependable where it matters.

A release about foundations, not fireworks

The focus of Amiberry 8.1.6 is clear: platform support, JIT stability, RTG and graphics improvements, Android and libretro fixes, safer configuration handling, upstream WinUAE syncs, and refreshed CI and package targets. For users, that translates into something simple: fewer rough edges, better platform coverage and fewer surprises when moving between devices.

What this update really means

Amiberry 8.1.6 is not trying to reinvent Amiga emulation. It is trying to make the emulator behave more reliably on the hardware people are actually using in 2026. That matters because Amiberry now lives in a much broader world than the classic desktop emulator scene. Users may be launching it on a Raspberry Pi, a Linux handheld, a Windows gaming PC, an Android tablet or a new ARM-based laptop. The emulator has to follow them.

Windows ARM64 finally gets serious attention

The most eye-catching part of the release is native Windows ARM64 support. Amiberry 8.1.6 adds and hardens Windows ARM64 release builds, including installer and signing support, release artifacts, JIT startup fixes and fault recovery improvements. That is an important move. Windows-on-ARM machines are no longer a curiosity, and emulators that want to feel current need to treat them as first-class systems rather than experimental targets. For users on newer Snapdragon-based laptops, this update should make Amiberry feel less like a port and more like a native citizen. The Windows build system has also been modernized. The x64 and ARM64 Windows builds are now unified around llvm-mingw, replacing the older MSYS2/GCC route. That kind of behind-the-scenes change rarely earns applause, but it often pays dividends later. Cleaner build systems usually mean fewer release hiccups, better consistency and a healthier project in the long run.

JIT stability: less glamour, more confidence

Another major thread in 8.1.6 is the x86-64 JIT. The release improves stability around high host-memory mappings, 32-bit address wrapping, unsafe control-flow fallbacks and signal recovery. For everyday users, the details are less important than the direction of travel. JIT compilation is one of the places where performance and fragility can meet. When it works, it helps emulation feel fast and fluid. When it misbehaves, it can produce the sort of hard-to-pin-down crashes that make retro computing feel more archaeological than nostalgic. Amiberry 8.1.6 is clearly trying to reduce that risk.

Why JIT work matters

Faster emulation is only useful when it is also trustworthy. This update appears aimed at making Amiberry’s fast path less fragile on modern host systems. That is especially relevant as Amiberry supports more architectures and more operating systems. An emulator can have excellent compatibility on paper, but users remember the crashes, freezes and strange edge cases. Stability work is what turns technical capability into daily usability.

RTG and graphics get cleaner

Graphics also receive a meaningful polish pass. Amiberry 8.1.6 enables RTG zero-copy by default, fixes RTG cursor fringe artifacts, improves RTG dirty tracking, adds truecolor ARGB32 hardware sprite support and improves OpenGL shader rendering paths. This is another area where the changelog hides the user benefit. RTG users want crisp output, smooth redraws and clean pointer behavior. Small graphical glitches can break the illusion quickly, especially when using Workbench setups, productivity software or high-resolution Amiga environments. The result should be a tidier visual experience, particularly for users who lean on Amiga graphics modes beyond the most basic classic setups.

Android and libretro users are not forgotten

Amiberry has always been attractive because it travels well. Version 8.1.6 continues that philosophy with Android improvements covering back and menu handling, GUI access fallbacks, two-finger tracking, default controls, on-screen keyboard sizing and version/build behavior. These are not glamorous features, but they are exactly the sort of changes mobile users notice. On Android, the difference between technically works and pleasant to use often comes down to input handling, menu access and sensible defaults. The libretro side also gets attention, with fixes for path isolation, log placement, frontend directory handling and Windows clang build linkage. For users running Amiberry through frontend environments, that kind of housekeeping can make the whole experience feel less brittle.

Configuration healing: the unsung hero

One of the more quietly welcome additions is improved configuration handling. Re-saving configs now removes duplicate or obsolete Amiberry-managed path entries, while avoiding premature display configuration cleanup. Anyone who has spent years with emulators knows how configuration files can become haunted. Old paths, duplicate entries and legacy assumptions build up slowly, then surface as strange behavior months later. Amiberry’s new config-healing work is not dramatic, but it is thoughtful. It suggests a project that understands how people really use emulators: across upgrades, copied folders, old setups and half-remembered tweaks.

WinUAE sync keeps the core moving

Amiberry 8.1.6 also syncs upstream WinUAE updates, including OCS Denise NTSC overscan behavior and 68020/030 cycle-exact interrupt timing fixes. That is important because Amiberry’s value is partly built on its relationship with WinUAE’s emulation core. Platform polish is welcome, but accurate Amiga behavior still matters. The upstream sync shows that this release is not only about packaging and modern hardware; it is also about keeping the emulation fundamentals aligned.

A better-built emulator for a broader world

The smaller changes are numerous: filesystem size reporting fixes, empty extended ROM handling on Windows, restoration of the Windows screenshot hotkey, Linux and macOS content-directory canonicalization, OpenGL fallback improvements, FreeBSD build and install support, a hotkey-driven debugger console, and updates to Dear ImGui, gamecontrollerdb and WHDBooter data. Taken one by one, these are modest. Taken together, they tell a story. Amiberry is becoming broader, cleaner and more resilient.

Verdict: a maintenance release worth installing

Amiberry 8.1.6 is not the sort of update that sells itself with a single dramatic feature. Its importance is cumulative. Windows ARM64 gets real support. JIT behavior is hardened. RTG graphics get cleaner. Android controls improve. Libretro integration is tidied. Config files become less troublesome. The build and packaging infrastructure moves forward. For Amiga enthusiasts, that is exactly the kind of release that matters. It is a reminder that emulation projects do not only advance through new features. Sometimes they advance by becoming less annoying, less fragile and more ready for the next generation of machines. And with Amiberry 8.1.6, that is precisely what seems to be happening.