Thrum

What is mobiletimerd, and why is it running on my Mac?

Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1; it was running as the logged-in user.

mobiletimerd is the macOS agent that manages alarms and timers, the ones you set in the Clock app or with Siri, and shows the notification when one fires. It starts at login and stays running so it can fire alarms on time, even when the Clock app is closed. It uses almost no CPU.

mobiletimerd at a glance

mobiletimerd
Made byApple (part of macOS, Clock)
TypePer-user agent
Location/System/Library/PrivateFrameworks/MobileTimer.framework/Executables/mobiletimerd
Runs asyour user
Started bylaunchd job com.apple.mobiletimerd
Can you quit it?Not usefully. launchd starts it at login, and alarms and timers depend on it.

What is mobiletimerd?

Its man page calls mobiletimerd the timer agent: it manages alarms and timers and is responsible for showing notifications when they fire. The name comes from the MobileTimer framework, which it lives in.

launchd starts it at login through the com.apple.mobiletimerd job and it runs as your user. Because it, not the Clock app, keeps track of alarms and timers, they still go off after you quit Clock.

Is mobiletimerd safe?

Yes. It is part of macOS in /System/Library/PrivateFrameworks and signed by Apple.

Why does mobiletimerd use so much CPU and memory?

How much CPU is normal for mobiletimerd?

mobiletimerd sits at 0% CPU nearly all the time with a small memory footprint. A blip when an alarm or timer fires is normal.

It is expected to be running even if you never use Clock.

How do you manage the alarms and timers it handles?

  1. Open Clock. Open the Clock app from the Applications folder to see alarms and timers.
  2. Delete alarms you no longer need. Remove old alarms so nothing fires unexpectedly.
  3. Check notification settings. System Settings > Notifications > Clock controls how alarm and timer notifications look and sound.
  4. Restart if alarms stop working. If alarms do not fire, restart the Mac; launchd starts mobiletimerd again at login.

When should you worry about mobiletimerd?

Steady CPU use by mobiletimerd is not expected. Restart, and check Clock for a large number of alarms.

A copy outside the MobileTimer framework would not be Apple's.

How do you check mobiletimerd in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), and type mobiletimerd 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 mobiletimerd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

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

How can Thrum help with mobiletimerd?

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 mobiletimerd 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. Click mobiletimerd in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.

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 mobiletimerd

Why is mobiletimerd running when I do not use Clock?

launchd starts it at every login so alarms and timers can fire at any time.

Can I quit mobiletimerd?

It would start again, and alarms or timers could be missed. It uses almost nothing, so leave it running.

Sources