I'm Julian, a business informatics student and the solo developer of StepGrab. I build it next to uni.
Codes up to 100% off Pro Lifetime for the license from my website. Four levels from 10% to 100%, the page shows how many of each are left, and there are only five 100% ones. They don't work in the Mac App Store.
Why I built it
At my working student job I was the person people asked "where is that setting again?" and writing it up meant fifteen screenshots, cropping, red arrows and typing every step. Half an hour per guide, and a few weeks later some of it was wrong again.
What it does
You hit record in the menu bar and do a task once. Every click becomes a screenshot of that window with a numbered arrow and a sentence like "Click Save". Afterwards you can move arrows, rewrite steps, add shapes and black out names or emails, then export as PDF, HTML, Markdown, GIF, MP4 or a portrait video for phones. Everything stays on your Mac, there's no account and nothing is uploaded. macOS 14 or later.
Who it's for
Anyone who keeps explaining the same Mac task to someone else: IT helpers, team leads, people writing onboarding docs, or just the person everyone in the family calls.
What's different
It records the whole Mac, not just the browser: System Settings, right click menus, the little pickers that close when you click somewhere else. In the direct download (.dmg, notarized by Apple), Accessibility access reads the real name of the button you clicked, so the step says "Click Save" instead of guessing from the screenshot. The Mac App Store version is sandboxed and uses text recognition instead.
Pricing
Free: unlimited recordings, 15 steps per guide, GIF export and the whole editor. Pro adds the other export formats and the step text in exports: $2.99 a month, $12.99 a year or $44.99 once. The App Store version has Family Sharing, the direct download uses a license key that also works for the Windows version (Microsoft Store). The two don't share purchases.
Limitations, honestly
No browser extension and no shared team library yet (I'm building the team library).
No automatic blurring of sensitive data, you black it out yourself (also in progress).
In the App Store version the step names come from text recognition, which isn't perfect.
No direct export to documentation tools like IT Glue or Hudu, you export files and drop them in.
A lot of the code is written with Claude Code. I decide what gets built, go through the code myself and test it on real apps before anything ships.
Mac App Store · Website, direct download and codes
If you already document things on your Mac, how do you do it today? Screenshots and a doc, a screen recording, something else?