What is photolibraryd on Mac, and why is it using the network?

Last updated: 2026-08-08

What it is

photolibraryd is a built-in macOS agent for the Photos library. Apple’s system manual describes it as the process that handles all photo-library requests. System binaries and launch configuration also show it taking part in library maintenance, thumbnail repair, library migration, and creation or upkeep of the Spotlight search index.

That makes photolibraryd an important part of the local Photos infrastructure, but it does not perform every photo-related job on its own. Apple assigns iCloud Photos activity primarily to cloudphotod. Shared Albums are primarily handled by mstreamd, while photoanalysisd performs analysis such as recognizing people, memories, and scenes. These distinctions matter when interpreting activity in a process monitor: seeing photolibraryd active does not establish that it is the process transferring all of the associated photos or videos.

Its verified executable is located at /System/Library/PrivateFrameworks/PhotoLibraryServices.framework/Versions/A/Support/photolibraryd, and its signing identifier is com.apple.photolibraryd.

Why it talks to the network

The network role of photolibraryd is narrower and less clearly documented than its local-library role. Apple’s manual pages attribute iCloud Photos activity to cloudphotod and Shared Albums activity to mstreamd. At the same time, the current macOS launch configuration registers background nsurlsessiond events for photolibraryd, and cloudphotod’s initial-download task explicitly lists photolibraryd as a participating process.

As a result, several photo operations may wake photolibraryd while network activity is taking place. These include the first synchronization of a library, importing or modifying photos, requesting an original that has not yet been stored on the Mac, receiving Shared Albums updates, and checking the library again after a repair. Some supporting traffic may consequently be recorded under the photolibraryd process name even when another photo service performs most of the media transfer.

Any remote objects involved should belong to Apple’s iCloud Photos or photo-sharing services. However, Apple has not published a set of hosts used exclusively by photolibraryd, the contents of its requests, or a byte-by-byte division of responsibility between photolibraryd, cloudphotod, mstreamd, and nsurlsessiond. Those details remain unverified. A process-level traffic total therefore cannot, by itself, identify what was sent or determine which cooperating service performed each part of the operation.

How much traffic is normal

There is no reliable fixed range for normal photolibraryd traffic. Apple does not publish a per-process baseline, so a specific number of megabytes would create a false expectation.

When photolibraryd is only maintaining a local library, repairing thumbnails, or supporting search indexing, its external network traffic should be close to zero. In a stable library, traffic directly attributed to it may consist mainly of state or metadata activity. Even that is a cautious expectation rather than a guaranteed ceiling.

During an initial sync, a request for originals, or a library recheck following repair, photolibraryd may be active at the same time as traffic on the scale of photos, videos, or an entire library. The main media transfers are usually handled by cloudphotod, mstreamd, or nsurlsessiond, but the available documentation does not provide a dependable way to divide every byte among them. “Usually small” should therefore not be treated as a promise about this process.

Can you turn it off

Apple does not provide a separate switch for photolibraryd. The appropriate verdict is to keep it: it is a core Photos library service, not an optional network client with its own supported disable control.

Force-quitting or otherwise disabling it can interrupt Photos library requests, thumbnail maintenance, Spotlight search-index work, migration, and other background library maintenance. launchd may also start it again when macOS or Photos needs the service. Removing its launch configuration, deleting library databases, or clearing files manually is not a supported substitute for diagnosing a library problem.

If the goal is only to stop iCloud Photos synchronization, use Apple menu  > System Settings > [your name] > iCloud > Photos under “Saved to iCloud” > turn off “Sync this Mac.” This stops the related cloud updates, but it does not disable photolibraryd. Local Photos libraries still rely on the agent.

What people get wrong

• “photolibraryd is malware, a cryptocurrency miner, or a third-party uploader.” That is not correct for the executable at the verified macOS system path. Its code-signing identifier is com.apple.photolibraryd, and its designated requirement includes an Apple anchor. A different file using the same name outside that path is a separate case and still needs independent verification.

• “photolibraryd is the iCloud Photos upload and download process.” That description is too broad. photolibraryd is first and foremost the local Photos library agent. Apple’s manual pages assign iCloud Photos activity to cloudphotod and Shared Albums to mstreamd, even though photolibraryd can participate in related workflows.

• “It only handles thumbnails, so any network connection is suspicious.” Its responsibilities go beyond thumbnails. Current system configuration associates it with photo-sync tasks and background URLSession events. That explains why network activity can accompany legitimate work, although it does not reveal the exact request contents.

• “Turning off iCloud Photos will permanently stop photolibraryd.” Turning off synchronization stops the relevant cloud updates. It does not remove the local Photos service, and photolibraryd can continue running for library requests, indexing, migration, repair, or other maintenance.

• “If it runs for a long time or uses more CPU, I should remove its launch item, delete the Photos database, or clear its caches.” Large-library maintenance, migration, indexing, and repair can all keep it active. If the library appears damaged, back it up first and use Apple’s Photos Repair Library tool instead of manually damaging system launch items or library files.

Seeing what it actually used

If the activity seems unusual, the next step is to inspect photolibraryd’s per-process totals over the same period in Bytetally and compare the timing with a sync, import, original request, or repair. Also check cloudphotod and nsurlsessiond during that window, because the documented responsibilities overlap. Traffic totals can show how much was attributed to each process, but they cannot reveal the unpublished request contents or prove an exclusive byte-by-byte division.

Related processes

Common questions