A Mac left on overnight never settles on macOS Tahoe 26.6.2 (August 23, 2026)
Chapters
What thirteen nights of logs show
The machine is a Mac mini M4 Pro on macOS Tahoe 26.6.2, left running without sleep and backing up hourly. The reading taken is the quantity of data written to the Persist logs, night by night, over thirteen days. The expectation being tested is the common one: that a Mac left on overnight does its housekeeping in the quiet hours and then settles.
It does not settle. The volume of log writes stays high all night, and the processes named as responsible are mediaanalysisd and photoanalysisd doing image analysis, CGPDFService doing PDF work, XProtect Remediator running its scans, and Time Machine taking its hourly backups. That is a machine which is never idle, on a desk where the owner thinks nothing is happening.
| Process named in the logs | What it was doing overnight |
|---|---|
| mediaanalysisd | Image analysis |
| photoanalysisd | Image analysis |
| CGPDFService | PDF work |
| XProtect Remediator | Malware scans |
| Time Machine | Hourly backups |
TL;DR
A Mac mini left running on macOS Tahoe 26.6.2 wrote heavily to its logs through all of thirteen consecutive nights, according to The Eclectic Light Company on August 23, 2026. The overnight actors it names are mediaanalysisd and photoanalysisd doing image analysis, CGPDFService doing PDF work, XProtect Remediator scans and hourly Time Machine backups. The author identifies no fault and makes no recommendation, so as of August 23, 2026 this is an open question about how macOS behaves rather than a confirmed defect.
- Verbatim: 'Far from its log entries dying down during the night, this record of the quantity of data written to the Persist logs over 13 days demonstrates how busy they remain overnight.'
- The named overnight processes are mediaanalysisd, photoanalysisd, CGPDFService, XProtect Remediator and Time Machine.
- The periodic maintenance scripts were removed in macOS Sequoia 15.0, so there is no nightly maintenance window left to point at.
- Backup sizes moved with it: the night of 18 to 19 August grew, the following night reduced, with no cause given.
- Apple has not acknowledged any of this, and no fix applies while the behavior is unexplained.
This is an open question, and the day was quiet
I want to be plain about what this is. The author reaches no conclusion, names no current fault and gives no recommendation, so nobody has established that anything is broken here. It is a measurement that contradicts a widely held assumption, which is worth knowing, and it is not a filed bug.
9to5Mac published six pieces on August 23, 2026, a Sunday: a MacBook deals buyer's guide, a Mophie battery-bank hands-on, an M6 iMac report, an iPhone Ultra piece, a report on Apple Stores and a CarPlay accessory item. None of them addresses a macOS bug, a security issue or a system update, so there was no new macOS development that day. This measurement is the only Mac-technical finding dated to it.
There is no nightly maintenance window left to point at
The old answer to overnight activity was the periodic maintenance scripts, and those were removed from macOS in Sequoia 15.0. So on macOS Tahoe 26.6.2 there is no scheduled nightly maintenance to attribute this to, and no documented window that ends.
That leaves the question the author sets out and does not answer: whether leaving a Mac on overnight lets this work run, or whether shutting it down each night simply defers the same work into your working hours. Nothing published on August 23, 2026 settles it.
The backup numbers move with it
Backup sizes on the same machine do not hold steady either. Verbatim: 'Some nights, such as that of 18-19 August, backups grew in size, while the following night they reduced in size.' The author also notes that daytime logging patterns shifted noticeably after the update to 26.6.2 on 2026-08-17, and writes 'I don't know what might account for that.'
The measurement behind those backup figures was published the day before, in The Eclectic Light Company on August 22, 2026: the backup container grew at just over 10 GB per week across 2026-08-11 to 2026-08-20, with large transient changes on 2026-08-17 to 2026-08-19, right after 26.6.2 went in. I covered those readings in the August 22 post. Two days of measurement on one Mac now point at the same unexplained period.
What the behavior costs while it is unexplained
The cost is not a crash or a lost file. It is that a Mac you believe is idle is writing to its SSD, drawing power and making heat all night, every night. On a machine that is left on for convenience, that is continuous work you did not ask for and cannot schedule.
There is no setting named in this measurement that turns any of it off, and no fix, because nothing has been identified as faulty. That is the state of it on August 23, 2026.
What you can do today
1. Decide the tradeoff knowingly. If you leave the Mac on, expect image analysis, PDF work, XProtect scans and hourly backups to run through the night. If you shut it down, expect that work to land while you are using the machine instead.
2. Read the overnight activity as ordinary work before you blame the hardware. The processes named here, mediaanalysisd, photoanalysisd, CGPDFService and XProtect Remediator, are macOS services doing analysis, indexing and scanning, so a Mac that is warm and busy at 3am has an explanation rather than a fault.
3. Give it power and air. A machine that never goes idle wants to be plugged in and not boxed in, since nothing published here stops the overnight work.
4. Keep watching backup capacity. The nightly figures move up and down with no published cause, so leave headroom rather than assuming a steady rate.
5. Do not go looking for a nightly maintenance setting to adjust. The periodic scripts left macOS in Sequoia 15.0, and no replacement window is documented.
Frequently asked questions
Is my Mac broken if it is busy overnight?
Nothing published on August 23, 2026 says so. The processes named are ordinary macOS services doing indexing, analysis and scanning work, and the finding is only that they stay busy all night instead of quieting down. No fault was identified.