iStat Menus alternatives: decide what you can drop

Every candidate on the list claims CPU, memory, temperature, network, and a clock. Read three product pages in a row and they blur together, because a feature grid cannot tell anyone which rows matter on their particular Mac.

The faster order is to start from what is already installed. iStat Menus bundles roughly ten independent readouts into one app, and on most machines only two or three of them are ever read in the menu bar. Once the unread ones are marked as expendable, the requirement shrinks from "a system monitor" to something specific enough to shop for. What follows is the full list of what the current version can display, a test for separating a reading from a decoration, the two capabilities that are genuinely hard to replace, and where free tools land.

Two different searches wear the same name

"Alternative" covers two situations that point in opposite directions.

The first is wanting to keep monitoring but change the supplier, usually because of the payment model, the supported macOS range, or something behaving badly. That search is about matching capability.

The second is wanting the menu bar space back. The numbers were nice to have, Activity Monitor covers the rest, and the row of readouts has simply grown past what fits. That search is not about monitors at all. Swapping one monitor for another that displays the same number of items reclaims exactly zero pixels.

The second case has a cheaper answer that most people never try, because it lives inside the app already: combined mode collapses several items into a single status item, with a choice of what stays visible and what moves into the dropdown. Testing that takes five minutes and often ends the search.

The full list of what it can put in the menu bar

Checked against the product page on 2026-09-10, for version 7.3:

Readout	What it can display
CPU and GPU	Per-core usage, history graphs, load averages, uptime, frequency, GPU temperature and frequency
Memory	Usage, history, memory pressure, compressed memory, swap, top apps
Disks	Used and free space, activity, S.M.A.R.T. status, per-app disk usage
Network	Send and receive rates, history, top apps by bandwidth, public and private IP, connectivity
Battery and power	Charge state, plus levels for AirPods, Magic Mouse, Magic Trackpad and other Bluetooth devices
Sensors	Temperatures, fan speeds, voltages, current, power. Fan control with speed curves
Date and time	Clock formats, calendar with upcoming events, world clocks, sun and moon detail
Weather	Current conditions, hourly forecast, weekly overview
Rules	Notifications keyed to CPU, GPU, memory, disks, network, sensors, battery, power, weather
Combined	Merges multiple items into one status item

Three layers hide in that table. Measuring the values, showing them in the menu bar, and alerting when a value crosses a line. Replacements differ enormously on the first and third layers and barely at all on the second.

The test that separates a reading from a decoration

Memory is a bad guide here, because settings that were configured once feel like settings that are used. A sharper question: has the menu bar display, on its own, ever changed a decision?

Some readouts pass easily. Seeing CPU pinned and killing an export. Seeing free space drop and clearing a scratch folder. Seeing a battery figure and deciding whether the charger is needed for the next meeting. Those earn permanent slots.

Others never pass. If the routine is to click the item and read the dropdown, the menu bar icon is doing nothing except occupying width, since opening Activity Monitor costs about the same. Weather is the common example. A forecast is something people look up, not something that changes a decision at a glance, unless the day involves going outside on short notice.

Run that test and the survivors usually number two or three. On a laptop it tends to be battery and a temperature. On a machine with a lot of network gear it tends to be throughput. On a video workstation it tends to be free space. Cutting from seven visible items to three removes most of the width problem before any replacement is considered, and it turns the shopping requirement into something a comparison table can actually answer.

The two capabilities that are hard to replace

Of the survivors, two are notably scarce in other products.

Sensor reading is the first. Pulling temperatures, voltages, current, and power off the hardware requires a privileged helper, and relatively few projects maintain that code.

Fan control is the second, and it is scarcer still. Reading fan speed is common. Setting it, ramping it gradually, and driving it from a temperature or battery curve is not.

Before treating either as a requirement, two facts are worth checking against the installed copy.

It can not control fan speeds. The iStat Menus Helper is needed to view some stats. Source: bjango.com, Mac App Store version differences, checked 2026-09-10

That is the Mac App Store build. Fan control is not in it at all.

The second fact is hardware. The project's known issues page states that on M3, M3 Pro, M3 Max, M4, M4 Pro and M4 Max Macs, fan control may not work correctly in situations where macOS has turned the fans off, and that solutions are being investigated.

Put together: on an Apple Silicon Mac of that generation, or on any copy bought through the App Store, fan control may never have been a working feature on that machine. A requirement that was never met is not a requirement to carry into the next purchase.

Rules are the layer people forget to check

The third layer of the table, alerting, is the one most often left out of a comparison and most often missed after a switch. The current version can fire a notification from CPU, GPU, memory, disk, network, sensor, battery, power and weather conditions, with thresholds and durations attached: a public IP that changed, an internet connection that dropped, CPU above a set percentage for longer than a set number of seconds, a disk running short of space.

That layer is worth auditing separately from the menu bar readouts, because the two do not overlap. A rule earns its place if it has ever fired usefully. A rule that was written during the first evening with the app and has never produced a notification since is configuration, not capability, and carrying it into the requirements list narrows the shortlist for no return.

Where a rule has proved useful, check specifically whether candidates offer the same trigger. Free monitors generally display values well and alert on them poorly or not at all, so a single genuinely useful rule can be the thing that keeps a paid tool in place. Two rules that fire regularly are usually enough to settle the whole decision on their own.

Disk space is the common survivor. A warning at a low free-space threshold arrives early enough to act on, whereas noticing the same thing from a menu bar figure depends on happening to look. That difference is exactly why the alerting layer deserves its own line in the comparison rather than being folded into the feature count.

What free tools actually cover

Knowing where the free tier stops makes the paid decision quick. Checked on 2026-09-10 against each project's own repository:

Tool	Licence	macOS	Coverage
Stats	MIT	12 Monterey and newer	CPU, GPU, memory, disk, network, battery, sensors, Bluetooth devices, multi-timezone clock
MenuMeters	GPL-2.0	See project repository	CPU, memory, disk, network

Stats covers the common four plus sensors, which is more than most people read. Its repository lists fan control among its modules with a note that the module is not maintained, so a fan curve is outside what it promises.

One practical difference is worth planning for. Because Stats installs a privileged SMC helper to read sensors, removing it is not a drag to the Trash. The project ships an uninstall script that quits the app and removes the helper daemon along with the application support directory and preferences. Reading the removal instructions before installing is the sort of thing that costs two minutes now and saves an afternoon later.

What the licence costs, and what "upgrade" means

If the payment model is the reason for the search, the numbers matter. Prices from the vendor's own checkout, requested for the United States on 2026-09-10:

Licence	Price
iStat Menus 7	US$11.99
iStat Menus 7 Family Pack	US$14.99
iStat Menus 7 Upgrade	US$9.99
iStat Menus 7 Family Pack Upgrade	US$12.99

Amounts are localised and local taxes may apply, so the figure on the screen at checkout is the one that counts. The family pack covers up to five family members, and every licence includes six months of weather data.

The word upgrade carries a condition that trips people up: the discounted price requires an existing iStat Menus 6 licence. Without one, the relevant number is the full price, and the gap between the two is small enough that hunting for a lost licence key can cost more time than it saves.

The trial runs for 14 days. That window is long enough to run the decision test above rather than to evaluate features, which is the higher-value use of it. Worth noting alongside: the current version requires macOS 11 or newer, and a 7.5 release for macOS 27 is announced as coming soon with a beta available.

If the problem is width, the monitor is not the thing to replace

For a menu bar that is simply full, three settings come before any product change. Combined mode merges items into one. Labels can be switched off so only figures remain. Item spacing can be set to compact, though that option is unavailable when multiple displays are attached.

When those are exhausted, the next tool is not another monitor. It is something that manages the menu bar itself, deciding which icons are visible and which are one gesture away. The axis that matters there is not the feature count but what happens after an icon is hidden. A tool where a hidden icon can be clicked without unfolding the bar removes the unfold, scan, click, fold loop entirely, which matters more for monitoring items than for most others, since their whole purpose is to be opened and read.

How it compares sets out how different tools approach hiding, including the macOS versions each requires, and Features covers splitting icons into ones that stay out of sight permanently and ones that surface on demand. Running both a monitor and a menu bar tool is a two-line budget rather than one, so checking Pricing early makes it easier to decide whether to pay for both or consolidate.

What to change first

Write down the readouts that have actually changed a decision, and cut the rest to the dropdown. If the remaining list still does not fit, the fix is a menu bar tool rather than a different monitor, and Koffret can be tested against the current setup before anything is uninstalled.