Thrum

What is diskimagesiod, and why is it using CPU or disk?

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

diskimagesiod handles the input and output for disk images attached to your Mac, such as .dmg files, sparse bundles and images used by other software. It uses CPU and disk whenever something reads from or writes to an attached image, especially a compressed or encrypted one. Ejecting images you are not using stops it.

diskimagesiod at a glance

diskimagesiod
Made byApple (part of macOS, DiskImages2)
TypeSystem daemon
Location/usr/libexec/diskimagesiod
Runs as_diskimagesiod (a system account)
Started bylaunchd job com.apple.diskimagesiod
Can you quit it?Not while an image is in use: it carries the image's reads and writes. Eject the image instead.

What is diskimagesiod?

The diskimagesiod(8) man page says it manages attached disk images and is part of the DiskImages2 framework. A disk image is, in Apple's words, a file that contains other files and folders. When one is attached, macOS sees it as a disk, and every read and write to that disk is turned into reads and writes of the image file by diskimagesiod.

Its launchd job allows several copies at once, so each attached image can have its own diskimagesiod. Two related jobs exist: com.apple.diskimagesiod.ram for RAM disks and com.apple.diskimagesiod.spb, which runs as root. The main job runs under the dedicated _diskimagesiod account.

Is diskimagesiod safe?

Yes. It is installed at /usr/libexec/diskimagesiod, signed by Apple (com.apple.diskimagesiod), and runs under its own restricted system account rather than as you or as root.

Why does diskimagesiod use so much CPU, disk and network?

How much disk is normal for diskimagesiod?

With no images attached there is no diskimagesiod running, or it is idle. While you copy from a downloaded installer, a short burst of CPU and disk is normal.

Steady activity during a network Time Machine backup or while a simulator runs is expected for as long as that work continues.

How do you stop diskimagesiod from using so much disk?

  1. List attached images. Run hdiutil info in Terminal. It lists every attached disk image and the file it comes from.
  2. Eject images you are done with. Eject them in Finder, or run hdiutil detach /dev/diskN with the device name from hdiutil info. Apple also recommends ejecting images when you finish, because a mounted image stays accessible to anyone using the Mac.
  3. Copy installers out, then eject. After dragging an app out of a .dmg, eject the image and delete the .dmg file if you no longer need it.
  4. Let backups and copies finish. If the image belongs to a network Time Machine backup, the activity ends when the backup completes.

When should you worry about diskimagesiod?

Look into it if diskimagesiod stays busy when hdiutil info shows no attached images, or when nothing should be using them. A restart detaches all images and clears it.

A diskimagesiod running outside /usr/libexec would not be Apple's.

How do you check diskimagesiod in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type diskimagesiod in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. 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 diskimagesiod process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password. nettop shows its live network traffic.

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'diskimagesiod' | grep -v grep
sudo fs_usage -w -f filesys diskimagesiod
nettop -p diskimagesiod

How can Thrum help with diskimagesiod?

Thrum's Disk tab shows read and write speed for the whole Mac, and its CPU and Memory tabs list diskimagesiod with the rest. macOS does not give per-process disk counters for processes owned by root or other users to an app without administrator rights, so Thrum shows diskimagesiod by CPU and memory, not by bytes written. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.

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 diskimagesiod

Why are there several diskimagesiod processes?

Its launchd job allows multiple instances, and attached images can each be served by their own copy.

Is diskimagesiod the same as hdiejectd?

No. diskimagesiod moves the data for attached images. hdiejectd manages attaching and ejecting them, and exits when no images are attached.

Sources