What is storedownloadd on Mac?

Last updated: 2026-08-08

What it is

storedownloadd is a built-in, on-demand, per-user macOS background process. Its executable is inside Apple’s private CommerceKit framework at /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/storedownloadd. It handles application and update package downloads for the Mac App Store.

launchd starts storedownloadd when it is needed. It is not a permanently running third-party download manager, and seeing it appear during an App Store task is consistent with its role. The normal executable is an Apple platform binary stored in a system-protected directory.

The name com.apple.storedownloadd is used as its code-signing identifier and launchd service label. Because the executable has no attached Info.plist, this is not an ordinary application CFBundleIdentifier in the usual sense.

Apple does not publish a current man page for storedownloadd or a complete public description of everything it does. It is therefore accurate to say that it handles Mac App Store application and update downloads, but not that every byte of App Store traffic must pass through it. That broader claim has not been fully verified.

Why it talks to the network

A network session commonly starts after you get an application from the App Store, redownload one you previously obtained, or install an application update. Automatic application updates can create the same kind of Store download task without a new manual action.

Two other App Store settings can generate automatic download work: downloading applications purchased on other devices and downloading in-app content automatically. Apple has not publicly confirmed that storedownloadd carries every task created by those settings, so their relationship to this process should not be stated as absolute.

The remote services generally belong to Apple’s store-content systems and content delivery infrastructure. Examples associated with that infrastructure include *.apps.apple.com, *.itunes.apple.com, and *.mzstatic.com. Delivery may also involve a third-party CDN or an Apple content cache on the local network. Apple has not published a verified one-to-one mapping between these domains and storedownloadd, so a connection to any particular hostname should be evaluated from the observed traffic rather than assumed from the process name.

How much traffic is normal

There is no published fixed “normal traffic range” for storedownloadd. When idle, it usually does not produce sustained high-volume traffic. Checks and requests for download information are more likely to involve small amounts of control traffic.

Once an actual installation or update begins, the transfer is on the same general scale as the selected application or update package. A small application produces a comparatively small download. A large application such as Xcode can make storedownloadd the dominant network user at that time.

Context matters more than a made-up MB threshold. A large total during an active App Store download fits the process’s purpose. Persistent transfers with no expected task are a reason to check the App Store for a pending update, redownload, or repeated attempt, but Apple provides no universal number at which the traffic becomes abnormal.

Can you turn it off

Apple provides no supported switch for turning off storedownloadd itself. There is therefore no System Settings path that disables this process.

Blocking or disabling it can cause App Store application downloads, redownloads, and updates to fail, stall, or retry. Force-quitting it normally interrupts only the current instance. If a download request still exists or a later request arrives, launchd can start the process again.

You can reduce some automatic triggers in App Store > Settings. The available controls include Automatic Updates, Automatically Download Apps Purchased on Other Devices, and Automatically Download In-App Content. Turning these options off does not disable storedownloadd, and it does not prevent a download that you start manually.

If bandwidth control is the goal, limiting the process is more appropriate than completely blocking it. Even then, Apple has not documented how storedownloadd behaves under bandwidth limits. An overly strict limit may cause a task to stall or make repeated attempts, so it is not safe to promise that throttling will merely make every download take longer.

What people get wrong

• “storedownloadd is a virus or an adware downloader.” The normal instance is an Apple platform binary inside the protected CommerceKit framework. The name alone is not enough to identify an unfamiliar executable, however. If a process named storedownloadd comes from another path, verify that path and its code signature separately.

• “Deleting it or permanently unloading its LaunchAgent is a safe macOS optimization.” Apple does not provide this as a maintenance method. Removing or disabling the service breaks Mac App Store download functions, and the executable resides under the system-protected /System directory.

• “storedownloadd handles every Apple update, including current macOS system updates.” The available evidence does not establish that. Apple documents macOS software updates separately from App Store application updates, so all system-update traffic cannot be attributed to storedownloadd on that basis.

• “A large amount of traffic from storedownloadd proves something is wrong.” Downloading a large application or update is enough to explain heavy traffic. Check the App Store for an active download, update, redownload, or retry before treating the volume itself as evidence of a problem.

• “Ending the process permanently stops automatic downloads.” Ending it affects the current running instance, not the service’s future availability. launchd can start storedownloadd again when another Store download request needs it.

Seeing what it actually used

First check the App Store for a current download, update, or repeated attempt. Then use Bytetally’s per-process statistics to examine how much traffic storedownloadd transferred during the same period. Comparing the timing and total with the Store task is more useful than judging the process from a single unexplained spike.

Related processes

Common questions