What is amsaccountsd on Mac?

Last updated: 2026-07-31

What it is

amsaccountsd is a built-in macOS background service from Apple Media Services. It runs on a per-user basis and exposes XPC services used by clients associated with Media & Purchases, including the App Store, Music, and TV.

Its work centers on media account state rather than downloading the media itself. Verified responsibilities include handling account information for those clients, completing work associated with signing in or out, maintaining cached server account data, processing push-driven updates, and supporting some purchase-related metadata. The verified launch agent uses the identifier com.apple.amsaccountsd, while the executable is located at /System/Library/PrivateFrameworks/AppleMediaServices.framework/Versions/A/Resources/amsaccountsd.

The name can make amsaccountsd sound broader than the available evidence supports. It is not a general-purpose audio, video, or App download process. There is also no verified basis for claiming that it synchronizes every Apple Account setting across devices or routinely checks every paid subscription attached to an Apple Account. Its confirmed scope is narrower: Apple Media Services account and control-layer work for media and purchase clients.

Apple does not publish a dedicated amsaccountsd manual page or process-specific support document. The description here therefore relies on its local launch configuration, code-signing identifier, linked frameworks, diagnostic strings, and Apple’s broader documentation for media accounts and network services.

Why it talks to the network

amsaccountsd needs network access because the account state it manages is not purely local. A connection may be triggered when a media account signs in or out, when the Apple Account or store account changes, when cached account data expires, or when a scheduled synchronization is due. Related push notifications can also wake this work, and App Store, Music, TV, or another client may ask it to perform an account or purchase-related operation.

Evidence in the local binary shows use of Apple Media Services, Apple Push Service, and CloudKit. Its connections can therefore involve categories such as Apple account authentication, Apple media-store services, APNs, and CloudKit. These categories describe the services involved; they are not a complete host-by-host map.

Apple has not published a definitive mapping from every amsaccountsd request to a particular hostname. Endpoints can also vary by region and macOS release. A connection to an unfamiliar Apple endpoint is therefore not enough by itself to determine which account operation caused it, and assigning a fixed list of domains to all amsaccountsd activity would be more precise than the evidence allows.

How much traffic is normal

Apple has not published a normal traffic range for amsaccountsd, so there is no reliable number of kilobytes or megabytes that can be used as a universal threshold. Claims that it always makes frequent small requests, or that its total commonly becomes large, are not supported by the verified material.

Its confirmed duties suggest a more limited expectation: traffic should generally consist of occasional or periodic authentication exchanges, account metadata, and push-control requests. Short bursts may occur around sign-in, sign-out, account changes, or purchase-related activity. This is an inference from what the service does, not an Apple-published traffic specification.

Under ordinary conditions, that control-layer activity should be substantially smaller than an App installation package or an audio or video stream. Even so, there is no dependable numeric boundary for declaring a particular total normal or abnormal. The useful comparison is the timing and pattern on the specific Mac: whether activity lines up with an account change, a store action, a push update, or another known trigger.

Can you turn it off

The practical verdict is to keep amsaccountsd available. Apple provides no separate System Settings path, switch, or supported control for disabling this daemon.

Force-quitting the process is not a permanent change. amsaccountsd is a RunAtLoad launchd user agent that provides system Mach and XPC services, so launchd can start it again when those services are needed. Deleting or modifying the system component is not an Apple-supported performance optimization.

Blocking or forcibly disabling amsaccountsd may prevent media account state from refreshing. Sign-in or sign-out work may remain incomplete, store and purchase-related state may become inconsistent, and push-driven updates may be delayed. The exact symptoms can differ between macOS releases.

Signing out through Store > Sign Out in the App Store or Account > Sign Out in Music removes the corresponding media account session, but it does not disable amsaccountsd. Signing out of the entire Apple Account in System Settings has a much wider effect than this daemon and should not be treated as its off switch.

What people get wrong

• “amsaccountsd is a virus or cryptocurrency miner.” An instance at the verified system path with the identifier com.apple.amsaccountsd is part of macOS. A file with the same name at another path does not gain that trust automatically and needs to be checked separately.

• “Quitting or deleting it will permanently speed up my Mac.” amsaccountsd is a RunAtLoad launchd user agent and supplies Mach/XPC services to other system clients. It can restart on demand, and altering a system component is not a supported optimization.

• “It uploads or synchronizes all of my files.” There is no evidence for that claim. Its verified behavior concerns media account data, push handling, CloudKit records, and purchase-related services; that is not the same function as iCloud Drive file synchronization.

• “The word ‘subscription’ in the binary proves it checks all Apple paid subscriptions.” It does not. Visible diagnostics specifically include subscriptions to CloudKit database notifications. Whether amsaccountsd queries paid-subscription status, and when it might do so, remains unverified.

• “All of its traffic must be music or video content.” Its verified role is primarily at the account and control layer. Actual App or media content is usually transferred by other components, although process attribution can change between system versions.

• “It is only telemetry, so it is safe to throttle or block.” There is no evidence that amsaccountsd is merely telemetry. It supports media-account and purchase-related system services, and Apple provides no dedicated throttling control for it.

Seeing what it actually used

To assess amsaccountsd on your own Mac, use Bytetally’s per-process statistics to check its upload and download totals and when the activity occurred. Compare those timestamps with media account sign-ins, store actions, account changes, and other known triggers. This gives you evidence from the specific Mac without assuming an unsupported universal traffic threshold.

Related processes

Common questions