What is nsurlsessiond, and why is it using so much network?
Last reviewed: 19 November 2026. Path, accounts, launchd jobs and man page checked on macOS 26.3.1.
nsurlsessiond is the macOS daemon that performs background downloads and uploads on behalf of apps and system services, so transfers can continue when the app that asked for them is not running. Its network use is really the traffic of those apps. It is part of macOS and safe.
nsurlsessiond at a glance
| nsurlsessiond | |
|---|---|
| Made by | Apple (part of macOS, Foundation) |
| Type | Daemon (one copy per user, plus a system copy) |
| Location | /usr/libexec/nsurlsessiond |
| Runs as | your user |
| Started by | launchd job com.apple.nsurlsessiond |
| Can you quit it? | Yes, but launchd starts it again, and background downloads in progress may restart or resume later. |
What is nsurlsessiond?
The man page describes nsurlsessiond as the daemon that performs tasks for background-configured NSURLSessions. Apple's developer documentation explains that with background sessions the actual transfer is performed by a process separate from the app, that the transfer continues even when the app is suspended, and that for time-insensitive transfers the system can wait for good conditions, such as being plugged in or on Wi-Fi.
On macOS 26 there are two copies: one runs as your user from the com.apple.nsurlsessiond launch agent, and one runs as the _nsurlsessiond system account from the com.apple.nsurlsessiond_privileged launch daemon for system services.
Is nsurlsessiond safe?
Yes. nsurlsessiond lives in /usr/libexec on the read-only system volume and is started by Apple launch jobs.
Why does nsurlsessiond use so much network and CPU?
- Large background downloads. Apps and system services that download big files in the background hand the transfer to nsurlsessiond, so the bytes are counted under it in Activity Monitor.
- Background uploads. Uploads such as cloud backups or media sync can also run as background sessions.
- Deferred transfers starting together. Discretionary transfers wait for good conditions. Plugging in the charger or joining Wi-Fi can release several at once.
- Many small transfers. Lots of small requests, or transfers that fail and retry, cost CPU even when the total data is small.
How much network is normal for nsurlsessiond?
Typical use is near 0 when no background transfers are pending. Heavy network use for minutes or hours is normal while a large download or upload runs.
Constant traffic for days without any finished download or upload you can identify is not typical.
How do you stop nsurlsessiond from using so much network?
- See its connections. Run
nettop -p nsurlsessiondin Terminal. The remote host names often reveal which service the transfer belongs to. Press q to quit. - Pause transfers one app at a time. Pause downloads, uploads or syncing in the apps you use, one at a time, and watch whether nsurlsessiond's traffic in Activity Monitor stops.
- Let it finish on power and Wi-Fi. If the transfer is wanted, leave the Mac on power and Wi-Fi; the system is designed to run such transfers then.
- Quit it once if it is stuck. If traffic is constant and nothing completes, select nsurlsessiond in Activity Monitor and quit it. launchd starts a fresh copy and pending transfers resume or restart.
When should you worry about nsurlsessiond?
Look closer if nsurlsessiond moves a lot of data every day and nothing you use is downloading or uploading; nettop shows the hosts. A copy outside /usr/libexec would not be Apple's.
How do you check nsurlsessiond in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type nsurlsessiond in the search field. The Network tab shows its Sent Bytes and Rcvd Bytes. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every nsurlsessiond 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 'nsurlsessiond' | grep -v grep
nettop -p nsurlsessiond
How can Thrum help with nsurlsessiond?
Thrum's Network tab shows upload and download speed for each process, including nsurlsessiond, and an optional second menu bar item shows the Mac's total upload and download speed. Click nsurlsessiond in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
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 nsurlsessiond
Why does nsurlsessiond use data when I am not downloading anything?
Apps and system services can start background transfers on their own, and the system may run deferred transfers when you plug in or join Wi-Fi.
Why are there two nsurlsessiond processes?
One runs for your user account and one runs as the _nsurlsessiond system account for system services.
Does quitting it cancel downloads?
Transfers in progress are interrupted. Apps that use background sessions are designed to resume or restart them.
Sources
- nsurlsessiond(8) man page: run man nsurlsessiond in Terminal
- Apple Developer: Downloading files in the background