RC stands for release candidate — the last build of a beta cycle, the one Apple considers finished and ready to ship. It comes after the final developer and public betas and, almost always, is the exact same build that lands on every other iPhone on release day. The word "candidate" is doing real work in that name, though: it means Apple believes this build is done, not that it's guaranteed to be the one that ships. If a serious problem turns up in the last stretch, Apple can withdraw it and issue a second RC before opening the public release.
If you've been running a beta for a few months and you suddenly see "Release Candidate" instead of "Developer Beta 7" in Settings, that's not a glitch — it's a promotion. The RC is Apple's own statement that testing is over and this build is what's going out to everyone. It's also the point where the risk calculus of running beta software flips: the gamble from June is, by RC time, close to a non-decision.
This guide explains what a release candidate is, how to spot one, why it's the safest moment to be on the beta track, and the one honest catch that keeps it from being a guarantee. None of this is tied to a specific iOS version — Apple has used the same process every year since betas began. Where it helps to see the idea in motion, we'll use the live iOS 27 cycle as the running example.
What "release candidate" actually means
A release candidate is a build that has cleared every internal milestone Apple sets during a beta cycle: the crash rate is down to what Apple considers shippable, features are locked, and engineers are no longer changing behavior — only fixing what's broken. It's the build Apple is nominating to become the public release. Nothing about the software is different in kind from a late-cycle beta; what's different is Apple's confidence in it.
That's a meaningful shift from an early beta. Developer beta 1 exists to find problems — it's the roughest build of the year on purpose, because its job is to surface bugs while there's months of runway to fix them. The RC exists to confirm there are no problems left worth holding the release for.
RC vs. beta: what's actually different
Mechanically, installing an RC works exactly like installing a beta — same Settings menu, same enrollment. The differences are in what the build represents, not how you get it.
- Stability. A beta is a work in progress; an RC is a finished product waiting for a release date. The crash reports and app-compatibility issues of the early betas have, by RC time, mostly been resolved.
- Purpose. Betas exist to find bugs. The RC exists to verify there's nothing left to find — a confirmation pass, not a discovery pass.
- Duration. A beta cycle runs for weeks between builds. An RC is usually around for days to a couple of weeks before it ships.
- Labeling. Covered in detail below — an RC drops the beta terminology entirely, everywhere Apple shows the build.
Is the RC really just the final release, early?
In practice, yes — and this is the part most people actually want to know. Apple's normal pattern is to build one release candidate, test it for a short window, and then ship that exact same build to the public a few days to two weeks later. If you install the RC, you are, in the overwhelming majority of years, installing the identical bits that later show up in Software Update for everyone else. You're not getting a preview of the final release. You're getting the final release, early, under a different label.
Here's the honest nuance, and it's the whole reason the build is called a candidate rather than "the final version, early": Apple doesn't always stop at one. If something meaningful turns up during the RC window — a bug serious enough to hold the release for — Apple pulls that build and issues a second one, RC2, with its own new build number. Whoever installed the first RC needs to update again to land on the build that actually ships. It's not common, but it's not hypothetical either, and it's exactly why "final" isn't used until the version reaches everyone.
How to tell an RC apart from a beta by its build number
You don't have to guess. Apple labels this clearly in two places, and the build number is the most reliable signal because it can't be spoofed by a stale cache or a slow-to-update app.
Check the label in Software Update
Go to Settings → General → Software Update. A beta build spells it out directly: "iOS 27 Developer Beta 7" or "iOS 27 Public Beta 5," with a number attached. A release candidate drops the beta language and the number entirely — it just says "iOS 27 Release Candidate." No count, because there's normally only going to be one, or at most two.
Check the build number in About
Go to Settings → General → About and look at the Build field. Every beta and RC gets its own distinct build number in Apple's internal sequence — for iOS 27, developer beta 1 shipped as 24A5355q on June 8, 2026, and beta 7 landed as 24A5424a on August 24. The RC carries a build number later in that same sequence. What actually marks it as an RC isn't a special format in the number — it's that Software Update stops calling it a beta at all. The label change is your confirmation, not the digits.
Worth knowing if you run other Apple devices side by side: iOS and iPadOS share the exact same build number in a cycle (iPadOS 27 beta 8 is also 24A5430a), while macOS, tvOS, and watchOS each carry their own numbering — true for RCs as well as betas.
Beta vs. RC vs. final release, side by side
| Dimension | Beta | Release candidate | Final release |
|---|---|---|---|
| Stability | Variable — rough early, better late | Effectively shipping quality | Shipping quality |
| Who gets it | Developers, then public beta testers | Anyone already enrolled in the beta program | Every eligible device, no enrollment needed |
| Can you stay on it? | Yes, but it's superseded every few weeks | Briefly — days to a couple of weeks, by design | Yes, until the next major version |
| What happens next | Another beta build, eventually an RC | Almost always becomes the final release unmodified | Point releases (x.1, x.2) follow over the year |
| Labeled as beta in Settings? | Yes — "Developer Beta" / "Public Beta" | No — just "Release Candidate" | No — version number only |
| Banking / payment apps | Often blocked as a fraud-prevention measure | Usually still blocked, since it's still pre-release | Work normally |
Why the RC is the safest moment in the whole beta cycle
Every beta cycle follows the same risk curve: rough at the start, smoother toward the end. Developer beta 1 is deliberately the worst build of the year — battery drain, app crashes, and missing polish are the expected cost of being first. Each subsequent beta narrows that gap. By the time a cycle reaches its RC, it has absorbed every bug report from every prior build, and third-party developers have had the entire cycle to test their apps against it.
That's what makes the RC categorically different from "just another beta, later." It isn't one more point on a gradually improving curve — it's where the curve ends. You're no longer trading stability for early access, because there's essentially nothing left to trade. If you'd install the public release anyway, waiting a few extra days for the RC to become official changes almost nothing about your risk.
For anyone weighing whether to join at all earlier in a cycle, our beta safety guide walks through the fuller risk curve from beta 1 onward — the RC is simply where that curve bottoms out.
What happens on release day if you're already on the RC
Since the RC is normally the exact build that ships, there's often nothing to install on release day — Software Update may simply show you're already up to date. What you do need to think about is what your phone does after that day, because staying enrolled in the beta program doesn't turn itself off just because a version shipped.
If Settings → General → Software Update → Beta Updates is still switched on, your phone keeps treating itself as a beta device — offering the next point release's beta, and eventually next year's major-version beta, instead of settling into ordinary, fully-tested stable updates. That's what the toggle is for, but plenty of people flip it on for an RC and forget it's still on months later.
If you're done with beta builds once the real version ships, turn Beta Updates off, or remove the beta configuration profile from Settings → General → VPN & Device Management. Our downgrade guide covers the related case of leaving a beta mid-cycle.
The one real catch: an RC is still pre-release software
Everything above points toward the RC being about as safe as beta software gets — and it is. But that's not the same claim as "no longer beta software," and the distinction is worth taking seriously. An RC hasn't been signed off the way a shipped, public release has. It's Apple's best build, tested and re-tested, but it hasn't cleared the very last gate.
The practical consequence is narrow but real: Apple can withdraw an RC. It doesn't happen every cycle, and when it does, it's usually because testing during the RC window surfaces something serious enough to be worth delaying for. When it happens, Apple pulls that build, issues a fresh RC with a new build number, and the release date can shift by a few days while the second candidate goes through its own short window. That's the entire reason the word "candidate" exists: a nomination, not a certification, until the exact same build reaches the public and becomes the official release.
None of that makes the RC risky in any meaningful sense — it's still, by a wide margin, the most stable pre-release build you'll ever install. "Almost certainly done" is the honest description, not "guaranteed done."
Watching it happen: the iOS 27 cycle right now
As a live example: iOS 27 reached developer beta 8, build 24A5430a, on Monday, August 31, 2026 — nearly three months after beta 1 opened the cycle on June 8. The currently shipping public release is still iOS 26.6.1 (build 23G83), and Apple hasn't announced an exact release date, but the pattern from prior years points to a final release around Monday, September 14, 2026. Going by that pattern, an iOS 27 RC is expected within weeks — the last build most testers see before the version number simply becomes official.
When that RC lands, everything here applies directly: check Software Update for the "Release Candidate" label rather than a beta number, treat it as close to risk-free as beta software gets, and check the Beta Updates toggle once iOS 27 is officially out if you don't want your phone reaching for iOS 27.1's beta automatically. Our iOS 27 release date page and should-you-install guide follow the countdown from here through launch.
Common questions
What does RC mean in iOS?
RC stands for release candidate — the build Apple believes is finished and ready to ship. It sits at the end of the beta cycle, after the last developer and public betas, and it's normally the exact build that becomes the public release a short time later.
Is the RC the same as the final version?
Almost always, yes — Apple typically ships the same build to RC testers and the general public. But it's called a candidate, not final, for a reason: if testing turns up a real problem, Apple can issue a second RC with a new build number before the public release goes out.
How do I know if I'm on a beta or an RC?
Check Settings → General → Software Update. A beta build says "Developer Beta" or "Public Beta" followed by a number. A release candidate simply says "Release Candidate" — no beta wording, no count — the clearest tell you're on the last build of the cycle.
Is it safe to install the RC?
Yes — the RC is the lowest-risk moment in the entire beta cycle. It has absorbed months of bug reports from every earlier beta and is the build Apple is about to hand to everyone else. The only real caveat is that it's still technically pre-release software, even though a pulled RC is rare.
Do I need to do anything once the final version ships if I'm already on the RC?
Usually no update is needed, since the RC and the public release are typically identical builds. Check Settings → General → Software Update → Beta Updates: if it's still on, your phone keeps offering prerelease builds instead of settling on stable releases only. Turn it off, or remove the beta profile, to get off the beta track for good.
Can Apple pull a release candidate?
Yes. It's uncommon, but it's the entire reason the build is called a "candidate" instead of "final." If a serious bug surfaces during the RC window, Apple can withdraw it and issue a second release candidate before the public release.
The verdict
RC means release candidate: the build Apple considers finished, sitting at the end of a beta cycle, and — almost always — the exact software that ships to everyone a short time later. Identify one by checking Software Update for "Release Candidate" with no beta label attached. It's the single safest window in the entire beta program, built on months of bug fixes from every earlier beta. The only honest asterisk: "candidate" means exactly what it says, and Apple can, rarely, replace it with a second RC if something surfaces late. Install it with confidence, keep an eye on the Beta Updates toggle once the real release lands, and you've got the whole cycle figured out.