Thrum

What is tccd, and why is it using CPU on my Mac?

Last reviewed: 19 November 2026. Path, accounts and launchd jobs checked on macOS 26.3.1.

tccd is the macOS privacy daemon: it checks and records whether apps may access protected data and devices, such as your Documents folder, camera, microphone or screen. It is busy when apps ask for those permissions or check them repeatedly. It is part of macOS and its decisions are managed in System Settings > Privacy & Security.

tccd at a glance

tccd
Made byApple (part of macOS, privacy controls)
TypeSystem daemon and per-user agent
Location/System/Library/PrivateFrameworks/TCC.framework/Support/tccd
Runs asroot, plus a copy for each logged-in user
Started bylaunchd job com.apple.tccd.system
Can you quit it?Not usefully. launchd restarts it, and apps waiting for a privacy decision stall meanwhile.

What is tccd?

TCC stands for Transparency, Consent, and Control. Apple's Platform Security guide says that on macOS 10.15 or later, apps need the user's consent before accessing files in Documents, Downloads, Desktop, iCloud Drive and network volumes, and that these choices are managed in System Settings > Privacy & Security. tccd is the daemon that holds those decisions and answers when an app asks; the tccutil man page calls this store the privacy database, "which stores decisions the user has made about whether apps may access personal data."

It lives inside TCC.framework and runs twice: com.apple.tccd.system as root for Mac-wide permissions, and com.apple.tccd as an agent for your own session. When you see a dialog asking whether an app may access a folder, the camera or the screen, the request has gone through tccd.

Is tccd safe?

Yes. tccd is part of macOS in a framework on the read-only system volume. It is what makes permission prompts possible, so it must keep running.

Why does tccd use so much CPU and memory?

How much CPU is normal for tccd?

Near 0% CPU, with blips when apps start or prompts appear. Two copies, one as root and one as your user, is normal.

How do you stop tccd from using so much CPU?

  1. Grant or deny the permission an app needs. Open System Settings > Privacy & Security and check the relevant list: Files & Folders, Full Disk Access, Screen & System Audio Recording, Accessibility, Camera or Microphone. An app that has the access it needs stops asking.
  2. Remove apps you no longer use. Turn off or remove old entries in those lists, especially apps that are uninstalled but still try to run helpers.
  3. Reset a confused permission. If an app keeps asking even after you allowed it, reset its decision with tccutil reset All com.example.app in Terminal (use the app's bundle ID), then allow it again when prompted.
  4. Find the app asking. Run log stream --process tccd for a minute while tccd is busy to see which apps are requesting access. Press Control-C to stop.

When should you worry about tccd?

Look closer at any app you do not recognise in Screen & System Audio Recording, Accessibility, Input Monitoring or Full Disk Access. Those permissions let an app see or control a lot; remove the ones you did not knowingly grant.

Sustained CPU from tccd usually means one app is retrying a denied permission; the log stream step identifies it.

How do you check tccd in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type tccd in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every tccd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'tccd' | grep -v grep

How can Thrum help with tccd?

Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when tccd is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.

Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.

Questions about tccd

What does TCC stand for?

Transparency, Consent, and Control: the system that asks for your consent before apps access protected data and lets you change those decisions later.

Where are TCC permissions shown?

In System Settings > Privacy & Security, under each category. On macOS 12 or earlier the same lists were in System Preferences > Security & Privacy > Privacy.

Is it safe to reset TCC permissions?

tccutil reset only removes the stored decisions, so apps ask again the next time they need access. It does not delete data.

Sources