What is parsecd on Mac?

Last updated: 2026-07-31

What it is

parsecd is an Apple-supplied macOS daemon that supports Siri Search features. It is launched on demand by launchd, so seeing it appear does not mean that you installed a new application or that it must run continuously.

Apple’s local parsecd manual page identifies several features that use it: Siri Suggestions, Spotlight Suggestions, Safari Suggestions, Lookup, the #images feature in Messages, and searches for Apple News articles. That list is broader than “Spotlight web search.” A request can reach parsecd through several parts of macOS even when the user is not looking at the main Spotlight window.

parsecd is also distinct from the processes that build the local Spotlight file index. Local file indexing is primarily handled by mds, mds_stores, and the mdworker family. High activity from parsecd should therefore be investigated as search, suggestion, content, download, cache, or retry activity—not automatically diagnosed as local file indexing.

The process belongs to Apple, with the code-signing identifier com.apple.parsecd, and its executable is located inside the system’s private CoreParsec framework. The name may be expanded informally as “Parsec daemon” or “CoreParsec daemon,” but the process name shown by macOS is parsecd.

Why it talks to the network

Network activity can begin when you open or use Spotlight, request Siri or Spotlight Suggestions, type into Safari’s address bar with Safari Suggestions enabled, use Lookup, search for an image through Messages #images, or search Apple News articles. These are request-driven features, so traffic may appear briefly around a search and then stop.

The destinations are mainly Apple search and suggestion services, together with Apple or partner content services needed for the requested result. Background URLSession work may also resume a configuration or resource transfer after the original interaction. Apple has not published a complete list of domains used by parsecd, so a fixed or exhaustive hostname list would not be reliable.

Safari’s address bar needs particular care when attributing traffic. Safari Suggestions, search-engine suggestions, and background preloading of a Top Hit are separate features. Search-engine suggestions are sent to the search engine selected by the user; they should not all be assigned to parsecd merely because the requests happened after typing in Safari.

How much traffic is normal

Apple has not published a normal byte range for parsecd, and there is no reliable official basis for calling a particular number of kilobytes or megabytes “normal.” Claims such as “tiny per query” may sound plausible, but they are not supported by an Apple measurement or a published threshold.

The feature design suggests that much of its activity consists of short-lived requests and responses triggered by searches or suggestions. Such exchanges would ordinarily be expected to remain well below media streaming or software-update traffic. That is a qualitative comparison, not a guaranteed allowance or a measured per-query limit.

Additional bursts can come from background resource retrieval, resumed downloads, cache refreshes, or retries after network failures. A brief spike therefore does not establish a problem by itself. Conversely, sustained high traffic should not be accepted as normal solely because parsecd is an Apple search process. With no published baseline, the useful questions are whether queries are repeating, a resource is being downloaded, cached material is refreshing, or failed connections are being retried.

Can you turn it off

Apple does not provide a System Settings switch that turns off the whole parsecd daemon. Its manual page exposes no configuration options and says that users should not run or manage the process manually.

You can reduce some of the activity by disabling individual features. The relevant partial controls include System Settings → Spotlight → Show Related Content and Safari → Settings → Search → Include Safari Suggestions. Neither setting is a master switch: parsecd also supports Lookup, Messages #images, Apple News searches, and other listed suggestion functions.

Force-quitting it, trying to unload it with launchctl, or deleting system files may work only temporarily because launchd starts the daemon when macOS needs it. Those methods are not supported by Apple. They can disrupt online search or suggestion behavior in Siri, Spotlight, Safari, Lookup, Messages #images, or Apple News. If the goal is to reduce network access, changing the individual feature settings is more precise than attempting to remove the shared daemon.

What people get wrong

• “It came from the Parsec remote desktop app.” It did not. parsecd is included with macOS by Apple and is unrelated to whether the similarly named third-party application is installed.

• “It is the Spotlight file indexer.” It is not. The local Spotlight index is primarily maintained by mds, mds_stores, and mdworker processes. parsecd supports online search, suggestions, and related content features.

• “Turning off Spotlight indexing will stop it.” That is not reliable. Spotlight Suggestions are only one part of its role; Safari Suggestions, Lookup, Messages #images, and Apple News article search can also use it.

• “It is the process that puts every dictionary lookup online.” That description is too broad. Apple’s manual page names Lookup, not every dictionary operation. A local dictionary query may need no network connection, and the available evidence does not show that all dictionary activity runs through parsecd.

• “Every request after typing in Safari belongs to parsecd.” Safari Suggestions, suggestions from the user’s selected search engine, and background Top Hit preloading are different functions. They should be attributed separately instead of being grouped under one process without evidence.

• “Killing it, unloading it, or deleting it is a useful optimization.” Apple provides no configuration interface for parsecd and says users should not run or manage it manually. Since it is launched on demand, forced termination may be temporary while also breaking features that depend on it.

• “Large continuous transfers are normal because it is a system search process.” Apple has published no traffic benchmark that supports that conclusion. Persistent traffic warrants checking for repeated queries, downloads, cache refreshes, or retries caused by network failures.

Seeing what it actually used

When the published baseline is absent, the next step is to measure parsecd over the same period in which you noticed the activity. Bytetally’s per-process statistics can separate its upload and download totals from Safari, Spotlight indexers, and unrelated processes. Compare short search-triggered bursts with sustained background transfers before deciding whether the behavior needs further investigation.

Related processes

Common questions