FreeBSD 15-STABLE now has disc1.iso images available for ARM64/aarch64. This is not a surprise if you have been following the development branch, but it is a milestone worth paying attention to. The STABLE branch means this code has been merged from CURRENT, tested, and deemed close to release quality. For anyone planning ARM64 deployments on FreeBSD, the path just got significantly clearer.
What Changed
Previously, running FreeBSD on ARM64 meant working with snapshot builds, custom images, or building from source. The availability of official disc1.iso images on the 15-STABLE branch changes the calculus. You now have a standard installation path that mirrors what amd64 users have had for years. Download the ISO, write it to media or mount it in your hypervisor, and install. No special handling required.
ARM64 support on FreeBSD has been maturing steadily across the 13.x and 14.x release cycles. Driver coverage has expanded, performance tuning has improved, and the toolchain has solidified. The 15-STABLE images represent the accumulated result of that work reaching a point where the release engineering team is confident enough to produce standard installation media.
Where This Matters
The practical implications break down into a few categories. First, single-board computers. The Raspberry Pi 4 and Pi 5 are obvious targets, and FreeBSD on these boards has gone from experimental to genuinely usable. If you are building lab environments, edge nodes, or lightweight network appliances, FreeBSD on a Pi is a real option now -- not a weekend project that ends in frustration.
Second, cloud ARM instances. AWS Graviton, Ampere Altra on Oracle Cloud, and similar offerings have been pushing ARM64 into the datacenter for the past few years. The economics are compelling: lower power consumption, competitive single-threaded performance, and often better price-per-core than equivalent x86 instances. With official FreeBSD 15-STABLE ARM64 images, deploying FreeBSD on these platforms becomes a first-class workflow rather than an exercise in custom image building.
Third, and more experimentally, Apple Silicon. FreeBSD on M-series chips is still limited and not production-ready, but the kernel support continues to progress. It is worth watching, even if it is not something you would deploy on today.
Why STABLE Matters
The distinction between CURRENT and STABLE is important here. CURRENT is the development branch -- it gets new features first, but it also gets new bugs first. STABLE is where code lands after it has been tested in CURRENT and deemed ready for broader consumption. It is not a release, but it is close. For production FreeBSD shops evaluating ARM64, STABLE is the signal that says this is ready for serious testing and staging environments, with a release likely on the horizon.
The Bottom Line
For shops already running FreeBSD on amd64, ARM64 represents an opportunity to diversify hardware without changing your operating system, your tooling, or your operational playbooks. Lower power draw, competitive performance, and expanding hardware options make ARM64 increasingly hard to ignore. The fact that FreeBSD now provides standard installation media on the STABLE branch removes one of the last practical barriers to adoption.
The Reddit discussion has additional context and community reactions if you want to dig deeper into the specifics.
Planning an ARM64 deployment? Learn about our FreeBSD systems engineering services or schedule a consultation.