StrokeIt for Mac: Mouse Gestures After Switching from Windows
StrokeIt defined mouse gestures on Windows for over a decade — 80 gestures, 140 KB, free. It never came to macOS. Here is what exists instead, and how to replicate the same workflow on your Mac.
On this page
- What StrokeIt was — and why it still matters
- StrokeIt and StrokesPlus are different apps
- Why StrokeIt never came to macOS
- What real users say about the gap
- What exists on macOS for ex-StrokeIt users
- Curflow for StrokeIt users
- Comparison: StrokeIt vs Curflow
- Mapping your StrokeIt setup to macOS
- For the user who hasn't thought about StrokeIt in years
- Frequently asked questions
- Is StrokeIt available for macOS?
- Are StrokeIt and StrokesPlus the same thing?
- Can I run StrokeIt on macOS with Wine or a virtual machine?
- What is the best StrokeIt alternative on Mac?
- Does Curflow work with an external mouse?
- Does it work on Apple Silicon?
StrokeIt — the mouse gesture app that defined an era on Windows — has no Mac version and hasn’t been meaningfully updated since the Windows 7 era. If you switched to macOS and miss drawing gestures with your mouse, Curflow is the closest alternative: the same hold-and-draw model, per-app context, intent-based recognition, and a setup that takes under two minutes.
You probably found this page the same way most StrokeIt users find it: you got a Mac, searched for StrokeIt, discovered it doesn’t exist for macOS, and started looking for what does. That search is common enough that Reddit threads about it appear regularly in r/macapps and r/mac.
What StrokeIt was — and why it still matters
StrokeIt was written by Jeff Doozan in the early 2000s and became the de facto mouse gesture tool on Windows. Not because it was the only option — but because it got the core interaction so right that alternatives felt unnecessary.
The numbers tell part of the story: 80+ predefined gestures, an installer of 140 KB (the recognition engine itself was 15 KB), and it was free for personal use. On a machine from 2003, StrokeIt consumed between 90 KB and 300 KB of RAM. It was essentially invisible.
But the real reason people still search for it two decades later is the interaction model. You held the right mouse button, drew a shape, and something happened. The gesture was the interface. No menus, no keyboard, no visual chrome. You thought about closing a tab, your hand moved, the tab closed. After a week it felt like the computer was reading your mind.
That feeling — of the tool disappearing into the workflow — is what made StrokeIt users loyal for life. It’s also what makes switching to a Mac without it so disorienting.
StrokeIt and StrokesPlus are different apps
This comes up constantly in forums: StrokeIt and StrokesPlus are not the same program. They were made by different developers, use different recognition engines, and have different feature sets.
- StrokeIt (tcbmi.com, Jeff Doozan): The original. Free for personal use. 80+ gestures. Lua scripting in the Pro version. Last meaningful update targeted Windows 7. The installer weighs 140 KB.
- StrokesPlus (strokesplus.net): A separate project with a different recognition approach and its own plugin architecture. Also Windows-only. Also no Mac version.
Both are mentioned in the same conversations because they solve the same problem on the same platform. But if you’re looking specifically for StrokeIt’s feel — the minimalist, no-config, just-works experience — that’s the one Curflow targets. We covered StrokesPlus in a separate post if that’s the tool you used.
Why StrokeIt never came to macOS
The short answer: it was built on Windows APIs that have no macOS equivalent, and development effectively stopped before Apple Silicon or even modern macOS security requirements existed.
The longer answer: global mouse input interception on macOS requires Accessibility API permissions — a fundamentally different security model from what StrokeIt was designed around. On Windows, a program could hook into mouse events relatively freely. On macOS, the user must explicitly grant that permission, and the system gates it behind specific entitlements introduced in macOS 10.14 Mojave.
A port wouldn’t just be a recompile. It would be a ground-up rewrite targeting a different operating system philosophy. Given that StrokeIt’s development slowed to a stop years ago, that rewrite was never going to happen.
What real users say about the gap
The “I switched to Mac and miss mouse gestures” thread is a recurring pattern. Three comments from recent Reddit discussions capture the pain point:
“Long-time XGestures user here. Just moved to macOS for work. The lack of mouse gestures is killing me.” — u/Guilty_Marketing_797, r/macapps
“Is it like XGestures? I used that for years on Windows.” — u/AlaskaInWinter, responding to a Curflow post
“Many years ago I was using something like Curflow… But I think it was on Windows.” — u/localToglobali, r/macapps
Three different users, three different threads, the same experience: they built muscle memory around mouse gestures on Windows, and macOS offers nothing equivalent out of the box. We wrote about this transition in detail — the muscle memory gap, why it’s harder than it sounds, and what actually helps.
What exists on macOS for ex-StrokeIt users
The Mac ecosystem has automation tools, but most aren’t designed for the hold-and-draw gesture model StrokeIt users expect.
BetterTouchTool supports cursor gestures but approaches them from a power-user philosophy: you define exact paths, speeds, and activation zones. Maximum flexibility, significant configuration time. We compared it to Curflow in detail.
Native macOS trackpad gestures are excellent — but only for trackpad users. If you use an external mouse, which is the StrokeIt demographic, the system provides nothing.
For a deeper breakdown of the macOS gesture landscape, see our comparison of browser vs system-level gestures on Mac.
Curflow for StrokeIt users
Curflow was not designed as a StrokeIt replacement. It was designed as a native macOS gesture tool that starts from the same interaction question: how do you trigger frequent actions without leaving your workflow?
The answer is the same one StrokeIt gave: hold a button, draw a shape, the action fires. No menus. No keyboard. No visual interruption.
Where Curflow differs from the original StrokeIt model:
Intent-based recognition. StrokeIt recognized gestures by matching drawn paths against stored templates. If your gesture deviated too much from the template, it failed. Curflow reads the direction of your movement and absorbs imprecision — the gesture works even if your hand isn’t steady. This matters because procedural memory builds faster when the system tolerates natural variation — you learn the direction, not the exact shape.
Per-app context from day one. The same gesture closes a tab in Safari, closes a window in Finder, and minimizes in VS Code. StrokeIt had application-specific actions too, but they required manual configuration. Curflow ships with preset flows that adapt to the active app automatically.
Built for the hardware you’re using. Universal Binary — runs natively on Apple Silicon (M1 through M4) and Intel Macs. No Electron, no Rosetta, no compatibility layers. Less than 10 MB. Battery impact is negligible.
First working gesture in under two minutes. StrokeIt was easy to configure too — that was its strength. Curflow preserves that philosophy: no configuration wall before something works.
Comparison: StrokeIt vs Curflow
| StrokeIt | Curflow | |
|---|---|---|
| Platform | Windows (95–Win7 era) | macOS (Apple Silicon + Intel) |
| Mouse gestures | 80+ predefined | 8 directions + shapes (customizable) |
| Recognition model | Path template matching | Intent-based (direction, tolerant) |
| Per-app context | Yes (manual config) | Yes (preset + custom) |
| Scripting | Lua (Pro version) | Built-in action library |
| Size | 140 KB installer | Under 10 MB |
| Price | Free (personal use) | 14-day free trial |
| Architecture | Native Win32 | Native Swift |
| Last updated | ~Win7 era | Active development |
Mapping your StrokeIt setup to macOS
Most StrokeIt users had the same core gestures configured. Here’s how those map to Curflow:
| StrokeIt gesture | What it did | Curflow equivalent |
|---|---|---|
| ← (left swipe) | Browser: go back | Draw ← → “Go Back” action |
| → (right swipe) | Browser: go forward | Draw → → “Go Forward” action |
| ↓ (down swipe) | Close tab | Draw ↓ → “Close Tab” action |
| ↑ then ↓ (up-down) | New tab | Draw ↑↓ → “New Tab” action |
| ← then → (left-right) | Minimize window | Draw ←→ → “Minimize” action |
| Circle | Refresh page | Draw circle → “Reload Page” action |
The process is not importing a config file — it’s recreating the gestures you already know by muscle memory. Most users report having their top 5 gestures set up within 5 minutes. The directional gestures (←, →, ↑, ↓) are the ones Curflow’s engine recognizes most reliably, which is convenient because those are exactly the ones StrokeIt users depended on most.
One practical difference: macOS handles the right-click contextual menu differently from Windows. Curflow respects those system conventions, which means the activation feel is slightly different at first. In practice, the adjustment takes less than a day for most users.
For the user who hasn’t thought about StrokeIt in years
There’s a specific pattern among StrokeIt users: you installed it sometime around 2005, configured five or six gestures, and then forgot it existed. It became part of how your hands worked. You never opened its settings again. It just ran.
That invisible-reliability is the hardest thing to replicate on a new platform. Curflow is designed around the same goal: configure once, then stop thinking about it. The tool should disappear into your workflow — not be something you manage.
Frequently asked questions
Is StrokeIt available for macOS?
No. StrokeIt is a Windows-only application. There is no Mac version, no port, and no announced plans for one. Development has been inactive since the Windows 7 era.
Are StrokeIt and StrokesPlus the same thing?
No. They are separate programs by different developers. Both provide mouse gestures on Windows, but they use different recognition engines and have different feature sets. Neither has a Mac version. We covered StrokesPlus separately.
Can I run StrokeIt on macOS with Wine or a virtual machine?
Technically possible with Wine or Parallels, but not recommended. Global mouse input interception through compatibility layers is unreliable on macOS, especially with Apple Silicon. You’d also lose the native feel that made StrokeIt worth using in the first place.
What is the best StrokeIt alternative on Mac?
Curflow is the closest alternative in interaction philosophy: hold a button, draw a shape, trigger an action. It adds per-app context, intent-based recognition that tolerates imprecision, and a native Swift architecture. BetterTouchTool also supports cursor gestures with more configuration options but a steeper learning curve.
Does Curflow work with an external mouse?
Yes. Curflow is designed for mouse input — the same device StrokeIt users have been using for years. No trackpad required.
Does it work on Apple Silicon?
Yes. Curflow is a Universal Binary — it runs natively on Apple M1, M2, M3, and M4 chips, as well as Intel-based Macs.
Curflow is a native macOS app that lets you draw gestures with your mouse to trigger any action — switch apps, close tabs, navigate desktops. Try it free for 14 days.
Read next:
- StrokesPlus Alternative for Mac — the other major Windows gesture tool, covered in detail
- I Switched to Mac and Missed Mouse Gestures — the full transition story
- BetterTouchTool vs Curflow — detailed comparison of the two main Mac gesture tools
- Browser vs System-Level Gestures on Mac — why browser extensions aren’t enough
- The Keyboard Killed My Flow — why gestures beat shortcuts for muscle memory
Write less. Gesture more.
Curflow turns your trackpad and mouse into a gesture engine. 14-day free trial, no card required.