yabai vs AeroSpace: Which Mac Tiling Window Manager Fits You? (2026)

yabai extends the macOS window manager and can control native Spaces. AeroSpace ignores native Spaces and runs its own i3-style workspaces. Here is how they differ on SIP, configuration, Spaces, and day-to-day upkeep.

yabai and AeroSpace both tile windows on a Mac from the keyboard, and both are free and MIT-licensed. They disagree on one basic question: should a tiling window manager work with Apple's native Spaces, or replace them?

yabai works with them. AeroSpace replaces them. Most of the practical differences follow from that choice.

TL;DR

Choose AeroSpace if you want an i3-style tree, fast workspace switching, one TOML file, and a setup that never asks you to touch System Integrity Protection. Choose yabai if you want to keep Apple's native Spaces and Mission Control, and you want to script windows, Spaces, and displays in detail. Neither tool saves a project and reopens it later: both arrange the windows that are already open.

Comparison at a glance

yabai AeroSpace
Tiling model Binary space partitioning[1] i3-like tree[3]
Workspaces Native macOS Spaces[1] Its own virtual workspaces; native Spaces are ignored[3][4]
SIP Optional. Partially disabling it unlocks a documented list of features[2] Never required[3]
Configuration yabairc, a shell script of yabai -m commands[5] ~/.aerospace.toml[4]
Hotkeys Not built in. skhd or another tool[1] Declared in the config, with binding modes[4]
Config GUI None None, by design[3]
macOS support Big Sur 11+ on Intel, Monterey 12+ on Apple Silicon, through Tahoe 26[1] Binary runs on macOS 13+[3]

Native Spaces or virtual workspaces

This is the difference that decides most people.

yabai describes itself as "an extension to the built-in window manager of macOS."[1] Your Spaces are still Apple's Spaces. Mission Control still shows them. Its README lists disabling the Space-switching animation and creating Spaces past the limit of 16 among its features.[1]

AeroSpace takes the opposite view. Its guide lists what it sees as the problems with native Spaces: the switching animation cannot be turned off, there is a limit on how many you can have, and Apple offers no public API to create, delete, reorder, or switch them.[4] So AeroSpace builds its own. When a workspace is not active, its windows are placed outside the visible area of the screen, and they come back when you switch to it.[4]

The guide also states the intended workflow: keep one macOS Space per monitor and stop interacting with native Spaces.[4] The README is blunt about it. AeroSpace "doesn't acknowledge the existence of macOS Spaces."[3]

What that means in practice:

  • If you already rely on Mission Control, or on apps assigned to specific desktops, yabai keeps that model and AeroSpace asks you to give it up.
  • If you find native Space switching slow and want numbered workspaces that switch instantly, AeroSpace was designed for exactly that.

System Integrity Protection

People often summarize this as "yabai needs SIP off, AeroSpace does not." The second half is accurate. The first half is too broad.

AeroSpace states it "will never require you to disable SIP." It says it uses the public accessibility API plus a single private call to read a window's ID.[3]

yabai tiles windows with SIP left on. Its README lists SIP as an optional caveat: you can partially disable it so yabai can inject a scripting addition into Dock.app.[1] The yabai wiki lists what that unlocks:[2]

  • moving, swapping, creating, and destroying Spaces
  • removing window shadows
  • window transparency
  • window animations
  • scratchpad windows
  • window layers (topmost, or on the desktop)
  • sticky windows
  • picture-in-picture for any window

If none of those matter to you, you can run yabai on a stock Mac. If your reason for choosing yabai is scripted control of Spaces, read that list first, because Space creation and movement are on it. yabai's own disclaimer makes no recommendation about whether you should disable SIP.[1]

Configuration and hotkeys

yabai has no config format of its own. The configuration file is a shell script that runs before yabai starts, and it is made of the same yabai -m commands you can run from a terminal. Every option can also be changed at runtime.[5] Hotkeys are a separate job: the README points to skhd or any other tool you prefer.[1]

AeroSpace uses a single TOML file. Key bindings live in the same file, and the config is the source of truth for them. It also supports binding modes, borrowed from i3, so one key can switch you into a "resize" mode with its own bindings.[4]

Neither has a settings window. AeroSpace says it will never provide one.[3]

If you want one dotfile and one tool, AeroSpace is the shorter path. If you want a window manager you can drive from any script, yabai's model suits that.

Multiple monitors

yabai requires "Displays have separate Spaces" to be turned on in System Settings.[1] After that, each display has its own native Spaces, the way macOS normally works.

AeroSpace shares one pool of workspaces across all monitors. Each monitor shows one workspace at a time, two monitors cannot show the same workspace, and every workspace has a monitor assigned to it.[4] This is the i3 model, and it will feel familiar if you come from Linux.

Maturity and upkeep

AeroSpace calls itself a public beta that can be used as a daily driver, and warns that breaking changes will happen until 1.0.[3] It is also not notarized, which the README explains at some length.[3] Two things it does not do yet, according to the same README: sticky windows and macOS native tabs.[3]

yabai supports a wider range of macOS versions, including Tahoe 26.[1] Its caveats are different: several System Settings options have to be set a certain way, and windows that use native macOS tabs, such as Terminal and Finder, do not behave correctly when you create tabs.[1]

Which one should you pick?

Pick AeroSpace if:

  • you want i3-style workspaces and do not mind leaving native Spaces behind
  • you will not disable SIP under any circumstances
  • you prefer one TOML file with bindings included

Pick yabai if:

  • you want to keep native Spaces and Mission Control
  • you want to script windows, Spaces, and displays from the shell
  • you are comfortable pairing it with a hotkey tool, and possibly with partially disabling SIP for the features listed above

If you are still weighing other options, seven AeroSpace alternatives covers Amethyst, Rectangle, Moom, and native macOS tiling as well.

What neither one does

Both tools manage windows that are already open. Neither README describes a way to save "the client project" as a set of apps, a browser profile, URLs, and terminal environment, and then bring it back after a restart.

That is a different job. ShiftPlus does that job and is not a tiler: it captures a named workspace and restores the apps, window arrangement, native Space placement, and browser profile with one hotkey. Some people run a tiler for live window behavior and a workspace manager for reopening a project. For how the Space-focused tools differ, see macOS Spaces managers compared.

FAQ

Does yabai work without disabling SIP?

Yes, for tiling. The yabai wiki lists the features that need SIP partially disabled, including moving, swapping, creating, and destroying Spaces, window transparency and animations, scratchpad windows, and sticky windows.[2]

Does AeroSpace use macOS Spaces?

No. AeroSpace emulates its own workspaces and hides the windows of inactive workspaces outside the visible screen area. Its guide recommends keeping a single macOS Space per monitor.[4]

Is AeroSpace stable enough for daily use?

Its README says it can be used as a daily driver while in public beta, and that breaking changes should be expected until version 1.0.[3]

Do I need skhd with AeroSpace?

No. AeroSpace reads key bindings from its own config file.[4] yabai does not define hotkeys itself, so it is usually paired with skhd or a similar tool.[1]

Sources

[1] https://github.com/koekeishiya/yabai — yabai README

[2] https://github.com/koekeishiya/yabai/wiki/Disabling-System-Integrity-Protection — yabai: Disabling System Integrity Protection

[3] https://github.com/nikitabobko/AeroSpace — AeroSpace README

[4] https://nikitabobko.github.io/AeroSpace/guide — AeroSpace Guide

[5] https://github.com/koekeishiya/yabai/wiki/Configuration — yabai: Configuration