# replayd, the film crew nobody booked

> replayd is the daemon behind ReplayKit recording and broadcast on a Mac. Measured: a camera-ready recording folder that has stayed empty since setup day.

Source: https://www.ribbonmac.com/guides/replayd-mac · Updated 2026-11-19

Open Activity Monitor on a quiet Mac and page down to the r's, and there it is between the printing daemons and the routing daemons: replayd, a few megabytes of memory, no CPU to speak of, running as you. It sounds like it should be doing something. Replay. The name suggests footage being kept of your screen, which is exactly the kind of thing a person wants to know about.

So here is what it actually is, measured on a Mac that has never once used it for a recording. The short answer covers more than the name suggests: it is the daemon behind apps that record themselves, and, as a live test below shows, it is in the path of every screenshot the system takes. The shortcut side of that flow, the part that catches the keystroke and shows the apology when a save fails, belongs to SystemUIServer, [measured on its own page](https://www.ribbonmac.com/guides/systemuiserver-mac).

## The receipts

The process on the measured Mac, macOS 27.0.1 on a MacBook Pro:

- Path: /usr/libexec/replayd
- Parent: launchd, pid 1, which is how every system daemon arrives
- User: your account, not root
- Binary: 4,583,120 bytes, triple architecture (x86_64, arm64e, arm64e.x1), built 24 September, signed by Apple on 9 August, Platform identifier 26, meaning it is Apple platform code
- Memory: about 3.9 MB resident
- Processor time: 3.64 seconds over a day and a quarter of continuous running

Those are the standard receipts this series checks for every daemon, and replayd passes all of them: Apple's signature, Apple's volume, launchd's child, and a cost so small the column rounds to zero.

## One honest manual

Most of these daemons have manual pages that say nothing, or one sentence, or in one memorable case literally "searchparty daemon is a daemon." replayd gets a real one. The whole of it:

> NAME
> replayd - MacOS daemon to support ReplayKit on macOS
>
> DESCRIPTION
> replayd implements in-app capture, recording, and broadcast features of ReplayKit
>
> HISTORY
> replayd first appeared in macOS 10.15

Dated 24 January 2019, back when 10.15 was still Catalina and the manual was presumably being written next to the code. There is a second line in the synopsis worth keeping, because it is Apple telling you the same thing this article will: takes no arguments, and users should not launch it manually.

One detail in the dates is better than trivia. The manual says the daemon first appeared in macOS 10.15, and Apple's developer documentation for the ReplayKit framework lists its macOS availability as 11.0 and later. The crew arrived a full year before the stage they were hired for. The daemon has simply been standing by since Catalina, waiting for apps that link the framework.

## What ReplayKit records

ReplayKit is Apple's framework for an app to record or stream itself. Apple's own one-line description of it: "Record or stream video from the screen, and audio from the app and microphone." Not the whole screen, and this is the distinction that matters: ReplayKit is in-app capture. A game that offers to save the clip of your last thirty seconds, a whiteboard app with a record button, an iPad app on an Apple silicon Mac that streams to a sharing service, those are ReplayKit customers. When you press the record button inside the app, the app hands the work to this daemon, and the daemon does the capturing, the file writing and the broadcasting.

The third-party screen recorders people actually use to capture the whole desktop, OBS and its relatives, do not go through replayd; they use the screen capture frameworks directly and ask the permissions daemon for access. That is why so many Mac owners have never seen replayd do anything. It is not the daemon behind screen recording in general. It is the daemon behind apps that record themselves.

## The camera crew in 7,691 strings

The binary carries 7,691 strings, and reading them is like finding the crew's call sheet. There is a class for high quality local recording sessions, with start and write failure paths. There are the broadcast strings, the connection to a broadcast extension being interrupted and invalidated, and a timeout waiting for a broadcast action to finish. There is the permission failure, flat and final: User denied screen capture.

And there is the camera rig. Strings for camera textures and screen textures, for compositing the two together, for scaling the camera image, for a full HD plus presenter overlay mode. That is the feature where your face sits in a corner of the recording, and the strings show the maths of stitching the two streams: compositeTime equals cameraTime plus addTime. A camera pass is even written into the daemon's sandbox profile, one line reading allow device-camera, sitting between the graphics access and the metadata reads. The film crew brings its own camera.

The strangest strings are the quietest ones. The daemon polls a screenshot count, and not loosely: its code carries a whole state machine for it, with states named ScreenshotCounterStartingAState through ScanningState, StreamingState and StoppedState, and a screenshot counter timer. It adds and removes screenshot timestamps. It updates what it calls the Control Center screen attribution with a bundle ID, which is the machinery behind the indicator that tells you which app is currently using your screen or camera. Even a daemon whose job is recording keeps a ledger of who else is recording.

## The screenshot test

Strings can be dead code, so this series tests them. The daemon had written zero log lines in half an hour of watching, so one screenshot was taken with the built-in screencapture tool, the same utility the keyboard shortcuts run, and the log was read again.

The daemon woke instantly. In the same tenth of a second, it accepted a client connection from the screencapture process, consumed a sandbox extension token from it, created a client for it, added it to the recording manager, and fetched the display. Then the line that settles what the screenshot strings are for, from replayd itself:

> +[SCScreenShotSession captureWindowServerScreenshot:isScreenshotConfiguration:withCompletionHandler:] screenshotProperties=...
> session=... Created screenshot status=0

replayd's own SCScreenShotSession class captured the WindowServer frame. Two hundredths of a second later, the screencapture process logged the other half of the handshake: Notifying biome of screenshot saved to..., source: EmbeddedScreen, style: EntireScreen. That is why the daemon's sandbox profile reads from the system's Biome store, and why a daemon named for replays is on duty at the login screen. Your screenshots are not kept by it; the file lands wherever screenshots go, on your Desktop by default. But the machinery that grabs the frame is here, and the class name says so twice over, captureWindowServerScreenshot, pointing straight at the compositor covered in [what WindowServer is on a Mac](https://www.ribbonmac.com/guides/what-is-windowserver-on-mac).

Which means the honest scope of this daemon is wider than its manual. ReplayKit on the label, screen recording and broadcast in the description, and the plain screenshot under the hood.

## Five doorbells and a login screen

The launch file, /System/Library/LaunchAgents/com.apple.replayd.plist, registers five mach services, which is five doorbells other processes can ring: the daemon's own name, a cache deletion service, a sharing session service for broadcasts, its notification twin marked experimental and non-launching, and a user notifications delegate so ReplayKit can put real notifications in front of you. On the measured Mac the launch configuration reported 52 runs in 28 days, roughly two a day, with the last exit reason being an idle memory exit, which is the system reclaiming a process that was doing nothing, on purpose. The immediate launch reason each time was ipc, a mach knock: an app or a system service asked for it, launchd delivered it, it served, it slept.

The one genuinely odd line in the launch file is LimitLoadToSessionType, which lists both Aqua and LoginWindow. The recording daemon is on duty at the login screen, before anyone has logged in. There is no recording happening there; it is simply cheaper for Apple to load one daemon everywhere than to special-case the lock screen, the same reasoning that puts the phone call daemon on Macs with no phone.

## Three seconds a day

Every daemon in this series gets asked the same question: what does it cost? For replayd the answer is close to nothing. Those 3.64 seconds of processor time over a day and a quarter work out to about three seconds a day, which is the same band as the phone call daemon's two and comfortably under the App Store agent's five. The log told the same story from the other side: in half an hour of watching, replayd wrote zero lines. Like the permissions daemon, it speaks only when spoken to.

There were no crash reports for it, in a folder this series checks every time. Fifty-two launches in twenty-eight days and not one of them went wrong.

## A folder that has stayed empty

The daemon has a folder for its work, /Library/Application Support/com.apple.replayd inside your home, and the sandbox profile on file spells out what it is allowed to touch: write to that folder, write to a cache folder, read from the system's Biome store, open the camera, deny everything else by default, and refuse to generate code on the fly.

On the measured Mac, that folder was created on 19 September at 20:46, which was the evening this Mac was first set up, and it is still zero bytes. Twenty-eight days of the recording daemon being on call, and it has never had a single thing to save. That is the most honest measurement in this article: whatever replayd is doing on a Mac where nobody records, it is not recording.

There is one wart worth naming, because this series names them. The sandbox profile exists, 5,423 bytes of deny-by-default rules, but the launch file also carries an entitlement that switches the sandbox off entirely. The profile is on file; the practice is unsandboxed. Apple does this for a handful of media daemons that need broad graphics and camera access, and it is the kind of thing you notice only by reading both files, which is why this article did.

## Is it filming you

No, and the architecture is the reason. A capture starts because an app asked, not because the daemon felt like it. The permission question is asked by a different daemon entirely, the permissions daemon that owns the screen recording toggle in Privacy and Security, and if you deny it, replayd's own code path logs the refusal and stops. When a capture does run, the Control Center attribution machinery names the app to you, in the direction that matters: the system telling the human, not the daemon hiding from them.

For the complete picture of that permission question, read the entry on [tccd, the permissions daemon](https://www.ribbonmac.com/guides/tccd-mac). For where the frames it records come from in the first place, the compositor that puts every window on the display is covered in [what WindowServer is on a Mac](https://www.ribbonmac.com/guides/what-is-windowserver-on-mac).

## The short version

replayd is the ReplayKit daemon: a 4.6 MB Apple-signed binary at /usr/libexec, running as you since macOS 10.15, that captures, records and broadcasts what apps ask it to, with a camera pass in its pocket for face overlays, a ledger of who else is using your screen, and, measured live, the SCScreenShotSession machinery that grabs the frame for the system's own screenshots. It costs about three seconds of processor time a day, relaunches itself invisibly twice a day, wrote zero log lines in half an hour on the measured Mac until one screenshot woke it, and has a work folder that has been empty since the evening the machine was born. It cannot usefully be quit, disabled or edited, and no search pattern of real people complaining about it survives contact with those numbers. It is not a virus, it is not filming you, and on a Mac where no app records itself, it is a camera crew that has been on the payroll for twenty-eight days with nothing on tape but your screenshots, which were yours all along.

## FAQ

### What is replayd on my Mac?

It is the daemon that backs ReplayKit, Apple's framework for recording and broadcasting what an app is doing. The manual page says it in one line: replayd implements in-app capture, recording, and broadcast features of ReplayKit. When a game offers to record your last goal, or an iPad app running on your Mac starts a screen broadcast, this is the process underneath, sitting at /usr/libexec/replayd, launched by launchd, running as your user account rather than root. It also has a second job the manual does not mention: a live test in the article shows that a screenshot taken with the system's screencapture tool is grabbed by a class inside replayd itself. It is signed by Apple inside the sealed system volume, it first appeared in macOS 10.15, and it is not malware. There is nothing to remove and nothing you need to do about it.

### Why is replayd running if I never record my screen?

Because it loads at login on every Mac, the same way the phone call daemon loads on Macs with no phone. The launch file carries no conditions about apps or hardware; it simply starts in every Aqua session, and even at the login screen. When nothing is recording, the daemon does essentially nothing: on the measured Mac it accumulated under four seconds of processor time in a day and a quarter of running, and the system reclaims idle copies on purpose, which is why launchd showed 52 launches in 28 days with the last exit reason being an idle memory exit, not a crash. It runs so that a ReplayKit app, whenever one appears, has something to talk to.

### What apps actually use replayd?

Anything that links the ReplayKit framework: games with built-in clip recording or live broadcast buttons, apps that ship a broadcast upload extension for streaming to a sharing service, and the quieter class, iPhone and iPad apps running on Apple silicon, which inherit ReplayKit because it has shipped on iOS since version 9. Before any capture starts, the app needs the screen recording permission in Privacy and Security, which is a different daemon's database, and replayd's own strings include the failure line for the case where you said no: User denied screen capture. The common thread is that the app records itself. Third-party screen recorders that grab the whole screen generally use different machinery and never wake this one.

### Why is replayd using CPU?

On the measured Mac it was not, in any meaningful sense: 3.64 seconds of processor time over a day and a quarter of continuous running, roughly three seconds a day, which puts it in the cheapest band of every daemon measured in this series, level with the phone call daemon and under the App Store agent. Its log produced zero lines in half an hour of watching, because it speaks only when something is actually being captured: a recording, a broadcast, or, as the article's live test shows, a single screenshot, which wakes it for a tenth of a second. There is no sustained high CPU complaint pattern around this process in search, and that absence fits the measurements: a daemon this cheap does not generate complaint threads. If the column ever jumps, a capture is genuinely underway, and the app doing it is the thing to close, not the daemon.

### Can I quit or disable replayd?

There is nothing to win. The manual's own synopsis line reads: takes no arguments, and users should not launch it manually. Quitting it buys a second of quiet before launchd starts it again; the launch configuration gives it a five second exit timeout and the system's pressured exit policy means the memory is reclaimed anyway when it is idle. The binary sits on the sealed system volume, which cannot be edited without breaking the seal the Mac verifies at boot, and there is no switch in System Settings because there is nothing to switch: with no ReplayKit app asking for a session, the daemon's whole job is to not be in the way.

### Is replayd recording me, or is it spyware?

No. It records only when an app asks it to, and only after the permission system said yes, and macOS shows which app is capturing: one of the daemon's own log strings is Updating Control Center screen attribution with bundleID, the machinery behind the indicator that names the app using your screen or camera. Its sandbox profile is on file for anyone to read, denies everything by default, and grants exactly three home folders plus a camera device for the in-recording camera overlay feature, while its recordings land in a folder inside your own Library. On the measured Mac that folder has been zero bytes since the evening the machine was set up. A daemon that had been secretly filming you for weeks would at least have filled its own folder.
