Thrum

What is AssetCacheLocatorService on my Mac?

Last reviewed: 19 November 2026. Path, accounts, launchd jobs and man page checked on macOS 26.3.1.

AssetCacheLocatorService is the Apple service that looks for content caches on your local network: Macs that keep copies of Apple software updates, apps and iCloud content so other devices can download them locally. It runs briefly when your Mac is about to download such content. It runs on every Mac, whether or not your network has a cache, and is safe.

AssetCacheLocatorService at a glance

AssetCacheLocatorService
Made byApple (part of macOS, Content Caching)
TypeXPC service (one copy per user, plus a system copy)
Location/System/Library/PrivateFrameworks/AssetCacheServices.framework/Versions/A/XPCServices/AssetCacheLocatorService.xpc/Contents/MacOS/AssetCacheLocatorService
Runs asyour user
Started bylaunchd job com.apple.AssetCacheLocatorService
Can you quit it?Yes, but launchd starts it again the next time a download looks for a cache.

What is AssetCacheLocatorService?

The man page says AssetCacheLocatorService finds macOS Content Caches on the local network. Apple's Mac User Guide explains that a Mac with Content Caching turned on stores software updates and apps downloaded from Apple, and optionally iCloud content, so client devices can get them from that Mac instead of the internet. AssetCacheLocatorService is the client side: it finds such a cache so downloads can use it.

On macOS 26 there are two copies: one runs as your user from a launch agent, and one runs as the _assetcache system account from a launch daemon. The command AssetCacheLocatorUtil reports what they find.

Is AssetCacheLocatorService safe?

Yes. It is an XPC service inside the AssetCacheServices framework in /System/Library, on the read-only system volume. It looks for caches; it does not share anything from your Mac.

Why does AssetCacheLocatorService use so much CPU and network?

How much CPU is normal for AssetCacheLocatorService?

Typical use is 0% CPU and almost no network. It appears for a moment around downloads and exits.

Sustained activity is not typical.

How do you check AssetCacheLocatorService's results?

  1. See which caches it finds. Run AssetCacheLocatorUtil in Terminal. It reports the content caches found for this Mac on the current network, including when there are none.
  2. Let downloads finish. If it appears during a software update or app download, it settles once the download starts.
  3. Quit it once if it misbehaves. If it uses CPU with nothing downloading, select it in Activity Monitor and quit it. launchd starts it again when needed.

When should you worry about AssetCacheLocatorService?

Constant CPU use is unusual. A copy outside the AssetCacheServices framework path would not be Apple's.

How do you check AssetCacheLocatorService in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), and type AssetCacheLocatorService in the search field. The CPU tab shows its % CPU. The Network tab shows its Sent Bytes and Rcvd Bytes. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every AssetCacheLocatorService process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). nettop shows its live network traffic.

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'AssetCacheLocatorService' | grep -v grep
nettop -p <PID>    # PID from the ps line above

How can Thrum help with AssetCacheLocatorService?

Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when AssetCacheLocatorService is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click AssetCacheLocatorService in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.

Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.

Questions about AssetCacheLocatorService

Does this mean my Mac is a content cache?

No. AssetCacheLocatorService only looks for caches. Your Mac serves as a cache only if Content Caching is turned on in System Settings > General > Sharing, which runs the AssetCache process.

Why are there two copies?

One runs for your user and one runs as the _assetcache system account.

Sources