i3 for Mac: the tiling window manager, on macOS
i3 is an X11 tiling window manager for Linux and BSD, so it will not run on macOS. What i3's tree, layouts and plain text config map onto on a Mac.
By Chethan Kumar S N · Updated
i3 is the window manager a generation of Linux users learned first, and the one every “tiling on the Mac” conversation eventually circles back to. It is a hard no on macOS, in a way that is worth understanding before you spend an evening on a config file that has nothing to run in. The useful question is not whether i3 works here. It is which part of i3 you actually live in.
Why i3 cannot run on a Mac
i3’s own homepage describes it in one line: “i3 is a tiling window manager, completely written from scratch. The target platforms are GNU/Linux and BSD operating systems.” That is a technical statement, not a policy. i3 is an X11 window manager. X11, the X Window System, is the display stack it was built against, and macOS neither ships it nor lets anything take over the job of drawing windows.
There is a Wayland port, and it is not i3. sway says it is “a tiling Wayland compositor and a drop-in replacement for the i3 window manager for X11”, and its promise is that it “works with your existing i3 configuration and supports most of i3’s features”. So sway is where i3’s ideas went on modern Linux. It is still Linux. Wayland is the display server sway stands in for, and macOS has its own window server that no third party can replace.
On a Mac a window manager is an ordinary app, not a display server. The one lever it has is the Accessibility permission, which lets it ask the system to move and resize windows it does not own. Every window manager for Mac, Ribbon included, is that and nothing more.
The part of i3 people miss: the tree
Ask someone what they liked about i3 and they will usually say the keyboard. The real answer is the data structure. From i3’s own user guide:
i3 stores all information about the X11 outputs, workspaces and layout of the windows on them in a tree. The root node is the X11 root window, followed by the X11 outputs, then dock areas and a content container, then workspaces and finally the windows themselves.
That is why i3 does not feel like a grid splitter. The building block is a container. It either holds a window or holds other containers, and any container can be split again, in either direction, at any depth. Two terminals side by side, then a third below the right one, then all three tabbed into one frame. The shape belongs to the container you are in, not to the screen.
The four layouts, and the keys
Inside any container i3 offers four layouts, and its guide gives each one a short definition:
| Layout | i3’s own description | Toggle |
|---|---|---|
| splith / splitv | “Windows are sized so that every window gets an equal amount of space in the container” | Modifier-E toggles the direction |
| stacking | “Only the focused window in the container is displayed. You get a list of windows at the top of the container” | Modifier-S |
| tabbed | “The same principle as stacking, but the list of windows at the top is only a single line which is vertically split” | Modifier-W |
Modifier is Alt by default, and i3’s own note is that its default keys “differ by one key from the popular text editor vi”, because the layout is meant to need the least finger movement.
Two of those travel to a Mac, and one of them is already built in.
tabbed is the same idea as macOS window tabs. Apple’s command is Merge All Windows, and it gathers an app’s windows of the type you are working in into one window with a tab each. The differences are small but worth knowing: macOS tabs are per app, they only appear in apps that use the system’s tabbed window, and the tab list is a bar rather than i3’s single line. The detail, including the setting that decides whether a new document opens as a tab, is in how to merge windows on a Mac.
splith and the tiling half is the part macOS will not do. There is no tiling engine you configure once and forget, so people install one. AeroSpace is the closest to i3 in spirit, a tree of splits with its own fast workspaces and a small config file. yabai goes further and drives the layout from the command line. Amethyst is the gentlest of the three to set up. All are free and open source, and each one is worth reading about before you pick.
Workspaces, the bar and the launcher
Two more pieces of i3 are worth naming, because they are what make it feel like a whole desktop rather than a window trick.
Workspaces. i3’s guide calls them “an easy way to group a set of windows”: Modifier plus a number switches to one, Modifier-Shift plus a number sends the focused window there, and a workspace that does not exist yet is created the moment you ask for it. macOS has the same idea under a different name. Spaces. Each job gets its own desktop, an app can be assigned to a space so it always opens where it belongs, and Control with the left or right arrow key steps between them. Moving a window across is a drag: push it to the edge of the screen and hold, or drag it onto a space thumbnail in Mission Control. The rest is in how to organize windows on a Mac.
The bar and the launcher are where the analogy stops. i3’s status bar is drawn by a bar program and fed by a status program, its own docs list i3status and external bars as separate pieces to configure, and the launcher dmenu is a separate program again, opened with Modifier-D. They are programs i3 starts rather than settings inside one app, and the look of both is yours to build. That is the point rather than a gap: i3’s homepage lists as a goal being “modifiable by people who do know how to program”, and the whole genre grew out of assembling a desktop from parts. On macOS you are handed the parts instead.
Which half of i3 did you use?
This is the only question that decides what to install.
If what you miss is the tree of splits, the layouts that fill the screen so nothing overlaps and nothing keeps the width you gave it, go to AeroSpace or yabai. That is i3’s own tradition and they carry it further than anything else on a Mac.
If what you miss is columns and keyboard widths, if the i3 layout you actually lived in was two or three full-height windows with everything else tabbed behind them, then the closer neighbour is PaperWM and niri, and Ribbon. Every window gets a full-height column on a strip that runs past the edges of the screen. The column keeps the width you set it to, Control-Option with the arrow keys walks the strip and carries the focused window along, and nothing shrinks to make room. Tabs are the one i3 habit it does not replace, so keep using macOS tabs for that.
What you leave behind, and what you keep
Gone, with no workaround. The config file, first. An i3 config is a plain text file of commands, and there is no X server on a Mac to read it and no IPC socket to talk to. i3’s guide points at a socket under your runtime directory as the place third-party programs connect, and macOS offers nothing equivalent. The bar and the launcher do not come along either, because they were separate Linux programs to begin with, and neither does i3’s ability to save a layout and restore it in a new session.
Kept. The ideas. A desktop you drive from the keyboard, windows that do not shrink to make space, a per-app rule so each app opens the width it wants, and a way to script the rest. Ribbon keeps those, with a Settings window instead of a text file, ribbon:// URLs, a ribbon command-line tool and Raycast scripts for the automation you would otherwise wire through i3’s IPC.
Ribbon is $15, once, for up to 3 Macs, with a full refund within 10 days, and it runs on macOS 14 Sonoma and later on Apple silicon and Intel Macs.
Questions
Can I install i3 on macOS?
No. i3 is an X11 window manager. Its own homepage says the target platforms are GNU/Linux and BSD operating systems, and X11 is the display stack it was written against. macOS does not ship the X Window System and does not let anything take over the job of drawing windows, so there is no layer for i3 to sit in. The one lever a Mac app has is the Accessibility permission, which lets it ask the system to move and resize windows it does not own. Every window manager for Mac, Ribbon included, is that.
What is the closest thing to i3 on a Mac?
It depends which half of i3 you used. If you miss the tree of splits that fills the screen so nothing overlaps, AeroSpace is the closest, with yabai as the more scriptable option and Amethyst as the easiest to set up. If what you used was fewer, full-height columns with everything else tabbed behind them, then a scrolling window manager such as Ribbon is closer. Start from i3's own tradition if you want a grid, from PaperWM and niri if you want columns.
What are i3's layouts?
Four. splith and splitv size windows so every one gets an equal share of the container, horizontally or vertically. stacking shows only the focused window plus a list of the others at the top. tabbed is the same idea with the list reduced to a single vertically split line. In i3's default config, Modifier-E toggles between splith and splitv, Modifier-S switches to stacking and Modifier-W switches to tabbed.
Is i3 Wayland or X11?
i3 is X11 only. The Wayland equivalent is sway, which describes itself as a tiling Wayland compositor and a drop-in replacement for the i3 window manager for X11, and it works with your existing i3 configuration. So the ideas moved to Wayland under a different name. Both are still Linux display stacks, and macOS has its own window server that no third party can replace, so neither runs on a Mac.
Can I use my i3 config file on a Mac?
No. An i3 config is a plain text file of commands that i3 reads, and there is no X server on macOS to run i3 and no IPC socket for a script to talk to. The guide points at a socket under your runtime directory as the place third-party programs connect. What does carry over is the ideas behind the config: per-app rules, keyboard control and a way to script the window manager. Ribbon keeps those in a Settings window you click through, plus ribbon:// URLs, a ribbon command-line tool and Raycast scripts.
Ready? Buy Ribbon for $15, or read all the guides.