What is screensharingd, and why is it running on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job, bundle ID and man page checked on macOS 26.3.1.
screensharingd is the macOS server that lets other computers view and control your screen. It runs only when Screen Sharing or Remote Management is turned on in System Settings, and uses CPU and network while someone is connected. If you did not turn either on, turn them off and check who has access.
screensharingd at a glance
| screensharingd | |
|---|---|
| Made by | Apple (part of macOS, Screen Sharing) |
| Type | System daemon (only with Screen Sharing or Remote Management on) |
| Location | /System/Library/CoreServices/RemoteManagement/screensharingd.bundle/Contents/MacOS/screensharingd |
| Runs as | root |
| Started by | launchd job com.apple.screensharing |
| Bundle ID | com.apple.screensharing.daemon |
| Can you quit it? | Quitting it disconnects anyone viewing the screen. To stop it for good, turn off Screen Sharing and Remote Management. |
What is screensharingd?
The man page says screensharingd listens for VNC connections from clients and should not be run directly; you enable Screen Sharing or Remote Management to use it. Its launch daemon is disabled by default and listens on the VNC port, which Apple's ports list gives as TCP 5900, advertised over Bonjour.
Apple's guide says Screen Sharing is compatible with VNC, that it is turned on in System Settings > General > Sharing, and that it cannot be on at the same time as Remote Management. The macOS 26 settings describe it as allowing users of other computers to remotely view and control this computer.
Is screensharingd safe?
screensharingd itself is Apple's, inside /System/Library/CoreServices/RemoteManagement on the read-only system volume. Whether its running is safe depends on who can connect, which you control in the Screen Sharing settings.
Why does screensharingd use so much CPU and network?
- Someone viewing the screen. While a viewer is connected, screensharingd captures and compresses the screen continuously. Large or high-resolution displays and fast-changing content such as video cost more.
- Sending screen updates. Every change on screen is sent to the viewer, so network use rises with how much is moving.
- Several viewers. More than one connected computer multiplies the work.
- Connection attempts. Each incoming connection, including failed ones, starts the service. On a network open to the internet that can mean repeated attempts by strangers.
How much CPU is normal for screensharingd?
With Screen Sharing and Remote Management off, screensharingd does not run. With them on and nobody connected, it is idle.
While someone is connected, noticeable CPU and network use is expected.
How do you stop screensharingd?
- Turn off Screen Sharing. Open System Settings > General > Sharing and turn off Screen Sharing.
- Turn off Remote Management. In the same list, turn off Remote Management if it is on. It also uses screensharingd.
- Limit who can connect. If you need it, click the Info button next to Screen Sharing and set Allow access for to only specific users.
- Reduce the cost while connected. Ask the viewer to use a smaller window or lower quality, and avoid playing video during the session.
When should you worry about screensharingd?
Look closer if screensharingd is running and you did not turn on Screen Sharing or Remote Management, or a connection is active that you did not expect. Turn both off and change your password. A Mac managed by an organization may have Remote Management turned on by its administrator.
How do you check screensharingd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type screensharingd 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 screensharingd 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 'screensharingd' | grep -v grep
nettop -p screensharingd
How can Thrum help with screensharingd?
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 screensharingd 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 screensharingd
Why is screensharingd running?
Screen Sharing or Remote Management is turned on in System Settings > General > Sharing.
Does screensharingd run when I share my screen in a video call?
No. Screen sharing in apps such as FaceTime or meeting apps uses those apps. screensharingd is the server for remote viewing and control of this Mac.
Which port does it use?
TCP 5900, the port Apple lists for Screen Sharing and Apple Remote Desktop.
Sources
- screensharingd(8) man page: run man screensharingd in Terminal
- Apple Support: Turn Mac screen sharing on or off
- Apple Support: TCP and UDP ports used by Apple software products