Time Machine backup sizes swing after the macOS Tahoe 26.6.2 update (August 22, 2026)
Chapters
TL;DR
Time Machine backup sizes on macOS Tahoe 26.6.2 swung sharply in the three days right after the update was installed, according to The Eclectic Light Company on August 22, 2026. Across nine days of measurement the container on the backup SSD grew steadily at a little over 10 GB per week, but 2026-08-17 to 2026-08-19 produced large transient changes that the backed-up data does not explain. Apple has not acknowledged this, no cause has been established, and there is no fix as of August 22, 2026.
- Measured growth was just over 10 GB per week on one backup container, steady until the 26.6.2 update went in on 2026-08-17.
- The large swings fall on 2026-08-17 to 2026-08-19, and very little in the Data volume being backed up should have changed because of a security update.
- Nothing tells you which files drove the spike, and the measurement reads only locally mounted APFS volumes.
- This is one Mac and one nine-day window, presented by its author as meriting further examination rather than as a confirmed defect.
- There is no published workaround beyond sizing backup storage for a spike you cannot account for.
What was measured
The test machine is a Mac mini M4 Pro running macOS Tahoe 26.6.2, backing up hourly to an external 2 TB SSD. The Eclectic Light Company measured used space in disk7, the single container on that backup SSD, from 2026-08-11 to 2026-08-20. The update to 26.6.2 went in on 2026-08-17, in the middle of that window.
Used space grew slowly across the nine days, at an overall rate of just over 10 GB per week. That part is unremarkable for a machine backing up every hour. What stands out is 2026-08-17 to 2026-08-19, where the figures show large transient changes that coincide with the update going in.
| Measurement | Value |
|---|---|
| macOS version | macOS Tahoe 26.6.2 |
| Mac | Mac mini M4 Pro |
| Backup target | External 2 TB SSD, hourly backups |
| Window measured | 2026-08-11 to 2026-08-20 |
| Steady growth | Just over 10 GB per week |
| Update installed | 2026-08-17 |
| Large transient changes | 2026-08-17 to 2026-08-19 |
Why a security update should not move the backup size
macOS Tahoe 26.6.2 is a security update. The author's point is the mismatch between the two sizes: 'precious little in the Data volume being backed up should have changed as a result of that update', so a backup that suddenly claims or releases a large amount of space is reporting something other than the size of what changed.
That matters because backup sizing is what people plan around. If installing a security update can move the used-space figure on a backup volume by an amount nobody can attribute, the figure stops being a measure of your own data.
What this measurement cannot tell you
No cause is established. Nothing in the piece names a process, a file or a Time Machine behavior as the source of the swings, and Apple has said nothing about it. The author flags the post-update spike as meriting further examination, which is the honest description of where this stood on August 22, 2026.
The measurement has a hard limit as well. The readings come from DeltaFree, and only locally mounted APFS volumes can be read, so backups to a NAS, to other networked storage or to an HFS+ volume cannot be measured this way at all. There is also no user-facing way to see which files drove the spike, which is why the space cannot be attributed.
A quiet day for Mac bug coverage
This is a thin story and I would rather say so than dress it up. 9to5Mac published seven pieces on August 22, 2026, a Saturday, covering a Pixel 11 camera feature, a tvOS indie app, a touchscreen MacBook rumor, iPhone 18 Pro event dating, an Apple @ Work column on AI Mac management, a poll and weekend deals. None of them touch a macOS bug, a security issue or a system update, and no new macOS development appeared that day.
So the day's macOS finding is this measurement: one Mac, published the same day, with no vendor response attached to it and no cause named.
What you can do today
1. Write down when you installed macOS Tahoe 26.6.2. On the Mac measured here that was 2026-08-17, and the install date is the reference point for any backup growth you are trying to explain.
2. Measure used space on the backup container with a tool that reads the volume directly, rather than trusting the figures Time Machine reports for its own backups. The container is the thing that runs out of room.
3. Leave headroom on the backup volume for a spike you cannot attribute. That is the whole mitigation as of August 22, 2026, and its cost is exactly that: capacity you pay for and cannot account for.
4. If a backup disk fills up shortly after an update, do not assume your own data grew. Nothing published on this day lets you attribute the space, so deleting your files is not the indicated response.
Frequently asked questions
Is this a Time Machine bug or a measurement artifact?
Undecided as of August 22, 2026. The readings come from the backup container itself rather than from Time Machine's own reporting, and the author's position is that the post-update swing merits further examination. No cause has been published and Apple has not commented.
Does this affect backups to a NAS?
Not known. The measurement reads only locally mounted APFS volumes, so backups to a NAS, to other networked storage or to HFS+ volumes were outside what was measured.