photoanalysisd on Mac: what it is, why it is high, what to do

What photoanalysisd does

Open Photos, click People & Pets, and you see faces grouped without having tagged anyone. Type "beach" or "birthday cake" in search and the right pictures appear. Memories assembles a slideshow of a trip you forgot. None of that is stored in the photo files; it is computed, on your Mac, by photoanalysisd. Its own manual page says it "handles background processing of photo libraries for Memories, People and scene or object based search."

It is one of a pair. mediaanalysisd runs the general-purpose image models behind Visual Look Up and Live Text across the whole system; photoanalysisd runs the Photos-specific work: face clustering, scene classification for search, picking the best shots for Memories and Featured Photos. After a big import you usually see both, plus photolibraryd, which manages the library database itself. Three names near the top of Activity Monitor, one job.

Two design choices explain most of what people see. It waits for idle time, so it looks like it starts for no reason ten minutes after you stop typing. And it pauses while Photos is open, which is why opening Photos to "check what is happening" makes the CPU drop and the mystery deepen.

Why photoanalysisd is using CPU right now

1. New photos. You imported from a camera, a phone, or a folder, or iCloud Photos pulled down a batch. Every new item is analyzed once.
2. A new Mac or a restored library. Analysis data is not synced through iCloud. A new Mac redoes the whole library from scratch, even if your iPhone already did the work. Expect days of idle time for a large library.
3. A macOS update. New versions bring new models and re-run parts of the analysis across the library.
4. The library was repaired or rebuilt. Holding Option and Command while opening Photos runs a repair, which discards analysis data and starts over.
5. A huge library. People with 50,000 to 100,000 items underestimate the work. One Apple Community account describes a 70,000-photo library that kept a machine busy for days because Photos "goes through your library multiple times."
6. A loop. Rare, but real: analysis reports complete, yet the daemon runs hard every night. Usually a corrupt item or a version bug. The Jan 2023 thread on this had users whose "CPU consumption remains very high" after turning off every related feature.

What normal looks like, and what is not

The shape of a healthy run on a MacBook that is plugged in and left alone:

Three things stretch the calendar time without adding work. Running on battery (older versions paused entirely on battery; newer ones throttle). Closing the lid. And opening Photos, which pauses it by design: one replier on Apple's forum put it as "while you are browsing or editing Photos, the process should not be running." If you check Activity Monitor with Photos open, you will see nothing and conclude it has finished when it has not.

The not-normal case is the repeat with no input: no new photos, Photos says analysis is complete at the bottom of the Library view, and still 100 percent every idle period for weeks. One user summarized the frustration: "These two processes consume hours of CPU-time on my machine."

Is it safe to quit photoanalysisd?

Yes, nothing breaks. It restarts a moment later and continues. It is a user-level agent, not a root daemon, so it is one of the few background processes where force quitting is genuinely harmless, which is also why it is genuinely useless: the unanalyzed items are still there.

The supported pause is opening Photos. The unsupported methods in old threads (unloading the launch agent, deleting its plist) need System Integrity Protection off and are undone by the next update. Skip them. The decision tree covers the general case:

If the real problem is that you do not want this analysis at all, you can turn off the features that depend on it in Photos settings (Memories, Featured Photos, Siri suggestions), which reduces the work, though it does not stop face detection.

What to do, in order

1. Open Photos if you need the Mac quiet now

   Analysis pauses while Photos is the active app. Leave it open on a second desktop during a video call or a render and the CPU is yours. Close it when you are done and analysis resumes.

2. Check progress at the bottom of the Library

   In Photos, click Library and scroll to the very bottom. It shows a count of items and, while working, a status line such as "Analyzing" or "Updating". If it says nothing, Photos believes it is done.

3. Plug in and leave the Mac awake overnight

   Connect power, leave the lid open, let the display sleep. For a big library this is the only thing that actually finishes the job. Several nights for 50,000-plus items is normal.

4. Let iCloud Photos finish first

   On a new Mac, analysis waits on downloads. Check Photos, Settings, iCloud for "Downloading" status. Give that a day before judging the analyzer.

5. Restart

   Clears a daemon stuck on one corrupt image or video. If the next idle period is quiet, done.

6. Update macOS

   Looping analysis has been fixed in point releases more than once. System Settings, General, Software Update.

7. Repair the library, last resort

   Quit Photos, then hold Option and Command while opening it and choose Repair. This rebuilds the database and restarts analysis from zero, so it costs you a full re-run. Only do it when analysis has looped for weeks and a restart and update did not help.

When to worry

photoanalysisd reads your photos; it never edits or uploads them, and it is not a privacy or security concern. The costs are indirect:

• Battery. A MacBook that drains in the bag after a photo import is usually this plus mediaanalysisd. Finish the job on power.
• Heat. Hours at 100 percent on a soft surface brings in kernel_task throttling. Desk, not duvet.
• Weeks of nightly runs with no new photos. A loop. Restart, update, then repair the library.
• Photos itself is slow or crashes. That points at photolibraryd and the library database, not the analyzer. The repair step helps there too.

Safe to Quit logs how many hours each process ran per day, so you can see the nightly runs shrinking (healthy) or staying flat (looping) instead of guessing. What is not a worry: the first few nights after a big import, however loud the fan.