A Blender-style pie menu for every app on your Mac

If you've spent serious time in Blender, you already know what pie menus feel like. You hit Z and the shade-mode pie pops up under your cursor. You flick north for wireframe, east for solid, south for material, west for rendered. You never read the labels. Your hand knows the directions before your eyes do.

That feeling — spatial selection faster than linear reading — is the entire pitch for radial menus. Blender figured it out first because it had to. 3D work involves hundreds of discrete operations, and a menu bar tall enough to list them all would reach to the ceiling. Pie menus turned the flat list into a directional gesture, and Blender users got noticeably faster.

The gap, if you work on a Mac: Blender's pie menus stop at Blender's window edge. The moment you Cmd+Tab into Finder, your browser, or Substance, you're back to linear menus, Cmd+Tab cycling, and Spotlight. The speed advantage you just spent two weeks building inside Blender evaporates the second you leave it.

Why Blender-style selection works

The reason pie menus feel fast isn't a trick. It's a real cognitive property. Linear menus force you to read each item, compare it to what you want, and target a narrow row of pixels. Pie menus turn the selection into a direction. Once you've used a particular pie a few times, the direction becomes reflexive, and the menu is almost invisible — you're not reading it anymore, you're just flicking.

Blender leans into this hard. The Tab key opens the mode pie, Z opens the shading pie, . opens the pivot pie. Each one has four or eight options, placed in consistent directions, with important items at the cardinal points. There's nothing special about the graphics — the speed comes from the shape of the interaction.

A system-wide radial menu gives you that same shape for everything else on your Mac. Not the tool-specific pies Blender ships with, but the equivalent gesture for "switch app," "open folder," "run script," "take a screenshot." The logic of "one hold, one flick, one release" is the same. Only the contents change.

What you lose vs Blender, honestly

A few things are worth naming up front, because Blender users notice them.

Blender's pie menus are contextual to Blender. The Z pie knows whether you're in edit mode or object mode and changes accordingly. A system-wide menu on macOS doesn't have that deep a view into the frontmost app — it can switch profiles when you switch apps, but it can't know whether you've got a vertex selected in Substance Painter.

Blender's pie menus are also scriptable in Python. You can write a custom pie that runs seven operators in sequence with your exact defaults. A system-wide menu on macOS isn't going to match that inside any single app. What it matches is the shape of the interaction, not the depth of the customization.

What you get instead: the same pie-menu reflex applied everywhere. Cmd+Tab becomes a flick. "Open Downloads" becomes a flick. "Launch reference viewer" becomes a flick. You trade deep integration with one app for a shallower but universal reach.

A 3D-workflow-adjacent profile

Here's what a useful menu looks like for someone whose day is Blender plus the apps that orbit it:

Eight wedges, two sub-menus, about fourteen distinct actions. None of them replace what you do inside Blender — Blender's own pies still handle the modeling, shading, and mode-switching. This layer handles everything between apps, which is where 3D workflows spend surprisingly more time than people expect.

How it feels after a week

The most Blender-native thing about a well-built system radial menu is the rhythm. Hold the trigger, flick, release. It matches the muscle memory you already have from Z, Tab, and .. There's no new timing to learn — the menu behaves like Blender's own pies because the underlying interaction is the same.

The part that feels new is the scope. You stop thinking of "switching to the reference viewer" as a separate conscious action. It becomes part of the same motor program as "change shading mode." Your hand doesn't care whether the action is inside Blender or outside it. Both are just directions.

This is the point where users tend to stop describing the menu as a launcher and start describing it as an interaction layer. Same way Blender users don't describe pie menus as a menu system — they just describe them as "how Blender works."

A few things to know

Trigger matters more than on other setups. Blender users already know the feel of hold-and-release pies. Don't map the system menu to something slow or ambiguous. A mouse side button or a short hotkey like Ctrl+Space feels right. A long combo does not.

Context profiles help, even without deep app integration. You can have one radial profile that's active when Blender is frontmost (3D-adjacent tools), another when a browser is frontmost (tabs, windows, bookmarks), another when Finder is frontmost (common folders, tags, archive actions). It's not as smart as Blender's mode-aware pies, but it's real context awareness, and it's enough for most workflows.

Eight wedges is the sweet spot, same as Blender. Blender's pies top out at eight cardinal directions for a reason — past that, the wedges get too narrow and selection gets imprecise. Resist the urge to cram twelve items into the top ring. Use sub-menus instead.

It doesn't replace Blender's own pies. Nothing at the OS level can. Keep Blender's internal pie menu addon enabled; use the system-wide menu for everything outside Blender's viewport. The two layers compose cleanly.