iStat Menus menu bar icon: hide it or keep it

The usual situation is this. CPU, memory, network throughput and a temperature reading all seem worth watching, but the right side of the menu bar ran out of room somewhere around the fourth icon, and something has to give. The good news is that the decision is rarely about which statistic to abandon. It is about which layer each statistic belongs on, and iStat Menus ships with several mechanisms for shrinking its own footprint before any external tool enters the picture.

Icons do not disappear because something broke

macOS lays status items out from right to left and stops drawing them the moment the bar is full. There is no warning, no error, no badge. The app keeps running, keeps sampling, and keeps updating a menu that is simply not being rendered. Bjango documents the behavior directly:

On smaller screens, and in situations where there’s a lot of menu bar items, macOS may hide some items. This is because the menu bar is full, and can not fit other items. In this situation, iStat Menus is running perfectly, but hidden from view. Source: bjango.com

Two things push a bar past capacity. The first is the number of status items. The second is the notch. On 14 inch and 16 inch MacBook Pro models and on M2 and later MacBook Air models, the camera housing splits the bar, and status items never wrap to the left side of it. Whatever does not fit to the right of the notch is dropped.

That second cause explains a symptom that looks like a bug. Switch to an app with a long menu of its own, something like Xcode or a professional video editor, and the left side of the bar expands to hold those menu titles. The space available to status items shrinks with it, and one or two icons vanish for as long as that app is frontmost. Nothing crashed. The geometry changed.

Nine items, and what each one costs

iStat Menus is not a single status item. The help documentation describes it as a set of nine separate and highly configurable menu items: CPU, GPU, memory, disks, network, sensors, power, time and weather. Each one is enabled independently, which is why an untouched installation can eat a surprising amount of horizontal space.

The cost is not fixed per item. It depends on the display mode chosen inside that item. A CPU pie chart is narrow. A CPU history graph is moderate. A CPU percentage rendered as text is wider still, and it grows and shrinks as the number changes. Add the word CPU as a label and the item is permanently a few characters wider. Put three temperatures in the sensors item and the bar pays for three readings.

The fastest way to audit this is to turn everything off and add back only what proves necessary. Holding Option and clicking an icon in the settings sidebar toggles that item without hunting for the switch in the main pane. Working through all nine takes a couple of minutes and usually settles at three or four.

A useful test for each item: how many times per day does the number actually get read. GPU utilization and S.M.A.R.T. status are things people check when troubleshooting, not things they monitor. Those belong somewhere other than the bar.

Combined mode is the answer the app already shipped

The single most effective setting for this problem is built in. Combined mode merges multiple iStat Menus items into one status item, with independent control over what appears in the bar and what appears in the dropdown.

Combined mode lets you combine multiple iStat Menus items into a single status item. You can choose which items are shown in the menu bar and which are shown in a combined menu, allowing you to save space in the menu bar while still having access to all the information. Source: bjango.com

The mechanics are simple. On the Combined tab, the plus button adds an item to the menu bar portion. Clicking Edit Menu and then the plus next to an item adds it to the dropdown portion. An item can live in both places at once. Removing works the same way in reverse: click a bar item and press Remove Item, or press the small close control in the menu editor.

This works because iStat Menus reports two different kinds of information. Rates and pressures, such as CPU load and network throughput, are worth glancing at continuously. States, such as free disk space, drive health, AirPods charge and a second time zone, only need to be correct when someone looks. Push every state into the dropdown and the bar can drop to one or two live numbers. The 7.0 release notes describe Combined mode as drastically overhauled, with any item now placeable in the menu bar.

Spacing, labels and display modes

When Combined mode is not enough, three settings remain.

Item spacing lives on the Global tab and offers standard or compact. Standard matches the padding macOS uses for other status items. Compact is tighter. One important limitation: compact spacing cannot be used when multiple displays are attached. Anyone running a permanent external monitor loses this option entirely, which is worth knowing before hunting for a setting that will not appear.

Labels are the cheapest thing to cut. The strings CPU, RAM and NET stop being useful once position alone identifies each item, and removing them trims several characters per item.

Display mode is where the largest savings hide. Version 7 added stacked modes that put a label and a value on two lines, trading vertical space for horizontal space, plus icon based modes for CPU, GPU, network and sensors. Switching a text percentage to an icon or a stacked pair can halve the width of an item without losing the reading.

External displays deserve a note of their own here. A large second monitor looks like it should solve the crowding problem, and in one sense it does, since the bar on a wide display has room for far more items. The catch is that macOS draws a separate menu bar per display, the built in screen keeps its own narrower bar with the notch intact, and attaching the monitor is exactly what disables compact spacing. The result is a layout that looks fine while docked and overflows the moment the laptop is undocked. Anyone who moves between the two states should tune the configuration for the smaller screen and treat the extra room on the external display as a bonus rather than the baseline.

Update frequency also sits on the Global tab. It does not affect width, but it affects cost. The 7.0 release notes state the app can use as little as one fifth of the CPU that iStat Menus 6 used with the same items, which makes a faster refresh rate cheaper than it once was.

Reordering and removal happen in the bar itself

Order is not set in the settings window. Hold Command and drag an icon in the menu bar and it moves. This applies to macOS status items generally, not just to this app.

The same gesture removes items. Command dragging an icon out of the bar deletes it, and that works for most system items too, including Wi-Fi, Bluetooth, volume and battery. Restoring one is done from the Control Center section of System Settings, where each item has a corresponding switch. The Bjango help page adds a smaller trick: setting the macOS system clock to analog display frees a noticeable amount of width for anyone who prefers the iStat Menus time item.

Order carries practical weight. The rightmost position survives longest when the bar fills up, and items further left are the first to be dropped. Placing the readings that matter on the right and the occasional ones on the left means overflow costs less.

Rules and hotkeys let an item leave the bar entirely

An item does not have to be visible to be useful, and this is the part most people skip. iStat Menus can raise a notification based on CPU, GPU, memory, disks, network, sensors, battery, power and weather conditions. The published examples include a notice when the public IP address changes, when the internet connection drops, when CPU usage stays above 60 percent for more than 10 seconds, and when free disk space runs low.

That changes the calculation for every state style reading. Free disk space in the menu bar is a number that gets ignored for months and then matters once. A rule that fires when the threshold is crossed covers the same need and costs zero width. The same applies to drive health, battery condition and connectivity.

Hotkeys are configured from the same tab. Adding an entry and assigning a key combination opens a specific dropdown even while another app is frontmost. One well chosen shortcut removes the argument for keeping a frequently opened item pinned to the bar, because the menu is reachable without the icon being visible at all.

Put together, the two features cover the two reasons an icon usually stays visible: to be watched, and to be clicked. Anything watched only for exceptions becomes a rule. Anything clicked often becomes a hotkey. What is left over is the short list that genuinely earns a permanent position.

Item Typical reason to keep it visible Better handled elsewhere
CPU, memory Load moves constantly and context matters Spikes can trigger a rule instead
Network Throughput changes second to second Connectivity loss can trigger a rule
Sensors Temperature trends during heavy work Fixed thresholds suit a rule
Disks Rarely changes minute to minute Rule on low free space
Power Percentage is already in the system bar Combined dropdown
Time, weather Duplicates the system clock in many setups Combined dropdown or a hotkey

Deciding what stays in the bar

The sequence that resolves this reliably has four steps. Turn off items that are never read. Keep in the bar only the readings whose movement carries meaning. Send everything else to the Combined dropdown. If width is still short, switch to compact spacing and drop labels.

Those four steps exhaust what iStat Menus can do about its own footprint. What remains is every other resident app holding a seat: cloud storage, a password manager, screen recording, keyboard layout, a VPN client, audio device switching. Individually small, collectively enough to push a live number off screen.

Bjango acknowledges this limit openly. The help page on hidden items points readers toward menu bar managers by name, which is an unusual thing for a developer to publish and a fair signal that no amount of internal tuning solves a bar crowded by other software.

What to change first

Start inside the app. Option click through the nine items, keep the three or four that get read, and move the rest into Combined mode. That alone recovers most of the space for most setups.

If other apps still crowd the bar after that, the remaining fix is a layer above iStat Menus rather than inside it, and the property worth checking before installing one is whether hidden icons stay clickable while the bar is collapsed. That difference decides whether frequently used icons can be hidden at all, and it is set out on How it compares alongside Features. Pricing for that kind of tool is listed on Pricing, and a build to test against a real menu bar is on Download.

Frequently asked questions

Why did my iStat Menus icons disappear from the menu bar?

Almost always because the bar filled up. macOS drops status items that do not fit and gives no error, so the app is still running normally and still collecting data. Combined mode, compact spacing and removing labels are the fastest ways to recover the space.

Which iStat Menus items are worth keeping visible?

Keep readings whose movement matters: CPU load, memory pressure, network throughput and temperature. Push states such as free disk space, S.M.A.R.T. status, Bluetooth device charge and world clocks into the Combined dropdown, where they are one click away and cost nothing in width.

How do you reorder or remove menu bar icons on a Mac?

Hold Command and drag the icon along the menu bar to reposition it. Command dragging an icon out of the bar removes it, which works for most system items as well as third party ones. System items can be brought back from the Control Center section of System Settings.

Why is compact spacing greyed out?

Compact spacing is unavailable when more than one display is connected. On a Mac with a permanent external monitor the option simply cannot be used, so the width has to come from removing labels, changing display modes, or moving items into Combined mode instead.

Back to all posts