Pie menus explained: why Blender, Maya, and games all use them

A pie menu is a circular menu. You trigger it — usually by holding a key or button — and a ring of options appears around your cursor. Each option occupies a wedge. You flick the cursor toward the wedge you want, release, and the action runs.

That's it. That's the whole idea. And yet every professional 3D application on Earth uses them, every major open-world video game ships one, and mainstream macOS has somehow managed to ignore them for forty years.

Here's why they exist, why they're faster, and why they keep showing up in the software that expert users reach for.

Where they came from

The pie menu was formalized at the University of Toronto in the late 1980s and early 1990s. Don Hopkins's research at the University of Maryland built early working versions, and Jack Callahan, Don Hopkins, Mark Weiser, and Ben Shneiderman published an influential 1988 paper comparing pie menus to linear menus.

The interaction design was then pushed further by Gordon Kurtenbach at the University of Toronto. His 1993 PhD thesis, The Design and Evaluation of Marking Menus, is the canonical text on the subject. Kurtenbach showed not just that radial menus were faster than linear ones in a controlled study, but that trained users could eventually stop looking at the menu entirely and perform the gesture from muscle memory — what he called "expert mode." He later took that work to Alias|Wavefront, which became Autodesk Maya, and marking menus have been baked into Maya ever since.

So the research is thirty-plus years old. It's not speculative. It's settled.

Why they're actually faster

The physics argument rests on Fitts's Law, which says the time to acquire a target is proportional to the distance to the target and inversely proportional to its size. In a linear menu — the kind macOS uses in every app — items further down the list are further from your cursor and therefore take longer to reach. The seventh item in a dropdown is always slower than the first.

In a pie menu, every item is the same distance from your starting point. The cursor is in the middle. Each wedge radiates outward by the same amount. That means every option has identical access time.

There's a second effect: direction is a stronger memory cue than position in a list. "North-east" is easier to recall than "the fourth item down." After a few repetitions, you stop reading the menu. You just flick.

Kurtenbach's experiments measured this. Trained users completing tasks with marking menus were consistently faster than users with equivalent linear menus, and the advantage grew with familiarity. Novices were already at parity; experts pulled ahead.

Where you've already seen them

Autodesk Maya has had marking menus since the 1990s. Hold space, flick toward a tool, release. Working 3D artists use dozens of them a day without looking.

Blender added pie menus as a first-class feature around the 2.7x era. Press Tab in Edit Mode for the shape-selection pie. Press N for the viewport menu. Most Blender power users customize these aggressively.

GTA V and Red Dead Redemption 2 use weapon wheels. Hold L1, time slows, flick toward a gun, release. Twenty million players have internalized the gesture without ever being taught what a radial menu is.

Destiny 2 uses a ghost wheel for sub-classes and an emote wheel for social actions. Same pattern.

Discord on mobile uses a reaction pie menu when you long-press a message.

The old Google Android gesture keyboard used pie menus for accented characters before Google retired it.

There's a pattern here. Pie menus show up wherever interaction speed matters more than menu chrome — games, creative tools, mobile contexts with limited screen real estate. They show up specifically where the UI is designed by people who care about how the hand feels, not just how the screen looks.

Why they never made it to mainstream desktop UIs

So if pie menus are measurably faster, why doesn't the macOS Finder use them? Why is the Windows Start menu still a list?

The short answer is cultural inertia. The dropdown menu was a decision made at Xerox PARC in the 1970s, inherited by the original Macintosh in 1984, and then locked in place by every operating system that copied the Mac's paradigm. By the time Kurtenbach's research was published in 1993, "File / Edit / View / Window / Help" had already been shipping for a decade. Users expected it. Developers built against it. The APIs were written for it.

There's also a discoverability argument. A pie menu is empty until you trigger it — you can't see its contents at rest. For a system that expects a casual, first-day-of-use user to find everything visually, that's a real problem. Linear menus self-describe by sitting in the menu bar.

And finally, there's input. Pie menus work best with a mouse or stylus where flick-and-release is cheap. On a touchscreen phone, pie menus are awkward (your thumb obscures the menu). On a keyboard alone, they don't apply.

None of those reasons are arguments against pie menus for power users. They're arguments for not making them the default menu type for every user. Which is correct. But it also means that for the last thirty years, anyone who wanted a pie menu on the desktop has had to go find one themselves.

Why they're finally arriving on macOS

A few things have changed in the last couple of years.

macOS added enough accessibility APIs that third-party apps can reliably draw overlays, capture global hotkeys, and interact with the frontmost app. The surface area for a good radial menu app now exists, where it didn't fully ten years ago.

Gamers who grew up on weapon wheels are now senior engineers and designers. The gesture isn't foreign — it's the one they used to swap from a sniper rifle to a shotgun. Asking them to use it to swap from Figma to Xcode is a short step.

And the productivity tool market has matured past "launcher with a text field." Raycast and Alfred raised the ceiling on what a launcher is allowed to be. Pie menus are the obvious next idea for the category — and they're the one pattern that expert users in every adjacent field have been using for decades.

We make Swik, which is a radial menu for macOS. But the broader point isn't about any one app. If you've ever used Maya, Blender, or GTA, you already know the gesture. The only question is whether you want it for the thing you do all day.