What the term means
A release candidate is the build Apple believes is finished. It is submitted as the version that will ship publicly unless something serious is discovered in the days that follow. In most cycles, nothing is, and the RC becomes the public release unchanged.
That is the practical distinction from every earlier beta. Beta 1 through beta 8 are works in progress; the RC is a finished product waiting for a launch date.
How to tell you are on the RC
Apple labels it explicitly in Software Update, and the build number is the giveaway — beta builds carry a distinctive extra digit and letter pattern that release builds do not. When the version you are offered stops looking like a beta build number, you are on the RC.
Both the developer and public channels receive the RC, usually on the same day. This is the one point in the cycle where the two channels are genuinely identical.
Why the RC is the safest early access
Everything that makes an early beta disruptive has been resolved by this stage: third-party apps have shipped compatible versions, the serious performance and battery regressions have been found, and the feature set is final rather than shifting.
The remaining risk is small but not zero. In some cycles Apple does replace an RC with a second one, and occasionally the public release carries a fix the RC did not. Neither is disruptive, but it is why the RC is described as a candidate rather than as the release.
What happens when the public release ships
Devices running the RC receive the finished version as an ordinary update if the two differ, or simply stay where they are if they are identical. Either way, you are on the shipping software without having to do anything, and betas stop being relevant to you.
If you want to leave the beta programme at that point, turning off Beta Updates once the public release has arrived is clean and requires no restore — this is by far the tidiest exit point in the whole cycle. Our exit guide covers it.
Where the RC sits in the year
The RC arrives in early September for the major releases, typically alongside the new iPhone announcement, with the public launch following within about a week. Point releases through the rest of the year follow the same pattern on a shorter timeline.
Our guide to the beta calendar lays out the full shape of the year, and the version comparison covers whether the move is worth making at all.
Frequently Asked Questions
Is the release candidate the same as the final release?
Usually, yes. The RC is the build Apple intends to ship, and unless something serious surfaces it becomes the public release unchanged.
Is it safe to install the RC?
It is the lowest-risk point in the entire beta cycle. Apps have caught up, the feature set is final and the serious regressions have been resolved.
Do developer and public channels get the RC at the same time?
Yes, usually on the same day. It is the one point in the cycle where the two channels are identical.
What happens to my device when the public version ships?
You receive it as an ordinary update if it differs from the RC, or you stay where you are if the builds are identical.