Guide

Does Time Machine work with a NAS?

Short answer: yes, under specific conditions — and those conditions got more fragile in 2026. Here's the complete, current picture, including what broke and what to check before you rely on it.

Updated August 9, 2026.

Quick answer

Yes — Time Machine can back up to a third-party NAS, but only one that explicitly supports "Time Machine over SMB." Synology, QNAP, UGREEN, and TrueNAS all ship this as a built-in feature. It does not work reliably over the older AFP protocol anymore, and 2026 has added some new fragility of its own. Details below.

The AFP deprecation timeline

AFP (Apple Filing Protocol) has been part of the Mac since the 1980s, and Apple has been walking away from it for years. Time Machine backup over AFP is already discouraged: Apple has stated that it "is not recommended and won't be supported in macOS 27 or later." macOS 27, code-named "Golden Gate," has been in public beta since July 2026, with a final release expected around September 2026 — and it removes the AFP client from macOS entirely.

That has a real consequence for old hardware, too: it ends support for AFP/SMBv1-only devices like the original Time Capsule and AirPort Extreme for good. If you're still backing up to one of those, macOS 27 is the point where that stops working outright, not just gets discouraged.

The 2026 SMB turbulence

It's widely reported — this isn't from Apple's own release notes, but it's a consistent account that's been corroborated widely across the Mac and NAS community — that macOS Tahoe 26.4 tightened SMB's default signing behavior at the same time as a separate credential-handling bug shipped. Together, the two broke a lot of existing Time Machine-to-NAS backups on Synology, QNAP, UGREEN, and TrueNAS devices alike, often surfacing as an error to the effect of "the backup disk image ... was ejected."

The workaround that circulated was manually editing /etc/nsmb.conf in Terminal to relax the new signing requirement — not something a mainstream user should have to do to keep a backup running. It's widely reported as resolved in macOS 26.5, so if you're on an earlier point release and seeing ejection errors, updating is the first thing to try. The honest lesson here isn't "NAS backups are broken" — it's that Time Machine's NAS support has real, recurring fragility tied to Apple's own protocol changes, not just to user error or to any one NAS vendor.

The older problem: sparse bundle corruption

This one predates 2026 by a decade or more, and it's separate from the SMB issue above. A Time Machine backup to a network destination doesn't live as plain files — it lives inside a single, growable "sparse bundle" disk image sitting on the share. That container has a long, well-documented history as a corruption vector: an interrupted backup, a network hiccup, or an unexpected disconnect can damage the bundle, and Time Machine's response is the familiar, unwelcome "Time Machine must create a new backup for you" — discarding accumulated history and starting over.

Long-time NAS-backup users have seen that message more than once. It's a structural property of how Time Machine stores network backups, not a one-time bug that got fixed.

What your NAS (and your Mac) actually need

To get a working Time Machine-over-SMB setup, three things need to be true at once:

Time Machine support has to be explicitly turned on in the NAS. This isn't the same as generic SMB file sharing — each vendor names and exposes it differently in their own admin interface. Synology, QNAP, and UGREEN each have a dedicated Time Machine option buried in their sharing or backup settings, and TrueNAS exposes it through its SMB share configuration.
SMB3 has to be the protocol version actually negotiated. Older SMB1/SMB2-only configurations aren't a reliable path for Time Machine anymore, on top of being a security downgrade generally.
Bonjour / network discovery has to be enabled on the Mac's network. This one catches people out: without it, the NAS share can be perfectly visible and mountable in Finder, and still never show up in Time Machine's own destination picker — Time Machine finds destinations through Bonjour, not through Finder's network browser.

Where a plain mirror fits

Time Machine and a mirror tool aren't really competing for the same job. Time Machine's job is point-in-time recovery of your whole Mac — go back to how a file, or the whole system, looked on some earlier date. A mirror's job is smaller and different: keep a plain, always-current, Finder-browsable copy of the specific folders you care about most, sitting on a NAS or drive, with none of the sparse-bundle-container or SMB/AFP protocol history above to track. A mirror is just files, copied over the network — not a special disk image.

That's the gap ThirdCopy sits in: a one-way mirror to a NAS or external drive, continuous by default, with no disk image, no protocol negotiation to babysit, and nothing to interpret if a run gets interrupted — worst case, the next run just catches up. It isn't a replacement for Time Machine's version history, and it isn't trying to be. For the full feature-by-feature picture, see ThirdCopy vs. Time Machine. Many people are best served running both: Time Machine for "what did this look like before," a mirror for "give me an ordinary, always-current copy I can browse without Time Machine at all."

Questions

Can Time Machine back up to a NAS?

Yes, if the NAS explicitly supports "Time Machine over SMB" — Synology, QNAP, UGREEN, and TrueNAS all build this in as a named feature you turn on in the NAS's own admin interface. Generic SMB file sharing without that explicit Time Machine support usually will not appear as a valid Time Machine destination, and the older AFP protocol is no longer a reliable path at all.

Why did my Time Machine NAS backup suddenly stop working in 2026?

This is widely reported to trace back to macOS Tahoe 26.4, which tightened default SMB signing behavior and shipped alongside a separate credential-handling bug — together they broke many existing Time Machine-to-NAS setups on Synology, QNAP, UGREEN, and TrueNAS devices, often with errors like "the backup disk image ... was ejected." A manual /etc/nsmb.conf edit circulated as a workaround; the underlying issue is widely reported as resolved in macOS 26.5, so updating is the first thing to try.

Will Time Machine still work with my NAS after macOS 27?

For any NAS using modern SMB with explicit Time Machine support — Synology, QNAP, UGREEN, TrueNAS — yes, that path isn't going away. What macOS 27 removes is the AFP client entirely, which Apple has already said won't support Time Machine going forward; it also ends the road for older AFP/SMBv1-only hardware like Time Capsule and AirPort Extreme.

Is Time Machine enough on its own?

For most people, Time Machine plus one more copy is safer than Time Machine alone. Time Machine gives you point-in-time version history of your whole Mac, but it's also the thing most exposed to the AFP/SMB protocol churn described above, and its sparse-bundle backup format has a long history of occasional corruption on network destinations. A plain, Finder-browsable mirror of your most important folders — on a NAS, an external drive, or both — is a simpler second copy that doesn't depend on any of Time Machine's network plumbing.

Try ThirdCopy free for 14 days — no card required.

Then $19.99 once. No subscription.

Time Machine, AFP, and macOS are trademarks of Apple Inc. Synology, QNAP, UGREEN, and TrueNAS are trademarks of their respective owners. ThirdCopy is made by Embay, LLC and is not affiliated with or endorsed by Apple or any NAS vendor named above. The macOS 26.4/26.5 and macOS 27 details above reflect widely reported, aggregated research as of the "Updated" date; confirm current behavior against Apple's own release notes before relying on it for a critical backup.