What is corebrightnessd, and why is it running on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job, man page and Displays settings labels checked on macOS 26.3.1.
corebrightnessd is a macOS system daemon whose man page says it manages Night Shift, the feature that shifts display colors toward warmer tones after dark. It runs as root, starts with the Mac, and normally sits at or near 0% CPU. There is nothing to configure in it directly; Night Shift is set in System Settings > Displays.
corebrightnessd at a glance
| corebrightnessd | |
|---|---|
| Made by | Apple (part of macOS) |
| Type | System daemon |
| Location | /usr/libexec/corebrightnessd |
| Runs as | root |
| Started by | launchd job com.apple.corebrightnessd |
| Can you quit it? | Not usefully. It runs as root and its launchd job keeps it alive. |
What is corebrightnessd?
The man page for corebrightnessd says it manages Night Shift and should not be invoked directly. Night Shift, in System Settings > Displays > Night Shift, warms the colors of the display after dark on a schedule you set or from sunset to sunrise, and its settings note that it does not apply to connected televisions or projectors.
launchd starts it at boot from the com.apple.corebrightnessd job in /System/Library/LaunchDaemons, runs it as root, and keeps it alive. Apple does not document its other duties in detail, so this page covers only what its man page and settings show.
Is corebrightnessd safe?
Yes. corebrightnessd is part of macOS, signed by Apple, and stored in /usr/libexec on the read-only system volume. It runs as root because it controls display settings for every user.
Why does corebrightnessd use so much CPU?
- Night Shift turning on or off. At the start and end of the Night Shift schedule, or when you move the color temperature slider, the display's colors are changed, which takes a moment of work.
- Sunset to sunrise schedule. The Sunset to Sunrise schedule depends on your location for the time zone, so location and time zone changes make it recalculate when Night Shift should run.
- Connecting or disconnecting displays. Night Shift applies to the displays that support it, so connecting or disconnecting a display changes what it has to adjust.
How much CPU is normal for corebrightnessd?
At or near 0% CPU almost all of the time, with brief activity when Night Shift changes or a display is connected.
Memory use is typically a few megabytes to a few tens of megabytes.
What can you do if corebrightnessd keeps using CPU?
- Check Night Shift settings. Open System Settings > Displays and click Night Shift. Set the schedule to Off, Custom or Sunset to Sunrise as you prefer; Off gives it the least to do.
- Check location for time zone. Sunset to Sunrise needs location for the time zone. If the schedule is wrong, check that Location Services is on in System Settings > Privacy & Security, or use a Custom schedule instead.
- Reconnect displays. If high CPU began when a display was connected, disconnect and reconnect it, or try another cable or port.
- Restart the Mac. corebrightnessd runs as root and restarts automatically, so a restart of the Mac is the clean way to reset it.
When should you worry about corebrightnessd?
Look closer if corebrightnessd stays above a few percent CPU for many minutes with Night Shift off and no display changes. That is unusual; a restart normally clears it.
It should run only from /usr/libexec/corebrightnessd as root.
How do you check corebrightnessd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type corebrightnessd in the search field. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every corebrightnessd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'corebrightnessd' | grep -v grep
How can Thrum help with corebrightnessd?
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 corebrightnessd 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 corebrightnessd
Does turning off Night Shift stop corebrightnessd?
No. The daemon keeps running, but with Night Shift off it has less to do.
Why does Night Shift not work on my TV?
Night Shift settings state that it does not apply to connected televisions or projectors.
Sources
- corebrightnessd(8) man page: run man corebrightnessd in Terminal
- Apple Support: Use Night Shift on your Mac