What is replicatord on Mac?

Last updated: 2026-08-05

What it is

replicatord is an Apple-supplied daemon that runs for each signed-in user and is managed by launchd. Apple’s bundled manual describes it as the “remote widget sync daemon.” Its job is to synchronize remote widgets and selected remote-device data used by iPhone Mirroring.

The verified executable is located at /System/Library/PrivateFrameworks/ReplicatorCore.framework/Support/replicatord, and its identifier is com.apple.replicatord.

Apple’s local client descriptions give the clearest picture of what it handles: widget timelines, snapshots, icons and interactions; Live Activities; source records for notifications forwarded from an iPhone; and placeholder records for iPhone apps. Those are specific cross-device records, not evidence that replicatord transports every part of iPhone Mirroring. In particular, the available documentation and system configuration do not establish that it carries the live mirrored display, audio, video, or dragged files.

Why it talks to the network

Network activity can begin when you enable or add an iPhone widget on the Mac. Refreshing its timeline, transferring its current snapshot or icon, and processing widget interactions can all require synchronization. Other supported triggers include receiving an iPhone notification or Live Activity after iPhone Mirroring has been configured, as well as updating placeholder records that let Spotlight discover iPhone apps.

Not all of this communication has the same route. Apple says iPhone widgets require the phone to be nearby or connected to the same Wi-Fi network. Local system configuration also registers Rapport for nearby-device discovery and IDS messaging for widget and replicator communication. That strongly supports a nearby-device path for at least some work.

Notifications and Live Activities are different: Apple says they can continue appearing on the Mac while the iPhone is away, provided the phone remains turned on. Those updates can therefore require internet access through Apple’s device-messaging or push infrastructure.

Apple does not publish stable hostnames for replicatord. It also does not confirm that every remote connection involved in this workflow belongs directly to this daemon. Companion services such as identityservicesd or apsd may own parts of the transport. A hostname, remote address, or nearby-device session should not be assigned to replicatord without process-level evidence.

How much traffic is normal

There is no verified per-process baseline for replicatord, and Apple publishes no dependable MB figure. Its traffic can remain close to idle control activity for long periods, then appear in intermittent bursts when widget archives, timelines or icons change, when notifications or Live Activities arrive, or when iPhone-app placeholder state is updated.

The total depends on which integrations are enabled and how active their apps are. That makes a fixed daily or monthly estimate unreliable. Large screen, media, or file transfers observed during an iPhone Mirroring session should not automatically be counted as replicatord traffic; attributing those payloads requires measurement of the process itself.

Can you turn it off

You can turn off the features that use replicatord, but Apple provides no single System Settings switch for the daemon itself.

For iPhone widgets, use:

Apple menu  > System Settings > Desktop & Dock > Widgets > iPhone Widgets

For forwarded notifications and Live Activities, where those controls are available, use:

Apple menu  > System Settings > Notifications > Allow notifications from iPhone

Turn off Allow notifications from iPhone and Allow Live Activities from iPhone as needed. To stop Spotlight from discovering iPhone apps, where that option is available, use:

Apple menu  > System Settings > Spotlight > iPhone Apps

Disabling these controls means the corresponding iPhone widgets, notifications, Live Activities, or app-discovery records will stop appearing or updating on the Mac.

To revoke iPhone Mirroring more broadly, open iPhone Mirroring > Settings and choose Revoke Access to [iPhone]. Using iPhone Mirroring again will require setup.

These are feature-level controls. Killing replicatord, permanently unloading its LaunchAgent, deleting the binary, or blocking it with a firewall is unsupported. Doing so can interrupt any clients that remain enabled and may cause failed synchronization or repeated retries.

What people get wrong

• “replicatord uploads Mac data for Apple Intelligence.” Apple’s manual assigns it to remote widgets and iPhone Mirroring device data. The available evidence does not identify it as an Apple Intelligence process or say that it uploads summaries of Mac data.

• “replicatord is malware or a cryptocurrency miner.” The genuine Apple binary at the verified System Library path is a normal macOS component. That conclusion does not automatically apply to a same-named executable found somewhere else; an unexpected copy should be investigated separately.

• “Replication means it is backing up or cloning the Mac or iPhone.” Here, replication refers to specific cross-device records. replicatord is not documented as a general backup daemon, Time Machine component, iCloud Drive engine, or full-device cloning service.

• “It must carry the live mirrored screen and audio.” That has not been verified. The documented datasets cover widgets, notifications, Live Activities, and app placeholders, but they do not prove ownership of screen, audio, video, or drag-and-drop file streams.

• “Same Wi-Fi means every connection is local.” Nearby widget and Mirroring activity may use local communication, but notifications and Live Activities can still reach the Mac while the iPhone is away. The opposite assumption is also unsafe: local traffic should not be labeled cellular or relayed without route evidence.

• “Quitting iPhone Mirroring stops all synchronization.” Apple says forwarded notifications and Live Activities can continue after setup while the iPhone is turned on. Closing the visible app therefore does not prove that every related background update has stopped.

• “Deleting or permanently unloading it is a harmless optimization.” launchd can restart managed components, while remaining widget, notification, Live Activity, or placeholder clients may fail or retry. Feature settings are the supported way to stop the corresponding behavior.

Seeing what it actually used

The next step is to measure replicatord over a representative period and compare its timestamps with widget refreshes, iPhone notifications, and Live Activities. Bytetally’s per-process statistics can isolate its observed traffic instead of assigning all iPhone Mirroring activity to it. Keep the measured byte count separate from any unverified guess about which payload produced it.

Related processes

Common questions