How Often Apple Updates Safari Technology Preview

This article explains the update schedule for Apple's Safari Technology Preview, detailing how frequently web developers and designers can expect new releases. It also covers what these updates typically contain, how the release cycle aligns with the WebKit project, and the simplest method for installing the latest builds.

Apple releases updates to Safari Technology Preview approximately every two weeks. While the company does not adhere to a rigid day of the week for every launch, this bi-weekly cadence has remained highly consistent since the standalone browser was first introduced in March 2016.

Occasionally, this two-week schedule may experience minor delays. Pauses in the release cycle typically happen around major holidays, during Apple's Worldwide Developers Conference (WWDC), or right before the public launch of a new macOS version. Outside of these rare exceptions, developers can reliably expect two updates per month.

The primary reason for this rapid, bi-weekly release schedule is to bridge the gap between the open-source WebKit engine and the public version of Safari. Each update packages the latest revisions made by Apple engineers to WebKit over the preceding fortnight. This allows developers to test bleeding-edge implementations of HTML, CSS, JavaScript, and Web APIs well before they are rolled out to the general public in major macOS and iOS updates.

In addition to new web standards, each two-week cycle brings improvements to the Safari Web Inspector, performance optimizations, and critical bug fixes based on developer feedback.

Keeping up with this frequent update schedule requires very little effort. Once Safari Technology Preview is installed via the Apple Developer website, all subsequent bi-weekly updates are delivered directly through the standard macOS Software Update mechanism located in System Settings. Because it operates as a completely separate application from the default Safari browser, developers can install these frequent updates without risking the stability of their primary browsing environment.