What is hdiejectd, and why is it running on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
hdiejectd is a macOS daemon that manages the disk images attached to the system and arbitrates attaching and ejecting them. It runs on demand while at least one image is attached and exits a short time after the last one is ejected. It is part of macOS and uses very little CPU.
hdiejectd at a glance
| hdiejectd | |
|---|---|
| Made by | Apple (part of macOS, DiskImages) |
| Type | System daemon |
| Location | /System/Library/PrivateFrameworks/DiskImages.framework/Resources/hdiejectd |
| Runs as | root |
| Started by | launchd job com.apple.hdiejectd |
| Can you quit it? | Yes, but it exits by itself shortly after the last disk image is ejected. |
What is hdiejectd?
The hdiejectd(8) man page says it manages disk images attached to the system, arbitrates the attach and eject processes, runs on demand, and exits automatically after a short time when no disk images remain attached. It has no settings.
The data inside an attached image is read and written by diskimagesiod; hdiejectd looks after the image's life cycle.
Is hdiejectd safe?
Yes. It is part of Apple's DiskImages private framework on the read-only system volume, runs as root, and is signed by Apple (com.apple.hdiejectd).
Why does hdiejectd use so much CPU?
- Opening a disk image. Double-clicking a .dmg or sparse bundle starts the attach process, which hdiejectd arbitrates.
- Ejecting. Ejecting an image in Finder or with
hdiutil detachgoes through hdiejectd as well. - Images attached by other software. Installers, backup tools and developer tools can attach images in the background, which keeps hdiejectd running for as long as they stay attached.
How much CPU is normal for hdiejectd?
Typically near 0% CPU with a small memory footprint. It is present only while images are attached.
If it is running when you have not opened any images, some software has attached one; that is usually expected.
How do you make hdiejectd exit?
- See which images are attached. Run
hdiutil infoin Terminal to list attached images and their source files. - Eject the images. Eject them in Finder's sidebar, or run
hdiutil detach /dev/diskNfor each device listed. - Wait a moment. Once no images are attached, hdiejectd exits by itself after a short time, as its man page describes.
When should you worry about hdiejectd?
Look into it if hdiejectd uses noticeable CPU for a long time, or an image refuses to eject. A restart detaches every image.
A process named hdiejectd outside the DiskImages framework path would not be Apple's.
How do you check hdiejectd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type hdiejectd 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 hdiejectd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'hdiejectd' | grep -v grep
How can Thrum help with hdiejectd?
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 hdiejectd 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. 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 hdiejectd
Why does hdiejectd keep running?
At least one disk image is still attached. hdiutil info shows which one.
Is hdiejectd needed?
Yes, for attaching and ejecting disk images. When none are attached it is not running.
Sources
- hdiejectd(8) man page: run man hdiejectd in Terminal
- hdiutil(1) man page: run man hdiutil in Terminal