Official builds of MassOS, produced by the developers of the MassOS Project, are made available on this web server. These builds can be directly downloaded, or used with the new MassOS upgrade utility.
You can browse all the available builds here - both the Live CD ISO images (.iso) and plain rootfs tarballs (.tar.zst) are provided. Note that builds are now in architecture-specific directories - for most systems, you therefore want the x86_64 subdirectory. For instructions on how to install MassOS, please refer to the the official installation guide.
Please note that the previously-used build directory, named massos-builds, is now transparently symlinked to the new x86_64 directory, so older workflows using it will continue to function normally without breaking. However we recommend migrating current and future workflows to the new directory layout, primarily because it helps improve support for multiple architectures.
Blake-2 checksum files (.b2) are provided alongside all builds. These can be used to verify the integrity of your download. Builds are also published with a detached GPG signature file (.asc) signed by this GPG key. Validating the GPG signature of a build can be done instead of or as well as checking the Blake-2 checksum, to verify the integrity of your download. All current and past GPG keys used to sign official MassOS builds can be found in the SIGNING-KEYS subdirectory.
MassOS builds are signed for UEFI secure boot. In most cases you will not need to download the secure boot certificates directly, as they are embedded into the bootable section of the MassOS ISO images, and the UEFI secure boot guide explains how to import the certificate from the ISO image. However, if for some reason you want/need to obtain them separately, you can download them from here.
Builds produced in 2026 and onwards are and will be signed by the updated 2026 MassOS secure boot certificate, which has a CN of MassOS Project Secure Boot Signing 2026. Builds from 2025 were signed by the older 2025 MassOS secure boot certificate, which has a CN of MassOS Project Official SB Signing 2025. The main reason for the migration was due to the old certificate lacking the Code Signing EKU, as well as because it was used to sign builds which (at the time) were not properly locked down and hardened under UEFI secure boot like newer builds are.