SiftMac
What is this process? · Updated 22 November 2026

What is nsurlsessiond, and why is it using my network?

By Mohit Nippanikar, who makes SiftMac

The short answer
On this page
  1. What nsurlsessiond is
  2. Why it’s busy
  3. What to do about it
  4. Should you quit or disable it?
  5. Questions

1. What nsurlsessiond is

The program is /usr/libexec/nsurlsessiond. Its manual page describes it as a per-user daemon that performs tasks for background-configured NSURLSessions; in practice you’ll often see two copies, one running as you and one as the system user _nsurlsessiond, started from launch files in /System/Library/LaunchAgents and /System/Library/LaunchDaemons.

An NSURLSession is how Mac and iPhone apps make network requests. When an app marks a session as a background session, Apple’s developer documentation says its transfers keep running even while the app is suspended, the download is performed in another process, and the app is woken when it completes. That other process is nsurlsessiond.

So it isn’t downloading anything for itself. Its traffic is the sum of every background transfer that apps and macOS have asked for.

2. Why it’s busy

Its CPU use is usually small; what stands out is network and disk. Apple’s documentation gives apps a discretionary option for transfers that aren’t urgent, so the system can wait for better conditions, such as being plugged in or on Wi-Fi. That’s why bursts often arrive when you connect a charger or join a fast network. Typical causes:

The folder names under its Downloads folder show who: on the Mac this page was written on they included com.apple.bird (iCloud Drive), com.apple.cloudd (CloudKit) and com.google.Chrome.

3. What to do about it

  1. Measure it. In Activity Monitor, click Network and sort by Rcvd Bytes or Sent Bytes.
  2. See which apps have downloads waiting, and how big each is, with the commands below.
  3. Watch its connections live with nettop -p nsurlsessiond (press q to quit). The server names often give away which service it is.
  4. Deal with the app, not the daemon. Pause the sync, cancel the download in the app, or quit it. If it’s iCloud on a new Mac, letting it finish is usually the answer.
ls ~/Library/Caches/com.apple.nsurlsessiond/Downloads
du -sh ~/Library/Caches/com.apple.nsurlsessiond/Downloads/* 2>/dev/null | sort -h

That folder usually holds little, since a finished download is handed to the app. Apple tells developers the file arrives in a temporary location and must be moved somewhere permanent to keep it. If one app’s folder there is large, it has a transfer in progress or one that never completed; updating, signing out of or uninstalling that app is the cleaner fix than deleting files out from under nsurlsessiond.

If your disk is filling while nsurlsessiond is busy, look at what the app is downloading: iCloud files go to iCloud Drive, podcasts to their own downloads folder, and so on.

4. Should you quit or disable it?

Quitting it in Activity Monitor interrupts every app’s background transfer at once. launchd starts it again on demand, and apps then retry, so the traffic usually comes back. It’s part of macOS’s sealed system volume, its manual page says it has no configuration options, and there’s no supported way to switch it off. Don’t turn off System Integrity Protection to try; it isn’t worth it.

To cut its traffic, quit or reconfigure the apps that use it, or, if iCloud Drive is the one getting in your way, turn off Sync this Mac in System Settings › your name › iCloud › Drive until you can let it finish.

Questions

Is nsurlsessiond a virus?

No. It’s Apple’s, at /usr/libexec/nsurlsessiond, and every Mac runs it. Any network use it shows was asked for by an app or a macOS service.

Why does nsurlsessiond use so much data?

Because it does other apps’ downloading. Find which app with its Downloads folder or nettop, then deal with that app.

Can I delete ~/Library/Caches/com.apple.nsurlsessiond?

It normally holds only unfinished downloads. Deleting them can break or restart those downloads. If one app’s folder stays large, fix or remove that app instead.

Why does it start when I plug in my Mac?

Apps can mark transfers as non-urgent so the system waits for better conditions, such as being plugged in or on Wi-Fi. Those transfers start once the conditions are met.

How SiftMac handles it. SiftMac leaves ~/Library/Caches/com.apple.nsurlsessiond alone, as it does every com.apple. cache: its App caches category skips them. Its space map still shows how big the folder is.

Download SiftMac · scanning is free, and so is your first 2 GB of cleaning · See how it works