Apple shipped the second public beta of macOS 27 Golden Gate on July 22, just days after developer beta 4 went out, per 9to5Mac’s release-day coverage. The public build carries the number 26A5388g — identical to this week’s developer beta — which means public testers are now running exactly the same bits as registered developers, minus the $99 membership. If you have been waiting for the beta program to settle down before putting Golden Gate on a Mac, this is the most sensible entry point so far this summer.
The installation itself takes about ten minutes of your attention and one longer unattended download. The preparation deserves more care than the install. Here is the complete process, in the order you should actually do it.
Before you touch the Beta Updates switch
Betas break things. macOS 27’s builds have been comparatively stable, but “comparatively” is doing real work in that sentence: testers have hit recurring performance and memory issues in Safari, and Apple’s under-the-hood rework of window management has made the Spaces feature unreliable in places. If your Mac earns you a living, do not put a beta on its primary volume.
Three preparation steps, none optional:
- Back up the whole machine. A Time Machine backup to an external drive is the cleanest insurance, because rolling back from a beta to the last stable macOS release requires erasing the Mac and restoring — there is no one-click downgrade. Apple’s own backup guide walks through the Time Machine setup if you have never used it.
- Check your free disk space. Beta installers for a full macOS release typically want 25–35 GB of headroom between the download and the expanded installation. If you are under 50 GB free, clear space first rather than letting the installer grind against a nearly full SSD.
- Consider a separate volume. Disk Utility can add an APFS volume alongside your main one in about a minute (Disk Utility → select your container → Edit → Add APFS Volume). Installing the beta there gives you a dual-boot setup: hold the power button at startup on Apple Silicon Macs to pick which macOS you boot. You get the new features without betting your daily environment on them.
One more sanity check: confirm the apps you depend on are known to work. Beta cycles reliably break audio drivers, VPN clients, backup agents, and anything that installs kernel or system extensions. A quick search of each vendor’s support page for “macOS 27” beats discovering the problem after the restart.
Step 1 — Enroll your Mac in the Apple Beta Software Program
Public betas flow through the Apple Beta Software Program, which is free. Open that page, click Sign Up (or Sign In if you enrolled in a previous year’s cycle), and log in with the same Apple Account your Mac uses. Enrollment is per-account, not per-device: once your Apple Account is registered, every Mac signed into it can see public beta builds.
If you enrolled in a previous beta cycle — say, for macOS Tahoe 26 — you do not need to re-enroll. Your account is still registered, and the new cycle’s builds appear automatically in the next step.
Step 2 — Turn on beta updates in System Settings
This is where the actual switch lives, and Apple has kept it in the same place it has occupied since macOS Ventura:
- Open System Settings from the Apple menu.
- Go to General → Software Update.
- Click the small ⓘ (info) button next to “Beta Updates.”
- In the dropdown at the top right of the panel that appears, select macOS 27 Golden Gate Public Beta.
- Click Done.
The Software Update pane will refresh and, after a few seconds, offer the macOS 27 public beta 2 as an available update. If the dropdown only shows “Off” and no beta options, the usual culprit is an Apple Account mismatch — check that the account shown in the Beta Updates panel is the one you enrolled at beta.apple.com, and that you are signed into it under System Settings → Apple Account.
Step 3 — Download and install
Click Update Now (or Upgrade Now, if you are coming from macOS Tahoe 26 rather than an earlier Golden Gate beta) and let the download run. The full installer is a multi-gigabyte pull, so the download time depends almost entirely on your connection; the installation and restart phase afterward typically takes 20–40 minutes depending on the Mac.
The Mac will restart at least once, sit on a progress bar longer than feels comfortable, and eventually land on the Golden Gate login screen. First login after a major beta also triggers several minutes of background reindexing — Spotlight, Photos analysis, and the new Siri content indexing all rebuild — so give the machine an hour before judging its performance.
What you actually get in public beta 2
Golden Gate’s headline is the new Siri app and the rebuilt Siri AI experience. After the assistant indexes content from Messages, Mail, and other apps, it can answer questions about your own data and act on multi-step requests. The standalone app keeps your conversation history in one place, which changes Siri from a fire-and-forget voice command into something closer to a running session.
Beyond Siri, the build public testers receive includes the changes developers have been living with through four developer betas:
- Search overhaul. Spotlight became noticeably unreliable on macOS Tahoe 26; the ground-up rework Apple did to prepare for Siri AI has largely fixed it in Golden Gate, though results can still vary while indexing settles.
- Liquid Glass refinements. The translucency effect that divided opinion on Tahoe 26 has been tuned, and windows now use a unified corner radius rather than varying by app and content.
- Smarter automation tools. Safari gains an extension builder that generates extensions from natural-language descriptions, and Shortcuts can now build a shortcut from a plain-English prompt instead of the manual block-by-block editor.
- Writing tools and Visual Intelligence. Apple Intelligence’s writing tools have been redesigned and are more efficient, and Visual Intelligence recognition has improved across the system.
- iPhone Mirroring flexibility. The mirroring window now supports more aspect ratios — widely read as groundwork for iOS apps on future foldable hardware.
Apple’s own macOS 27 Golden Gate preview page has the full feature rundown if you want the complete marketing-grade list before committing.
Known rough edges in this build
Two issues have followed the beta cycle from the developer builds into the public ones. First, Safari can develop performance and memory pressure over long sessions — if the browser gets sluggish, quitting and relaunching it recovers the memory. Second, Spaces (Mission Control’s multiple desktops) can behave unpredictably: desktops occasionally reorder or forget window assignments after waking from sleep. Neither is data-threatening, but both are worth knowing about before you move your daily workflow over.
Report anything else you hit through the Feedback Assistant app, which comes preinstalled on beta builds. Public beta feedback genuinely does get triaged — it is the entire point of the program.
Public beta vs. developer beta: which channel should you ride?
Because public beta 2 and developer beta 4 are the same build (26A5388g), the practical difference between the two channels this cycle is timing, not content. Developer builds arrive first — usually by several days to a week — and occasionally ship rougher, since Apple uses the developer channel to catch the worst regressions before promoting a build to public testers. The public channel effectively gives you Apple’s pre-filtered picks of the developer builds.
The dropdown in the Beta Updates panel actually lists both options if your Apple Account is registered as a developer, and you can switch channels at any time without reinstalling — the Mac simply waits for the next build offered on whichever channel you selected. For anyone whose goal is “see the new Siri and the Golden Gate redesign before fall,” the public channel is the right ride: fewer updates to babysit, fewer regressions, and you still end up on the identical final release.
If a build refuses to appear after switching channels, two fixes cover nearly every case: toggle Beta Updates off and back on, or sign out and back into your Apple Account under System Settings. Both force the update catalog to refresh.
How to leave the beta program
If Golden Gate is not working out, you have two exits, one easy and one thorough:
- Stop receiving betas (easy). Go back to System Settings → General → Software Update, click the ⓘ next to Beta Updates, and set it to Off. Your Mac stays on the current beta build but will only update to release versions from then on — meaning you simply wait until the final macOS 27 release ships in the fall and update onto the stable channel.
- Roll back now (thorough). Erase the Mac and restore from the Time Machine backup you made before installing, or reinstall the current stable macOS via macOS Recovery and migrate your data back. This is the disruptive path — which is why the backup in step one was not optional.
For most people who install public beta 2, the sensible plan is the first one: ride the remaining summer builds, file feedback when something misbehaves, and arrive at the fall release already settled in. The same enrollment covers the release-candidate builds, so you will land on the final macOS 27 the day it ships — a few weeks ahead of the people who waited.
