# photoanalysisd High CPU on Mac: What to Check in Photos

> Check whether Photos analysis is making progress, recognize a library problem, and protect your originals before considering a repair.

Published: 2026-10-20 | Updated: 2026-10-25

If Activity Monitor shows `photoanalysisd` or `mediaanalysisd` using CPU while your Mac is slow, investigate Photos and media processing before deleting anything. These names can appear during background analysis. Their presence does not by itself prove that an Apple Intelligence feature is malfunctioning or that the photo library is corrupt.

The important distinction is progress versus repetition: work that settles after a library change needs a different response from the same disruption returning without any new photos.

## Check what changed in the photo library

Think about the period immediately before the slowdown. Did you import a large collection, restore a library, enable iCloud Photos, move to a new Mac or update macOS? These are useful clues to record, not proof of a single cause.

Apple documents that Photos [indexes images and videos for People & Pets](https://support.apple.com/en-ca/105081). This is why photo analysis is not simply a cache-cleaning task. Disabling Siri is not evidence that every Photos analysis job should stop.

Open Photos and check whether the expected library and recent imports are present. Note any visible sync or analysis status. Avoid repeatedly changing libraries or toggling cloud synchronization while trying to establish what is happening.

## Read the library status separately from the process name

Apple's [iCloud Photos troubleshooting instructions](https://support.apple.com/en-us/101559) describe where to find the Mac status: open Photos, select Library, choose All Photos and scroll to the bottom. Record the actual message rather than replacing it with a general claim that Photos is stuck. A pending upload, paused synchronization and completed synchronization call for different follow-up checks.

Synchronization and image analysis are different jobs. A completed upload count does not prove that all local analysis has finished. Likewise, a process using CPU does not prove that new photos are failing to upload. Check whether the recent photos you expect are visible and whether the status changes between observations.

If Photos reports that synchronization is paused, follow the reason it gives. Apple specifically advises against turning iCloud Photos off as a general response to a sync problem. If the message concerns iCloud capacity, inspect that account's storage; deleting a random local cache does not increase the cloud quota. If the message concerns power or a network condition, address that condition before attempting library repair.

For a large library migration, give the system an uninterrupted opportunity to work on power and a suitable connection. Apple notes that synchronization can take overnight or longer for larger files. That guidance is about synchronization, not a promise that photo analysis will finish on the same schedule.

## Observe one quiet period

In **Activity Monitor › CPU**, choose **View › All Processes**, search for the process and record the CPU reading while the slowdown occurs. Also check Memory and disk activity. A busy CPU process and low available storage can coexist without one explaining the other.

If the Mac remains usable and Photos has just received new content, allow a period with little other work and check whether the activity settles. On a notebook, connect power for this observation and keep it ventilated. There is no universal completion time for every library, and closing the Photos window does not prove that background work has ended.

If you need the machine immediately, save work and restart it normally once, then compare the same conditions. A temporary improvement is useful evidence but is not a permanent repair.

## Distinguish normal work from a case worth reporting

| Observation | What it tells you to check |
| --- | --- |
| Activity follows a large import and later settles | Allow the library work to finish |
| The same slowdown returns without new content | Record version, timing and library state |
| Photos also cannot open or displays library errors | Back up, then consider Apple's repair path |
| Several unrelated apps are slow | Check memory pressure and other workloads |
| The main problem is lack of disk space | Review storage without altering the library database |

Keep this comparison separate from the [general Mac process guide](https://mole.fit/blog/mac-processes-explained). A process name is a starting point for diagnosis, not a deletion target.

## Keep a short observation record

Record the start time, recent library change, Photos status message, whether the Mac is on power and which process is busy. Later, record the same fields again. Include what the slowdown prevents you from doing, such as typing in another app, rather than relying on fan noise alone.

A useful result might be that a large import is now visible, the pending count is falling and CPU activity becomes intermittent. That combination supports letting the work continue. A different result is an unchanged error message and the same recurring disruption after a normal restart, with no new content added. That gives Apple Support a much narrower case to investigate.

Do not create a completion estimate by dividing the number of photos by one observed minute of activity. Videos, file availability and different analysis tasks make the work uneven. There is also no universal CPU percentage above which the library must be corrupt. The comparison is whether useful progress occurs and whether the disruption settles.

If the Mac is needed for other work, save that work and avoid launching additional imports during the observation. Repeated force-quits or service-disabling commands can interrupt the very process whose progress you need to assess. One normal restart and a documented comparison are easier to interpret than a sequence of unrelated resets.

## Verify the backup before a repair

Before using Repair Library, identify the library that Photos actually opens and the backup that can restore it. If multiple libraries exist, do not assume the largest package is the active one. Check the library location in Photos settings and confirm that the intended package is included in the backup.

With optimized storage, some originals may exist only in iCloud. Copying a small local library package does not prove those originals were independently preserved. Decide whether the available backup contains the originals you care about, and allow enough time and disk space if they must first be downloaded or exported. Do not delete the cloud copy to make that test.

After a repair, check recent imports, a few older photos or videos and the library's sync status. A new period of activity can be part of iCloud checking the repaired library, so compare the original error and actual ability to open photos rather than expecting immediate silence. If the repair fails, keep the backup and error details for support instead of repeatedly rebuilding or editing the package's internal database.

## Repair the library only for a library problem

Apple's [Photos Repair Library instructions](https://support.apple.com/en-gb/118221) are intended for a library that will not open or Photos behaving unexpectedly. High CPU alone is not a reason to rebuild it.

Before repair, make an independent backup. Quit Photos, hold **Option-Command** while opening it, then use the Repair Library window if that is the appropriate next step. Repair can take time, and iCloud Photos may check the library again afterward. Do not start it just before you need to work or before verifying the backup.

An iCloud-synced collection is not a substitute for an independent backup. Apple explains [photo-library backups](https://support.apple.com/guide/photos/back-up-your-library-pht6d60d10f/mac), including the effect of optimized originals. Make sure the material you expect to recover is actually included.

## Leave the library's internal files alone

Do not remove databases from inside the Photos library package or permanently disable system services to lower a CPU figure. That changes the functionality you are trying to diagnose and may create a new problem.

For a persistent case, collect the macOS version, when activity starts, what changed in the library and whether Photos reports an error. Share those observations with Apple Support. If you also need disk space, review unrelated downloads and backed-up personal files first, using the [System Data guide](https://mole.fit/blog/what-is-system-data-on-mac) to avoid treating the entire category as disposable.

---

Canonical HTML page: https://mole.fit/blog/photoanalysisd-high-cpu-mac
Blog index for agents: https://mole.fit/blog/llms.txt
Site index for agents: https://mole.fit/llms.txt