Time Machine over Wi-Fi vs Ethernet vs Cloud

Every Mac user with more than one drive eventually asks the same question: should Time Machine back up over Wi-Fi, over Ethernet, or to the cloud? The answer is rarely a clean one — it depends on how much data you have, how often you change it, what you are willing to spend, and what kind of failure you are most worried about.

This article gives you the honest version: the theoretical bandwidth, the real-world numbers, the way each setup tends to fail, and the hybrid setup that most experienced Mac users eventually settle on.

The Bandwidth Math (Theory vs Reality)

Backup speed has two ceilings: how fast your network can move bits, and how fast your destination can write them. For Time Machine, the network is almost always the limit. Here is what each common transport actually delivers in practice.

Wi-Fi 5 (802.11ac)

The marketing number is 866 Mbps for an 80 MHz channel with two spatial streams, or 1.3 Gbps with three streams. The number you actually see on a Mac in an average home is closer to 300 to 450 Mbps for sustained transfer, depending on distance from the access point, interference, and how many other devices are on the same band. Older Wi-Fi 5 client chips, or AC1200-class routers, can drop closer to 200 Mbps.

Wi-Fi 6 (802.11ax)

Marketing numbers up to 1.2 Gbps per stream. Real-world sustained throughput on a modern MacBook is typically 700 to 900 Mbps in the same room as the access point, dropping to 400 to 600 Mbps a couple of walls away. Wi-Fi 6 also handles dense environments much better than Wi-Fi 5 — useful if you live in an apartment building where the 5 GHz band is crowded.

Wi-Fi 6E and Wi-Fi 7 (6 GHz band)

Wi-Fi 6E adds the 6 GHz band, which is currently mostly empty, so real-world throughput in good conditions can approach 1 Gbps. Wi-Fi 7 adds 320 MHz channels and multi-link operation, with real Mac throughput of 1.5 to 2 Gbps in ideal conditions. The catch: range on 6 GHz is shorter than 5 GHz, so you typically need to be in the same room.

Gigabit Ethernet

Sustained throughput of about 940 Mbps after protocol overhead. This is the floor everyone should aim for if they are doing serious local backups. It is consistent, low-latency, and immune to Wi-Fi's usual problems. A USB-C to Ethernet adapter for a MacBook costs less than the time you will save on a single big backup.

2.5 GbE and 10 GbE

If you have a NAS with 2.5 GbE or 10 GbE and a Mac that supports it (some Mac mini, Studio and Pro models ship with 10 GbE), you can saturate the destination disk rather than the network. For Time Machine, this rarely matters in incremental mode — there is just not that much data to move every hour. It does matter for the initial backup of a 1 TB+ machine.

Typical home fibre uplink

Cloud destinations are limited by your upload bandwidth, which is what almost everyone forgets. Common consumer plans:

• Cable / VDSL: 10 to 50 Mbps up
• Mid-tier fibre: 100 to 300 Mbps up
• Symmetric gigabit fibre: 1 Gbps up
• Mobile hotspot / tethering: 5 to 30 Mbps up, often capped or throttled

That 1 Gbps symmetric fibre line is, for cloud backup purposes, basically as fast as Gigabit Ethernet to a local NAS. If you have one, the local-vs-cloud speed argument disappears.

How Time Machine Actually Backs Up

Before we look at numbers, it helps to know what Time Machine is doing on the wire. The behaviour is different in important ways depending on the destination.

Initial full backup vs incrementals

The first backup is a complete copy of every file Time Machine considers eligible. After that, every hourly backup writes only the changed files (and changed APFS extents on a directly attached APFS destination). For most users, daily change is in the range of a few hundred MB to a few GB — small enough that even a slow connection finishes in minutes.

APFS snapshots and "thinning"

On an APFS-formatted destination directly attached to your Mac, Time Machine uses APFS snapshots. These are extremely efficient — only changed blocks are written, and old snapshots are "thinned" automatically as space gets tight. Network Time Machine destinations (including all cloud destinations) cannot use APFS snapshots directly; they use a sparsebundle disk image that contains an APFS volume.

SMB3 vs AFP (legacy)

AFP, Apple Filing Protocol, was the original Mac network file protocol. It is deprecated, no longer the default in macOS, and noticeably slower than SMB3 for Time Machine workloads. SMB3 is what every current cloud Time Machine service uses, and what every modern NAS supports as the recommended protocol. SMB3 also brings native encryption-in-transit, which is essential for cloud destinations.

Sparsebundle bands and chunking

The sparsebundle format that Time Machine uses on a network destination is a folder of small "band" files, typically 8 MB each. As the backup grows, more bands are created. This design lets the sparsebundle grow without rewriting the whole image and lets backups resume after a disconnect. The downside: a bad write at the wrong moment can leave a band file in an inconsistent state. Robust SMB3 servers and well-handled reconnect logic minimize this. Cheap consumer NAS firmware, frequent Wi-Fi drops, or Macs that sleep mid-write maximize it.

Real-World Initial Backup Times

Here is what the bandwidth math actually means in time, for the initial Time Machine backup, on a typical Mac. These numbers assume the destination disk can keep up with the network — which is true for any modern SSD-backed NAS or any cloud SMB destination, but may not be true for an old USB 2 spinning disk.

250 GB initial backup

Transport	Effective throughput	Estimated time
Wi-Fi 5, room next door	~250 Mbps	~2.4 hours
Wi-Fi 6, same room	~800 Mbps	~45 minutes
Gigabit Ethernet	~940 Mbps	~38 minutes
Cloud, 50 Mbps up	~45 Mbps	~13 hours
Cloud, 300 Mbps up	~270 Mbps	~2.2 hours
Cloud, 1 Gbps symmetric	~900 Mbps	~40 minutes

500 GB initial backup

Transport	Effective throughput	Estimated time
Wi-Fi 5, room next door	~250 Mbps	~4.7 hours
Wi-Fi 6, same room	~800 Mbps	~1.5 hours
Gigabit Ethernet	~940 Mbps	~1.25 hours
Cloud, 50 Mbps up	~45 Mbps	~26 hours
Cloud, 300 Mbps up	~270 Mbps	~4.4 hours
Cloud, 1 Gbps symmetric	~900 Mbps	~1.3 hours

1 TB initial backup

Transport	Effective throughput	Estimated time
Wi-Fi 5, room next door	~250 Mbps	~9.5 hours
Wi-Fi 6, same room	~800 Mbps	~3 hours
Gigabit Ethernet	~940 Mbps	~2.5 hours
Cloud, 50 Mbps up	~45 Mbps	~52 hours
Cloud, 300 Mbps up	~270 Mbps	~9 hours
Cloud, 1 Gbps symmetric	~900 Mbps	~2.6 hours

Two things jump out. First, Wi-Fi 6 in good conditions is genuinely competitive with Gigabit Ethernet for backups. Second, fast symmetric fibre makes cloud backup competitive too — the "cloud is too slow" argument is a 2014 argument, not a 2026 one.

The other thing worth saying out loud: this is the longest backup you will ever run. Every hourly backup after the first is small enough to finish in seconds to a few minutes on any of these transports. The choice between Wi-Fi, Ethernet, and cloud is overwhelmingly about the first backup and about reliability — not about everyday performance.

Reliability and Failure Modes

Speed is the part everyone obsesses over. Reliability is the part that matters more.

Wi-Fi: packet loss and sparsebundle corruption

Wi-Fi backups are convenient but fragile. The failure modes that bite real users:

• Roaming between access points mid-backup, momentarily losing the SMB connection
• The MacBook lid closing, putting the Mac to sleep mid-write
• Microwave ovens, baby monitors, or neighbours' networks introducing 2.4 GHz interference
• Cheap consumer routers dropping older client connections under load

None of these usually destroys a backup. Time Machine is generally good at recovery. But over months, the chance of a sparsebundle ending up in an unrepairable state on a Wi-Fi-only NAS is meaningfully higher than on Ethernet.

Ethernet: rock-solid, what to watch for

Ethernet is the most reliable Time Machine transport. Cable problems are the only common issue: a damaged cable, a bad port on a cheap switch, or a mismatched negotiation that drops to 100 Mbps. ifconfig en0 in Terminal will tell you the actual link speed; if it does not say 1000baseT or higher on a Gigabit setup, the cable or switch is the problem.

The other thing to watch: power-saving on USB-C Ethernet adapters. Some adapters drop the link when the Mac sleeps and do not always recover cleanly on wake. If you see backups failing right after a sleep cycle, this is usually why.

Cloud: SMB3 reconnect, resume on disconnect

Cloud Time Machine destinations are surprisingly robust because they have to be — every consumer internet connection drops occasionally. A well-built cloud SMB service handles this with proper SMB3 session reconnect, server-side write-ahead logs, and clean handling of partial writes. Capsule Backup, for example, handles this transparently — if your Mac drops off Wi-Fi mid-backup, it picks up where it left off when it reconnects, with no sparsebundle damage.

The cloud failure mode is different: ISP outages, captive portals on hotel Wi-Fi, or providers that have not implemented SMB3 reconnect properly. Choose a provider that has, and these stop being problems.

When Each Option Makes Sense

If you have to pick just one transport, here is when each is the right answer.

• Wi-Fi to a local NAS: When you have a Wi-Fi 6 or 6E router, the NAS is a few rooms away, and you back up a desktop or stationary MacBook. Acceptable for under-500 GB Macs. Avoid if you back up a heavily mobile MacBook that sleeps and roams constantly.
• Ethernet to a local NAS: When you back up a desktop Mac (mini, Studio, iMac) or a MacBook used at a fixed desk. Best raw speed and reliability. Requires you to plug in.
• Cloud-only: When you travel, work from many locations, or simply do not want to own a NAS. With a fast symmetric upload, cloud is essentially as fast as a local NAS. With a 50 Mbps upload, the initial backup is slow but subsequent backups are unnoticeable.

For more on choosing the right destination for your workflow, see our setup guide.

The Hybrid Setup: Multiple Time Machine Destinations

You do not actually have to choose. Since macOS Sierra, Time Machine has supported multiple destinations natively, rotating through them automatically.

How macOS multi-destination works

In System Settings > General > Time Machine, you can add as many backup disks as you want. Each hourly backup goes to one destination, in rotation. Over time, every destination ends up with the full backup history. If one destination goes offline (say, your NAS is down or your laptop is away from home), the others keep going.

The recommended hybrid: local NAS plus cloud

The setup most experienced Mac users converge on:

• Local NAS over Ethernet — the fast everyday destination. Restores are instant. The first backup finishes in an evening.
• Cloud SMB destination — the offsite copy. Survives theft, fire, flood, and ransomware that takes out your local network. Slow on the first backup, invisible afterwards.

This satisfies the 3-2-1 rule (three copies, two media, one offsite) without you doing anything beyond pointing Time Machine at both destinations and letting macOS do the rest.

Rotation cadence and what to expect

Time Machine alternates between destinations on each hourly backup. So if you add two destinations at noon, the noon backup goes to destination A, the 1 pm backup goes to destination B, and so on. Over the course of a day, both destinations see most of the same data, with at most an hour of lag.

The initial backup runs separately on each destination. If you add the cloud after a year of local-only Time Machine, the cloud has to start from scratch — Time Machine cannot copy backup history from one destination to another.

What About Backup for Specific Use Cases?

Some workflows have their own answers.

Video editors and creatives

If you work with multi-TB Final Cut or DaVinci Resolve projects, Wi-Fi is rarely enough and even Gigabit Ethernet starts to feel slow. 10 GbE to a local NAS is the answer for the working set; cloud Time Machine is the offsite tier. We go deeper on this on our page for creatives.

Developers

Developers tend to have small "real" data and enormous caches (node_modules, Xcode build folders, Docker volumes, virtual machines). The right answer is usually exclude the caches in Time Machine settings, then back up whatever is left to whichever destination is convenient. With small data, even a 50 Mbps upload to the cloud is fine.

Households with multiple Macs

One NAS plus one cloud subscription with unlimited devices is hard to beat. Each Mac points at both destinations; you get fast local restores and survivable offsite. See our pricing for what unlimited devices actually means.

Putting It All Together

The honest summary is simple. Ethernet is the fastest and most reliable single transport. Wi-Fi 6 is "fast enough" for most Macs if you do not roam mid-backup. Cloud is the right answer if you travel, want offsite survivability, or have a fast symmetric uplink. And the strongest setup is not picking one — it is letting Time Machine alternate between a fast local destination and a cloud destination so you have both speed and survivability.

The most common mistake we see is people optimising for first-backup speed and ignoring reliability. The first backup is one evening. The next ten years of incremental backups are the actual product. Pick the destination you will trust on year three when the only thing that matters is whether the restore works. For more on the security model behind cloud Time Machine, see our security overview, and for the cloud-vs-iCloud comparison see our iCloud comparison.