The Evolution of Safari's Feature Release Cadence

The Safari web browser has significantly transformed its update schedule over the past several years, moving away from a rigid annual cycle to a dynamic year-round release model. Historically, new web platform features were locked behind major autumn operating system updates for iOS and macOS. Today, Apple utilizes frequent point releases throughout the year to deliver new CSS, HTML, and JavaScript capabilities continuously, ensuring faster innovation for developers and a more consistent web experience for users.

The Legacy Annual Cycle

For over a decade, Safari's feature updates were strictly tied to Apple's major operating system schedule. Announced at WWDC in June and released to the public in the fall, Safari only received new web standards once a year. Minor updates throughout the year (such as X.1 or X.2 releases) were reserved almost exclusively for security patches, stability improvements, and critical bug fixes.

This slow pace created a bottleneck for the web development community. While browsers like Chrome, Firefox, and Edge adopted "evergreen" update models—shipping new features every four to six weeks—developers often had to wait up to a year for Safari to support modern web APIs.

Transition to Feature-Packed Point Releases

Starting notably with the Safari 14 and Safari 15 cycles, Apple fundamentally changed its deployment strategy. Recognizing that the modern web moves too fast for annual updates, the WebKit team began bundling new web platform features into minor OS updates.

Under this evolved cadence, point releases—especially spring updates like Safari 15.4, 16.4, and 17.4—became massive feature drops in their own right. These mid-cycle updates now routinely rival the main ".0" autumn releases in the sheer volume of new web technologies, developer tools, and APIs they introduce.

The Role of Safari Technology Preview

This shift to continuous delivery was largely enabled by the groundwork laid by Safari Technology Preview. Introduced in 2016, this standalone version of the browser receives updates roughly every two weeks, showcasing the latest additions to the WebKit engine.

By using Safari Technology Preview as a live testing ground, Apple established a pipeline for continuous integration and developer feedback. Once experimental features are stabilized in the preview build, Apple no longer holds them back until the fall; instead, they are merged directly into the next scheduled iOS and macOS point release.

Influence of the Interop Project

The push for year-round feature releases was further accelerated by the Interop project—a cross-browser benchmark collaboration between Apple, Google, Microsoft, and Mozilla that began in 2022. The goal of Interop is to ensure that web technologies work identically across all major browsers.

Because Interop tracks browser compatibility scores continuously throughout the calendar year, relying on a single annual release would leave Safari lagging behind for months at a time. Shipping features in winter and spring point releases allows Apple to steadily resolve compatibility issues and address developer pain points rapidly.

The Modern Release Cadence

Today, web developers can expect four to six significant feature updates to Safari every year. Following the major autumn release, Apple consistently delivers substantial web platform additions in its late fall, winter, and spring OS updates. Furthermore, Apple makes these new Safari versions available as standalone updates for the previous two major versions of macOS. While Safari's distribution remains tied to operating system updates on iOS, decoupling web features from the annual OS overhaul has effectively turned Safari into a modern, continuously advancing browser.