Apple Beta Build History

Why Track Build Numbers

A version number tells you which release you are on. A build number tells you which exact copy of it — and that is the only thing precise enough to troubleshoot with, compare notes on, or verify that an update actually installed. Two devices can report the same version while running different builds, which is how a release candidate and the public release usually differ.

The gaps matter as much as the builds. Across the cycles recorded here the average interval between consecutive betas is about 11 days. A build that arrives inside a week almost always means a fix that could not wait; a gap past three weeks usually means the cycle is consolidating ahead of a release candidate. Reading the rhythm is the closest thing there is to predicting a launch date.

Everything below comes from Apple's official developer release feed, which we poll every 15 minutes and record permanently. Builds are never rewritten once logged, so the history stays accurate even after Apple's own feed rolls them off. Where a build is missing, it is because it shipped before we began archiving rather than because it did not exist.

iOS 27

Some builds in this cycle shipped before we began archiving, so the intervals around them are left blank rather than measured across a missing build.

iPadOS 27

Some builds in this cycle shipped before we began archiving, so the intervals around them are left blank rather than measured across a missing build.

macOS 27

Some builds in this cycle shipped before we began archiving, so the intervals around them are left blank rather than measured across a missing build.

tvOS 27

Some builds in this cycle shipped before we began archiving, so the intervals around them are left blank rather than measured across a missing build.

visionOS 27

Some builds in this cycle shipped before we began archiving, so the intervals around them are left blank rather than measured across a missing build.

watchOS 27

Some builds in this cycle shipped before we began archiving, so the intervals around them are left blank rather than measured across a missing build.

audioOS 27

audioOS 26

macOS 26

Some builds in this cycle shipped before we began archiving, so the intervals around them are left blank rather than measured across a missing build.

tvOS 26

Some builds in this cycle shipped before we began archiving, so the intervals around them are left blank rather than measured across a missing build.

iOS 26

Some builds in this cycle shipped before we began archiving, so the intervals around them are left blank rather than measured across a missing build.

iPadOS 26

Some builds in this cycle shipped before we began archiving, so the intervals around them are left blank rather than measured across a missing build.

visionOS 26

Some builds in this cycle shipped before we began archiving, so the intervals around them are left blank rather than measured across a missing build.

watchOS 26