SwiftBar

SwiftBar turns executable scripts into scheduled menus and actions in the macOS menu bar. It suits people who want to build or adapt small, personal tools and are comfortable working with plugins. Its strongest case is flexibility at no cost; its main trade-offs are a script-based setup and a macOS 12 minimum.

Overview

SwiftBar runs plugins from a local folder and turns their standard output into menu items. Scripts can be written in Bash, Python, Ruby, Swift, or JavaScript, so users can work in a familiar language rather than learn a dedicated plugin system. The constraint is that each plugin must be an executable script that follows SwiftBar’s required output format; this is not a visual menu editor for people who want to configure everything through ordinary settings.

Menus can include icons, colors, dropdowns, submenus, and click actions. Items can also be rearranged, grouped, and customized. Those options make SwiftBar adaptable to different workflows, though what appears in the menu ultimately depends on the plugins a user creates or installs.

Key features

Scheduled scripts and actions

Users set when plugins run, using intervals in filenames or cron syntax in metadata. Menu items can open URLs, run shell scripts, refresh plugins, or trigger assigned keyboard shortcuts. This is useful when a menu item should do more than display information, but it rewards users willing to manage executable scripts and their schedules.

Plugin sources and compatibility

A repository is accessible from the Get Plugins menu, and SwiftBar’s product page describes hundreds of community-created plugins. It also adopts the BitBar plugin API, allowing existing BitBar and xbar plugins to run. That compatibility can reduce the work of building a collection from scratch, although plugins still need to meet SwiftBar’s output requirements.

Shortcuts and packaged plugins

SwiftBar supports plugins made with the macOS Shortcuts app and provides a user interface for setting their refresh schedule. Packaged plugins can live in.swiftbar directories with a main script and optional supporting files, which gives a plugin a way to keep related assets together.

Pricing

SwiftBar’s Free plan costs nothing and includes open-source software for running plugins from a local folder on macOS 12 or later. There is no paid tier or trial to weigh against that plan. It is a strong fit for individuals who can supply or adapt their own plugins; the cost of entry is time spent working with scripts rather than a subscription.

Platforms

SwiftBar runs on macOS Monterey (12) and later. The latest stable release, version 2.1.1, requires macOS 12 or later, so it is not a fit for Macs that cannot run that minimum. Installation is available as a direct download from GitHub Releases or through Homebrew. The project is open source under the MIT license and is described by its maker, Ameba, as an open-source project.

Who it's for

SwiftBar is best for Mac users who want information and actions surfaced in a configurable menu and are comfortable creating or adapting executable plugins. It is particularly compelling for people who already use Bash, Python, Ruby, Swift, JavaScript, or Shortcuts, and for those with BitBar or xbar plugins to reuse. People seeking a conventional icon organizer with no script or plugin setup should look elsewhere.

Pros and cons

Flexible menu presentation: icons, colors, dropdowns, submenus, grouping, rearrangement, and custom items let users shape the menu around their needs.

Useful plugin reach: the repository, community plugins, and BitBar/xbar compatibility offer a starting point beyond writing every plugin yourself.

Actions as well as display: plugins can open URLs, run shell scripts, refresh, and use keyboard shortcuts, making menu items useful controls as well as readouts.

Script knowledge is the price of flexibility: plugins must be executable and produce output in SwiftBar’s required format, which adds setup and maintenance work.

macOS 12 floor: Macs that cannot run Monterey or later are excluded.

Alternatives

For a broader set of menu-bar customization options, see the Menu Bar Customization Software directory.

Overhang is another free macOS option; choose it if its macOS 14 Sonoma-or-later requirement and universal Apple silicon and Intel binary suit your Mac.

Vanilla is a freemium macOS option whose free plan hides menu-bar icons; pick it if hiding icons is the need, rather than script-generated menus.

iBar-Menubar is a freemium macOS alternative with a free download and in-app purchases; consider it if that model suits your preference.

Lloyd is a free, MIT-licensed macOS menu-bar utility; it is an option for readers who want a different free utility.

Octobar offers a free plan capped at five active modules and a 4.99 USD one-time Pro plan for unlimited active modules; choose it if a module-based model fits better than script plugins.

Pelmet is a free, open-source alternative that requires macOS 27; consider it only if that OS requirement works for you.

xbar is a free, open-source, MIT-licensed option; it is worth considering if you prefer that project instead of SwiftBar’s BitBar-compatible implementation.

Bartender is a paid option with a 19.99 USD yearly Pro subscription and a 24.99 USD one-time Bartender 7 plan; choose it if you want a paid alternative rather than a free, script-driven tool.

Verdict

Choose SwiftBar if you want a free, open-source way to turn scripts into customizable macOS menu-bar information and actions, especially if you can reuse existing BitBar or xbar plugins. Look elsewhere if you want a purely visual organizer, cannot meet the macOS 12 minimum, or do not want to manage executable plugins and their output format.