What is coreauthd, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, accounts, launchd jobs and man page checked on macOS 26.3.1.
coreauthd is the LocalAuthentication daemon: it keeps track of authenticated sessions and presents the authentication interface when an app asks you to confirm it is you with Touch ID or your password. It uses a little CPU each time such a prompt appears. It is part of macOS and safe.
coreauthd at a glance
| coreauthd | |
|---|---|
| Made by | Apple (part of macOS, LocalAuthentication) |
| Type | System daemon and per-user agent |
| Location | /System/Library/Frameworks/LocalAuthentication.framework/Support/coreauthd |
| Runs as | root, plus a copy for each logged-in user |
| Started by | launchd job com.apple.CoreAuthentication.daemon |
| Can you quit it? | Not usefully. launchd restarts it, and Touch ID and password checks wait until it is back. |
What is coreauthd?
The man page says coreauthd "provides LocalAuthentication services. It maintains the authenticated contexts and presents the authentication user interface." LocalAuthentication is the framework apps use to authenticate users "biometrically or with a passphrase they already know", in Apple's words, so an app can ask for Touch ID instead of building its own password check.
There are two launchd jobs: com.apple.CoreAuthentication.daemon runs as root and com.apple.CoreAuthentication.agent runs in each user session. The fingerprint matching itself is not done by coreauthd; Apple's security guide says the Secure Enclave compares sensor data against stored templates, and the fingerprint data never leaves the device.
Is coreauthd safe?
Yes. It lives inside the LocalAuthentication framework on the read-only system volume and is the process that shows the system's authentication prompts. It does not hold your fingerprints.
Why does coreauthd use so much CPU and memory?
- Authentication prompts. Each Touch ID or password confirmation for an app, password AutoFill, or a settings change creates and evaluates an authentication context.
- Apps checking an existing session. Apps can ask whether a recent authentication is still valid instead of prompting again. Frequent checks show as small, regular activity.
- Authenticated contexts. It keeps active authentication contexts in memory until they expire. A few megabytes per copy is typical.
How much CPU is normal for coreauthd?
Near 0% CPU, with blips when you see Touch ID or password prompts. Two copies, one for the system and one for your session, is normal.
How do you stop coreauthd from using so much CPU?
- Answer pending prompts. An authentication prompt waiting behind other windows can make an app retry. Look for it in Mission Control.
- Review Touch ID settings. Open System Settings > Touch ID & Password to see where Touch ID is used, such as Use Touch ID to unlock your Mac and Apple Pay, and to manage fingerprints.
- Find the app asking. Run
log stream --process coreauthdin Terminal while prompts appear to see which app requests them. Press Control-C to stop.
When should you worry about coreauthd?
Prompts asking for Touch ID or your password that you did not trigger are worth investigating; check which app is in front or named in the prompt before approving.
Sustained CPU from coreauthd without prompts is unusual and points to an app checking authentication in a loop.
How do you check coreauthd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type coreauthd 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 coreauthd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'coreauthd' | grep -v grep
How can Thrum help with coreauthd?
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 coreauthd 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 coreauthd
Does coreauthd store my fingerprints?
No. Apple's security guide says fingerprint templates are encrypted so that only the Secure Enclave can read them, and the data never leaves the device. coreauthd handles the prompt and the result.
What is the difference between coreauthd and biometrickitd?
coreauthd manages authentication sessions and prompts for apps. biometrickitd provides support for biometric operations, which on a Mac means the Touch ID sensor.
Sources
- coreauthd(8) man page: run man coreauthd in Terminal
- Apple Developer: LocalAuthentication
- Apple Platform Security: Biometric security