photolibraryd, the process that owns your photo library
photolibraryd is the daemon that owns your Mac's Photos library. What it does, the three background jobs it runs, and whether you can stop it.
By Chethan Kumar S N · Updated
There is a family of processes on a modern Mac whose names are all one word with the vowels pushed to the end, and photolibraryd is the one that sounds the most like a threat. Search for it and you will find forum threads asking whether it is safe, a handful of answers saying it is, and a second set of answers telling you to quit it. That second set is the problem, because the process is holding your photo library open, and the advice to force quit it is written by people who have not realised that.
The name is not that bad once you take it apart. Photo and library are obvious. The d on the end is the old Unix convention for a background process, the same one that gives you httpd and sshd. So the whole thing means the background service for the photo library, and it says nothing about a file of yours.
Everything below comes from three places: Apple’s own documentation, the files the daemon and its framework ship 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 or modified, no photo was opened, and no setting was changed.
What photolibraryd actually is
One command gives you its identity:
$ ps -o pid,ppid,user,%cpu,rss,time,etime,comm -p 81700
PID PPID USER %CPU RSS TIME ELAPSED COMM
81700 1 chethankumar 0.0 12512 0:01.51 07:06:21 /System/Library/PrivateFrameworks/PhotoLibraryServices.framework/Versions/A/Support/photolibraryd
Read it in order. The parent is PID 1, which is launchd, so the system started it and not an app. It runs as your user account, not as root and not as a hidden system account. It lives inside a framework in the System folder rather than in /usr/libexec, which is where most background daemons with names like this one sit.
That difference is worth a sentence, because it explains the whole process. The download daemon nsurlsessiond runs two copies, one as you and one as a privileged account called _nsurlsessiond. The analysis daemon mediaanalysisd has no such account, and neither does this one:
$ dscl . -read /Users/_photolibraryd
<dscl_cmd> DS Error: -14136 (eDSRecordNotFound)
No such user exists, because there is nothing for a privileged half to do. Every photo library on a Mac belongs to a person who is logged in, so the daemon runs as that person and asks the operating system for permission the same way any other process would.
The binary is small and boring, which is the point:
$ ls -l .../PhotoLibraryServices.framework/Versions/A/Support/photolibraryd
-rwxr-xr-x 1 root wheel 1290288 Sep 24 12:40 photolibraryd
$ lipo -archs .../photolibraryd
x86_64 arm64e arm64e.x1
$ codesign -dvvv .../photolibraryd 2>&1 | grep -E "Identifier|Authority|Platform|TeamIdentifier|flags"
Identifier=com.apple.photolibraryd
CodeDirectory v=20400 size=1104 flags=0x2000(library-validation) hashes=24+7 location=embedded
Platform identifier=26
Authority=macOS Software Signing
Authority=Apple Code Signing Certification Authority
Authority=Apple Root CA
TeamIdentifier=not set
Just over a megabyte, three architectures including the arm64e variant Apple uses for code that talks to the kernel or the security hardware, signed under the platform authority rather than by a developer team. On a real Mac the framework’s own library is not even a file on disk any more, because system libraries live in the shared cache. What is left in the framework is a Support folder holding this one executable and a Resources folder holding its words.
The one that owns the library, not the ones that read it
There are three daemons in the Photos pipeline and they are easy to confuse, so it helps to see what each one is allowed to do. Reading the entitlements is the fastest way, because Apple writes them in plain names.
photolibraryd carries 82 entitlement keys. The interesting ones are not the file permissions, they are the door keys:
$ codesign -d --entitlements - .../photolibraryd 2>/dev/null | grep "\[Key\]" | grep -E "photos|photoanalysisd|mediaanalysisd|cloudphotod|cachedelete|corespotlight|Messages|addressbook|spaceattribution"
[Key] com.apple.mediaanalysis.datastore.client
[Key] com.apple.mediaanalysisd.client
[Key] com.apple.private.CacheDelete
[Key] com.apple.private.cloudphotod.access
[Key] com.apple.private.corespotlight.internal
[Key] com.apple.private.corespotlight.receiver
[Key] com.apple.private.corespotlight.search.internal
[Key] com.apple.private.imcore.imdpersistence.database-access
[Key] com.apple.private.photoanalysisd.access
[Key] com.apple.private.photos.allowcollectionshare
[Key] com.apple.private.photos.migration.access
[Key] com.apple.private.photos.service.mediaconversion
[Key] com.apple.private.security.storage.Messages
[Key] com.apple.spaceattribution.private
[Key] com.apple.security.assets.pictures.read-write
[Key] com.apple.security.personal-information.addressbook
[Key] com.apple.spotlight.photos.entitledattributes
That list is the whole architecture in seventeen lines. It can talk to photoanalysisd and to mediaanalysisd, which is how work gets handed out. It can talk to cloudphotod, which is the iCloud side. It receives for Spotlight, which is how a photo shows up in a system wide search. It answers CacheDelete, which is the service macOS asks when it wants disk space back, and it carries com.apple.spaceattribution.private, which is how the storage pane knows that a chunk of what it calls System Data actually belongs to Photos.
Two of the entries are the ones people find unsettling, and both are easy to misread. com.apple.private.security.storage.Messages and com.apple.private.imcore.imdpersistence.database-access give the daemon read access to the Messages database, and com.apple.security.personal-information.addressbook gives it Contacts. That is not surveillance. It is the plumbing for the suggestions Apple describes on the Photos privacy page: faces get names from Contacts, and the people you message are the ones Photos offers when it suggests who to share an album with. If you have ever wondered how Photos guesses the right person so often, that is the answer, and it never leaves the Mac.
The sandbox is on, which matters for the part that comes next:
$ codesign -d --entitlements - .../photolibraryd 2>/dev/null | grep -A2 "com.apple.security.app-sandbox"
[Key] com.apple.security.app-sandbox
[Value]
[Bool] true
So this is a sandboxed process that cannot wander the disk, and one of the grants it was given is com.apple.security.assets.pictures.read-write. That single entitlement is why the daemon can open your library when a terminal or an editor cannot.
Why the library folder refuses to open
Try to look inside a Photos library from a shell and you get a message that reads like a permissions mistake:
$ ls -la ~/Pictures/Photos\ Library.photoslibrary/
ls: /Users/chethankumar/Pictures/Photos Library.photoslibrary/: Operation not permitted
The permissions do not explain it. The folder is readable and executable by you, and the only access control entry on its parent is a rule that stops the group from deleting the Pictures folder itself:
$ ls -le@d ~/Pictures/
drwx------+ 6 chethankumar staff 192 Sep 26 14:29 /Users/chethankumar/Pictures/
0: group:everyone deny delete
Operation not permitted, rather than permission denied, is the tell. That is the system’s privacy layer refusing on purpose rather than Unix saying no, and it is why this page contains no picture of what is inside the library. Three paths behave the same way on this Mac: the library bundle, the daemon’s own container, and the Photos folder inside your Library folder.
$ ls ~/Pictures/Wallpapers # ordinary folder, no output because it is empty
$ ls ~/Library/Photos # part of the Photos storage
ls: /Users/chethankumar/Library/Photos: Operation not permitted
$ ls ~/Library/Containers/com.apple.photolibraryd/Data/
ls: /Users/chethankumar/Library/Containers/com.apple.photolibraryd/Data/: Operation not permitted
That is worth knowing for a practical reason. Half the advice about this process involves deleting something. Delete the database, delete the cache, delete the container. On any Mac running a recent version of macOS you cannot do that from a normal shell in the first place, and if you grant Full Disk Access to make it possible, you have handed the keys to the library to a tool that has no idea how to write to it.
The 34 steps of opening a library
The most useful thing in the daemon’s log is also the least expected: it writes down what it is doing, step by step, in English. Each step is a named operation in an object called a library services state node, and the state machine they run through is short:
initializing -> prep-accessible -> prep-pre-migration -> prep-migration -> prep-post-migration -> running
There is also a state called unobtainable, which is what you see if the library cannot be reached at all. On this Mac the log recorded all seven states for one library inside a seven hour window, in that order, which is what a normal open looks like.
Then there is the queue of named operations. This is a direct quote from the log, lightly trimmed:
LSM-1: Starting operation {name = 'Notify library availability'} with QoS QOS_CLASS_UTILITY
LSM-1: Starting operation {name = 'Prefetch sensitive content analysis policy'}
LSM-1: Starting operation {name = 'Signal cascade donation'}
LSM-1: Starting operation {name = 'Open syndication library'}
LSM-1: Starting operation {name = 'Initialize photo stream'}
LSM-1: Starting operation {name = 'Initialize change handling'}
LSM-1: Starting operation {name = 'File System Import Notify Enter'}
LSM-1: Starting operation {name = 'Create singleton albums if required'}
LSM-1: Starting operation {name = 'Detect and enqueue outstanding transaction crash recovery operations'}
LSM-1: Starting operation {name = 'Update graph label set'}
LSM-1: Starting operation {name = 'Check for MAD version bump'}
LSM-1: Starting operation {name = 'Tell photoanalysisd about a newly opened library'}
LSM-1: Starting operation {name = 'Attribute photo library filesystem storage to its owner'}
LSM-1: Starting operation {name = 'Handle thumbnail rebuild request'}
LSM-1: Starting operation {name = 'File System Import'}
LSM-1: Starting operation {name = 'Start Journal Manager'}
LSM-1: Starting operation {name = 'Backup exclusion attribute'}
LSM-1: Starting operation {name = 'Initialize CPL manager'}
LSM-1: Starting operation {name = 'Handle locale change if necessary'}
LSM-1: Starting operation {name = 'Post migration finalization'}
LSM-1: Starting operation {name = 'Recovery from Duplicate Merge crash recovery'}
LSM-1: Starting operation {name = 'Asset creation recovery'}
LSM-1: Starting operation {name = 'Cleanup invalid SSBs'}
LSM-1: Starting operation {name = 'Register background job service on library'}
LSM-1: Starting operation {name = 'Initialize cache delete support'}
That is twenty five of the thirty four names the log uses on this machine, and the ones missing from it are the smaller checks that only run in some conditions, things like Check filesystem for Sync Root, Check for auto-create well-known library and Create constraints director.
Two of those lines deserve to be pointed at, because they answer questions people actually ask.
Attribute photo library filesystem storage to its owner is why your Photos library can turn up as System Data in the storage pane instead of under Photos. The daemon is handing macOS the accounting for its own files.
Detect and enqueue outstanding transaction crash recovery operations is why a Mac that lost power in the middle of an import does not usually lose photos. The work was journalled, and the first thing the library does on open is look for unfinished business and put it back on the list.
The whole sequence is the honest answer to “what is it doing.” It is not scanning your library. It is opening it, in the order it has to be opened in, with a name for every step.
The three background jobs
Once the library is open, the daemon registers a background job service on it. In the log, the service prints the jobs it is holding and how many items are pending on each:
label = "com.apple.photos.backgroundjobservice.submissioncoalescer";
"com.apple.photolibraryd.backgroundjobservice.duplicatedetector" = 1;
"com.apple.photolibraryd.backgroundjobservice.hubble" = 2;
"com.apple.photolibraryd.backgroundjobservice.lowprioritysearchcharger" = 1;
Three jobs, four pending items, and they did not move all day. That is worth dwelling on, because it is the opposite of what people expect when they see this process in Activity Monitor and assume it is chewing through something enormous.
The duplicate detector is the one most people will recognise when it fires, because Photos has a Duplicates album and something has to fill it. The low priority Spotlight charger walks the library and feeds items into the search index, and it is deliberately built to run at low priority so that a system wide search stays current without competing with you for the machine. And then there is a job called hubble, which is Apple’s internal name for it and carries no explanation anywhere on disk. It has two items pending here and it was not in a hurry about them.
Their scheduling is written into launchd rather than into the daemon, and it is about as explicit as scheduling gets:
| Job | Runs | Requires external power | Requires you to be idle |
|---|---|---|---|
curatedlibraryprocessing | every 3 h, at most once per 2 h | no | yes |
periodicmaintenance | daily, at most once per 12 h | yes | yes |
lowprioritysearchcharger | within 1 h of being asked | yes | yes |
duplicatedetector | within 4 h of being asked | yes | yes |
hubble | within 15 min of being asked | yes | no |
Read the last column, because that is the design. Every one of these jobs waits until you stop touching the keyboard, with a single exception, and nearly all of them wait for a power cable as well. The daemon is not supposed to work while you are working, and the scheduler that decides is not Photos at all. It is dasd, the power and background task daemon:
$ launchctl print gui/501/com.apple.photolibraryd | grep -E "state|runs|reason|monitor"
state = running
runs = 27
immediate reason = ipc (mach)
last exit reason = JETSAM_REASON_MEMORY_IDLE_EXIT
monitor = com.apple.dasd
Twenty seven starts. An immediate reason of ipc, meaning something asked for it over a mach port rather than it waking on a timer. And a last exit reason that is not a crash: a jetsam exit is the memory manager reclaiming a process that was sitting on memory while idle. The launch agent says the same thing in its own words, with EnablePressuredExit set to true and a process type of Adaptive. Both are instructions to launchd that the process should be kept while it is useful and dropped without ceremony when it is not.
That is also why force quitting it does not achieve anything. The same property list carries this:
"KeepAlive" => { "Crashed" => true }
Kill it, and launchd treats that as a crash and starts it again. The only thing you will have done is made the library reopen from scratch, which is the slowest thing it ever does.
Why it is so cheap, measured
Here is the part that should settle the question. All three daemons in the Photos pipeline were running on this Mac at the same moment, and one command compares them:
$ ps -o pid,rss,time,etime,comm -p 81700 81709 78454
PID RSS TIME ELAPSED COMM
81700 12512 0:01.51 07:06:21 .../PhotoLibraryServices.framework/Versions/A/Support/photolibraryd
81709 18656 0:03.27 07:06:27 .../PhotoAnalysis.framework/Versions/A/Support/photoanalysisd
78454 14672 2:45.87 07:33:58 .../MediaAnalysis.framework/Versions/A/mediaanalysisd
In macOS, the time column is minutes and seconds, so those read as one and a half seconds, three seconds, and two minutes and forty six seconds. The process that owns the library, the one people search for and worry about, had used the least processor time of the three by two orders of magnitude. The one doing the machine learning had done a hundred times more work, and it is the one nobody notices because its name does not sound like something that has your files.
That is the right frame for this whole family. Owning a library is mostly bookkeeping. Reading it is the expensive part.
Even the naming is misleading in the other direction. The daemon is one point two megabytes, photoanalysisd is three hundred and sixty three kilobytes, and mediaanalysisd is eleven megabytes because it carries the models. Size tells you about the work, not about the risk.
So what has it actually been doing
A day’s worth of this daemon’s log on this Mac runs to 2,456 lines, which sounds like a lot until you sort them:
$ log show --predicate 'process == "photolibraryd"' --last 24h \
| grep -oE "\[com.apple.photos.backend:[A-Za-z.]+\]" | sort | uniq -c | sort -rn
381 [com.apple.photos.backend:LibraryServices]
148 [com.apple.photos.backend:Syndication]
126 [com.apple.photos.backend:Backend]
46 [com.apple.photos.backend:GatekeeperXPC]
37 [com.apple.photos.backend:ResourceCaching]
32 [com.apple.photos.backend:Migration]
32 [com.apple.photos.backend:AnalysisCoordinator]
21 [com.apple.photos.backend:PhotoSharing]
16 [com.apple.photos.backend:BackgroundJobService]
14 [com.apple.photos.backend:PhotosObjectLifecycle]
8 [com.apple.photos.backend:ChangeHandling]
6 [com.apple.photos.backend:FeatureAvailability]
4 [com.apple.photos.backend:LibraryBundle]
4 [com.apple.photos.backend:AssetImport]
2 [com.apple.photos.backend:DuplicateDetection]
Library services at the top, which is the open sequence, then syndication, which is the shared library and Spotlight work, then ordinary backend housekeeping. Two lines for duplicate detection in a whole day, which matches the four pending items above.
The syndication lines are the ones that explain what the process is for, and one of them is worth quoting in full:
[sync.spotlightReceiver] addOrUpdateSearchableItems, itemCount:1, bundleID:<private>
There were 59 of those in the day, each one adding an item to the search index. That is the mechanism behind a thing you have probably used without thinking about it: the reason a photo of a dog can be found by searching a handful of words is that this daemon put it in Spotlight’s index and told it what was in it.
Next to them were 19 lines like this one:
[sync.spotlightReceiver] Chat was updated: BCE1983E-... autoDonating=0 (was on) in library ...
That is Messages again, and autoDonating is the daemon’s own word for the guess it is making about you. It is deciding whether a conversation is one it should propose for automatic sharing into a shared library, and on this Mac the answer was no for every chat it looked at. Apple has never published that flag name, and there it is in the log, spelled plainly.
Then there is the cache side, which is the part that touches your disk:
(CacheDelete) [com.apple.cache_delete:client] Registered: com.apple.photolibraryd.cacheDelete, result: 0
That registration is the daemon volunteering to be asked a question. When macOS is short of space, it asks every registered service how much it could give back, and Photos answers through this daemon because it is the only process that knows which thumbnails, renders and downloads are safe to throw away. If the System Data figure in your storage pane moves after a while, this is a thread worth pulling.
The iCloud half is a different process
Everything above is the local library. The sync side has its own daemon, cloudphotod, and telling them apart fixes a lot of confusion. It is noticeably bigger and it names the whole cast it works with:
$ ls -l /System/Library/PrivateFrameworks/CloudPhotoLibrary.framework/Versions/A/Support/cloudphotod
-rwxr-xr-x 1 root wheel 9990608 Sep 24 12:40 cloudphotod
Nearly ten megabytes, and its launch agent lists who joins in when a first download begins:
"com.apple.cloudphotod.initialdownload.fastpass" => {
"InvolvedProcesses" => [ "cloudphotod", "nsurlsessiond", "cloudd",
"com.apple.photos.VideoConversionService",
"com.apple.photos.ImageConversionService",
"photolibraryd" ]
Six processes for one job, and the reason is mundane: cloudphotod coordinates, nsurlsessiond does the transferring, cloudd talks to iCloud generally, the two conversion services make the versions your devices need, and photolibraryd writes the result into the library, because it is the only one allowed to. Its own mach services include com.apple.photos.cloud.pushnotification and one named com.apple.aps.photos.cloud.datarepair, which is an unusually honest name for what happens when a sync goes wrong.
That split is worth remembering the next time Photos looks stuck. If the progress bar says it is downloading, the busy process is likely cloudphotod or nsurlsessiond. If Photos is slow to open, or a library has to be rebuilt, photolibraryd is the one doing it.
Can you stop it?
Apple does not document this process at all. The term does not appear in the 211 topics in the macOS user guide index, it does not appear in any of the pages consulted for this article, including the Photos guide’s own section on the library file, and it is not named on the Photos privacy page either. Everything above came from the operating system’s own files rather than from a support article about it.
There is also no on switch, and the reason is structural. The launch agent declares four mach services, four launch events, and a set of jobs that are scheduled by another daemon entirely. It is not a service waiting to be turned off, it is a thing that gets asked to do work, and it will get asked again the moment you open Photos.
What you can change is how often it is asked, and every lever is upstream:
Quit Photos when you are finished with it. The library closes, the daemon goes idle, and the background jobs lose their reason to run.
Unplug the Mac if you would rather the heavy jobs waited. Four of the five schedule entries in that table require external power, so on battery the daemon is mostly left alone, which is also why a laptop that is always plugged in does more of this work than one that is not.
Turn off iCloud Photos if you do not want the sync pipeline running. In Photos, Settings, iCloud, the iCloud Photos checkbox stops the flow at the source, and Apple’s own page on it explains that the library then remains in iCloud and available to your other devices. Note that only the System Photo Library ever syncs, which is why a second library you created stays exactly where you left it.
And if the library itself is the problem, there is a lane built for it. Apple documents it as Repair your photo library: quit Photos, then hold Option and Command while opening it, and choose Repair in the window that appears, which rebuilds the library. Apple’s instruction to back it up first is not boilerplate. That is the same daemon doing an honest rebuild, and it is the one time you will see it use a lot of processor time on purpose.
What not to do is the advice you will find most often. Deleting the container, truncating a database, or disabling the launch agent will either fail because of the sandbox and the system volume, or succeed and leave you with a library that has to be rebuilt from a backup you may not have.
The words Apple ships with it
One more thing is worth showing, because it is the closest thing to an explanation of what the daemon is for that ships without being written down. Next to the binary are six string tables holding 1,137 English phrases, and they are the sentences you have seen on screen without ever wondering who produced them:
There is a problem with the Photos library.
Please launch Photos to fix it.
To view and select photos, update your photo library.
Syncing...
Downloading...
Restoring...
Unable to Upload
iCloud Photos is paused; unable to download.
Write failed
That is the vocabulary of a library, not of a photo editor. There is no word here about cropping, filters or albums. Every phrase is about opening the library, updating it, moving things into it, or telling you it cannot. That is exactly the job description, written by the people who wrote the process, in the file the process loads on every launch.
Where window managers fit
Nothing on this page is a window problem, and dressing it up as one would be dishonest. A daemon that opens a database and runs three scheduled jobs is doing real work, and the fact that it is cheap does not make it a fault. If a Mac feels slow, the causes in this family are the analysis daemons, not this one.
The other kind of slowness, the kind where a fast machine still cannot find anything, comes from what is on the screen rather than what is behind it. Twenty windows stacked in one corner, a Dock you have stopped reading, and Control Up used as an expedition will do more to make a Mac feel slow than any background daemon, and unlike the daemon you can fix that in about 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
photolibraryd is the process that owns your Photos library. It runs as you, in a sandbox, from a one point two megabyte binary inside a System framework, signed by Apple under the platform authority. It is the only one of the three Photos daemons that is allowed to open the library, and the only one allowed to talk to the other two, which is the entire architecture in a sentence.
It keeps its own log, and the log is the answer to the only question that matters. A library open is a fixed sequence of about thirty named steps, starting with the crash recovery queue and ending with the cache delete registration. Three background jobs stay registered on the open library, and on this Mac they sat with four items pending for a whole day.
The measurements make the point better than any reassurance. It had used one and a half seconds of processor time across seven hours, against three seconds for the analysis scheduler and two minutes and forty six seconds for the media analysis daemon. The process with the scary name is the cheapest one in the pipeline.
And if you do want to reduce it, the answer is not to attack the process. Quit Photos, unplug the laptop, or turn off iCloud Photos. The levers are all upstream, because this is the one thing in the system that is allowed to hold your library, and that is not a design mistake.
Questions
What is photolibraryd on my Mac?
It is the process that owns your Photos library. Its path is /System/Library/PrivateFrameworks/PhotoLibraryServices.framework/Versions/A/Support/photolibraryd, it is signed by Apple, and it runs in a sandbox as your user account rather than as a system account. Everything Photos does to a library goes through it: opening it, importing into it, migrating it after an update, telling Spotlight what is in it, telling the analysis daemons what needs looking at, and answering when macOS asks how much disk space the library could give back. It is not a virus, and on this Mac it had used one and a half seconds of processor time across seven hours of running.
Why is photolibraryd using so much CPU?
Usually because it is opening a library, not because it is analysing one. It keeps a set of named background jobs, and three of them were registered and pending on this Mac: a duplicate detector, a job called hubble, and a low priority Spotlight charger. A library open runs a fixed sequence of about thirty named steps, and the log prints each one as it starts. On a healthy Mac it stays near zero percent and wakes in bursts when Photos is opened, when you import, or when a background job fires. If it is pinned at high CPU for a long time, the library is more likely in trouble than the process.
Is photolibraryd a virus or malware?
No. It ships with macOS inside a framework in the System folder, it is signed by Apple under the authority macOS Software Signing, its identifier is com.apple.photolibraryd, and it is a universal binary carrying three architectures. It is also sandboxed, which means it can only reach the folders it has been granted. The reason it looks suspicious is the name: a process with no icon, no window and a d on the end is exactly what a piece of malware would be called, except that malware would not be able to live in the System folder in the first place.
Can I stop or disable photolibraryd?
Not permanently, and trying is where people damage their libraries. Its launch agent sets KeepAlive for the Crashed case, so launchd brings it straight back if you force quit it. It is also not a free standing service with an on switch: it is started on demand through four mach services, and it owns the only thing that is allowed to open the database. The levers that work are all upstream of it. Quit Photos when you are not using it, keep the Mac unplugged if you want the maintenance jobs to be deferred, and turn off iCloud Photos if you do not want the sync side running at all.
What is the difference between photolibraryd, photoanalysisd and mediaanalysisd?
They are three stages of one pipeline, and photolibraryd is the first. It owns the library and decides what needs doing. photoanalysisd is the scheduler that picks what to analyse and in what order. mediaanalysisd is the one that actually looks at the images with machine learning models. Reading the entitlements of photolibraryd is the clearest proof of the arrangement, because it is the only one of the three with permission to talk to the other two: com.apple.private.photoanalysisd.access and com.apple.mediaanalysisd.client are both in its list. It also had the smallest CPU figure of the three on this Mac, by a wide margin.
Ready? Buy Ribbon for $15, or read all the guides.