Show CPU and memory in your Mac menu bar

Updated 2026 · a 8-minute read

A menu bar system monitor lets you see how hard your Mac is working at a glance — handy when the fans spin up, a video export drags, or the battery is draining faster than it should. The catch: most monitors add several icons to an already-crowded bar, trading one problem for another.

This guide covers what's actually worth monitoring, how to interpret the numbers (which is where most people go wrong), and how to get the readouts without losing half your menu bar to them.

The built-in option: Activity Monitor

Before installing anything, know that macOS already ships a capable tool. Activity Monitor lives in Applications → Utilities, and it's the authoritative source for everything below.

A trick most people miss: right-click its Dock icon and choose Dock Icon → Show CPU History (or CPU Usage). The Dock icon becomes a live graph, giving you an always-visible readout for free. Keep Activity Monitor in your Dock and you have a permanent CPU monitor with nothing installed.

The limitation is that it's a window, not a glance. You have to switch to it, and it occupies Dock space rather than the menu bar. For continuous awareness while you work, a menu bar readout is the better shape.

What the numbers actually mean

This is the part worth understanding, because several of these metrics are routinely misread — and acting on a misread number is how people end up "fixing" problems they don't have.

CPU: percentages above 100% are normal

Activity Monitor reports CPU per core, so on a 10-core machine the theoretical maximum is 1000%. A process at 300% isn't broken; it's using three cores' worth of capacity. Menu bar monitors usually normalise this to 0–100% across all cores, which is friendlier but means the two tools will disagree — that's expected, not a bug.

Two sub-figures are worth watching:

User — time spent on your applications. High user time during a video export or compile is exactly right.
System — time spent in the kernel. Persistently high system time with low user time is the odd one, and often points to heavy disk or network I/O, or a misbehaving driver or background daemon.

Load average: not a percentage

The three load-average numbers (1, 5 and 15-minute) confuse people because they aren't percentages. They represent the average number of processes waiting to run. The useful comparison is against your core count: on a 10-core Mac, a load of 4 is comfortable, a load of 10 means fully saturated, and a sustained load well above 10 means work is queuing up and things will feel sluggish.

Memory: "used" is the wrong number to watch

This is the most common misreading on modern Macs. People see 26 GB of 32 GB used and panic. That's usually fine. macOS deliberately uses free RAM for caching, because unused memory is wasted memory — it will hand it back the moment something needs it.

The number that actually matters is memory pressure, shown as a graph in Activity Monitor's Memory tab. Green means you're fine regardless of how "full" RAM looks. Yellow means macOS is working to free memory. Red means you genuinely need to close things or add RAM.

The breakdown is worth knowing too:

App Memory — what your running applications hold.
Wired Memory — cannot be paged out; the kernel and essential services.
Compressed — macOS compresses inactive pages rather than writing them to disk. Seeing several GB compressed is normal and is the system working as designed; it's far faster than swapping.
Swap Used — actually written to disk. Small amounts are routine. Large and growing swap alongside red pressure is the real warning sign.

Network: rate versus total

Menu bar monitors typically show a live rate in KB/s or MB/s with up and down arrows. Useful for confirming a transfer is progressing, or spotting an app quietly uploading when you didn't ask it to. Distinguish that from cumulative totals since boot, which answer a different question — "how much data have I moved today" rather than "what's happening right now."

A practical use: if your Mac feels slow and CPU is idle, glance at network. A cloud sync client reindexing thousands of files can make a machine feel unresponsive while barely touching the CPU.

Disk: free space and I/O are different problems

Free space matters because macOS needs headroom for swap, caches and updates. Getting close to full causes strange, hard-to-diagnose slowdowns. As a rough guide, keep at least 10–15% free.

Disk I/O — read and write rates — is a separate signal. High sustained I/O with low CPU usually means indexing (Spotlight after a big copy), a backup running, or a sync client catching up.

Battery: health and cycles

Two numbers tell you where a laptop battery stands:

Cycle count — one full charge's worth of discharge, not one plug-in. Modern Mac batteries are rated for 1000 cycles.
Maximum capacity / health — current capacity as a percentage of original. Gradual decline is normal chemistry. Apple considers a battery consumed below 80% health.

You can see both natively in System Settings → Battery → Battery Health, and in more detail by holding Option and choosing System Information from the Apple menu.

One slot instead of five

Dedicated monitors are powerful but typically spend a separate menu bar slot on each metric — CPU in one, memory in another, network in a third. If you're already short on menu bar space, that's trading one problem for another.

Barkeep takes the opposite approach: a single menu bar slot shows a live CPU sparkline and network rates, and clicking it opens a full dashboard with per-core load, the memory breakdown described above, disk, battery health and cycle count, and the top processes sorted by CPU or memory. One slot, the whole picture — and because Barkeep also hides your other icons, you come out ahead on space rather than behind.

It reads everything from macOS's own public system APIs, so it needs no permissions at all to show these numbers — no Accessibility, no Screen Recording, no network access.

What a free monitor can't show you

An honest limit worth stating: on Apple Silicon, reading sensor temperatures and fan speeds requires private APIs that a lightweight free app is right to avoid. If those specific readouts matter — you're overclocking, diagnosing thermal throttling, or just like watching the numbers — a paid tool like iStat Menus remains the reference and is worth the money for that use case.

For the everyday questions — why is my Mac slow, what's draining the battery, is that upload finished — CPU, memory, network, disk and battery cover it.

A quick troubleshooting flowchart

Next time your Mac feels slow, read the metrics in this order:

CPU high? Check top processes. A runaway process is the most common cause, and quitting or restarting it usually fixes it outright.
CPU fine, memory pressure yellow or red? You're short on RAM. Close the heaviest apps — browsers with many tabs are the usual culprit.
Both fine, but disk I/O high? Something is indexing, backing up or syncing. Usually the fix is patience; it will settle.
Everything low but still sluggish? Check free disk space, and check whether a network drive or cloud folder is stalling — waiting on I/O looks like nothing at all on a CPU graph.

Get Barkeep — free