Apple Splits July 20 Between iOS 27 Beta 4 and 26.6 Release Candidates

Apple used July 20 to advance both of its software tracks. On the Apple Developer releases page, the company posted iOS 27 beta 4 and macOS 27 beta 4 for developers, while also listing release candidates for iOS 26.6 and macOS 26.6. The build numbers show that the current shipping branch is now close to public release even as Apple continues iterating on its fall platforms.

That split matters because the two lines do different jobs. Beta 4 is part of the feature and tuning cycle for iOS 27 and macOS 27, where Apple is still refining Siri AI, interface behavior, and broader system changes ahead of autumn. The release candidates, by contrast, signal that iOS 26.6 and macOS 26.6 are moving from experimentation to stabilization.

The practical detail in iOS 26.6 is modest but relevant. 9to5Mac reports that Apple’s release notes describe bug fixes, security updates, and Spotlight index optimization to prepare devices for iOS 27. That does not turn 26.6 into a headline feature release, but it does suggest Apple is using the last pre-iOS-27 update to lay groundwork for a smoother migration later.

The rhythm behind these releases is familiar to anyone who follows Apple’s software calendar. Each June, WWDC introduces the next major versions; developer betas then arrive through the summer at intervals of roughly two to three weeks, public betas trail slightly behind, and by early autumn the builds converge into a shipping release. A release candidate sits at the very end of that pipeline: it is the build Apple believes is final, published under a label that lets developers verify their apps one last time. Historically, when no critical issue surfaces, the RC and the eventual public release are identical down to the build number.

Beta 4 occupies a specific place in that arc. By the fourth developer build of a cycle, the headline features have generally been shown, and the work shifts toward performance, battery behavior and interface refinement — which is consistent with reporting that Apple is still tuning Siri’s AI capabilities and system behavior in this round. It is also, historically, the stretch of the summer when feedback from a wider pool of testers starts shaping the release, as the beta audience grows beyond the developers who installed day one.

The late point release has its own tradition too. An x.6 update at the end of a version’s life rarely carries marquee features; its job is security patching, bug cleanup and — as the Spotlight note in 26.6 suggests — preparing the installed base for the migration ahead. Rebuilding or optimizing on-device indexes before a major upgrade is the kind of housekeeping that makes the eventual jump feel faster, because less has to be reconstructed the first time the new system boots.

The perennial advice about test builds still applies. Betas are test software: they can break third-party apps, shorten battery life and occasionally require a full restore, so they belong on secondary devices rather than a daily phone. A release candidate is far safer, but it is not final until Apple says it is. For most people, the right move is to wait for 26.6 to ship publicly — something the RC stage suggests is close — and to let beta 4 remain a preview for those whose job is to care.

Developers read the same calendar differently. An RC is the cue to run final compatibility checks on the current system, while beta 4 is the moment to take the autumn APIs seriously: framework churn typically slows from this point in a cycle, and apps built against the summer SDKs need real testing time before the fall release lands on customers’ devices.

For users and developers, the takeaway is straightforward. If you need stability, 26.6 is now the branch to watch. If you are testing what ships this fall, beta 4 is the new checkpoint. Apple is not choosing between them; it is closing one software chapter while still rewriting the next.