# replicatord, the daemon that brings a nearby iPhone to your desktop

> replicatord syncs iPhone widgets and iPhone Mirroring data to your Mac. Measured: a radio link to a nearby phone, a sealed database, nineteen seconds a day.

Source: https://www.ribbonmac.com/guides/replicatord-mac · Updated 2026-11-18

Every so often a Mac asks its owner a genuinely strange question. Do you want replicatord to accept incoming network connections? The name explains nothing. It is not an app anyone installed, it has no icon, and the firewall dialog it appears in offers no hint of what breaks if you say no. Some people say no, the prompt comes back a day later, and eventually they end up reading a page like this one.

The name decodes better than most. Replicator is the project name in the framework's own version file, ReplicatorCore, and replication is exactly the job: copying data that lives on an iPhone into the Mac, over the air, so the Mac can show things that belong to the phone. Add the d for daemon. Apple never uses the word in any settings pane, because settings panes are named after features, and this daemon sits under two of them, both quoted from its own manual page: remote widgets, and remote device data for iPhone Mirroring.

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, with an iPhone in the room.

## The receipts

| What | Measured |
|---|---|
| Path | /System/Library/PrivateFrameworks/ReplicatorCore.framework/Support/replicatord |
| Size | 267,808 bytes, three architectures in one file: x86_64, arm64e and arm64e.x1 |
| Version | Project Replicator, version 1.0, build 985 |
| User | The logged in user, not root |
| Parent | launchd, process 1, always |
| Running | Current run a day and a half, 26 runs on the clock |
| Processor time | 28.9 seconds across that day and a half, about nineteen seconds a day |
| Memory | 5 MB resident, sampled twice, minutes apart |
| Manual page | replicatord(8), present, dated September 23, 2024 |
| Log volume | 10,588 lines in seven days |

Two rows deserve a pause before the rest. A manual page, which in this series of daemon measurements is rare enough to note every time, and it is four lines long and complete. And 26 runs in a day and a half, which is the opposite of the cable daemon's one launch in 28 days. This is a process built to come and go.

## The manual page, in full

Most of these daemons ship with no documentation at all, so when Apple writes one, it is worth reading to the end. Here is the entire description of replicatord(8), and it is the best one line job description in the series:

> replicatord is a daemon that provides data syncing for remote widgets and remote device data for iPhone Mirroring. There are no options for replicatord, and users should not run replicatord manually.

Dated September 23, 2024, which is the macOS Sequoia era, the release that introduced iPhone Mirroring. That is the whole management story as well. No options, no manual running, nothing to administer. What the manual page does not say is what the two features are, so here they are in Apple's own words from the Mac User Guide.

The first feature is iPhone widgets on the Mac desktop. The User Guide's page Add and customise widgets has a section headed Use iPhone widgets on your Mac, with three requirements: the iPhone uses iOS 17 or later, both devices are signed in to the same Apple Account, and the iPhone is near the Mac or on the same Wi-Fi network. The switch lives in System Settings, under Desktop and Dock, in the Widgets section, and it is labelled Use iPhone widgets. When you click one of those widgets and see Open [app name] on your iPhone to continue, that is the replication boundary showing through: the app is not on the Mac, so the Mac hands the touch back to the phone.

The second is iPhone Mirroring. The User Guide's page Control your iPhone from your Mac explains that it lets you control your iPhone from your nearby Mac, that when it is on you can also receive iPhone notifications on your Mac and keep track of Live Activities, and that the devices must be within 10 metres, 30 feet, of each other, with Wi-Fi and Bluetooth on and the same Apple Account on both. The page also carries two honest caveats: it is not available in every country, and if you use a VPN its configuration must not prevent local networking, or some Continuity features stop working. That caveat matters here, because this daemon's whole life is local networking.

## How it wakes: invited, never scheduled

The launch file is at /System/Library/LaunchAgents/com.apple.replicatord.plist, and it reads like the opposite of the always on daemons. RunAtLoad is false: it does not start at boot. KeepAlive lists one condition, Crashed, meaning launchd promises to restart it only if it dies badly. There is no timer, no interval, no schedule of any kind.

Instead there are two events, and they explain the daemon's whole rhythm. The first is a notification, keybag first unlock, the moment the system's cryptographic store opens after you log in. The second is the interesting one: a LaunchEvent watched through rapportd, Apple's Continuity discovery daemon, for a service advertisement of type com.apple.ApplicationService.chrono arriving from a nearby device. In plain language, the Mac's radio hears an iPhone announcing widget services in the room, and launchd starts replicatord in response. launchd's own report names its monitors directly: rapportd and notifyd. [The rapportd page](https://www.ribbonmac.com/guides/rapportd-mac) in this series covers the discovery side of that handshake, the part that never mentions this daemon by name. And the word chrono in that service name is not a coincidence: it is the Chrono project, whose Mac half is [chronod](https://www.ribbonmac.com/guides/chronod-mac), the timeline daemon that decides when each of those replicated widgets refreshes. The courier delivers; the clock decides when to open the parcel.

The rest of the configuration is the system keeping a small daemon on a short leash. EnablePressuredExit is on, so the system may ask it to volunteer to die when memory is wanted elsewhere, and the jetsam memory limit is 24 MB against the 5 MB it actually uses. Minimum runtime three seconds, exit timeout five, throttle interval three. POSIXSpawnType Adaptive, the class for work that arrives unprompted. One environment variable is set that tells it not to build any database in process, which is a promise about where its books live, and they live somewhere specific.

## The measured conversation

What makes this daemon different from everything else measured in this series is that you can watch it work. The unified log for seven days held 10,588 lines, and the most recent ones, written while this page was being researched, describe a live conversation. The log names the application service, com.apple.ApplicationService.chrono. It names the other end, by owner and model, an iPhone17,1. It names the transport, UDP, multipath, and the interface, awdl0, which is the private radio interface AirDrop and Continuity use, the one that exists purely so nearby Apple devices can talk without touching your Wi-Fi.

The process's own open file table agrees. replicatord held a UDP socket on port 55029, bound to every interface, with two live flows to another device over link local IPv6 addresses, the fe80 addresses that only mean something inside one room. That socket is the answer to the firewall question from the top of this page. The application firewall's job is to notice processes that accept packets from other machines, and this one does, on purpose, because that is what replication between two devices physically is. The binary is on the sealed system volume and signed as an Apple platform binary. Allow is safe. Deny simply starves the two features.

And the books. The daemon keeps a SQLite database, three files, at ~/Library/Group Containers/group.com.apple.replicatord/replicatord/, the main file 6,471,680 bytes on this Mac. Try to read it and the system stops you cold: an ls of the directory and a sqlite3 open of the file both come back with authorization denied, the privacy wall rather than Unix permissions, lifting only for tools granted Full Disk Access. The size above was measured through the daemon's own open file table, which is the honest way to report a folder your own terminal cannot enter. A daemon that keeps a copy of phone data, in a container an administrator cannot read, is a design decision worth knowing about rather than a problem.

## The vanishing act

People report replicatord appearing and disappearing from Activity Monitor, and the configuration explains that too. launchd's report for the daemon ended with the phrase that ends most of its runs: last exit reason, JETSAM_REASON_MEMORY_IDLE_EXIT. The system reclaimed it while it was idle, on purpose, because EnablePressuredExit is set and the daemon had nothing to do. Then the next event, a phone unlocking nearby, a widget refresh, a Mirroring handshake, starts it again, and the run counter ticks up. Twenty six runs in a day and a half is not instability. It is the intended life cycle of a process whose only reason to exist is another device's presence.

One more thing worth knowing before you go looking. The log's error lines include, on an entirely healthy Mac, entries like No response handler found and connections reported as already cancelled, ignoring cancel. A page of error text that costs nothing is normal for this daemon. The signal that something is actually wrong is the CPU column, not the log.

## Three processes and a simulator

If you see more than one replicatord, count your simulators. Every iOS simulator runtime ships its own copy, inside the runtime image, and a booted simulator starts it the way a real iPhone would. On this Mac two extra copies were alive at the moment of measurement, one from an iOS 27.0 runtime and one from 27.1, each up for two days. It is the same pattern [the assistantd page](https://www.ribbonmac.com/guides/assistantd-mac) documents, and it is also the reason the search results for this name lean iPhone and iOS: developers meet the process on both sides of the fence.

## What it costs

This site keeps a running ledger of what macOS daemons cost, and replicatord lands in the cheap band: about nineteen seconds of processor time a day, on 5 MB of memory, cheaper than the notification daemon's 36 seconds, dearer than the cable daemon's one. Unlike most entries in [that ledger](https://www.ribbonmac.com/guides/why-is-my-mac-running-slow), its workload has an off switch that actually works, because the workload is a feature you can see. Turn off Use iPhone widgets in System Settings under Desktop and Dock, close iPhone Mirroring, and the phone in your pocket stops being invited to talk.

So that is replicatord: a courier the size of a wallet photo, born the day Apple decided a Mac desktop should show an iPhone's widgets, woken by the radio hearing a phone in the room, keeping its copies in a folder you cannot read, and asking the firewall's permission to do its one job.

## FAQ

### What is replicatord on my Mac?

It is the remote widget sync daemon, in the words of its own manual page, the process that provides data syncing for remote widgets and remote device data for iPhone Mirroring. Two features depend on it. iPhone widgets on the Mac desktop, the ones that arrive from apps installed on your phone, need their data replicated across the air, and iPhone Mirroring, the feature that puts your locked iPhone on the Mac screen, needs device data carried the same way. It runs as your own user, launched by launchd, out of a private framework called ReplicatorCore, and it does not run at boot: its configuration says start only when a nearby iPhone announces itself or the keychain unlocks, which is why it comes and goes from Activity Monitor rather than sitting there since day one.

### Why does the firewall ask if replicatord can accept incoming connections?

Because it opens a real network socket. On the measured Mac it held a UDP socket on port 55029 bound to every interface, with live flows to another nearby device over link local IPv6 addresses, the fe80 addresses that only exist inside one room. The traffic rides awdl0, the same private radio interface AirDrop uses, and the log names the other end by model. The application firewall sees a process accepting packets from other machines and puts its standard question on screen. The binary is on the sealed system volume and signed as an Apple platform binary, so Allow is safe. If you never use iPhone widgets or iPhone Mirroring, Deny costs you those two features and nothing else.

### Why is replicatord using CPU?

On the measured Mac it used 28.9 seconds of processor time across a day and a half of running, about nineteen seconds a day on 5 MB of memory, with 26 launches on the clock, because it exits when idle and returns when invited. It cannot burn CPU thinking about an iPhone, only talking to one, so a busy replicatord means a conversation: a phone nearby refreshing widgets, or a Mirroring session handing data over. The toggle that removes the demand is in System Settings under Desktop and Dock, Widgets, Use iPhone widgets. Turn it off and the phone has no one to replicate to. Its log also shows that a healthy day includes error chatter, including lines reading No response handler found, which look worse than they are.

### What is the replicatord database in my Library?

It is a SQLite database at ~/Library/Group Containers/group.com.apple.replicatord/replicatord/replicatord.sql, 6,471,680 bytes on the measured Mac, with the usual write ahead log and shared memory files beside it, which is the replicated store the daemon keeps its copies of phone data in. You cannot read it, and neither could an administrator's terminal: the folder sits behind the privacy wall, and both an ls of the directory and a sqlite3 open of the file come back with authorization denied unless the tool has been granted Full Disk Access. The size was measured the honest way, through the process's own open file table.

### Why do I see more than one replicatord in Activity Monitor?

Almost always because Xcode simulators are running. Every iOS simulator runtime ships its own copy of the daemon inside its runtime, and a booted simulator launches it the way a real iPhone would. On the measured Mac two extra replicatord processes were alive at once, one from an iOS 27.0 runtime and one from 27.1, each two days old, alongside the Mac's own. This is the same pattern the Siri and dictation daemon shows, and it is why searching the bare name leans iPhone and iOS: developers meet this process on the phone side of the fence.

### Can I quit or disable replicatord?

There is nothing to quit and no options to pass it. The manual page states it in one line: there are no options for replicatord, and users should not run replicatord manually. It is configured to restart only if it crashes, and it is woken by events rather than kept alive, so killing it in Activity Monitor buys seconds of quiet before the next event brings it back. The levers that exist are the features: System Settings, Desktop and Dock, Widgets, Use iPhone widgets, and the iPhone Mirroring app itself. Switch the features off and the daemon simply stops being invited, which is the closest thing to disabling it that Apple provides.
