What is storeuid on Mac?

Last updated: 2026-07-31

What it is

storeuid is an on-demand user-interface agent built into macOS. Its executable is part of Apple’s private CommerceKit framework, and the verified system component uses the identifier com.apple.storeuid.

Its job is to present interfaces needed by App Store and StoreKit workflows. Those interfaces include in-app purchase confirmation, Apple account authentication, payment dialogs, purchase restoration, and prompts that ask users to rate or review an app. It can therefore appear even when the App Store itself is not the application currently in front of you: another app can request a StoreKit operation that needs system-provided interface elements.

storeuid is not the main service responsible for downloading applications or installing updates. Its role centers on user interaction and transaction coordination. That distinction matters when interpreting process-level traffic, because a large App Store download should not automatically be assigned to storeuid merely because its name contains “store.”

Why it talks to the network

storeuid is activated when a StoreKit operation needs an interface. Common triggers include an app requesting an in-app rating prompt, starting or restoring an in-app purchase, or asking StoreKit to show account authentication, purchase confirmation, payment, or redemption-related screens.

The agent cooperates locally with appstored and other App Store services through XPC. The associated remote activity belongs to Apple App Store, Apple Media Services, and commerce transaction services. That activity can support account handling, storefront information, transactions, and policy metadata used for rating prompts.

There is an important attribution limit here. Apple has not publicly documented whether each individual connection is opened directly by storeuid or sent on its behalf by another store daemon, and that behavior may change between macOS releases. A connection observed near a StoreKit prompt therefore does not, by itself, prove which member of the store-service group created the remote socket. The broad purpose of the communication is known, but connection-by-connection ownership remains unverified.

How much traffic is normal

Normal activity ranges from no active connection while storeuid is idle to brief, small transfers of control information or metadata when a StoreKit action occurs. It is generally much smaller than application downloads, application updates, or media transfers.

Apple has not published a dependable byte range for storeuid. There is therefore no verified MB figure that can serve as a universal threshold. The amount can also depend on which StoreKit interface was requested and which supporting store service actually handled the remote connection. A short burst around a purchase, authentication, restoration, or review workflow is consistent with its role; a precise expected total is unverified.

If substantial traffic appears under this name, treat the measurement as something to investigate rather than assuming it represents an App Store download. Process attribution, timing, and the StoreKit action occurring at that moment provide more useful context than an invented fixed limit.

Can you turn it off

Apple does not provide a System Settings or App Store setting that disables the entire storeuid service.

Blocking it through unsupported methods may cause purchase confirmations, account authentication, payment screens, purchase restoration, and in-app review prompts to fail or arrive late. Simply ending the process does not create a lasting disable switch: because it is an on-demand service, launchd can start it again when another XPC request needs it.

The App Store setting for in-app ratings and reviews is narrower. Turning that option off controls requests for rating and review prompts; it does not disable the StoreKit interfaces used for purchases, account authentication, or payments. The description of normal traffic as minor should likewise not be read as evidence that the service can be disabled safely. It means its usual network use is small, not that its functions are disposable.

What people get wrong

1. “storeuid is malware or a third-party advertising process.” The verified macOS instance is an Apple-provided component located under /System/Library and identified as com.apple.storeuid. That system component is part of CommerceKit. The path and identity are important when evaluating a process that happens to use the same or a similar name.

2. “storeuid downloads App Store applications and updates.” That overstates its role. The inspected system component is centered on StoreKit and CommerceKit interfaces plus transaction coordination. Its presence does not justify attributing a large application download or update to it.

3. “storeuid only displays rating pop-ups.” Rating and review prompts are only one part of its work. It also contains interfaces related to purchase confirmation, account authentication, payment sheets, purchase restoration, and other StoreKit user-interface protocols.

4. “Killing or disabling storeuid will noticeably save bandwidth or make the Mac faster.” There is no basis for that claim. The service is activated on demand, and its normal communication is usually absent or sporadic. Ending it is not a persistent disable mechanism, while interfering with it may disrupt StoreKit workflows.

5. “Disabling In-App Ratings & Reviews disables storeuid.” That setting only controls whether apps can request rating and review prompts. It does not switch off the purchase, authentication, payment, restoration, or other StoreKit interfaces handled by storeuid.

Seeing what it actually used

If storeuid appears in a network monitor, the next step is to measure the process rather than infer traffic from its name. Bytetally’s per-process statistics can show what storeuid used during the relevant period, which you can compare with the time of a purchase, authentication, restoration, or review request. Keep the connection-attribution limitation in mind when interpreting activity shared across App Store services.

Related processes

Common questions