Hidden Bar vs Ice: how to pick a free menu bar manager

The right side of the menu bar has filled up, an icon that used to be easy to find is now buried between two sync indicators, and the search that follows is usually "hidden bar vs ice". Both are free, both are open source, and both do the same central job: they put a divider in the menu bar and hide whatever sits on the wrong side of it. The decision between them almost never comes down to a feature checklist. It comes down to where the app is distributed, which macOS versions it runs on, and what has to happen when a hidden icon is needed again.

There is a reason the problem arrives suddenly rather than gradually. Menu bar space is fixed, and every background utility installed over a year claims a slice of it on the assumption that it deserves to be permanent. On MacBook models with a notch, the usable width on the right shrinks further, and when an app with a long set of its own menus is in front, items can stop appearing entirely. They are still running. They are just off the end of the available space, which is a confusing way for something to fail. macOS itself only solves part of this: system items that live in Control Center can be toggled from System Settings, but that switch does nothing for icons belonging to apps installed later. That gap is the reason these two tools exist.

What the two have in common

It is worth being clear about the shared ground first, because it is larger than the differences.

Both Hidden Bar and Ice are free. Neither one holds a core feature behind a purchase. Both publish their source code, so the behavior can be inspected rather than trusted on faith. Both work by adding a separator to the menu bar: icons dragged to the left of it disappear, icons to the right stay visible. Both let you set aside a second group of items that stay hidden even when the bar is expanded, which is where things that get touched a few times a year belong.

Both also rely on the same macOS mechanic for arranging icons. Holding Command and dragging a menu bar item moves it, and that is the step that actually decides what is hidden. Installing either app changes nothing on its own. The rearranging is manual, it takes a few minutes once, and skipping it is the most common reason someone concludes that a menu bar manager "did not work".

So the honest framing is this: either app will get the menu bar tidy. The differences show up in the weeks after that.

Where you get them, and how updates arrive

This is the difference with the most practical weight, and it has nothing to do with features.

	Hidden Bar	Ice
Main distribution	Mac App Store	Release page published by the developer
Price	Free	Free
Source code	Public	Public
How updates arrive	Through the App Store update flow	In-app update check, or download the new build
macOS requirement	Check the listing before installing	Check the listing before installing

Facts above reflect what each project published as of September 5, 2026.

Coming from the Mac App Store means the app went through Apple's review, updates land in the same place as everything else, and the app can be restored from the purchased list after a machine swap. On a work-issued Mac where installs from outside the App Store are restricted by policy, that single row can settle the question before any feature is compared.

Downloading directly from a developer's release page means fixes and new behavior can ship without waiting on a review cycle. In exchange, the first launch goes through Gatekeeper's confirmation, and staying current is a habit rather than something the system handles quietly in the background.

Neither route is better in the abstract. The question is which one matches the machine and the policy it lives under.

macOS version requirements decide this more often than features

Menu bar managers sit close to the operating system, and the way macOS handles menu bar items has changed across recent releases. That pushes projects to raise their minimum version.

Ice targets a newer macOS baseline than Hidden Bar does. For anyone still running an older release on hardware that works fine otherwise, that is often the end of the comparison: one of the two simply will not install. This is also the detail most likely to be out of date in any article, including this one, so the reliable move is to open the current listing and read the requirement line right before installing rather than trusting a number written months earlier.

The same caution applies in the other direction. After a major macOS upgrade, a menu bar manager is one of the first utilities to behave oddly, because the thing it manipulates was changed underneath it. Checking whether a build has been released for the new OS version, before upgrading rather than after, avoids a week of confusion.

What happens after an icon is hidden

The daily experience is shaped by one question: when a hidden icon is needed, how many steps does it take to reach it?

Hidden Bar keeps this simple. Clicking the divider expands the bar, the hidden icons reappear in their normal positions, and the target gets clicked from there. Clicking again, or waiting out a timer that can be configured, collapses it. There is very little to learn, and the behavior is easy to predict.

Ice offers the expand-and-collapse path as well, and adds another one: hidden items can be presented in a separate strip, so the item can be reached without the menu bar itself widening back out. The visual state of the screen stays put while the click still lands.

Whether a hidden icon can be reached without expanding the bar is the axis worth deciding on before installing anything. If the plan is to hide only things touched once a month, expanding is a non-issue and the simpler behavior wins. If a frequently used icon is going into the hidden group, that extra expand-and-collapse cycle repeats several times a day, and the difference compounds.

Appearance controls

Ice includes settings that change how the menu bar itself looks, covering things like tint and edge treatment. These are used when a wallpaper makes the bar hard to read, or when the area around the notch should look cleaner than the default.

Hidden Bar does not go in this direction. It stays focused on hiding.

This difference reverses depending on who is reading. For someone who wants the bar to match a specific desktop, appearance settings are a reason to choose. For someone who wants fewer settings to think about, their absence is a reason to choose. It is a preference about how much time to spend configuring, not a quality gap.

Maintenance, and who answers when something breaks

Choosing a free open source utility carries a shared condition: there is no commitment that development continues. macOS gets a significant update roughly every year, and utilities that hook into the menu bar feel those updates directly.

The useful signals are public. Look at the date of the most recent release, whether the listing mentions support for the current macOS version, and how quickly reported issues get a response. All of that is visible on the project pages before installing, and it tells more about the next twelve months than any feature list does.

Support works differently too. With an open source project, questions go to a community space and answers arrive when someone has time. That is a reasonable trade for a free tool. For a utility that gets used every working day, it is fair to also price the paid options, comparing them not on features but on whether there is a support channel and a maintenance commitment behind them. Free has a real cost when something stops working during a deadline.

Deciding what to hide and what to keep

The decision that matters more than the app choice is which icons go behind the divider. A useful test is not how often an icon gets clicked. It is whether seeing it carries information.

Keep visible the items whose changing state is the point:

• battery or power state
• network connection status
• the clock
• the indicator that a microphone or camera is in use
• the indicator that a recording or screen share is running

Move behind the divider the items whose state does not need watching:

• background apps that only check for updates
• cloud storage sync indicators, when a stalled sync is not a daily concern
• launchers and clipboard tools that respond to a keyboard shortcut anyway
• management apps used only during one specific kind of work

Reserve the always-hidden group for things touched a few times a year. Writing this list down before opening the settings prevents the opposite failure, which is hiding so much that finding anything requires expanding the bar constantly.

One category deserves a separate decision: icons that are only relevant during a specific kind of work. A design suite manager matters while designing and is noise the rest of the week. A container tool matters during development and not during a call. These are the items where the answer changes by context rather than being fixed, and the practical approach is to hide them by default and accept the expand step on the days they are needed, rather than keeping them visible for the occasional day they earn their space.

Setup steps people skip

Three things account for most reports that a menu bar manager is not doing anything.

The first is permissions. Because these apps manipulate menu bar items, macOS may require an explicit grant under System Settings, and the app sometimes needs a relaunch immediately after that grant to pick it up.

The second is launching at login. If the manager itself does not start with the session, the menu bar returns to its crowded state after every restart, which reads as the app failing rather than as a setting that was never enabled.

The third is the Command-drag pass. Icons to the left of the divider are the hidden ones, and putting them there is manual. This is the step that turns an installed app into a tidy menu bar, and it is the one most often left undone.

What to change first

Start by writing the keep list and the hide list, because that work carries over to whichever app ends up installed. Then check the macOS requirement on both listings, since that often narrows the choice to one. If the hide list contains anything used daily, weigh how the tool behaves when a hidden icon needs a click, and compare that against the paid options as well, including what Koffret documents about reaching hidden items and how it lines up on pricing.