photoanalysisd using high CPU on Mac? Here's why

You opened Activity Monitor because the fans were up and the Mac felt warm, and near the top of the list is something cryptic: photoanalysisd, using a lot of CPU, often with photolibraryd nearby. First, the reassuring part. This is almost never a virus. Seeing photoanalysisd use high CPU on a Mac usually means Photos is analyzing your library in the background, not that anything is wrong.

What photoanalysisd actually is

It isn't an app you installed. It's a background process that belongs to Photos, and its job is to look inside your pictures and videos so the app can organize and search them. Specifically, it uses on-device machine learning to:

• Recognize faces and group them, so you can name people in the People album.
• Detect objects and scenes (dogs, food, beaches, receipts) so searching "sunset" or "dog" in Photos actually finds them.
• Build Memories: the auto-curated slideshows and collections keyed to people, places, and dates.

A companion process, photolibraryd, manages the library database itself. The important detail is that all of this analysis happens on your Mac, not in the cloud. That's a privacy win (your full-resolution photos aren't shipped off to be scanned), but it also means your Mac does the heavy lifting, which is why photoanalysisd can light up the CPU. Malware would show up as some other process; this is the machinery of a feature you already use.

Why photoanalysisd uses high CPU

Analyzing a photo library is heavy work. Every image and video has to be decoded and run through several recognition models (faces, scenes, objects), and the results written into the Photos database. Across thousands of items, that adds up to a lot of CPU (and some GPU) at once.

The key thing to understand is that this is front-loaded, catch-up work. Apple designed it to run only when your Mac is idle and plugged into power, and to back off when you start using the machine or unplug to battery. So it's meant to be invisible. It just isn't, if the backlog is large and you happen to be watching Activity Monitor while it runs.

What sets off a big analysis pass

A spike almost always traces back to something that handed Photos a lot of new material, or reset what it had already analyzed:

• Importing a lot of photos. A camera dump, an AirDrop batch, or a big import gives photoanalysisd thousands of new items to scan.
• A new or migrated library. Setting up a Mac with Migration Assistant, restoring from backup, or opening a library on a new machine means everything gets analyzed from scratch.
• A macOS update. Updates sometimes ship improved recognition models, which triggers a re-analysis of the library; this is the single most misread trigger ("my Mac got hot right after updating").
• Turning on iCloud Photos. When your whole library syncs down, your Mac still analyzes each photo locally, so enabling iCloud Photos can kick off a long run.

What's normal, and what isn't

• Normal: high photoanalysisd CPU for a while after an import, a migration, or a macOS update, with the fans up, then it quiets down and stays quiet. A large library can take many hours spread across several idle sessions over days, because it only works while the Mac is idle and charging. Let it run.
• Worth investigating: photoanalysisd stays pegged for weeks and never seems to finish, or it spikes every time you wake the Mac with no new photos being added. That can point to a stuck or damaged library rather than normal catch-up.

There's no official "normal percentage" here. Judge it by direction: is it working through a backlog and gradually going quiet, or stuck in place indefinitely?

How to check in Activity Monitor

1. Open Activity Monitor (in Applications → Utilities, or search for it with Spotlight).
2. Click the CPU tab.
3. Type photo into the search box in the top-right to filter down to photoanalysisd and photolibraryd.

Watch for a minute. If the number is high but drifting down over time, the analysis is progressing; leave it alone. Opening Photos and letting it sit in the foreground can also nudge it to work faster.

High numbers in Activity Monitor aren't automatically bad, by the way. The same is true of your RAM, where a "full" reading is usually healthy. If it turns out to be a different process at the top of the list, mds_stores runs high while Spotlight indexes and kernel_task runs high to manage heat for their own reasons, and photoanalysisd is one of the processes worth checking when the fans are loud for no obvious reason.

What to do about it

Work from gentlest to most drastic:

• Let it finish. This is the right answer most of the time. Plug in, stop actively using the Mac, and let it run; leaving it idle overnight with Photos open is the fastest way to get through a big backlog, because that's exactly the condition it waits for.
• Don't force-quit it as a fix. You can select photoanalysisd in Activity Monitor and quit it, and it'll stop for now. But macOS just relaunches it later to finish the same job, so you've paused the work, not ended it, and the analysis restarts from where it left off. It's not a process to "kill" permanently.
• Rein it in temporarily by unplugging. Since it's designed to pause on battery, working unplugged for a while quiets it down and defers the analysis until you're charging again, useful when you need full CPU right now.
• Repair a stuck library (last resort). If photoanalysisd truly never settles after days of idle time, the library itself may be damaged. Quit Photos, then hold Option-Command while opening it and choose Repair Library in the dialog that appears. This checks and rebuilds the library database. The honest caveat is that repairing (or importing into a fresh library) means Photos has to analyze everything again afterward, so expect photoanalysisd to be busy, and the fans possibly loud, for a while right after.

What not to do is treat a warm Mac and a named daemon as an infection. photoanalysisd running hard after an update or a big import is Photos doing exactly what it's supposed to do, on your hardware, to keep your photos private.

By the time you've opened Activity Monitor, the frustrating part of a photoanalysisd spike is that you still can't tell whether it's normal catch-up work that will finish overnight or a stuck library, and whether the fans are Photos' fault or something else's. Plumby keeps a live readout of CPU, memory, and temperature in your menu bar and calls out when the load is just temporary background work, so a loud fan points you to the real cause instead of a virus that was never there. It only reads and reports, and it never touches your photo library, so you can watch photoanalysisd trend down and finish, and know when it actually has.