The "menu-bar system monitor" is one of the oldest Mac utility categories. iStat Menus shipped around 2007 and defined the shape: small graphs and readouts in the top-right of your screen, showing CPU, memory, network, temperatures, disk, battery. Fifteen years on, plenty of alternatives exist — MenuMeters, Stats, iStatistica, Sensei, ActiveStat, and a dozen others — and the underlying platform has changed enough that what makes a good monitor in 2026 isn't quite what it was in 2010.
Here's a framework for evaluating them, and then how the main options stack up.
What actually matters on Apple Silicon
The move from Intel to Apple Silicon in 2020 broke most of the old assumptions.
CPU percentage is less useful than it was. On Intel Macs, a single "CPU %" number was informative because every core was roughly the same. On Apple Silicon, you have performance cores and efficiency cores, and macOS is aggressive about parking work on the efficiency cores whenever it can. Total CPU % averages across cores of very different capability, so a machine at "20% CPU" might be lightly loaded (four E-cores doing housekeeping) or heavily loaded (a P-core pinned by a compiler). A good 2026 monitor separates P and E cores in its readout, or at least shows per-core usage.
Temperature readings are patchier. Intel Macs exposed dozens of thermal sensors via SMC. Apple Silicon exposes fewer, and the sensor names moved. Some tools that predate the M1 transition still show sensors, but the values are approximate — the "CPU temperature" you see is often a proxy derived from the SoC power draw and package temperature, not a direct sensor reading. This isn't the tool's fault; the hardware just doesn't publish what it used to.
Power draw is the useful new axis. Apple Silicon exposes CPU and GPU power in watts, which turns out to be a much better proxy for "how hard is this machine working" than CPU %. A P-core cluster running at 15 W is doing real work; the same machine at 2 W is idle no matter what the CPU graph says. Any monitor that surfaces package power is telling you something you couldn't get from Activity Monitor at a glance.
Memory pressure beats memory percentage. macOS aggressively compresses memory, so "used" and "free" are misleading — a machine at 90% memory used can be perfectly happy. What matters is memory pressure (green/yellow/red). Activity Monitor shows this; some third-party tools do, some don't.
What to look for in a menu-bar monitor
1. Readouts you can actually read at a glance
The whole point of a menu-bar monitor is that it lives at the periphery of your vision. If the graphs are too small to parse, or the numbers are too precise for the space, they add clutter without giving you information. A good monitor gives you two or three things you can absorb in a quarter-second: a sparkline, one number, maybe an icon. If you find yourself squinting or opening the menu to read what's happening, the design has failed.
2. Restraint about what it shows by default
Full-featured monitors like iStat Menus expose everything — CPU per core, per-core temperature, per-interface network, per-drive I/O, fan RPM, battery cycles. This is powerful and configurable, but the default install is a wall of graphs. In 2026, the right default is one or two indicators, and everything else is opt-in. Most people don't need to see network throughput 24/7; they need to know when something is wrong.
3. Efficiency
A system monitor should not itself be a meaningful source of CPU usage. Polling every second uses more power than polling every five seconds; drawing animated graphs uses more power than drawing static ones. Good tools measure their own footprint and stay under 1% CPU on average. Some don't.
4. Native rendering
Menu-bar tools built in Electron or with web-tech wrappers are much heavier than SwiftUI/AppKit native tools. This matters both for power draw and for how the tool looks — native menu bar items render at exact pixel offsets and respect system dark mode transitions instantly. Non-native ones tend to flicker at wakeup and look slightly off.
5. Read-only, no cloud, no telemetry
A system monitor doesn't need an account. It doesn't need to upload readings. It doesn't need to phone home. The category has a bad recent history of tools quietly adding analytics; check the privacy policy before installing.
How the main options stack up
iStat Menus
The incumbent. Still the most feature-complete monitor on the platform — every sensor macOS exposes, plus weather and time zone readouts as bonus modules. If you want maximum information density and you're happy tuning the display to hide what you don't need, iStat Menus remains the top pick. The trade-off is complexity: the settings pane has hundreds of toggles, and the default install is busy.
Stats
Free, open source, native. A serious effort to build "iStat Menus but clean and free." It covers the essentials — CPU, GPU, memory, network, disk, battery, sensors — and does them well. If budget matters and you want something maintained by the community, Stats is the answer.
The downside is polish. It's actively developed but rough around the edges; the UI is functional rather than considered, and configuration can feel improvised.
Sensei
Sold itself as a "Mac utility suite" — monitoring plus optimisation. The monitoring part is competent but the "optimisation" features on Apple Silicon are essentially placebo (macOS manages caches, swap, and startup items better than any third-party tool). If you're evaluating Sensei for its monitor, it's fine; if you're being sold on its cleanup features, be sceptical.
MenuMeters
The classic. Free, tiny, does CPU/memory/network/disk and nothing else. Hasn't changed much in years, which for this category is a feature. If you want the smallest possible tool that puts four sparklines in your menu bar and stops there, MenuMeters is still it.
ActiveStat
ActiveStat is our take. It focuses on the readouts we found ourselves actually looking at — CPU (with P/E-core separation on Apple Silicon), memory pressure, GPU load, network throughput, battery, and per-core temperature where available. It's SwiftUI-native, quiet by default, and doesn't try to be a suite. It's what we wanted iStat Menus to be if you took out the busy defaults and the feature sprawl.
ActiveStat is on the App Store and available direct. Small studio, no telemetry, no subscription. If you're monitoring an Apple Silicon Mac and iStat Menus feels like too much, it's worth a look.
The one-line summary
Pick iStat Menus if you want maximum information and don't mind tuning it down. Pick Stats if you want free and open source. Pick MenuMeters if you want tiny and unchanging. Pick ActiveStat if you want something native, restrained, and built with Apple Silicon in mind from day one.
And if you're not sure whether you need a menu-bar monitor at all: try opening Activity Monitor once a week for a month. If you find yourself doing it more than that, you'd probably benefit from a menu-bar tool. If not, you probably don't need one.