Thrum

What is ContainerMetadataExtractor on my Mac?

Last reviewed: 19 November 2026. Path, bundle ID and code signature checked on macOS 26.3.1.

ContainerMetadataExtractor is a small helper that iCloud Drive uses to read information, such as names and icons, from an app's bundle for that app's iCloud container. It runs briefly when apps that use iCloud are installed or updated and then sits idle. It is part of macOS and safe.

ContainerMetadataExtractor at a glance

ContainerMetadataExtractor
Made byApple (part of macOS, iCloud Drive)
TypeXPC service
Location/System/Library/PrivateFrameworks/iCloudDriveService.framework/XPCServices/ContainerMetadataExtractor.xpc/Contents/MacOS/ContainerMetadataExtractor
Runs asyour user
Bundle IDcom.apple.CloudDocsDaemon.container-metadata-extractor
Can you quit it?Yes. macOS starts it again when iCloud Drive needs it.

What is ContainerMetadataExtractor?

ContainerMetadataExtractor is an XPC service (a helper process that a single part of macOS starts on demand) inside Apple's iCloudDriveService framework. Its bundle identifier is com.apple.CloudDocsDaemon.container-metadata-extractor, which ties it to iCloud Drive's daemon, bird.

An iCloud container is the storage area in iCloud that belongs to one app; apps that keep documents in iCloud Drive get their own folder there. The helper's job, as its name and internal functions show, is to extract metadata for a container from the app bundle that owns it, including properties and icons. Running that work in a separate process keeps bird from loading other apps' bundles itself.

Is ContainerMetadataExtractor safe?

Yes. It is inside the iCloudDriveService framework on the read-only system volume and is signed by Apple. It reads app bundles; it does not upload anything itself.

Why does ContainerMetadataExtractor use so much CPU and memory?

How much CPU is normal for ContainerMetadataExtractor?

It typically runs for a moment and uses little CPU or memory. It may stay listed in Activity Monitor while idle at 0% CPU.

How do you stop ContainerMetadataExtractor from using so much CPU?

  1. Let app installs and updates finish. After a batch of App Store updates, any extra activity stops once iCloud Drive has read the updated apps.
  2. Check whether iCloud Drive is busy. If bird is also busy, look at the iCloud Drive status icon in the Finder sidebar and let the sync finish.
  3. Quit it if it seems stuck. Select it in Activity Monitor and click the Stop button (the X in the toolbar), then click Quit. macOS starts it again only when it is needed.

When should you worry about ContainerMetadataExtractor?

Steady CPU use over a long time is unusual for this helper. If it keeps restarting at high CPU, an app with a damaged bundle may be the cause; check which apps were updated recently.

How do you check ContainerMetadataExtractor in Activity Monitor and Terminal?

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

In Terminal, the first command lists every ContainerMetadataExtractor process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'ContainerMetadataExtractor' | grep -v grep

How can Thrum help with ContainerMetadataExtractor?

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 ContainerMetadataExtractor 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 ContainerMetadataExtractor 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 ContainerMetadataExtractor

Can I delete ContainerMetadataExtractor?

No. It is on the read-only system volume and is part of iCloud Drive. Quitting it is harmless, and macOS starts it again when needed.

Does it send my data anywhere?

Its job is to read information from app bundles on this Mac for iCloud Drive. Syncing itself is done by bird and cloudd.

Sources