rapportd, the daemon that lets your Apple devices find each other
rapportd is the daemon behind Handoff, call relay and device pairing on your Mac. What it listens for, why the firewall asks about it, and why there are three of them.
By Chethan Kumar S N · Updated
Two kinds of search land here.
One is a person who opened Activity Monitor, sorted by name, and found a process called rapportd that has been running since the day they set the Mac up. It has no icon and no window, they never installed anything with that name, and the internet’s first answer to any unfamiliar process is always the word virus. The other kind arrives from a dialog: macOS has asked whether rapportd should be allowed to accept incoming network connections, the wording sounds like a permission question about software, and nobody outside Apple has ever published a sentence explaining what this one does.
Both land on the same daemon, and it is less sinister than either search expects. rapportd runs Rapport, the protocol Apple devices use to notice each other, pair with each other, and hand work between each other. When your Mac relays a call from your iPhone, unlocks because your watch is nearby, or shows a handoff arrow in the Dock, this is one of the processes underneath.
Everything below comes from reading the process, its man page, the three launchd jobs that own it, its binary’s own strings, the files it holds open and the socket it listens on, on an M1 Pro MacBook Pro running macOS 27.0.1, build 26A434, with 25 days of uptime. Nothing was quit, no setting was changed, and the one command Apple’s documentation suggests for this daemon was run exactly once, which is a story later on this page.
What the process is, in one command
$ ps -Awwo pid,ppid,user,%cpu,rss,time,etime,args | grep "[r]apportd"
1037 1 chethankumar 0.0 10976 24:44.94 25-23:10:05 /usr/libexec/rapportd
Every column in that line says something.
Parent process 1 is launchd, so no app you opened started this and quitting the app that seems responsible will not stop it. The user is your own account rather than root, which is the first hint that pairing is treated as a per-person thing: your devices, your Apple Account, your daemon. The path, /usr/libexec/rapportd, is a system folder that file protection keeps locked, and the file is 5,123,552 bytes of Apple code, a universal arm64e build whose signature reads com.apple.rapportd with platform identifier 26, which is Apple’s own marking for a shipping OS component.
The time column is processor time rather than elapsed time: 24 minutes 45 seconds of actual work, against 25 days and 23 hours of existing. That works out at roughly 0.066 per cent of one core over the whole life of the process. A daemon can be many things, but with numbers like those it cannot be the reason a Mac feels slow, and the memory column agrees: 10,976 KB, about 10.7 MB, roughly a thirtieth of what one browser tab costs.
The man page is nine years old and two sentences long
Apple documents this daemon in /usr/share/man/man8/rapportd.8, dated 24 March 2016, and the whole thing is:
Daemon that enables Phone Call Handoff and other communication
features between Apple devices.
Use '/usr/libexec/rapportd -V' to get the version.
That is the entire official description of a protocol that has since grown to carry pairing, identity exchange and device discovery. Two sentences, one of which is wrong in an instructive way.
The page suggests running the binary with the --version style flag to print a version. Running it does not print anything. What it does is start a second rapportd, because that is what the binary does when executed, and macOS kills the stray copy moments later. On this Mac the command exited with code 137, which is a kill signal, and a process check afterwards confirmed only the original PID 1037 remained. So the one piece of advice in the man page is a leftover from a different era of the tool, and the honest version is: there is no supported way to ask rapportd for its version from the command line. The version exists, it just lives elsewhere, in the framework beside it: /System/Library/PrivateFrameworks/Rapport.framework carries CFBundleShortVersionString 7.1, build 1038.
Three jobs in launchd, and two share a name
Searching the launch folders for the daemon’s name returns three files, which is the first surprise, and two of them carry the exact same label, which is the second.
The one that is actually running is a per-user agent, /System/Library/LaunchAgents/com.apple.rapportd-user.plist, and its label is simply com.apple.rapportd. The second is a system-wide daemon, /System/Library/LaunchDaemons/com.apple.rapportd.plist, with the same label and one difference in its arguments: it runs the binary with --system. This is the same pattern the iCloud daemon cloudd uses, two copies of one program under one label, one for your login session and one for the machine. The third file launches a different program entirely, RapportUIAgent, a small app in CoreServices that exists to put things on screen when pairing needs to be shown to you.
On this Mac the states differ sharply. The user agent reports state running, runs = 1, pid 1037, and last exit code = never exited, meaning it has been up since login without a single crash. The system daemon reports state not running with runs = 0, meaning that in 25 days of uptime nothing has ever needed the system-wide copy on this machine. RapportUIAgent has also never run. That is a quiet but useful fact: a Mac that never triggers the features behind those two jobs simply never starts them, which is what on-demand looks like from the inside.
All three jobs carry the same three settings that describe rapportd’s temperament. EnablePressuredExit is true, so the system may reclaim its memory when idle and restart it later, which explains a rapportd that seems to vanish from Activity Monitor and reappear. EnableTransactions is true, so it finishes a unit of work and goes quiet rather than holding the machine awake. And there is no KeepAlive key at all: launchd does not keep it alive, it opens it when something knocks.
The twelve doors, read from the property list
The most readable description of what rapportd is for is not on Apple’s website. It is the Mach services list in its own property list, and each entry is a door with another process on the other side of it:
com.apple.rapport
com.apple.rapport.people
com.apple.rapport.private-discovery
com.apple.rapport.remote-text-input
com.apple.rapport.RPPairing
com.apple.rapport.StatusUpdates
com.apple.CompanionLink
com.apple.PairingManager
com.apple.RemoteDisplay
com.apple.ApplicationService.ServiceDiscovery
com.apple.private.alloy.coreduet.sync-idswake
com.apple.private.alloy.nearby-idswake
Twelve doors, and the names are a cast list of the two-device features. RPPairing is the pairing protocol itself, RP being Rapport, and PairingManager and CompanionLink sit beside it. RemoteDisplay is the screen-sharing side. remote-text-input and StatusUpdates are what they sound like: a way to send typing to another device, and a way to publish what a device is up to. The two entries with the word idswake in them are wake-ups from Apple’s identity services, the relay that carries traffic between devices that are not on the same network. The plain com.apple.rapport entry is the door the rest of the system uses.
The system-wide copy has just three doors of its own, and one of them names its feature outright: com.apple.AutoUnlock.System.AuthenticationHintsProvider. AutoUnlock is Apple Watch unlock, the Mac that wakes because the watch on your wrist is close and unlocked. The other two are service discovery entries, one of them for the push notification service. So the split is clean: your login session gets the pairing and handoff work, and the system copy exists for the machine-level features, watch unlock chief among them, which is why a Mac that never uses it never starts it.
The agent’s property list also declares what wakes it: a launch event matching one notification, com.apple.rapport.prefsChanged, and launchctl confirms the monitor for it is notifyd. Change a setting in the AirDrop & Handoff pane and it is notifyd that taps rapportd on the shoulder. The job also publishes an event of its own, com.apple.rapport.matching, which is how the rest of the system learns that a device was found or lost.
The listening socket, and the dialog it causes
Here is the answer to the firewall question, measured rather than guessed:
$ lsof -nP -i | grep rapportd
rapportd 1037 chethankumar 10u IPv4 ... TCP *:55038 (LISTEN)
rapportd 1037 chethankumar 11u IPv6 ... TCP *:55038 (LISTEN)
One TCP port, held open for listening on both IPv4 and IPv6, on all interfaces. The port number is chosen by the system, so yours may read differently than 55038, but the shape is the same: a socket waiting for another device to connect. That is what a listening socket is for, and holding one is the exact condition that makes macOS’s firewall ask whether a process may accept incoming network connections. The prompt names rapportd because rapportd is the Apple process on a Mac that most routinely holds such a socket.
What the dialog never tells you is who is expected to call. The honest answer from the protocol’s own behaviour is other Apple devices on the same network: the discovery traffic that finds your iPhone or iPad, and the connections that carry pairing and handoff between them. Sometimes the caller is named in another daemon’s paperwork: the launch file of replicatord, the widget sync daemon, waits for a rapportd advertisement of a chrono service before it even starts, so the iPhone widgets on a Mac desktop are, literally, something this daemon woke up. One floor up, audiomxd, the audio route arbitration daemon, spends its days weighing the same kind of nearby device list, deciding which Apple gadget the AirPods belong to right now. Apple’s Continuity documentation says that the features are built into the operating systems and that some require Wi-Fi and Bluetooth, and it describes what you get, relay calls, hand off tasks, unlock with Apple Watch, without ever naming the daemon doing the listening.
So the dialog is a real decision with plain outcomes. Allow, and the local device-to-device features can answer when another Apple device comes looking. Block, and the process keeps running exactly as before, but callers are refused, while the features that can route through Apple’s servers rather than your living room continue. Either way, nothing has been installed, and nothing is exfiltrating: the prompt is a firewall rule question, not a verdict about the software.
Why there are three of them in Activity Monitor
A Mac can show more rapportd rows than jobs in the launch folders, and the third and fourth copies have a mundane owner: Xcode.
Each installed iOS simulator runtime carries a complete mini macOS-style userspace, and that includes its own rapportd. On this Mac, two runtimes are installed, and both of their daemons were running:
.../iOS 27.0.simruntime/Contents/Resources/RuntimeRoot/usr/libexec/rapportd
.../iOS 27.2.simruntime/Contents/Resources/RuntimeRoot/usr/libexec/rapportd
One had been up 19 hours, the other 7 days, and neither had used more than ten seconds of processor time. They live inside the simulator runtime’s RuntimeRoot folder and only exist while Xcode’s simulator services are using them. If a crash report or a “quit unexpectedly” dialog ever names rapportd on a developer’s Mac, the odds are good the path in the report is one of these, because resetting a simulated device takes its daemons down with it. The thing to check in any rapportd oddity is the path column, not the name: /usr/libexec/rapportd is the system one, anything under a simruntime belongs to Xcode, and only the first of those is Apple system code running as part of your Mac.
The pairing protocol, read out of its own binary
Nobody outside Apple has published a Rapport specification, but the daemon’s binary contains its own working vocabulary, and it is more descriptive than the man page.
The pairing half is built on well-known parts. The binary contains a Swift distributed actor called RPPairingDistributedActor whose methods narrate the whole sequence: resolveBonjour, then startPairVerify, then exchangePAKEIdentities, then pairAndReceiveIdentity. In order, that is find the other device using Bonjour, verify it, run a PAKE exchange, which is the family of protocols where two parties prove a shared secret without ever sending it, and swap identities at the end. There is a version of the pairing listener that starts with a PIN and a version that starts without one, and log strings for setting a PIN on the local endpoint, which is the number-typing ritual of device pairing rendered as source code.
The identity half is people-shaped, and the files the daemon holds open agree. Alongside its own framework it had Contacts error tables, AddressBook strings, OpenDirectory strings, and a CorePhoneNumbers ruleset open, the last being the data that formats phone numbers the way each country expects them. The binary’s own strings talk about contact with email and phone, family identity request, friend identity response, and removing an identity, which is the Apple Account side of deciding who is allowed to pair with what.
The transport half is named in two words that appear again and again in those strings: BLE and IDS. BLE is Bluetooth Low Energy, the radio that lets two devices notice each other at arm’s length, and the strings describe ignoring BLE devices found with no identity, which is what happens when any old Bluetooth beacon wanders past. The radio itself belongs to a different daemon, bluetoothd, which does the actual scanning and advertising that Rapport’s proximity work depends on. IDS is Apple’s identity services relay, the server-side path that carries frames between devices that are not near each other, and the binary logs IDS sends, IDS headers and unsupported IDS frames as first-class events. Rapport, in one sentence assembled entirely from its own vocabulary: notice over Bluetooth, verify and pair with PAKE over Bonjour, then talk either peer to peer on your network or relayed through Apple’s servers.
What the numbers say about the scare stories
The search suggestions for this daemon include virus, remove and quit unexpectedly, so it is worth being blunt about the evidence.
The process is Apple’s. Its signature says so, its folder says so, and the three launchd jobs that own it are in the system folders that macOS keeps sealed. There is no version of rapportd that a webpage or a download installed.
The process is cheap. Twenty-five days of running cost 24 minutes and 45 seconds of one core, and 10.7 MB of memory, and both of those numbers include every Bluetooth advertisement it evaluated and every pairing it took part in. A battery problem that shows rapportd in Activity Monitor is almost never a rapportd problem. The radio work it coordinates would show up under the Bluetooth and Wi-Fi system processes anyway, because those are the processes that actually touch the radios.
And the process is quiet. Its log on this Mac produced no lines at all in the window sampled for this page, which is what a daemon that finished its work and went idle looks like from the log’s point of view.
If you actually want it to stop doing things
There is no switch labelled Rapport or rapportd in System Settings, because the setting you want is named after the feature, not the machinery. The Handoff toggle lives in the AirDrop & Handoff pane, and turning it off removes one of the reasons anything knocks on those twelve doors. Signing a device out of the Apple Account removes its identity from the pairing work entirely, and the identity strings above are what stop mattering when you do. Apple’s own Continuity page states the dependency in the other direction: some features require Wi-Fi and Bluetooth, so the transports can be turned off too.
Quitting the process itself, for the record, achieves a respawn. The job has no KeepAlive, but it also has twelve Mach service doors, and the next process that knocks gets a freshly launched daemon, which on this Mac had happened exactly once since boot. As for removal, the binary sits on the sealed system volume, so there is no supported way to delete it and no unsupported way worth the recovery partition.
What this page cannot tell you
The protocol’s over-the-air format is not documented anywhere Apple publishes, so every claim here about the network side comes from what the daemon does at the edges: the socket it holds, the Bonjour names it resolves, the BLE and IDS vocabulary in its own binary. What the frames contain once encrypted is not observable from the Mac and is not claimed.
The mapping between the twelve doors and Apple’s feature names is likewise read from the names themselves. Two of them name their features outright, AutoUnlock and CompanionLink, and the rest are identified by what they do rather than by a published table, because no published table exists.
And one number on this page is a snapshot: listening ports are assigned by the system, so 55038 is what it was on this Mac on this day, not a constant of the protocol.
Where window managers fit
rapportd is about the space between your devices, and nothing on this page changes the space on your screen. The two meet in the same complaint, though, the sense that the computer is full of machinery you never asked about. Some of that machinery is daemons quietly earning their 24 minutes a month, and some of it is a desktop where the windows you want are buried three layers deep.
Ribbon is for the second kind. Windows stay at full size on a single scrolling strip instead of stacking, so the window you want is one swipe away and nothing hides behind anything. It is $15, once, for up to 3 Macs, with a full refund within 10 days, and it runs on macOS 14 Sonoma and later on Apple silicon and Intel Macs. You can drive the strip in your browser before installing anything.
The short version
rapportd is the daemon that runs Rapport, Apple’s protocol for nearby devices to find each other, pair and hand work over. Handoff, relaying calls and texts from an iPhone, Apple Watch unlock and device pairing all sit on top of it, and the macOS User Guide page describing every one of those features never says its name. The feature half of the handshake lives one layer up in sharingd, whose own log records receiving Handoff payload requests via Rapport: sharingd spots the neighbour, rapportd carries the session.
It is measurable, and the measurements are dull in the good way. One process per login session plus an idle system copy under the same label, ten megabytes of memory, 25 minutes of processor time in 26 days, no crashes, and no log lines while idle. Extra rows in Activity Monitor come from iOS simulator runtimes, which ship their own copy.
The firewall dialog names it because it holds a listening TCP socket, which is precisely the condition the dialog exists to ask about. Allowing it lets the local device-to-device features answer; blocking it refuses callers and changes nothing else about the process.
There is nothing to remove and nothing worth quitting. The switches that exist are the ones named after features, in the AirDrop & Handoff pane, and the man page’s own version flag, for the record, starts a second daemon instead of printing a version, which is the most Apple documentation fact on this page.
Questions
What is rapportd on Mac?
It is the daemon that runs Rapport, Apple's protocol for letting nearby Apple devices discover each other and pair up. The system's own man page calls it the daemon that enables Phone Call Handoff and other communication features between Apple devices, and the macOS User Guide page that describes those features, called Use Continuity to work across Apple devices, never mentions rapportd once. It is the machinery under Handoff, relaying calls and texts from an iPhone, device pairing, and several of the features that need two Apple devices signed in to the same Apple Account. On this Mac it ran as PID 1037, launched by launchd as a per-user agent, holding 10.7 MB of memory and 24 minutes 45 seconds of processor time across 25 days and 23 hours of running, which is about 0.066 per cent of one core.
Why does rapportd want to accept incoming network connections?
Because it holds a real listening socket. Running lsof against the process shows one TCP port open for listening on both IPv4 and IPv6, on this Mac port 55038, waiting for other devices on your network to connect. When the macOS firewall is on, any process that opens a listening port triggers the accept incoming network connections prompt, and rapportd is the Apple process most likely to be named in it. Allowing it is what lets device-to-device features answer when another Apple device comes looking. Blocking it does not remove the process, it only refuses the callers, and the features that route through Apple's servers instead of your local network carry on either way.
Is rapportd a virus or malware?
No. The binary at /usr/libexec/rapportd is signed by Apple with the identifier com.apple.rapportd and platform identifier 26, it is a universal arm64e build, and it sits in a folder that system file protection keeps even root from writing to. No installer you ran put it there and no uninstaller can take it out. The name looks strange because it ends in d for daemon, the same convention as httpd and sshd, and Rapport itself is just the internal name of the protocol. If a process with this name is using noticeable CPU, check the path in Activity Monitor: copies running from a path containing iOS Simulator runtimes are the ones Xcode ships for its simulated iPhones, not anything that touched your system.
Can I stop or disable rapportd?
There is nothing to gain and no switch labelled rapportd anywhere in System Settings. The daemon is started on demand when another process knocks on one of its twelve doors, and launchd reports the reason it is awake as ipc, meaning something asked for it. Quitting it in Activity Monitor means launchd opens it again the next time a feature needs it. What you can actually turn off are the features: the AirDrop & Handoff pane in System Settings has the Handoff switch, signing one device out of the Apple Account removes its identity from the pairing work, and turning off Bluetooth and Wi-Fi, which Apple's own Continuity page says some features require, takes away the transport. The daemon then simply idles, which it is very good at.
Why are there two or three rapportd processes in Activity Monitor?
Because macOS ships two permanent copies and Xcode can add more. There is a per-user agent, the one that runs as your account and does the pairing work, and a system-wide daemon under the same launchd label that exists mainly for Apple Watch unlock and push service discovery, which on this Mac had never once been started. Those two are one process each. Beyond that, every installed iOS simulator runtime carries its own copy of rapportd inside its RuntimeRoot, so a Mac with two runtimes installed shows four rapportd rows: one real, one idle system one, and two simulator copies that belong to Xcode. The simulator copies are also the usual source of rapportd quit unexpectedly reports, because they get cleaned up when Xcode resets a simulated device.
Ready? Buy Ribbon for $15, or read all the guides.