Thrum

Why is Messages using so much CPU or memory on my Mac?

Last reviewed: 19 November 2026.

Messages relies on background services as well as the app: imagent and identityservicesd send and receive iMessages, and with Messages in iCloud on, your whole message history syncs to the Mac. A first sync after turning that on or setting up a new Mac, long conversations full of photos and videos, and full-screen message effects are the usual causes of high CPU or memory. Settings > General > Keep messages limits how much history the Mac stores.

Which processes work for Messages?

Because imagent keeps running, Messages-related CPU can appear even when the app is not open.

Why does Messages get busy after setup or a sync?

Enable Messages in iCloud (Messages > Settings > iMessage) stores your history in iCloud so each device shows the same conversations. When it is first turned on, or on a new Mac, the whole history downloads, along with attachments. Sync Now in the same pane asks the Mac to catch up; once the setting is on, updates happen automatically.

Long conversations with many photos, videos and links keep large previews in memory when you scroll through them. Full-screen effects such as balloons and fireworks draw animations, which you can stop from playing automatically.

How do you make Messages use less?

  1. Limit how long messages are kept. Choose Messages > Settings > General and set Keep messages to 30 Days or 1 Year instead of Forever. Apple notes that older conversations, including attachments, are then removed automatically.
  2. Turn off automatic effects. In the same General pane, turn off Auto-play message effects so full-screen effects do not play when messages arrive.
  3. Let the first sync finish. After turning on Enable Messages in iCloud or setting up a new Mac, leave Messages open on power until the history has finished downloading.
  4. Close heavy conversations. Switch away from conversations full of video and images when you are done with them, so their previews are released.

When should Messages' activity concern you?

Some CPU from imagent or identityservicesd while messages arrive is normal and brief. Steady CPU from either one for hours, with no sync running, often means the Mac is repeatedly retrying something, such as a sign-in. Check that iMessage shows you as signed in under Messages > Settings > iMessage, and install pending macOS updates.

How can Thrum help with Messages?

Thrum's Memory tab shows memory pressure, swap, and the eight processes using the most memory, so you can see how much Messages holds and whether the Mac is short of memory. An optional alert tells you when memory pressure turns critical. Click Messages 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

Does Keep messages delete them from my iPhone too?

With Messages in iCloud on, the Keep messages period applies to message conversations in your account, so it affects your other devices as well. Apple notes the same option is in iCloud settings.

What is imagent on a Mac?

It is the background agent behind iMessage. It sends and receives messages for the Messages app and keeps running when the app is closed.

Sources