HeartbeatHocusFocusFilesMacHyperTile
Guide

audiomxd, the daemon that decides where your sound goes

audiomxd decides which nearby Apple device your sound belongs to. Measured: one run since boot, about nine seconds of CPU a day, sealed behind its own account.

By Chethan Kumar S N · Updated

You are listening on your iPhone. You open your MacBook, and the AirPods flip. The music did not stop, it moved, and you never clicked anything. Somewhere under that handoff a decision was made, Mac or iPhone, and the process that makes it is called audiomxd.

The name looks like keyboard mash until you decode it. Audio, the subject. The d on the end, the family suffix every daemon carries, from httpd to launchd. And the mx in the middle, which is the real clue: it stands for MediaExperience, the name of the private framework the binary links before almost anything else. Apple’s own account database says the same thing out loud. The daemon runs as a reserved user whose real name is not audiomxd but Audio and MediaExperience Daemon.

Unlike most processes in this series, this one has a manual page, and it is short enough to quote whole. audiomxd(1), dated October 20 2022: “audiomxd is a daemon that manages audio route arbitration on macOS along with other nearby Apple devices such as iPhones and iPads. audiomxd was introduced with macOS version 14.0.” Two sentences, and the first one answers the question people actually type: this is the machinery under automatic device switching, the part that talks to the other gadgets in the room.

Here is what it looks like on a real Mac, macOS 27.0.1 on a MacBook Pro, 29 days of uptime, the same machine this site’s other daemon pages are measured on.

The receipts

WhatMeasured
Path/usr/libexec/audiomxd, on the sealed system volume
Size565,104 bytes, three architectures in one file: x86_64, arm64e and arm64e.x1
SignatureApple platform binary, identifier com.apple.audiomxd
User_audiomxd, its own reserved account, user id 294
Runs1 since boot 29 days ago, and it has never exited
Processor time4 minutes 33 seconds across 29 days, about nine seconds a day
Memory6.3 MB resident. The 466 GB in the virtual column is reserved address space, not usage
Memory cap200 MB soft limit, enforced by the system’s jetsam policer
Home/private/var/db/audiomxd, and asking to read it gets Permission denied
Manual pageaudiomxd(1), dated October 20 2022, two sentences long
Log volumeZero lines in a thirty minute window: it works silently
Siblingcoreaudiod, one second older, at 1,893 hours of processor time over the same 29 days

Put the two side by side and the division of labour is the whole story:

ps -o pid,rss,time,etime,comm -p 659 868
  PID   RSS       TIME      ELAPSED          COMM
  659  53600  1893:26.24  29-03:12:27       /usr/sbin/coreaudiod
  868   6336     4:32.97  29-03:12:26       /usr/libexec/audiomxd

The sound server that touches the hardware has burned 1,893 hours keeping audio alive. The referee that decides where it goes has spent four and a half minutes. One is a power plant, the other is a committee.

The search picture matches a name people meet by accident, usually on an iPhone first. The bare seed returns audiomxd itself, then audiomxd high cpu usage reddit, is audiomxd, audiomxd iphone 11 pro and stacks audiomxd. The what is family tops out with what is audiomxd in activity monitor, the exact question this page answers, alongside what is audiomxd on iphone. The mac family carries macos audiomxd high cpu. And there is no virus row anywhere in the family, which for a process with this strange a name is its own quiet finding.

A launch file that is still under construction

The best description of this daemon is not the manual page, it is the launch file, /System/Library/LaunchDaemons/com.apple.audiomxd.plist, because that file reads like a half finished move. audiomxd exposes thirteen doors over Mach, and only three of them are open:

The doorState in the launch file
com.apple.coremedia.systemcontroller.xpcOpen, unconditional, listed twice
com.apple.audio.voicetrigger.xpcOpen, unconditional
com.apple.audio.orchestrator.registrar.serviceOpen, unconditional
com.apple.audio.AudioSessionBuilt, locked behind the SmartRoutingMacOS flag
com.apple.mediaexperience.endpoint.xpcBuilt, locked behind the same flag
com.apple.coremedia.volumecontroller.xpcBuilt, locked behind MoveMXRoutingToAudiomxdOnMac
com.apple.coremedia.routediscoverer.xpcBuilt, locked behind the same flag
com.apple.coremedia.routingcontext.xpcBuilt, locked behind the same flag
com.apple.coremedia.endpointuiagent.xpcBuilt, locked behind the same flag
com.apple.audio.SystemSoundServer-OSXBuilt, locked behind sss_in_audiomxd
com.apple.airplay.agent.servicesBuilt, locked behind a flag
com.apple.mediaexperience.xctest.xpcBuilt, locked, a testing door

Read the flag names and you can watch the migration in progress. SmartRoutingMacOS, the feature that hands your AirPods to whatever you just picked up. MoveMXRoutingToAudiomxdOnMac, which says plainly that routing work is being moved into this daemon. sss_in_audiomxd, the system sound server packing its bags. The doors are framed, hinged and sitting in the file, and they open the day Apple flips the flags in a system update. That is what a daemon looks like in the middle of being promoted.

The launch file even carries a sentence Apple probably did not mean to ship. Above the last key sits a code comment explaining a conclave setting, and the comment cites its source: a link to a thread on Apple’s internal Slack, dated April 2025, visible to anyone who reads the plist on their own Mac. Nothing secret is leaked, the link opens nowhere without an Apple login. It is just odd, in the way a builder’s chalk mark on a finished wall is odd, and it confirms the same thing the flags do: this file is worked on, actively, by people mid job.

An iPhone daemon that moved in

The sandbox profile tells you where this daemon grew up. com.apple.audiomxd.sb, 118 lines on the sealed system volume, is stamped Copyright 2017, which is six years before the Mac version existed and one year before the Mac hardware this site is measured on was announced. The profile was written for the iPhone, where audiomxd is a familiar suspect, and it came across with macOS 14.

Inside, the anatomy of a referee. It reads the Bluetooth preferences and the network configuration, because those are the inputs to any routing decision. It reads the audio plug in folders, /Library/Audio/Plug-Ins among them, so it knows what virtual devices exist. It holds three IOKit keys to the audio engine, the control channel, the engine channel and the power domain. Then the phone book, thirty six Mach services it is allowed to call, and the list is a cast list for Continuity: the AirPlay endpoints, both Bluetooth services, the sound server, the media remote daemon, the system controller, even the time synchronisation expositor, because two devices handing off audio must agree on the clock.

And in all 118 lines there is not one network permission. No outbound rule, no remote connect, nothing. The daemon that decides which of your devices gets the AirPods cannot talk to the internet at all. Its whole world is the machine it runs on, the radios it reads, and the Apple devices in the room, reached through other local processes. Its one writable corner is /private/var/db/audiomxd, and when an administrator’s terminal asks to look inside, macOS answers Permission denied, the same privacy wall this series keeps meeting around sealed stores.

The honest cost

Measured plainly: one run since boot, about nine seconds of processor time a day, six megabytes of memory, zero log lines while you watch. On the iPhone side of the family, audiomxd is a name that shows up in battery drain threads, and the high cpu rows in its search family are real. On a Mac, the same daemon is nearly free, because a Mac is usually the only candidate in the room and arbitration with no rivals costs nothing.

If it ever does climb, the question is never the daemon, it is the negotiation: two devices fighting over one pair of headphones, or a headset that keeps dropping. Restart it, with the kickstart command above, and if the climb returns, follow the flipping device instead. Meanwhile it asks for nothing: no settings, no configuration, no attention. The handoff either works, in which case you never think about it, or it annoys you, in which case the fix is in Bluetooth settings, not Activity Monitor. The referee is not the problem. The referee is why the music moved.

Questions

What is audiomxd on my Mac?

It is the daemon Apple's manual page describes in one line: a daemon that manages audio route arbitration on macOS along with other nearby Apple devices such as iPhones and iPads. Route arbitration is the decision half of audio. When your AirPods jump from your iPhone to your Mac because you opened the lid, something had to weigh the candidates and pick a winner, and this is that something. It ships with the system, launchd starts it at boot under its own reserved account named _audiomxd, and the manual says it arrived with macOS 14.0. It is signed by Apple on the sealed system volume, like every process in this series.

Why is audiomxd using so much memory?

Almost certainly it is not. The real number on the measured Mac is 6.3 MB of resident memory, and launchd holds a kill switch over it anyway, a soft memory cap of 200 MB that recycles the daemon if it ever crosses the line. The number that startles people is the virtual memory column, 466 GB on the same process, and that column is bookkeeping, not usage: it counts the address space the daemon reserves, some of it for the audio stacks it is prepared to host, and almost none of it is backed by real RAM. If Activity Monitor's Memory tab worries you, read the Memory column, never the Virtual Memory column.

Why would audiomxd use high CPU?

Because a negotiation is looping, not because the daemon is busy thinking. Its baseline on the measured Mac is about nine seconds of processor time a day across 29 days, one continuous run since boot, so any real spike is event driven: AirPods flipping back and forth between two devices, a Bluetooth headset renegotiating, an iPhone nearby repeatedly advertising itself as an audio target. The restart that clears a stuck state is sudo launchctl kickstart -k system/com.apple.audiomxd, sound blips for a moment and routing rebuilds. But if it climbs again within minutes, the loop is still live somewhere, and the device to fix is the one doing the flipping, not the referee.

Is audiomxd a virus or something Apple installed?

It is Apple's, and you can check in five seconds. The real daemon lives at exactly /usr/libexec/audiomxd, and codesign -dv on that path reports Identifier=com.apple.audiomxd with a platform signature, the class of signing Apple reserves for its own operating system files. Malware does occasionally dress up as system process names, so the path column in Activity Monitor is the honest test: a copy running from anywhere except /usr/libexec, or out of an Xcode simulator runtime, is not this daemon. There is no virus row in its search family at all. The name just looks strange because it compresses MediaExperience into mx.

What is the difference between audiomxd and coreaudiod?

One owns the hardware, the other owns the decision. coreaudiod is the sound server, the daemon every app talks to in order to actually play and record, and it measured about an hour of processor time a day on this machine. audiomxd sits beside it as the referee for where audio goes, which device, which output, which of your Apple gadgets gets the AirPods, and it measured four and a half minutes across 29 days, roughly nine seconds a day. They even start together: on the measured Mac audiomxd came up one second after coreaudiod, and each runs under its own reserved account, _audiomxd and _coreaudiod.

Can I quit or disable audiomxd?

Not in any way that sticks, and there is no reason to. It is a system LaunchDaemon on the sealed system volume, its launch file sets EnablePressuredExit to false so the system will not reclaim it for convenience, and on the measured Mac it had run exactly once, continuously, since boot 29 days earlier. There is no settings switch for route arbitration anywhere in System Settings because the feature it serves is invisible by design: devices hand off and you never see the paperwork. The lever you actually have is the same as for any stuck audio state, restart the daemon, and it comes back within seconds, picked up again by launchd.

Ready? Buy Ribbon for $15, or read all the guides.