MacsyZones: a FancyZones style window tiler for macOS

Windows on macOS do not tile, and that is the gap

MacOS does not ship with a window tiling manager in the sense that Linux desktops or Windows power toys provide, and that is the gap MacsyZones addresses. The project description puts it plainly: make your workflow more efficient, organize your windows with ease.

The README calls MacsyZones a FancyZones equivalent for macOS, and that comparison is the most useful description of the product available. FancyZones is a Microsoft PowerToys utility that lets you define a layout on a large monitor, divide it into sections, and drop windows into those sections. MacsyZones reproduces that model: it allows you to create layouts and sections in your layouts as you want and fit your windows into sections with ease.

That vocabulary, layouts and sections, is the whole data model, and it is worth understanding before installing anything. A layout is the arrangement you define for a screen, a section is a region within that layout, and windows are assigned to sections. The freedom the README claims, that you can create layouts and sections in your layouts as you want, is the freedom that makes the tool useful on a mixed monitor setup, where a laptop screen and an external display need different arrangements.

The audience is therefore specific: someone on macOS with a big display and several applications open at once, who wants a repeatable arrangement rather than dragging windows into place every time. The macOS-specific audience matters, because the implementation is a Swift application built as an Xcode project rather than a cross-platform tool.

Installing with Homebrew or from the website

There are two routes and both are short.

The README documents a Homebrew cask:

brew install --cask macsyzones

Or you visit macsyzones.com to download MacsyZones, which is where the releases are also linked from through the GitHub release badge at the top of the README.

That is the entire installation story, and it is worth contrasting with the way a window manager is usually obtained on Linux, where you would add a repository, install a package, and configure the compositor. MacsyZones installs as an ordinary macOS application, and the repository top level confirms the shape: a MacsyZones.xcodeproj/ directory, a MacsyZones/ source directory, MacsyZones-Bridging-Header.h, media/ for the screenshots used in the README, and scripts/.

The Xcode project is the giveaway. This is a native macOS application, built and signed the way an App Store or direct-download macOS utility is, with a bridging header for the Objective-C interop it needs. The user experience is a normal app with a settings window, not a service you run and configure in a dotfile.

The README also points at a Discord server for the community, and mentions SECURITY.md and a Code of Conduct in the repository, which is the usual accompaniment to an application that asks for system-level permissions.

Free and Pro, and what the money pays for

The README has a section headed Buy to support me, and it is short: you can buy MacsyZones Pro, described as the same MacsyZones just Pro, to support the author, and the purchase is made through the MacsyZones website.

That sentence carries the important information and also the ambiguity. The wording says the Pro edition is the same application with the label changed, which tells you the base app is fully functional and that the paid tier exists as a way to fund the work rather than as a set of features the free version withholds. The README does not enumerate a feature matrix between the two, so anyone who needs to know exactly what the free build omits has to compare them directly or read the website.

The funding model is also broader than the Pro purchase. There are Patreon and GitHub Sponsors links, and a table of cryptocurrency addresses for BTC, ETH and USDT and USDC, and XMR, with a note that donating USDT or USDC is preferred. The same section promotes a second application, QuakeNotch, described as an agentic AI quake terminal app, sold on its own website.

For an evaluator, the pattern to note is that this is a solo-developer project where the commercial product and the open repository are the same codebase. That has a direct consequence for the licence, which is the next thing to look at.

GPL-3.0 on a product that is also sold

The licence section names the copyright holder and year, then states the GNU General Public License v3.

The README paraphrases the terms in a way that is worth reading closely: you may copy, distribute and modify the software as long as you track changes and dates in source files, and any modifications to or software including GPL-licensed code must also be made available under the GPL along with build and install instructions.

That is the standard GPL-3.0 formulation, and it has a consequence specific to this kind of project. If you take the source, modify it, and distribute it, you must publish your modified version under the same licence and provide the build and install instructions. For a MacsyZones Pro purchase that has been paid for and closed source, and for anyone building a modified variant they intend to keep to themselves, that is a real constraint, and it is different from the terms of a proprietary window manager.

The repository licence field says GPL-3.0, and the LICENSE file at the root of the tree is the authoritative text. Note that GPL-3.0 also carries the patent grant and the anti-tivoisation provisions, which matter if you intend to distribute a build to a group of users rather than to run it yourself.

The releases are tagged normally. The recent ones are v3.1.1 on 2026-09-15, v3.1 on 2026-09-14 and v3.0.4 on 2026-05-31, and each release note in the list mentions a new seamless way to snap. The repository is not archived and the last push was on 2026-09-15, so the 3.1 line is current.

What the repository shows and what it does not

The top level of the tree is small and mostly application source: .github/, .gitignore, CODE_OF_CONDUCT.md, CONTRIBUTING.md, LICENSE, MacsyZones-Bridging-Header.h, MacsyZones.xcodeproj/, MacsyZones/, README.md, SECURITY.md, media/ and scripts/.

Two observations follow. First, there is no package manifest of the kind an npm or Cargo project would have, and no configuration schema, because there is nothing to install beyond the app. The scripts/ directory is the interesting one: it holds the automation that turns a commit into a signed build and a release, and that automation is what makes the Homebrew cask and the website download possible.

Second, the README does not describe the configuration model in detail. It says you can create layouts and sections in your layouts as you want, and it shows a screenshot of the settings window, but it does not enumerate the options, the keyboard shortcuts, the display detection behaviour, or how a window is assigned to a section. The screenshot in the README is the primary documentation for the settings, and the Discord server is where the community answers practical questions.

The README also has a MacsyZones in action section with two hosted video assets, which is the closest thing to a demonstration of the snapping behaviour.

So the evaluation has to happen with the application in hand rather than from the repository alone. For a tool whose entire value is how it feels while you drag a window onto a multi-monitor layout, that is a reasonable requirement, but it does mean you should install the free build and try it before deciding.

Editorial conclusion

MacsyZones suits a macOS user who arranges windows on a large display and wants the layout and section model that FancyZones offers on Windows, and who is comfortable installing a third-party window manager that will be asking for accessibility permissions. It does not suit a team that needs a commercial licence file for the base product, and it does not suit a user who expects the same behaviour on Linux or Windows from this repository. Before adopting, install it with brew install --cask macsyzones, compare the free build against the Pro tier for the features you actually need, and read the LICENSE file, since the GPL terms require modified versions to stay GPL and to carry build and install instructions.

Frequently asked questions

Official sources

1. License: GPL-3.0
2. Project website
3. README
4. Releases
5. rohanrhu/MacsyZones on GitHub