Thrum

What is icdd, and why is it using CPU on my Mac?

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

icdd is the Image Capture discovery daemon: when you connect a device that contains images, such as a camera, iPhone or scanner, it finds the right driver module so apps like Photos, Image Capture and Preview can use it. It is idle most of the time and busy when devices connect or network scanners are found. It is part of macOS and safe.

icdd at a glance

icdd
Made byApple (part of macOS, Image Capture)
TypeUser agent
Location/System/Library/Image Capture/Support/icdd
Runs asyour user
Started bylaunchd job com.apple.icdd
Can you quit it?Yes, but launchd starts it again at once, and cameras and scanners are not detected while it is gone.

What is icdd?

The man page describes icdd as the ImageCapture Discovery Daemon, a system daemon responsible for matching devices containing images with the appropriate driver modules. It runs as your user, starts at login and launchd keeps it running.

Camera communication over the PTP protocol is handled by a separate process, ptpcamerad; icdd decides which module handles which device.

Is icdd safe?

Yes. icdd lives in /System/Library/Image Capture/Support on the read-only system volume and runs from an Apple launch agent.

Why does icdd use so much CPU?

How much CPU is normal for icdd?

Typical use is 0% CPU, with brief activity when a device connects.

Sustained CPU with nothing connected is not typical.

How do you stop icdd from using so much CPU?

  1. Disconnect cameras and phones. Unplug devices you are not importing from and see whether icdd settles.
  2. Remove unused scanner software. Uninstall old scanner or camera driver packages using the maker's uninstaller.
  3. Remove old printers and scanners. In System Settings > Printers & Scanners, remove devices you no longer have.
  4. Quit icdd once. Select it in Activity Monitor and quit it. launchd starts a fresh copy.

When should you worry about icdd?

icdd at high CPU for a long time with nothing connected is unusual and often points to a third-party driver. A copy outside the Image Capture support folder would not be Apple's.

How do you check icdd in Activity Monitor and Terminal?

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

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

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

How can Thrum help with icdd?

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

Why does icdd run when I have no camera?

It starts at login so it is ready when any image device or scanner appears.

Is icdd related to Photos importing from my iPhone?

Yes. It finds the device and the driver; Photos or Image Capture then imports.

Sources