How to Keep Time Capsule Working in macOS 27: 3 Options

If you want to keep using an Apple Time Capsule after upgrading to macOS 27, you have three options: stay on macOS 26, install a community tool called TimeCapsuleSMB, or replace the hardware. This guide covers all three, including step-by-step setup for TimeCapsuleSMB, so you can make the right call before the upgrade window closes.

The core problem: macOS 27 removes AFP, the networking protocol every Time Capsule depends on, and Time Machine in macOS 27 requires SMBv2 or SMBv3, which excludes unmodified Time Capsule hardware. AppleInsider confirmed the cutoff this week. The public beta is expected around early July; release is projected for mid-September, per Eclectic Light. That's roughly three months to sort this out.

Which path fits your situation

A few facts that matter for the decision:

• AFP removal is not retroactive. Any Mac that stays on macOS 26 or earlier keeps working with Time Capsule as before, per Eclectic Light.
• Apple silicon owners who want to upgrade to macOS 27 will need a compliant backup target in place first. Without one, upgrading means losing Time Machine coverage entirely, per Eclectic Light.
• The youngest Time Capsule is 13 years old. Apple discontinued the product line in 2018, per gHacks.

Why macOS 27 breaks Time Capsule (and why Tahoe already started)

All Time Capsule models rely on AFP, the default Mac file-sharing protocol since System 6, and SMB1, the original Server Message Block version from 1987, per gHacks. AFP is gone entirely in macOS 27. SMB1 was already deprecated in macOS 26. From macOS 27 onward, Time Machine requires SMBv2 or SMBv3, which covers modern NAS hardware and shared drives on a Mac, but not any Time Capsule model. (AppleInsider; gHacks.)

This didn't arrive without warning. macOS 26 (Tahoe) introduced a subtler version of the problem first: erase a Time Capsule to start a fresh backup set, and Time Machine refuses to initialize a new backup store because it expects APFS format, which Time Capsule hardware cannot provide. Existing HFS+ backup stores kept working. New ones wouldn't create. Eclectic Light documented this earlier this year, along with a workaround that required booting into a Sequoia container to pre-create the store. Anyone who erased their Time Capsule after upgrading to Tahoe and missed that workaround lost the ability to create new backups without reverting the OS.

macOS 27 removes what's left. macOS 26 already displayed warnings about the end of support for AirPort Disk and Time Capsule disks, and AFP deprecation was flagged in macOS 15.5 release notes, per AppleInsider. macOS 27 also introduces network security requirements including TLS 1.2 or higher, ATS-compliant cipher suites, and valid certificates; Time Capsule hardware cannot meet these requirements, per gHacks and Eclectic Light.

What this means for your existing backups: Stay on macOS 26 without erasing the Time Capsule and your backup history remains intact. Switch to TimeCapsuleSMB or a replacement device and you start a new backup chain. Your existing Time Machine history stays on the Time Capsule drive and is readable on macOS 26, but it won't carry over automatically to a new destination.

Time Capsule AFP removal: should you patch or replace?

Before running any setup commands, decide which camp you're in. The install steps are only worth your time if TimeCapsuleSMB is actually the right fit.

Good candidates for TimeCapsuleSMB:

• You have a fifth-generation Time Capsule (the 2013 tower model). This is the only generation that auto-restarts the Samba server after a reboot. First through fourth-generation models require a manual activate command every time the device loses power. If your home loses power occasionally, you will periodically find your backups have silently stopped. (gHacks; GitHub.)
• Your Time Capsule has been reliable: no repeated backup failures, no drive corruption that forced a full erasure, no power supply trouble.
• You're comfortable with Terminal and community software that is actively developed but not a finished product.
• You have a second backup destination. There is no published long-term restore testing for TimeCapsuleSMB. AppleInsider was explicit about this uncertainty. Running it as your only backup is not a reasonable risk.

Skip the workaround and replace instead if:

• Your Time Capsule has a troubled history. Six Colors noted that backup failures historically forced a full drive erasure with no recovery path, and there was never a Disk First Aid equivalent for the device. Hardware already showing strain is not a good candidate for a community Samba patch.
• You have an Apple silicon Mac and plan to upgrade to macOS 27. Apple silicon owners who expect to move to macOS 27 soon have less room to postpone this decision; staying on macOS 26 is a harder long-term position for M-series machines, which will see security updates and new features land on macOS 27 first.
• You want backup infrastructure that runs without periodic manual intervention or tolerance for experimental software.

TimeCapsuleSMB setup: how to keep Time Capsule working in macOS 27

TimeCapsuleSMB, created by Microsoft engineer James Chang, installs a modern Samba server directly on the Time Capsule's ARM hardware, layering SMB3 support on top of Apple's existing firmware without modifying it. The device advertises over Bonjour, appears in Finder's Network folder, and accepts authenticated SMB3 connections that macOS 27 recognizes. Current builds ship Samba 4.24.3. (GitHub; AppleInsider.)

The tight fit is worth understanding: Time Capsule hardware has roughly 900 KB of free persistent storage and a 16 MB RAM disk, so the Samba build had to be compiled specifically for the device's ARM processor, per gHacks.

One thing to know before you start: switching to SMB via TimeCapsuleSMB begins a new Time Machine backup chain. Your existing backup history stays on the drive and remains readable on macOS 26, but the new SMB destination is treated as a fresh start.

Prerequisites confirm these before starting:

• A Mac running macOS 14 or later, or a Linux machine on the same local network
• Homebrew installed
• Python 3.9 or later
• smbclient installed
• Your Time Capsule password (retrieve it from AirPort Utility now if you're unsure it becomes the Samba login password after setup)

Setup steps:

1. Clone or download the TimeCapsuleSMB repository to your Mac. Use the repository's current Quick Start commands rather than copying steps from any article, including this one the project is under active development and the README is authoritative.
2. Install required dependencies via Homebrew; confirm Python 3.9+ and smbclient are available locally.
3. Run the Quick Start sequence from the README. Five commands handle the full deployment. Enter your Time Capsule password when prompted this becomes your Samba login password.
4. The deploy script writes its payload to /mnt/Flash on the Time Capsule (persistent, approximately 900 KB available) and creates a .samba4 folder at the root of the hard drive. Wait for deployment to complete and the device to reboot.
5. Once back online, check Finder's Network folder. Your Time Capsule should appear. If it doesn't, go to Go → Connect to Server and enter smb://<your-time-capsule-hostname>.local/<share-name>.
6. When prompted for credentials, enter any string as the username and your Time Capsule password.
7. Open Time Machine settings and select the Time Capsule share as your backup destination.

Verify before you rely on it: Force a small backup immediately after setup, then browse the resulting backup on the same Mac. Confirming the restore path works now is far better than discovering a problem when you actually need it.

Generation-specific warning: First through fourth-generation models (NetBSD 4 devices) require a manual activate command after every reboot. The Samba server does not restart on its own. Fifth-generation tower models (NetBSD 6) handle this automatically. (GitHub; gHacks.)

On authentication: Guest access is disabled. The system accepts any string as a username but validates the Time Capsule password. Fine for a home network; worth thinking carefully about in a shared office setting.

To reverse: The uninstall script removes the payload from /mnt/Flash and the .samba4 folder from the hard drive, then offers to reboot. The Time Capsule returns to factory state. (GitHub.)

Run this alongside your existing backups on macOS 26 first. No published restore-testing data exists, no long-term reliability evidence, no official compatibility matrix across generations. Treat it as a promising experiment, not a proven solution.

Replacement options and your action window

If TimeCapsuleSMB isn't the right fit, three paths cover most situations, per Six Colors:

• Attach a drive to a desktop Mac. Simplest option. USB 3.x SSDs connect at 5 to 10 Gbps and back up considerably faster than Time Capsule managed over Wi-Fi. Best for one or two Macs in a single location. Requires the host Mac to be awake when other machines need to back up not a drop-in appliance replacement, but reliable.
• Buy a NAS with Time Machine support. Modern NAS hardware speaks SMBv2/v3 natively and works with macOS 27 out of the box. More setup involved; more capability and repairability in return. The right call for households or small offices that need an always-on backup target independent of any single Mac.
• Switch backup software. Third-party tools sidestep the protocol question entirely and tend to offer better versioning, restore verification, and transparency about whether backups actually succeeded. Worth a hard look if Time Capsule's history of silent failures ever left you uncertain your backup was usable.

Your window: The public beta arrives around early July, release around mid-September, per Eclectic Light. Don't wait until then to find out your backup situation is broken.

• Before the beta: Install TimeCapsuleSMB on macOS 26 and verify it, or order replacement hardware. Either way, act now.
• Before upgrading any production Mac: Confirm your Time Machine destination is macOS 27-compatible, whether that's a verified TimeCapsuleSMB setup or a compliant replacement device.
• If you have an Apple silicon Mac: This is the urgent case. Intel Macs can hold on macOS 26 longer. M-series machines face a narrower window before deferring OS upgrades starts to cost security coverage.

The decision comes down to hardware and appetite for maintenance. Fifth-gen Time Capsule, clean track record, second backup already in place: TimeCapsuleSMB is worth trying. Aging hardware, troubled backup history, or zero tolerance for manual intervention: spend the time on a replacement instead.