# usbmuxd, the daemon at the iPhone end of the cable

> usbmuxd is the daemon every plugged-in iPhone talks through. Measured: a world-writable socket, a sandbox that reads USB descriptors, a week of silence.

Source: https://www.ribbonmac.com/guides/usbmuxd-mac · Updated 2026-11-17

Page down Activity Monitor to the letter u and there is a process most people have never had a reason to meet: usbmuxd, two megabytes of memory, no CPU to speak of, running since the day the Mac booted, under a user account you never created. It has no icon, no settings pane, and no public documentation beyond a manual page. It is also the only reason a cable between a Mac and an iPhone means anything at all.

The name decodes honestly. USB, mux short for multiplexer, d for daemon. A multiplexer is a switchboard: many conversations, one line. That is precisely the job. A phone plugged into a Mac offers a pile of services over that single USB connection at once, a backup here, a photo import there, a debugger, a syslog, and usbmuxd is the piece that splits the one physical pipe into numbered channels and lets the right app take the right line. Every iPhone-over-cable feature you have ever used on a Mac went through this one small process.

Here is the thing measured on a real Mac, macOS 27.0.1 on a MacBook Pro, 28 days of uptime, the same machine this site's other daemon pages are measured on.

## The receipts

| What | Measured |
|---|---|
| Path | /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/Resources/usbmuxd |
| Size | 661,632 bytes, three architectures in one file: x86_64, arm64 and arm64e |
| Version | usbmuxd-571.0.0.0.1, built 20 August 2026 |
| User | _usbmuxd, its own account, user ID 213 |
| Parent | launchd, process 1, always |
| Running | 28 days, one launch in total, never exited |
| Processor time | 21 seconds over 28 days, under a second a day |
| Memory | 2 MB resident |
| Manual page | usbmuxd(8), present, dated April 2017 |

Two rows deserve a pause. One launch in 28 days and never exited: this is not a process that crashes and comes back, it is furniture. And a manual page, which in this series of daemon measurements is almost an event, since most of these processes ship with none. usbmuxd has one, four short sections, and it opens with the best one-line job description of any of them:

> The usbmuxd daemon manages communications between MacOS hosts and iOS devices. USB and WiFi (via Bounjour) connections are supported.

That is Apple's own text, typo included: Bounjour, with an n, in a manual page that has shipped for nearly a decade. It also states that the daemon "is started automatically at boot time and does not require user or operator intervention", which is the whole management story in one line. There is nothing to administer. The options list is three flags long: `--version`, which prints the build string quoted in the table above, `--launchd`, which launchd passes it, and `--debug n` for a debug level nobody outside Apple has much use for.

## The launch file, read plainly

The configuration lives at /Library/Apple/System/Library/LaunchDaemons/com.apple.usbmuxd.plist, and every key in it is a small statement of intent. KeepAlive and RunAtLoad: start at boot, restart if it ever stops. EnableTransactions: it participates in the system's coordinated shutdown instead of being killed blind. EnablePressuredExit, set to false: under memory pressure, the system may not ask this daemon to volunteer to die, the same protected status the push daemon holds. POSIXSpawnType, Interactive: it is classed with interactive work, not batch work, because when a phone appears, someone is usually waiting on the other end of that cable.

launchd's own report fills in the life story. Minimum runtime ten seconds, exit timeout five, one run, zero forks, one exec, never exited. The memory governor has it on a short leash: a 60 MB soft limit and a 50 MB hard limit, generous against the 2 MB it actually uses, and a thread limit of 32. None of these numbers will ever matter to you, and that is the point. The configuration is Apple telling the system exactly how much rope this daemon gets, and the daemon using almost none of it.

## The socket: one door, mode 777

The single most interesting fact about usbmuxd is not in the process list. It is a file that is not a file: /var/run/usbmuxd, a Unix stream socket, created at boot, owned by root, with permission bits srw-rw-rw-. Read, write, execute for everyone. The launch file sets this on purpose: SockPathMode 511, which is 777 in decimal.

That openness is the design. Any process on the Mac, running as any user, may connect to that socket and start a conversation, and the conversation has a grammar you can read in the daemon's own strings. A client connects and requests the device list. The daemon answers with what is attached. The client then requests an attach or a connect to one device, identified the way USB identifies everything, a device number and a location ID, written in the log grammar as a number at an address, like 3 at 0x14100000. If a listener misbehaves there is a line ready for it too, "listener ignored, blacklisted", and a version check that refuses clients too old to talk sense: "using old version, current=".

On the measured Mac, at the moment of writing, the socket sat connected to nothing. Zero clients. The door was open all week and nobody knocked, which brings us to the week itself.

## A week of nothing

The unified log keeps a record of everything a daemon says, and most daemons say a lot. photolibraryd produced 2,456 lines in a day. accountsd logged a census of its callers. usbmuxd, over the last 24 hours, produced zero lines. Not near zero: zero. Over seven full days, a search of its entire log for every attach and detach line, the words it uses when a device appears or disappears, returned nothing at all.

The reason is sitting on the desk: no iPhone or iPad has been plugged into this Mac for at least a week. The daemon's whole vocabulary is device-shaped, "Attaching DeviceID", "Detaching DeviceID", "notify of device attach", "there are N listeners", and for seven days none of those sentences had a subject. This is the quietest daemon this series has measured, and it is quiet for the most honest possible reason: the hardware it exists for did not come near the machine.

That silence is also the answer to the CPU question people search for. usbmuxd cannot burn processor time thinking about phones. It wakes when something attaches, works while clients talk, and goes still. The searches for usbmuxd high cpu usage and usbmuxd 100 cpu describe the one scenario where it turns loud: a device that keeps appearing and vanishing, usually through a worn cable, a cheap hub or a dying port, each reconnection restarting the conversation. The fix is the physical layer, and the daemon is the messenger.

## What its sandbox confesses

macOS daemons this deep in the system ship with a sandbox profile, and usbmuxd's is a readable file at /System/Library/Sandbox/Profiles/com.apple.usbmuxd.sb. Most of it is the usual furniture, deny everything by default, then a short list of allowances, and then a list that is practically an anatomy lesson. To do its job, the daemon asks the system for permission to read USB descriptor properties, and the properties it names are the fields of a USB device's identity card:

| It asks to read | What that field is |
|---|---|
| idVendor, idProduct | Who made the device and which model it is |
| iManufacturer, iProduct, iSerialNumber | The strings a device reports about itself |
| bDeviceClass, bDeviceSubClass, bDeviceProtocol | What kind of device it claims to be |
| bMaxPacketSize0, bcdUSB, USBSpeed | How it talks and how fast |
| Bus Power Available, PortNum | The electrical facts of the port |
| SupportsIPhoneOS | Whether it is a phone-class device at all |

That last row is the whole daemon in one property name. usbmuxd does not watch USB in general. It asks each device, in effect, whether it supports iPhone OS, and a memory stick, a keyboard or a camera answers no, and the switchboard never engages. This was tested from the other side on this very Mac: the exFAT mount-and-write experiment described on the fseventsd page of this series plugged a volume into the machine, and usbmuxd's entire week of logs stayed empty. Disks are not its business.

The rest of the profile matches the job description. It may read and write exactly two places on disk: its own cache folder and /private/var/db/lockdown, the trust store. It may open network connections outward, which sounds broad until you read the man page again, USB and WiFi connections are supported, and the Wi-Fi path to a phone is a real network conversation, discovered through Bonjour, which explains the permissions to reach the DNS discovery daemon and the network configuration daemon. It may talk to one referee by name, the Trust Evaluation Agent, the system's own judge of whether a trust decision is sound. And the only extra code it is permitted to load is IOUSBLib, the USB library itself. The file even carries Apple's own build-time scaffolding left in the comments, a block labelled "Training wheels ON", commented out, above the live rules labelled "Training wheels OFF".

## The account and the trust store

The daemon does not run as root, and it does not run as you. It runs as _usbmuxd, user ID 213, a service account whose directory entry contains a real name field that most accounts leave blank: iPhone OS Device Helper. No home folder in /Users, no login shell. Instead, the account's home directory points straight at /var/db/lockdown, which is the tell.

That folder is where macOS keeps the records written the first time you connect a phone and tap Trust This Computer. Each trusted phone gets a record, the cryptographic proof of the handshake, and the account that owns those records is the account the daemon runs as. Try to look from the outside and the system stops you cold, an ls from an administrator's terminal returns Operation not permitted, the privacy wall, not a Unix permission, lifting only for tools granted Full Disk Access. A daemon that cannot be read by the admin of the machine, holding the keys to which phones this Mac trusts, is the opposite of a loose cannon. It is a key safe.

The code signature agrees. The binary carries exactly one entitlement, com.apple.private.security.storage.Lockdown, the right to that one storage domain, and nothing else. No access to your files, no screen, no location, no automation. Of every daemon measured in this series, this is the narrowest grant of them all.

## The cheapest entry in the ledger

This site keeps a running ledger of what macOS daemons cost, and usbmuxd takes the crown. Twenty-one seconds of processor time across 28 days is under a second a day, cheaper than CommCenter's two seconds, cheaper than the App Store agent's five, on a machine where the top spenders burn minutes a day. Its 2 MB of memory is a rounding error on a browser tab. A process this cheap, holding a door open for hardware that may never arrive, is about as close to free as software gets.

One last thing the search results will not explain on their own. Type usbmuxd into Google and the completions lean Linux: usbmuxd arch, usbmuxd fedora, usbmuxd ubuntu, usbmuxd windows. Nothing is wrong. Those rows belong to an open-source usbmuxd, maintained by the libimobiledevice project, that runs the same socket protocol on other systems so tools like its command-line clients can talk to iPhones there too. On a Mac the daemon is Apple's own, built into a private framework, and the two never meet.

So that is usbmuxd: a switchboard the size of a receipt, sitting since boot under an account named after a job description, holding open one world-writable door and one unreadable folder, waiting with a week of silence for a phone that has not called yet.

## FAQ

### What is usbmuxd on my Mac?

It is the USB multiplexer daemon, the process a manual page describes in one line: it manages communications between MacOS hosts and iOS devices. When you plug an iPhone or iPad into a Mac, the phone offers many services over that one cable at once, backups, photo imports, music sync, app debugging, and usbmuxd is the switchboard that splits the single USB connection into numbered channels and hands each one to whichever app asked for it. It runs under its own service account, _usbmuxd, from the moment the Mac boots, and every program that wants to talk to a plugged-in phone does so through one socket, /var/run/usbmuxd. It is part of macOS, signed on the sealed system volume, and there is nothing to remove.

### Why is usbmuxd using so much CPU?

On the measured Mac it was the cheapest process in the whole daemon ledger: 21 seconds of processor time across 28 days of running, under a second a day, on 2 MB of memory. When it does climb, the mechanism is visible in its own vocabulary, because its log lines are all about devices attaching and detaching. A phone or a cable that keeps dropping and reconnecting makes it work, and so does a client stuck in a connect loop, a photo import that restarts or a backup that never finishes. The fix ladder is physical first: another cable, another port, no hub in between, then close the syncing app doing the hammering. A plain USB stick cannot wake it at all. The device property its sandbox asks the system for is literally named SupportsIPhoneOS.

### What is the usbmuxd socket?

It is the one door every iPhone conversation on the Mac goes through: /var/run/usbmuxd, a Unix stream socket created at boot with permission bits 777, which means any local process may connect. A program that wants a phone opens that socket, asks for the list of attached devices, then asks to be connected to one of them by device number. The protocol is public enough that Linux and Windows machines run an open-source usbmuxd that listens at the same path, which is why searching the bare name leans Linux: those results belong to the open-source twin, not to something that has invaded your Mac.

### What is the _usbmuxd user account?

It is the daemon's own service account, least privilege applied to a switchboard: user ID 213, group 213, no login shell, and a real name in the local directory that says exactly what it is for, iPhone OS Device Helper. Its home directory is the telling part. The account's home is /var/db/lockdown, the folder where macOS keeps the trust records written when you tap Trust This Computer on a phone, and reading that folder needs Full Disk Access even from an administrator's terminal, where the answer comes back as Operation not permitted. The daemon holds the keys to the phone trust store, and nothing else on the Mac can casually read them.

### Can I quit or disable usbmuxd?

Not usefully. It is a system launch daemon configured with KeepAlive and RunAtLoad, and on the measured Mac it had launched exactly once in 28 days and never exited, which is launchd promising to start it again the moment it goes away. Killing it buys nothing even on a Mac that never sees an iPhone, because its measured cost is under a second of processor time a day and about 2 MB of memory. When it genuinely misbehaves, the cause is on the cable or in a client app, and the honest fix is the cable or the app, not the daemon.

### Is usbmuxd a virus or spyware?

No. It lives on the sealed, read-only system volume, is signed as an Apple platform binary, and runs inside a sandbox that denies everything by default and then asks for a short, inspectable list: the USB descriptor fields of attached devices, the lockdown trust folder, and outbound network for the Wi-Fi path to phones. It holds exactly one entitlement, the right to the lockdown storage. The one folder it owns is the one your own terminal cannot list without Full Disk Access. It shows up in virus searches for the same reason every unfamiliar process name does, people type the name plus the word virus and the box autocompletes the fear, and its manual page has been shipping since April 2017.
