What is nsurlsessiond on a Mac, and why is it using the network?
In short: nsurlsessiond is part of macOS. Apps hand it their downloads and uploads so the transfer can carry on after the app closes or goes to sleep. When it uses a lot of network, it is doing some app's work, not its own. Blocking it stops those background transfers for every app; finding out which app the traffic belongs to is the better fix.
Apple's own description is one line: nsurlsessiond is "the background NSURLSession daemon" that "performs tasks for background-configured NSURLSessions" (man nsurlsessiond). In plain words, it is a helper that runs in the background (a daemon) and does network transfers on behalf of apps.
Why apps hand it their downloads
An app that needs to download something large, or something that isn't urgent, can ask macOS to do it in the background. Apple's developer documentation explains that in this case the transfer "is performed by a process that is separate from your app's process", so it keeps going even when the app is suspended, and the system can wait for good conditions, such as being plugged in or on Wi-Fi (Apple Developer).
That separate process is nsurlsessiond. It runs once for each user logged in to the Mac.
So when Activity Monitor's Network tab shows nsurlsessiond at the top, an app has asked for a background transfer: for example, an update being fetched, media being downloaded, or a large file going up to a cloud service. The bytes belong to that app; nsurlsessiond only carries them.
Is it safe?
The genuine nsurlsessiond is Apple's and lives at /usr/libexec/nsurlsessiond. That folder is protected by System Integrity Protection, which stops other software, even with an administrator password, from changing files there (Apple). To see where the running copy lives, type this in Terminal:
ps -ax -o comm | grep nsurlsessiond
It should print /usr/libexec/nsurlsessiond.
Should you block it?
Blocking nsurlsessiond doesn't block one app. It stops background transfers for every app that uses it, and you won't always know which ones until something stops updating or syncing. It is better to find the app behind the traffic:
- Look at where it connects. A tool that records connections by name shows the servers nsurlsessiond talks to, and the names usually give the app away: the domain of an app's maker, of a cloud service, of a podcast host.
- Pause the obvious suspects. Cloud storage apps, media apps with offline downloads and app updaters are likely candidates. Quit them one at a time and watch whether the traffic stops.
- Wait. A large one-off download, such as a new version of an app, looks dramatic for a while and then ends.
How Ranger shows it
Ranger lists nsurlsessiond in Traffic like any other program, with every domain it reached and when. That's usually enough to tell whose download it was. Unlike a few core services that Ranger never blocks, nsurlsessiond can be switched off in Ranger, for an hour, a day or for good, if you decide you want background transfers to stop. You can also block just the one domain that bothers you.
Our guide to seeing which apps use the internet covers the free ways to look, starting with Activity Monitor.