iStat Menus on Mac: how to set it up

Installation finishes in under a minute. The settings window that opens afterwards is where people stall, because nine tabs of options appear at once and none of them announce which one matters. In practice the app only needs four decisions made properly, and after that it can be left alone for months. Those decisions are whether to install the helper, which items to enable, what each enabled item puts in the menu bar, and how often it refreshes. Working through them in that order avoids most of the confusion.

Decision one: the helper component

The download itself is a ZIP archive from the product page. Unarchive it, run the app, and a prompt appears asking about additional components. That prompt is the first real decision, and version 7 changed what it means. The release notes for 7.0 record it directly:

Added ability to install without an admin password (the helper is optional). Source: bjango.com

Version 6 effectively required an administrator password during installation. Version 7 does not, and the helper is now a separate choice.

What the helper buys is access to temperatures, fan speeds and a subset of other statistics. Everything else, meaning CPU usage, memory, disk usage, network throughput, the clock and weather, works without it. Anyone using a managed machine without admin rights, or anyone who prefers to keep the number of background components down, can decline it at install time and add it later if temperature readings turn out to matter.

One related constraint is worth knowing before choosing an install route at all. The Mac App Store build cannot control fan speeds under any configuration, and still needs the helper for some readings. If adjusting a fan curve is the reason for installing the app, the direct download is the only version that does it.

Decision two: turn everything off, then add back

The settings sidebar lists the nine independent menu items: CPU, GPU, memory, disks, network, sensors, power, time and weather. Each is enabled separately.

Adding items one at a time from a clean slate works better than pruning a full set, because it forces each item to justify itself. Holding Option and clicking an icon in the sidebar toggles that item without opening the tab and finding the switch. Going through all nine takes two or three minutes, and most setups settle on three or four.

The question that resolves each one quickly is how many times a day the number gets read, not how interesting it is. GPU utilization is fascinating and almost never consulted. Drive health is important and never changes on the timescale of a glance. Both belong somewhere other than a permanent slot in the menu bar.

Decision three: what each item puts in the bar

This is where most confusion happens, because enabling an item and populating it are two separate actions. Inside each tab there is a menu bar area and a dropdown area. The plus button adds a component to the bar, clicking a component opens its options, and Remove Item takes it out again.

Sensors, disks and power are the three that catch people out, and the developer documents the symptom:

The sensors shown in the menubar are determined by the “items in menu bar” area in the Sensors tab. If this is blank, nothing will show. To add a sensor click the + button. Source: bjango.com

An item switched on with an empty list produces no icon at all. It looks like a broken install and it is an empty field.

Component choice also sets how much width the item takes. CPU alone can display a pie chart, a live graph, a history graph, a text percentage, a label, or the stacked label and value modes added in version 7. History graphs accept a time range from 10 minutes up to 28 days, with steps at 1, 3, 6 and 12 hours and 1, 3, 7 and 14 days. A ten minute window catches short spikes. A seven day window shows whether a machine is under sustained load. They answer different questions, so the range is worth setting deliberately rather than leaving at the default.

Decision four: theme, spacing and refresh rate

The Global tab holds the settings that apply across the app, and there are three worth setting once.

Theme is chosen from a carousel where the upper half controls menu bar appearance and the lower half controls the dropdown menus. Since 7.0 the default menu bar theme uses the macOS accent color as its primary color, so it changes with the system setting.

Spacing offers standard, matching other macOS status items, or compact, which is tighter. Compact is unavailable while more than one display is connected, which is a common source of confusion on docked laptops.

Update frequency trades responsiveness against resource use. This costs less than it used to: the 7.0 notes describe the app as using as little as one fifth of the CPU that version 6 used with the same items configured.

Language follows the system setting, since version 7 is localized for more than 30 languages.

Rules, hotkeys and the dropdown

Two features change what needs to be visible at all, and both are configured from the rules tab.

Rules raise notifications based on CPU, GPU, memory, disks, network, sensors, battery, power and weather conditions. Documented examples include the public IP address changing, the internet connection dropping, CPU usage staying above 60 percent for more than 10 seconds, and free disk space running low. Any reading that only matters when it crosses a threshold is better served by a rule than by a permanent icon.

Hotkeys are added from the same tab by creating an entry, choosing which menu it opens and assigning a key combination. The shortcut works while another app is frontmost, so a frequently opened menu does not need a visible icon to stay reachable.

What sits behind those menus is substantial, which is why moving things out of the bar costs less than it appears to. The CPU menu carries per core usage, load averages, uptime, frequency and the processes using the most CPU. Memory carries pressure, compressed memory, swap and the heaviest processes. Network carries a per app bandwidth breakdown along with public and private IP addresses. Disks carry S.M.A.R.T. status and per app disk usage. Power carries battery detail plus charge levels for AirPods, Magic Mouse and other Bluetooth devices. The menus also include an app launcher, and since 7.0 it can be pointed at any app, which is useful for jumping straight to Activity Monitor or Terminal after spotting something.

Three starting configurations

The four decisions land differently depending on what the machine is used for. These are starting points rather than rules, and each one assumes the other items stay available in the dropdown.

Machine and use	Items to enable	Helper	Notes
Laptop under sustained load, such as video or compilation work	Sensors, CPU, power	Yes	Temperature and fan readings are the point, so the helper and the direct download are both required
Desktop with a permanent external display	CPU, memory, network	Optional	Compact spacing is unavailable while a second display is attached, so plan widths for the built in screen
Older Intel Mac on macOS 11 or 12	CPU, memory, disks	Yes	The direct download is the only route, since the App Store build requires macOS 14.0 or later

The laptop case is the one where the install route matters most, because fan control only exists in the direct download. The desktop case is the one where width planning matters most, since the configuration that fits comfortably while docked is the one that overflows the moment the machine is used on its own screen. The older Mac case is decided before any setting is touched, by the system requirement alone.

Weather is deliberately absent from all three. It is the one item billed separately, with six months included and data packs afterwards, so switching it on is a decision about a recurring cost rather than about screen space.

What to verify once, immediately after setup

Three checks confirm the configuration is real rather than theoretical, and all three take a minute.

Count the icons actually visible in the menu bar against the items enabled in settings. If the numbers differ, macOS is hiding the overflow and part of the configuration is doing nothing. Second, open each dropdown once so the contents are familiar, since the whole approach depends on knowing where information went after it left the bar. Third, create one rule with a threshold low enough to fire immediately, confirm the notification arrives, then raise the threshold to a realistic value. Notification permissions are easy to miss, and a rule that never fires is indistinguishable from a machine that never has a problem.

Where setups break, and how to recover them

Two failures account for most of the trouble reports.

The first involves location access. Weather for the current location needs Location Services, and there is a case where permission has been granted in System Settings but the Request Location Access button keeps appearing in the menu. The documented fix is to open System Settings, go to Privacy and Security, then Location Services, switch it off and switch it back on.

The second follows macOS upgrades. After a major system update the app may stop launching or stop updating its statistics. The fix is System Settings, General, Login Items, where the iStat Menus entry should be switched off and back on again. There is often more than one entry, named after either the app or the developer, and all of them need the same treatment. A Terminal command to reset the login items database exists as a further step, but it affects login item settings for every other app on the machine, so it belongs last rather than first.

Installation itself can also fail on permissions, most often on machines where the home folder has been moved to an external drive and launch agents no longer load correctly. The developer publishes the commands that restore ownership on the relevant folders. Separately, settings can be exported and imported, which is the fastest way to carry a finished configuration to a second Mac instead of repeating all four decisions.

What to change first

Install without the helper, enable three or four items, populate each one deliberately, and set update frequency once. Then check whether the result actually fits, because a configuration that overflows the bar on a laptop screen has not finished.

If other resident apps are the reason it does not fit, the fix sits above iStat Menus rather than inside it, and the thing to verify before adding one is whether hidden icons remain clickable while the bar is collapsed. That single property decides how much can be hidden, and it is covered on Features and How it compares, with a build to test on Download.