What is AirPlayXPCHelper, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and code signature checked on macOS 26.3.1.
AirPlayXPCHelper is the macOS system helper that manages AirPlay: finding AirPlay speakers and TVs, keeping the list of output routes, and running streams to them. It uses CPU and network while you stream audio, video or a mirrored screen to an AirPlay device. It is part of macOS and safe.
AirPlayXPCHelper at a glance
| AirPlayXPCHelper | |
|---|---|
| Made by | Apple (part of macOS, AirPlay) |
| Type | System daemon |
| Location | /usr/libexec/AirPlayXPCHelper |
| Runs as | root |
| Started by | launchd job com.apple.AirPlayXPCHelper |
| Can you quit it? | Not usefully. launchd keeps it running, and AirPlay streams stop while it restarts. |
What is AirPlayXPCHelper?
Apple does not publish a man page for AirPlayXPCHelper. Its launchd job shows its role: it provides the media services for AirPlay endpoints (devices you can play to), an endpoint picker, route discovery, playback sessions, remote control, audio streams and volume control. launchd keeps it running as root.
AirPlay uses Bonjour to find devices; Apple lists UDP port 5353 (Multicast DNS) for AirPlay discovery and TCP port 7000 and the 49152 to 65535 range among AirPlay ports. The prompts you see, such as entering an AirPlay code for an Apple TV, come from AirPlayUIAgent.
Is AirPlayXPCHelper safe?
Yes. AirPlayXPCHelper is signed by Apple with the identifier com.apple.AirPlayXPCHelper and lives in /usr/libexec on the read-only system volume.
Why does AirPlayXPCHelper use so much CPU and network?
- Streaming to an AirPlay device. Sending music, video or a podcast to an Apple TV, HomePod or AirPlay speaker runs through it for the whole session.
- Screen mirroring. Mirroring or extending the display to an Apple TV or AirPlay-capable TV means encoding the screen continuously, which costs the most.
- Sending the stream. The stream goes over your local network, so network use rises with video quality.
- Looking for devices. Opening an AirPlay menu or picker makes it look for devices on the network.
How much CPU is normal for AirPlayXPCHelper?
Typical use is 0% CPU when nothing is streaming. Several percent while streaming audio, and more while mirroring the screen, is normal.
High CPU with nothing playing over AirPlay is not typical.
How do you stop AirPlayXPCHelper from using so much CPU?
- Stop AirPlay you are not using. Open Control Center and turn off Screen Mirroring, and switch audio output back to the Mac's speakers or headphones with the Sound control in Control Center.
- Check the network. A weak Wi-Fi signal makes streams retry. Move closer to the router or connect the Apple TV by Ethernet.
- Restart the AirPlay device. If streams stutter or the helper stays busy, restart the Apple TV or speaker.
When should you worry about AirPlayXPCHelper?
AirPlayXPCHelper busy for a long time with no AirPlay in use is unusual; restart the Mac. A copy outside /usr/libexec would not be Apple's.
How do you check AirPlayXPCHelper in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type AirPlayXPCHelper in the search field. The CPU tab shows its % CPU. 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 AirPlayXPCHelper process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). nettop shows its live network traffic.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'AirPlayXPCHelper' | grep -v grep
nettop -p <PID> # PID from the ps line above
How can Thrum help with AirPlayXPCHelper?
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 AirPlayXPCHelper 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 AirPlayXPCHelper
Why is AirPlayXPCHelper always running?
launchd keeps it running so AirPlay devices and audio routes are available at any time. It is idle when nothing streams.
Does it handle AirPlay to my Mac?
Apple does not document which process receives AirPlay. The AirPlay Receiver setting is in System Settings > General > AirDrop & Handoff.
Sources
- launchd job: plutil -p /System/Library/LaunchDaemons/com.apple.AirPlayXPCHelper.plist
- Apple Support: TCP and UDP ports used by Apple software products