What is parsec-fbf on Mac?

Last updated: 2026-07-31

What it is

parsec-fbf is an Apple-shipped background component inside the private CoreParsec framework. It runs per user from /System/Library/PrivateFrameworks/CoreParsec.framework/parsec-fbf and has the Apple code-signing identifier com.apple.parsec-fbf.

The bundled implementation includes pipelines related to search sessions, ranking, suggestions, and engagement feedback. Those functions are associated with Apple search surfaces such as Siri and Spotlight. In practical terms, parsec-fbf participates in collecting and flushing feedback about how Apple’s search features are used and how their results perform.

Apple does not publicly document parsec-fbf by name. Its identity, location, scheduling behavior, and several implementation details can be verified locally, but its complete payload schema cannot. It would therefore be too strong to claim that every field it sends, or every Apple feature that may feed data into it, is known.

Why it talks to the network

The launch agent for parsec-fbf defines a feedback flush task. That task becomes eligible approximately once an hour, but only after a randomized delay and when both networking and external power are available. Eligibility does not guarantee that a transfer occurs: the process may have no feedback waiting to be sent.

A separate cleanup task becomes eligible daily. An internal notification can also request an immediate upload, so not every connection needs to line up with the approximate hourly schedule.

The binary connects to Apple search and feedback infrastructure. It contains an Apple-owned smoot.apple.com endpoint and can obtain additional upload destinations from configuration supplied by a server. The full destination list has not been verified, so seeing another Apple-provided destination would not by itself contradict the known implementation. Conversely, the embedded endpoint is not evidence that every run uploads to it.

How much traffic is normal

There is no verified normal byte range for parsec-fbf. Apple does not publish an expected daily or monthly total, and the available evidence does not support assigning it a specific number of kilobytes or megabytes.

Expected behavior can range from no transfer while the Mac is idle or the relevant data sharing is turned off to intermittent, compressed feedback batches following search activity. This is scheduled batch traffic, not a continuous media stream. A short burst followed by a long quiet period is therefore more consistent with the known design than a permanently active stream, but no individual byte total can be declared normal from the available evidence.

The upload and download values found in the launchd configuration are scheduler estimates. They are not measurements of actual traffic and should not be presented as usage limits, typical batch sizes, or promises about what a particular Mac will transfer.

Can you turn it off

Yes, if “turn it off” means opting out through Apple’s supported data-sharing controls. It does not mean unloading, deleting, or force-blocking the system executable.

For Apple Search feedback, go to:

System Settings > Spotlight > Help Apple Improve Search

Turn that setting off. Apple states that this prevents it from storing your search queries for the purpose of improving Search. It does not disable Spotlight or local search. Limited information may still be sent when needed to provide current online suggestions, so the setting should not be understood as an all-offline mode.

Searches originating from Siri have a separate control:

System Settings > Privacy & Security > Analytics & Improvements > Improve Siri & Dictation

Turn that off as well if you do not want to share Siri and Dictation recordings and transcripts for improvement. Disabling only this Siri setting does not cover non-Siri search queries; Help Apple Improve Search remains a separate choice.

These settings govern data sharing, not whether parsec-fbf is allowed to launch. The process may still appear for cleanup or other internal work after you opt out. Its presence in a process list is therefore not proof that search feedback was uploaded.

What people get wrong

• “It belongs to the Parsec remote-desktop app.” It does not. This executable is supplied by Apple under /System/Library and identifies as com.apple.parsec-fbf. The matching word in the name does not make it part of the third-party Parsec application.

• “It only uploads Siri analytics.” That description is too narrow. The local implementation covers broader Apple Search feedback, and Apple’s corresponding setting refers to queries from Safari, Siri, Spotlight, Look Up, and #images.

• “It is Spotlight’s filesystem indexer.” It is not. Killing or disabling parsec-fbf is not a supported way to stop Spotlight indexing, and the process’s feedback role should not be confused with filesystem indexing.

• “An hourly interval means it uploads continuously or exactly on the hour.” The task only becomes eligible approximately hourly. Its initial timing is randomized, and the feedback flush depends on networking and external power. It may become eligible without having anything to transfer.

• “Turning off Improve Siri & Dictation covers every search query.” It does not. Non-Siri queries are covered by the separate Help Apple Improve Search control.

• “Turning off Help Apple Improve Search makes every Apple-assisted search offline.” Apple says limited information may still be sent to provide up-to-date online suggestions. The setting stops storage of queries for improving Search; it is not a universal network cutoff.

• “Unloading or force-blocking the launch agent is the same as opting out.” It is not. Force-disabling the agent is unsupported and not recommended. macOS may relaunch it, and a system update may restore its configuration. Apple’s privacy settings are the supported controls for the relevant data sharing.

Seeing what it actually used

Because no reliable normal byte range exists, the useful next step is to check your own Mac rather than compare it with an invented benchmark. Use Bytetally’s per-process statistics to find parsec-fbf, observe its actual upload and download totals, and compare periods of search activity with idle periods.

Related processes

Common questions