The Haiku source is continually built by a dedicated machine. These "nightly images" are provided mainly for development and testing purposes. You can download and install these snapshots to check out the latest features and bugfixes, be aware though that they may be unstable at times.


Missing Optional Packages

To keep the file size down, nightly images lack a few optional packages included in regular releases, for example Python, WonderBrush, Subversion etc.
installoptionalpackage -l entered in a Terminal will list all available packages,
installoptionalpackage {packagename} downloads and installs a specific package.


Image File Formats

The nightly images are provided in different formats and their uses are detailed below. The following guides are useful: Burning to CD, Writing to USB stick and Using VirtualBox.

  • universal anyboot - can be burned to compact discs, written directly to USB sticks, or used with QEMU.
  • VMDK - works out of the box in VMware and VirtualBox.
  • raw hard disk - can be written directly to disks or USB sticks (note: considered obsolete, in favor of anyboot).
  • CD ISO - can be burned to compact discs (note: considered obsolete, in favor of anyboot).

tar.xz archives

In addition to providing nightly images as the common compression format ZIP, a newer XZ format is being utilized for distribution. The tar.xz files are roughly half the size of their zip counterpart. However, 3rd party software is usually required for extraction.


Latest Stable Release

Official releases leading up to and including R1 Final are distributed only as a GCC 2 Hybrid for the x86 architecture. Applications made for Haiku should be tested on the latest available stable release.

With the release of Haiku R1 Alpha 4, there now are official image files available. Please head over to the download page at the Haiku website to get a Haiku image from one of our mirrors. Additionally, a commemorative CD may be ordered from Haiku, Inc.


Nightly Images

These are regularly built images always using the latest code. While we do try to keep our code in a working state at all times, these are not considered to be stable and may be broken in various ways at any given point in time. They are provided mainly for development and testing purposes.

GCC 2 Hybrids are recommended, as they are the most similar to official releases. Developers who choose to release software that requires a nightly build, are requested to provide a build for the latest stable nightly image.

Unsupported variants (GCC 2 Only, GCC 4 Only, GCC 4 Hybrid, x86_64, and non-x86 hardware) are available below. They are provided for development and testing purposes only. The non-x86 builds are in the early stages of development. If you're lucky, those non-x86 builds will boot just enough to crash.

All of these variant builds are unsupported.
Releasing software that requires these unsupported builds is discouraged.

x86 based unsupported variants
x86 GCC 2Unsupported x86-gcc2 RSS feed | x86 GCC 4Unsupported x86-gcc4 RSS feed | x86 GCC 4 HybridUnsupported x86-gcc4hybrid RSS feed | x86_64Unsupported x86_64 RSS feed
non-x86 unsupported variants
ARMUnsupported ARM RSS feed | m68kUnsupported m68k RSS feed | mipselUnsupported mipsel RSS feed | PowerPCUnsupported PowerPC RSS feed