HeartbeatHocusFocusFilesMacHyperTile
Guide

photoanalysisd, the daemon that reads your photo library

photoanalysisd is the Photos daemon that reads your library on your Mac. What it builds, what it waits for, and whether you can stop it.

By Chethan Kumar S N · Updated

photoanalysisd turns up the way most of these processes do. Nobody installs it, nobody recognises the name, and it appears in Activity Monitor at the moment you are already worried about something else. Because the name has no vowels in useful places and no dictionary meaning, it invites the two worst answers on the internet: it is a virus, or it is spyware reading your photos.

It is neither. photoanalysisd is the Photos app’s own analysis engine, and the work it does is why Photos knows that the person in a picture is someone you have named, that a shot is a beach rather than a park, and that four photos from one evening belong together. Apple has a lot to say about that analysis in the abstract and nothing at all to say about this process by name, which is exactly the gap this page is meant to fill.

Everything below comes from three places: Apple’s own documentation for Photos, the resource files the framework ships on disk, and read-only checks on the Mac this was written on, a 14 inch MacBook Pro with an M1 Pro running macOS 27.0.1. Nothing was uninstalled, no library was rebuilt, and no Photos setting was touched.

What photoanalysisd actually is

One command gives you its identity:

$ ps -Awwo pid,ppid,user,%cpu,rss,etime,args | grep "[/]photoanalysisd"
81709     1 chethankumar   0.0  11424 04:03:28 /System/Library/PrivateFrameworks/PhotoAnalysis.framework/Versions/A/Support/photoanalysisd

Read that the way you would read any process line. The parent is PID 1, which is launchd, so a system component started it rather than an app. The user is you, not root, so it runs with your permissions and can only reach what you can reach. The path sits in /System/Library/PrivateFrameworks, the same protected territory as the bird process that handles iCloud Drive, which is a strong signal that it is Apple’s code. And the elapsed time of a little over four hours tells you it was started recently, not at boot.

The system also ships a file that describes the job in plain terms, and this is where the interesting part starts:

$ plutil -p /System/Library/LaunchAgents/com.apple.photoanalysisd.plist
  "Label" => "com.apple.photoanalysisd"
  "EnablePressuredExit" => true
  "EnableTransactions" => true
  "ProcessType" => "Interactive"
  "MachServices" => { "com.apple.photoanalysisd" => true }
  "Program" => "/System/Library/PrivateFrameworks/PhotoAnalysis.framework/Versions/A/Support/photoanalysisd"

A LaunchAgent with a label of com.apple.photoanalysisd is launchd’s bookkeeping for this process, and EnablePressuredExit is a sentence in its own right: macOS is allowed to end this process when it is idle and let it start again later. That single key explains most of the confusion around it, and we come back to it below.

Ask launchd how the job is actually behaving rather than how it is configured, and you get the running commentary:

$ launchctl print gui/501/com.apple.photoanalysisd
	state = running
	program = /System/Library/PrivateFrameworks/PhotoAnalysis.framework/Versions/A/Support/photoanalysisd
	minimum runtime = 10
	exit timeout = 5
	runs = 20
	pid = 81709
	immediate reason = ipc (mach)
	last exit reason = JETSAM_REASON_MEMORY_IDLE_EXIT

Three of those lines matter. runs = 20 means this job has started twenty times since the last login, so it is a process that comes and goes rather than one that sits there. immediate reason = ipc (mach) means it was woken by a call over Apple’s internal messaging rather than by a timer or a login item. And last exit reason = JETSAM_REASON_MEMORY_IDLE_EXIT is the system saying, in the least friendly words available, that it reclaimed the memory of a process that was not doing anything.

Ten jobs, one process

The plist does not say “run the analysis”. It lists ten separate named tasks, and each one carries its own conditions. That list is the best answer to the question of when and why photoanalysisd wakes up:

TaskRepeats everyWaits for
backgroundanalysis6 hoursface results from mediaanalysisd, external power, an idle Mac
highlightenrichment6 hoursbackgroundanalysis
searchdonation6 hoursbackgroundanalysis
graphNonIntensiveTasks2 hoursexternal power
photolibraryNonIntensiveTasks2 hoursexternal power
music8 hoursexternal power
featuredcontent24 hoursbackgroundanalysis and highlightenrichment
libraryprocessing24 hoursbackgroundanalysis
wallpaper24 hoursbackgroundanalysis
internal24 hoursbackgroundanalysis and highlightenrichment

Read the conditions off the file itself rather than trusting the summary and you get Apple’s own vocabulary:

  "com.apple.photoanalysisd.backgroundanalysis" => {
    "ExpectedDuration" => 2700
    "RandomInitialDelay" => 2700
    "RepeatingTask" => { "Interval" => 21600, "MinDurationBetweenInstances" => 6000 }
    "RequiresExternalPower" => true
    "RequiresBuddyComplete" => true
    "RequiresProtectionClass" => "C"
    "ResourceIntensive" => true
    "PowerNap" => true
    "PreventsDeviceSleep" => true
    "Priority" => "Maintenance"
  }

Four of those keys do most of the work. RequiresExternalPower is why a Mac on battery shows nothing. RequiresBuddyComplete means the setup assistant has to be finished, so this never runs on a machine that is still being set up. ExpectedDuration of 2700 seconds says Apple expects the first pass over a library to take about three quarters of an hour of work, and RandomInitialDelay of the same length is there so that every Mac in an office does not start at once. ResourceIntensive is Apple labelling its own job as one you would notice if it ran at the wrong moment.

The dependencies are the other half of the story, because photoanalysisd does not do everything itself:

    "Dependencies" => [
      { "DependencyIdentifier" => "com.apple.mediaanalysisd.photos.face",
        "DependencyType" => "DependencyTypeCompletion" }
      { "DependencyIdentifier" => "com.apple.mediaanalysisd.photos.face.fullResults",
        "DependencyType" => "DependencyTypeResult",
        "ResultDependencyBatchSize" => "500" }
    ]

In plain terms: the heavy visual models live in a different daemon, mediaanalysisd, and photoanalysisd waits for its face results in batches of 500 before it begins. That division of labour is worth holding onto, because it changes what you should expect to see in Activity Monitor. If you are looking for the process doing the expensive image work, photoanalysisd is often the wrong culprit.

launchctl print names the thing that wakes it. Each task descriptor includes a line reading monitor = com.apple.dasd, and dasd is the background task scheduler, the part of macOS that decides when maintenance work is allowed to run. That is why the process appears at strange hours: it is not on a clock you set, it is on a queue you cannot see.

What it produces, in Apple’s own words

Apple never names this daemon in its user documentation, which is a count rather than a suspicion. The index of the macOS 27 Photos User Guide contains no entry for photoanalysisd, none of the Photos pages fetched while writing this mention it, and a site restricted search for the name returns no Apple documents at all. So the useful question is not what the daemon is called but what the analysis is for, and there Apple is unusually specific.

Its Photos and privacy page states the boundary and the list in one paragraph. Apple does not access your photos or videos, and does not use them for research and development. Photos uses on device machine learning, and the analysis includes scene classification, people and pets identification, photo quality analysis, and audio classification.

That list maps directly onto features you can see. People and pets identification is why the Photos guide says the app sorts photos and videos of people, dogs and cats into a collection. Group photos go further: Apple’s page on that feature says Photos uses on device technology to create a collection for each group of people who often appear together. Scene classification is what makes search work, and Apple’s own example of a search is the giveaway, because it suggests typing basketball, beach or birthday cake. None of those words are in any file name. Something had to look at the pictures.

Photo quality analysis is what puts the best shot of a burst in front of you, and audio classification is why a video with a birthday song in it behaves differently from silent footage. The results are then handed to the features that feel like magic: Memories, Featured Photos, the photos that rotate as a wallpaper, and the fact that a photo of a receipt can be found by typing the shop’s name.

The receipts are on your disk

You do not have to take any of that on faith, because macOS ships the vocabulary. Inside the framework there is a folder of resources, and one file in it is the complete word list this analysis works from:

$ ls /System/Library/PrivateFrameworks/PhotoAnalysis.framework/Versions/A/Resources
CPAnalyticsConfig-photoanalysisd.json  ContextualPrompts.json  Localizable.loctable
WhimsicalPrompts_en_GB.json  ...  164 entries, including 44 .lproj folders

Count the English strings in that loctable and you get 1,863 of them, in 44 locales. Split them by prefix and the shape of the thing appears: 1,655 of the keys are moment titles, 173 are contextual prompts, and 35 are everything else.

The contextual prompts are a machine readable recipe list, and this is where it gets interesting:

$ python3 -c "... ContextualPrompts.json ..."
contextual prompts: 160
trigger types: {'Holiday': 118, 'PersonBirthday': 36, 'SeasonInHistory': 6}
feature types: {'Holiday': 118, 'Person': 36, 'Season': 6}

 - Daisies and daffodils | SeasonInHistory
 - Springtime delights | SeasonInHistory
 - Christmas memories | Holiday
 - Thankful for my loved ones at Thanksgiving | Holiday

Read a couple of entries in full and you can see the mechanism rather than guess at it. One recipe names itself Springtime delights and carries a trigger telling the analysis to look for the season spring in the history of the library. Another is a person’s birthday, which is why a birthday memory appears the week of the birthday. 118 of the 160 are holidays, which explains why Christmas, in a library that has photos from many Decembers, is so heavily represented in Memories.

There is a second file for the moodier collections, and it is the clearest statement of how specific this analysis gets:

$ python3 -c "... WhimsicalPrompts_en_GB.json ..."
recipes: 24, traits: 240
prompts: ['A birds-eye view', 'Among the wildflowers', 'Best eats', 'Dramatic skies',
          'From sunrise to sunset', 'Just desserts', 'Ocean breezes', 'Splish splash',
          'But first, coffee', 'Tiptoe through the tulips', 'Where earth meets sky']
moods: Gentle, Neutral, Peaceful, Chill, Dreamy, Excited, Extreme, Amused, Epic, Happy

Twenty four themed collections, ten described scenes each, so 240 descriptions of the kind of photo that would belong, alongside a musical mood and keywords such as Sunrise, Sunset, Beach and Flower. Open the file and the first entry asks for a coastline seen from the air, a city skyline, a mountain range, desert dunes, a vineyard, a forest canopy, a river delta, a lavender field, icebergs and a coral reef. That is not a vague sense of the outdoors. It is a shopping list.

$ ls -l /System/Library/PrivateFrameworks/PhotoAnalysis.framework/Versions/A/Support/photoanalysisd
-rwxr-xr-x  1 root  wheel  371168 Sep 24 12:40 photoanalysisd

$ codesign -dv /System/Library/PrivateFrameworks/PhotoAnalysis.framework/Versions/A/Support/photoanalysisd
Identifier=com.apple.photoanalysisd
Format=Mach-O universal (x86_64 arm64e arm64e.x1)
Platform identifier=26

A 363 kilobyte binary that ships with 1,863 strings, 160 recipes and 240 scene descriptions is not doing the recognising itself. It is the part that knows what to ask for and what to do with the answers, and the framework it lives in has a version number of 911.0.134 with a copyright line from 2015, which tells you how long this has been evolving under a name almost nobody has heard.

Where the heavy lifting actually happens

Ask any Mac with Photos open which process is working hard and the answer is usually not photoanalysisd. On this machine, a few minutes apart:

$ ps -Awwo user,pid,rss,%cpu,etime,comm | grep MediaAnalysis
chethankumar  78454  173648  0.0  04:31:13 /System/Library/PrivateFrameworks/MediaAnalysis.framework/Versions/A/mediaanalysisd
chethankumar  81700    9296  0.0  04:03:46 /System/Library/PrivateFrameworks/PhotoLibraryServices.framework/Versions/A/Support/photolibraryd
chethankumar   6102    4816  0.0  01:05:01 cloudphotod

mediaanalysisd was holding around 170 MB, roughly fifteen times photoanalysisd’s footprint, and its binary is a different scale of thing entirely: 11 MB against 363 KB. That is the face detector and the image classifier. photoanalysisd orchestrates it.

photolibraryd is the third member of the family and the one that owns the library database, and its own launch file keeps a maintenance rhythm of its own, with a curated library job every three hours that waits for the Mac to be idle and a daily maintenance job that waits for external power. Its own page reads the log line by line and shows that it is the cheapest of the three by a wide margin. cloudphotod is the iCloud Photos side, and it is worth reading because it lists the whole cast in one place:

    "InvolvedProcesses" => [ "cloudphotod", "nsurlsessiond", "cloudd",
      "com.apple.photos.VideoConversionService",
      "com.apple.photos.ImageConversionService", "photolibraryd" ]

That is Apple’s own map of which processes handle a first download of an iCloud photo library. The nsurlsessiond in that list is the courier, and its own page shows the folder that names every app it has carried bytes for. Note what is in it and what is not: the downloads and the conversion run elsewhere, and photoanalysisd is not part of that phase at all. If you have just turned on iCloud Photos and everything is slow, this list is the honest explanation.

Reading its numbers

The tricky part of judging photoanalysisd is that both numbers people watch move for reasons that look alarming and are not.

$ ps -o pid,%cpu,rss,time -p 81709
81709   0.0   7520   0:01.83
81709   0.0   7536   0:01.83

Two things in that output. The CPU time column is minutes and seconds on macOS, and after four hours of life this process had used under two seconds of CPU, which is what a library that has nothing to do looks like. And the memory figure is lower than the 11,424 KB in the first command on this page, taken minutes earlier. The footprint went down while the process sat idle, which is not a leak being plugged: it is macOS reclaiming pages from a process that told launchd it was fine to end. EnablePressuredExit in the plist is the permission slip for exactly that.

So the reading order for this process is the opposite of the instinct. A figure of 0.0% with a shrinking RSS is the healthy state. A figure of 100% or more, sustained, with the process alive for a long time, is the state that means it is working through something.

Why it gets busy, and when

Given the configuration, the busy case is predictable, and it is almost always a library that changed faster than the analysis could keep up:

A first import, or the first Mac that gets an existing library. Apple expects a full analysis pass to take about 45 minutes of work, and on a large library it is more.

Switching on iCloud Photos on a Mac that already has a library in the cloud. Apple’s own list of involved processes shows the download and conversion jobs, and every photo that arrives is a photo that then needs analysing.

A restore, a migration to a new Mac, or adding a second library. The analysis state travels with the library, but anything new in it does not come pre-read.

A big batch of screenshots, or a camera import of a few thousand frames. Photo quality and scene classification both scale with the number of pictures.

The reason it feels arbitrary is the staggering. Jobs are configured with a random initial delay, they only run on external power, and the two intensive ones additionally want the machine idle. So the answer to “why is it running now” is usually “because this is the first moment it was allowed to”.

The library itself is protected

One thing this page cannot do, and will not pretend to, is size the analysis for you, because the library is behind Apple’s data protection:

$ du -sh ~/Pictures/"Photos Library.photoslibrary"
du: /Users/chethankumar/Pictures/Photos Library.photoslibrary: Operation not permitted

That is not a fault and not corruption. A photo library is protected in the same category as your Messages database and your Mail, and reading it from a terminal needs Full Disk Access granted to the terminal itself. If you are seeing that message in your own shell, it means the protection is doing its job.

It also has a practical consequence for this question. Any tool that claims to show you exactly how much disk space photoanalysisd’s work is using is either measuring something else or has been given access you may not want to give it. The honest version is the one Apple’s own Settings pane shows: the size of the library, not the size of its analysis.

Can you quit it, or turn it off?

You can quit it, and it will come back, and that is the design rather than a frustration to defeat. It is a LaunchAgent, launchd supervises it, and its last recorded exit on this Mac was the system reclaiming it when idle. Force quitting it pauses the analysis until the next scheduled window, changes nothing else, and does not reduce the work waiting to be done.

There is no switch labelled analysis. What Photos does offer is control over the output, in Photos, then Settings, then General:

Show Featured Content decides whether photos you featured on an iPhone or iPad are drawn into featured content on the Mac. Show Holiday Events decides whether holiday groups become memories, and turning it off is the honest way to stop receiving a Christmas memory every December. Show Memories Notification decides whether you are told when a new one is ready. And the two Reset buttons, one for suggested memories and one for suggested people and pets, undo a choice you made to see less of something rather than stopping the analysis itself. If you want fewer of something in particular, the cleaner route is the per person option, which is Control click a person in People and Pets and choose Don’t Feature.

One switch does reduce the analysis that leaves your Mac, and it is worth knowing which one it is. Enhanced Visual Search, in Photos settings under Search, lets Photos match landmarks and points of interest to an index Apple maintains, and Apple’s privacy page describes the machinery in unusual detail: homomorphic encryption, differential privacy, and a relay that hides your IP address. That is a different mechanism from photoanalysisd and it has its own off switch. If your concern is what ever leaves the machine, that setting is the one to read about, not this process.

What this page cannot tell you

Apple publishes no CPU figure, memory figure or expected duration that counts as normal for photoanalysisd, so there is no threshold to measure against. The 45 minute expected duration in the plist is an internal estimate for one task, not a promise about your library.

Apple also never names the process in its user documentation, so the name cannot be looked up in the place you would normally look. Everything above about the name comes from the operating system’s own files rather than from a support article about it.

And the analysis state is not something you can inspect, edit or repair from outside. It lives with the library, it is protected, and the only supported way to rebuild it is Photos’ own repair option, which is a large hammer for a small question.

Where window managers fit

None of this is a window problem. If you came here because a Mac felt slow, the photo analysis is a plausible explanation for a few hours after a big import and a very unlikely one for a machine that has been quiet for a week.

The other half of the same feeling is what is on the screen. A desktop with nineteen overlapping windows, a Dock full of things you cannot identify, and Control Up used as a search expedition will make a fast Mac feel slow no matter what the background jobs are doing, and that is the part you can actually fix in a minute.

Ribbon replaces the stacking with one rule: windows stay at full size on a scrolling strip, and the one you want is a swipe away instead of buried. It is $15 once for up to 3 Macs, with a full refund within 10 days, and it runs on macOS 14 Sonoma and later on Apple silicon and Intel Macs. You can drive the strip in your browser before installing anything.

The short version

photoanalysisd is the Photos app’s analysis engine, it is Apple’s own daemon inside a private framework, and it runs as you rather than as root.

It is not a background hum. It is ten separate tasks that only run when a scheduler says so, on external power, with the machine idle, and the two expensive ones wait for face results from mediaanalysisd first. That is why it disappears from Activity Monitor: macOS is allowed to end it when it is idle, and the launchd record on this Mac showed twenty starts since the last login and a last exit that was a memory reclaim.

What it produces is documented in Apple’s own words, and the vocabulary it works from is sitting in a file on your disk: 1,863 English strings, 160 contextual recipes, and 240 described scenes in 24 themed collections. Nothing about that analysis leaves your Mac, and the one Photos feature that does reach Apple’s servers has its own switch under Search.

So the readings that look alarming usually are not. Under two seconds of CPU after four hours, and a memory figure that went down rather than up, is a healthy daemon with nothing to do. If it is genuinely busy, the cause is almost always a library that just grew by a few thousand photos, and the cure is external power, a little patience, and leaving the lid open long enough for the job it was told to wait for.

Questions

What is photoanalysisd on my Mac?

It is the Photos app's analysis engine. It runs as you, not as root, and on this Mac its path is /System/Library/PrivateFrameworks/PhotoAnalysis.framework/Versions/A/Support/photoanalysisd, which is Apple's own code inside a private framework rather than anything an app installed. Its whole job is to look through your photo library on the machine itself and produce the things Photos needs in order to feel organised: who is in a picture, what the scene is, which moments deserve to be gathered into a memory, and which photos match a search for a beach or a birthday cake.

Why is photoanalysisd using so much CPU?

Because it is doing the reading and the classifying, and that is real work. It does not run continuously: the jobs that start it are configured to wait for external power and an idle Mac, which is why a laptop on battery rarely shows it doing anything. The case that makes it noticeable is a library that changed a lot at once, which usually means a first import, a new Mac, a restore from a backup, or iCloud Photos downloading a backlog of originals. On this Mac, four hours after it started, it had used under two seconds of CPU in total and sat at 0.0%, which is what a quiet library looks like.

Can I quit photoanalysisd or turn it off?

You can quit it and it will come back, because it is a LaunchAgent supervised by launchd, and its last recorded exit reason on this Mac is a memory related idle exit, which means the system kills it on purpose when it is not needed. There is no Photos setting that says run analysis or do not run analysis. What the settings do change is how much there is to do: Show Featured Content, Show Holiday Events and the two Reset buttons for suggested memories and suggested people and pets in Photos, Settings, General. Turning those off means the daemon has less to build, not that it goes away.

Is photoanalysisd malware, and does Apple see my photos?

It is Apple's own daemon and it is present on every Mac with a photo library. Apple's Photos and privacy page is unusually direct about the boundary: Apple does not access your photos or videos, and does not use them for research and development, and the analysis runs on the device. The one Photos feature that does talk to Apple's servers is Enhanced Visual Search, which matches landmarks to an index Apple maintains, using homomorphic encryption, differential privacy and a relay that hides your IP address, and it has its own switch in Photos settings under Search. That is a separate mechanism from photoanalysisd and it is off or on independently of it.

Why is photoanalysisd not running or missing from Activity Monitor?

Because it is not supposed to be there most of the time. It is started by a background scheduler, dasd, when one of ten named tasks is due, and until then there is no process to see. On this Mac the launchd record showed twenty starts since the last login and a last exit reason of a memory related idle exit, so the pattern is start, work, get reclaimed. If you opened Activity Monitor with All Processes selected and found nothing, that is a quiet system rather than a missing daemon, and the next thing to check is whether Photos is showing any sign of the features it feeds, such as a People and Pets collection or a new memory.

Ready? Buy Ribbon for $15, or read all the guides.