What is runningboardd, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
runningboardd is a macOS daemon that manages process assertions, requests that keep a process in a particular state, such as running in the background, while the assertion is in effect. Its CPU use follows how often apps and services start, stop and change state, so it is busiest when many apps launch or switch. Ongoing high use usually points to an app or service that keeps restarting.
runningboardd at a glance
| runningboardd | |
|---|---|
| Made by | Apple (part of macOS) |
| Type | System daemon |
| Location | /usr/libexec/runningboardd |
| Runs as | root |
| Started by | launchd job com.apple.runningboardd |
| Can you quit it? | Not usefully. launchd restarts it on demand, and apps rely on it to stay in the right state. |
What is runningboardd?
The runningboardd(8) man page describes it as an assertion services daemon that manages process assertions to ensure those processes are kept in the appropriate state while assertions are in effect. An assertion is a request such as "keep this process running while it finishes a task"; runningboardd tracks which processes hold which assertions and adjusts their state accordingly.
Its launchd job, com.apple.runningboardd, provides the com.apple.runningboard service that apps and system services talk to. Because it sees every app launch and state change, its log messages in Console are a common sight when diagnosing app launches.
Is runningboardd safe?
Yes. runningboardd is part of macOS at /usr/libexec/runningboardd, runs as root and is started by launchd. The man page says there are no options and that users should not run it manually.
Why does runningboardd use so much CPU and memory?
- Many apps launching or switching. Opening, quitting and switching between apps changes their state, and each change goes through runningboardd.
- A process that keeps restarting. A helper or service that crashes and relaunches repeatedly makes runningboardd set up and tear down its state each time.
- Login and wake. Many apps and services start or resume at login and after sleep, which produces a burst of assertion changes.
- Many tracked processes. runningboardd keeps state for each process it manages, so its memory grows with the number of apps, extensions and helpers running.
How much CPU is normal for runningboardd?
Typical: near 0% CPU when you are not opening or switching apps, with short spikes when apps launch.
Steady CPU use for minutes while you are idle is not normal and usually means some process is being relaunched repeatedly.
How do you find what keeps runningboardd busy?
- Look for a restarting process. In Activity Monitor, sort by PID and watch for a process that keeps reappearing with a new PID. That process is the likely cause.
- Read its log messages. Open Console, start streaming and filter by the process
runningboardd. Repeated messages naming the same app or service show which one it is handling. - Update or quit the app named. Quit the app or service that appears in the messages and check whether runningboardd settles. Update the app if it keeps happening.
- Restart the Mac. A restart resets the state of every process. If runningboardd is busy again soon after, use the Console step to find the source.
When should you worry about runningboardd?
Worry if runningboardd holds high CPU for long periods while you are not using the Mac. It reacts to other processes, so the real cause is the process named in its log messages.
A runningboardd outside /usr/libexec would not be Apple's.
How do you check runningboardd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type runningboardd 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 runningboardd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'runningboardd' | grep -v grep
How can Thrum help with runningboardd?
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 runningboardd 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 runningboardd
Why does runningboardd write so many log messages?
It records state changes for apps and services as they launch, suspend and exit, so a busy Mac produces many messages. They are useful for diagnosis and harmless.
Is runningboardd related to App Nap?
Apple's man page only says it manages process assertions and keeps processes in the appropriate state. It does not describe a link to App Nap, so this page does not claim one.
Sources
- runningboardd(8) man page: run man runningboardd in Terminal