Apple has now announced macOS 27 Golden Gate for this fall. The preview centers on Siri AI, broader Apple Intelligence features, faster AirDrop and network file browsing, and smaller changes across Mail, Safari, and the system. None of that changes the practical upgrade question: will the Mac and the apps you rely on be ready?
The difference between those groups is rarely luck. It's an afternoon of boring preparation, done in June while nothing is on fire. Here's the checklist I run on my own Macs every summer, in order.
Check Apple's official support list
Apple's official compatibility list is short and clear. macOS 27 supports the 2026 MacBook Neo, MacBook Air and MacBook Pro models with Apple silicon from 2020 onward, iMac models with Apple silicon from 2021 onward, Mac mini models with Apple silicon from 2020 onward, Mac Studio models from 2022 onward, and the 2023 Apple silicon Mac Pro.
Open the Apple menu and choose About This Mac to confirm the model and chip. The important dividing line is Apple silicon. Apple's current list does not include Intel Macs, even when they can run macOS 26.
If your Mac is not on the list, keep using the newest macOS version Apple offers for it and keep automatic security responses enabled. An unsupported major upgrade is not worth turning a dependable work machine into an experiment.
Make a backup you have actually restored from
An untested backup is a theory.
Every October I hear from someone whose Time Machine drive quietly stopped backing up in spring, and who discovered that fact at the worst possible moment. So before any major upgrade, I want two layers:
- Time Machine, to an external drive or a NAS. Check it under System Settings, General, Time Machine, and look at the date of the last backup. It should say today or yesterday, not three months ago.
- One more copy somewhere else. Either a full clone of your data to an external SSD with Carbon Copy Cloner, or continuous cloud backup with Backblaze. On Apple silicon a truly bootable clone is mostly a relic (the signed system volume made those fragile years ago), but a complete data clone still earns its keep: if the internal disk dies mid-install, everything you care about exists on a drive in your hand.
Then the step almost everyone skips: restore something. Pick one file, open Time Machine from the menu bar, go back a day, and bring it back. Confirm it opens. That's two minutes, and if those two minutes fail, you just found the problem in June instead of during a broken upgrade in October.
The same afternoon list from this guide, in tappable form.
Inventory the apps you depend on
Write down the apps you would be genuinely upset to lose for a week. Not everything installed, just the load-bearing ones. For most people that's five to ten items: the password manager, the backup tool, a couple of menu bar utilities, maybe an audio interface driver or a VPN.
Now check each developer's website or release notes for a compatibility statement. The usual suspects for breakage are apps that install system extensions, hook into audio, or draw over other apps, because those touch the parts of macOS that change most between versions. Droppy's own macOS 27 readiness landed in its 14.1 release, so if it's on your list, that box is already ticked.
Two more things while you're in inventory mode. First, dig up your license keys and make sure they live somewhere that isn't only this Mac. Second, for any app that hasn't shipped an update since 2023 or so, treat the silence as an answer: assume it breaks, and start auditioning a replacement now rather than mid-upgrade.
Free up 30 to 50 GB before install night
The installer alone is a double-digit gigabyte download, and the upgrade process wants generous working room on top of it. My rule: 30 GB free at minimum, 50 GB if you want the whole thing to be a non-event. Check where you stand under System Settings, General, Storage.
The space usually hides in the same few places. Old iPhone and iPad backups sit in that same Storage pane, often several full device images deep. The Downloads folder collects disk images you mounted exactly once. The Trash you've been meaning to empty counts too. And if you're a developer, your simulator runtimes and derived data are probably worth more than all of the above combined.
Don't cut it close. An installer that runs out of disk space partway through is usually recoverable, but recovering it is precisely the kind of evening this post exists to prevent.
Screenshot your settings
Major upgrades occasionally reshuffle the furniture. Login items get re-prompted, extensions get disabled pending approval, and menu bar icons come back in a different order. None of it is data loss. But reconstructing how you had things arranged, from memory, three weeks later, is quietly one of the most annoying parts of any upgrade.
So spend five minutes with ⌘⇧3 for the whole screen or ⌘⇧5 for a selection, and capture:
- System Settings, General, Login Items & Extensions, both halves of it
- The menu bar, the entire strip, so you know what ran there and in what order
- The Dock and your Finder sidebar
- Displays settings, if you've tuned a multi-monitor arrangement
The menu bar shot tends to pay for itself twice, because it's also the moment you notice how much is running up there. If half the icons make you go "what even is that", the menu bar cleanup guide is a better use of your afternoon than any OS update. And if your setup involves an external monitor with carefully arranged spaces, I've covered MacBooks and external displays separately.
The honest case for waiting for 27.1
Here's the paragraph most upgrade guides won't write: if your Mac earns your living, don't install macOS 27 in week one.
Not because .0 releases are disasters. The large majority of people who upgrade on day one are completely fine. But every year, some slice of users hits something real: an audio driver that stops passing signal, a printer that vanishes, a niche but essential app that crashes on launch. If your machine is how invoices get paid, the rational move is to let other people find those bugs for you. The .1 release typically follows within a couple of months, with the loudest problems fixed.
Weigh what's actually on each side of the trade. Waiting costs you a few weeks without features you've lived without for years. Upgrading early risks, however slightly, being the person whose Tuesday deadline collides with a fresh OS bug. That trade isn't close.
I run new macOS versions early myself, but that's because testing Droppy against them is literally the job. If it weren't, I'd wait.
If you must run the beta
Every summer, some of us can't resist. Fine. Two rules.
Never on your main Mac. Not "probably not". Never. Betas exist so bugs can be found, and the early ones find plenty.
Use a separate volume. Open Disk Utility, select your internal drive, and add a new APFS volume with the plus button in the toolbar. APFS volumes share free space with the rest of the disk, so you're not carving out a fixed partition. Install the beta there, and on Apple silicon, hold the power button at startup to choose which system to boot. Your daily macOS stays untouched on its own volume.
One trap that catches people even with a separate volume: data formats. Signing in to iCloud on a beta can migrate things like your Notes or Photos library to a newer format that the current OS can't read back. Keep iCloud sign-in minimal on the beta side, or use it with a spare account, and you avoid the one beta problem that leaks back into your real setup.
Boring upgrades are earned
None of this is exciting. That's the point.
The whole list is one afternoon, and most of that is waiting on a backup to finish while you do something else. Run through it in June and the fall release becomes exactly what it should be: you click a button, something downloads, and an hour later you have a slightly newer Mac and no story to tell. The people with stories are the ones who skipped the checklist.