What is storekitagent on Mac?

Last updated: 2026-07-31

What it is

storekitagent is an Apple system process. Its local macOS man page identifies it as the StoreKit support agent, and the executable at the verified system location has the code identifier com.apple.storekitagent. The verified path is /System/Library/Frameworks/StoreKit.framework/Support/storekitagent.

The agent runs within each signed-in user’s session. It is not designed to remain active simply because the Mac is running: macOS starts it on demand when software uses StoreKit or when relevant App Store account state changes. Its launch configuration also permits pressured idle exit, so seeing the process appear and later disappear is consistent with how it is configured.

StoreKit is the Apple framework used for App Store commerce features such as presenting products, making or restoring purchases, reading transactions, and checking current entitlements. However, that framework-level description does not establish that every StoreKit task happens inside storekitagent. Apple has not publicly documented the exact division of work between this agent and other App Store services, including appstored.

Why it talks to the network

StoreKit may need to contact Apple’s App Store commerce services when an app asks for localized product information or prices, begins a purchase, restores previous purchases, examines transaction history, checks current entitlements or subscription status, or receives an update for a purchase or renewal completed elsewhere.

Depending on the operation, the exchanged information can include storefront and product metadata, purchase authorization and results, signed transactions or receipts, and entitlement or subscription updates. These are commerce and account-state operations; they are not evidence that storekitagent is uploading arbitrary personal files.

Apple documents that StoreKit connects to the App Store on an app’s behalf. What Apple does not document is whether storekitagent itself owns every network connection corresponding to those requests. Some work may be divided among StoreKit and other App Store services, so attributing every StoreKit-related connection to this one process would go beyond the available evidence.

The local launch configuration exposes a StoreKit APS endpoint. APS refers to Apple Push Service, but a direct network connection from storekitagent to that service has not been verified. The endpoint alone is not enough to claim that this process directly maintains an Apple Push Service connection.

How much traffic is normal

Apple publishes no normal per-process byte range for storekitagent. There is therefore no reliable MB figure, daily allowance, domain list, or upper bound that can be presented as normal for this process.

Its on-demand and idle-exitable configuration suggests that traffic can range from none while StoreKit is unused to short bursts of metadata or transaction activity when an app performs a relevant operation. The amount may also depend on which StoreKit action is taking place. Product lookup, purchase authorization, restoration, and entitlement refreshes do not necessarily exchange the same data.

This kind of control-plane traffic would ordinarily be expected to remain far below application downloads, media streaming, or system updates. That is only a general expectation, however; Apple has not documented this comparison specifically for storekitagent. If the process appears to account for substantial sustained traffic, measurement at the process and connection level is more useful than relying on an unsupported numerical threshold.

Can you turn it off

The practical verdict is to keep storekitagent available. Apple provides no supported System Settings switch for disabling the agent, so there is no settings path to follow.

Force-unloading it or blocking its communications may prevent apps from loading StoreKit products and localized prices, completing or restoring purchases, or refreshing transactions, entitlements, and subscription state. Because macOS launches the process on demand, launchd may also start it again after it has been terminated.

Stopping the local process does not cancel subscriptions associated with the App Store account. Subscription billing and account state are maintained by the App Store; killing a helper on one Mac is not a cancellation request. Apple Account settings for media and purchases can change matters such as password or Touch ID requirements, but they do not provide a switch for storekitagent.

What people get wrong

• “It appeared unexpectedly, so it must be malware or adware.” The executable at the verified system path is an Apple platform binary with the code identifier com.apple.storekitagent. The name alone is not enough to authenticate a file, though: a similarly named executable found outside protected Apple system locations should be assessed separately.

• “It continuously uploads my personal files.” No Apple documentation supports that claim. Its launch definition is on-demand and allows pressured idle exit. Apple has not published a process-specific privacy or protocol specification, so it would also be inaccurate to invent a complete list of everything the process exchanges.

• “Disabling it is a harmless battery or bandwidth optimization.” There is no supported process switch, and blocking it can interfere with legitimate StoreKit operations. Apple documents no performance benefit from disabling it.

• “It is used only when a subscription renews.” StoreKit also covers product and price lookup, purchases, restoration, transaction history, current entitlements, and other App Store interactions. The precise subset implemented inside storekitagent remains partly unverified, so not every such operation should automatically be attributed to it.

• “It handles all App Store app downloads and updates.” The storekitagent man page establishes StoreKit support, while macOS has a separate appstoreagent for App Store support. Large downloads should not be assigned to storekitagent without connection-level evidence.

• “Killing it will cancel an existing subscription.” It will not. Terminating a local helper does not change subscription billing or cancel the subscription held by the App Store account.

Seeing what it actually used

If the concern is a real traffic spike, the next step is to measure storekitagent rather than compare it with an undocumented threshold. Bytetally can show per-process traffic over the period in question, helping distinguish a short StoreKit burst from sustained transfer. Treat that measurement as evidence of byte usage, not proof of the exact StoreKit operation or remote service involved.

Related processes

Common questions