Before I built StepGrab, my process looked like this: take a screenshot, paste it into a doc, crop it, draw an arrow, type out the instruction. Repeat eleven times. Then three months later someone asks the same question and I can't find the doc anyway.
I'm curious how everyone else handles this, because I suspect the honest answer for a lot of people is "I don't." You explain it over a call, the other person takes notes, and then the next new hire asks the exact same thing.
No wrong answer here, and I'm not fishing for anyone to tell me my approach is better. I want to see what the actual split looks like, especially how big the "I just explain it again" group is next to the people already using a documentation tool.
If your answer is messier than the options, put it in the comments. The messy ones are the useful ones.
Hey Product Hunt, I'm Julian. I study business informatics in Germany and StepGrab is what I build next to uni.
At my working student job I was the one everyone asked "where was that setting again?". Writing it down meant fifteen screenshots, cropping, red arrows in Preview, and typing every step. The screenshots were never the slow part. The sentences were.
So StepGrab writes them. You hit record and do the task once. Every click becomes a step: the screenshot from the moment you clicked, a numbered arrow, and a sentence like "Click Save". Open menus stay in the picture, and keyboard shortcuts become their own steps.
The difference to Scribe or Tango: it's a desktop app, not a browser extension. It records any app on Mac and Windows, also on the free plan, and nothing leaves your computer. No account.
Worth trying first: record something you explain every week, black out an email address in the editor, export it as HTML and send it to a colleague.
Free for guides up to 15 steps. Pro is $2.99 a month, $12.99 a year or $44.99 once, and one license key works on Mac and Windows.
For Product Hunt: 35% off Lifetime with the code PRODUCTHUNT until November 24.
I also put 5 free Lifetime licenses and 20 codes for 50% off on stepgrab.net/try/producthunt, first come first served.
One honest question: what do you use for this today, and what would make you switch?
Julian
If I record a task with a few Ctrl shortcuts in a row, can I merge them into one step in the editor?
change a step on the pc. does the mac open that same file?
The cross-platform part is what I'd want to understand first — when a guide recorded on Mac opens on Windows, do the step labels translate things like Cmd to Ctrl, or do they stay exactly as recorded? For a guide shared across a mixed team, that detail decides whether it reads clean on both sides.
Congrats on the launch, Julian! The detail I liked most is that redactions are actually burned into the export, not just a box drawn on top. That's the part most screenshot guides get wrong, and it's what makes something like this safe to send outside the company.
Also nice that you're open about the Mac split: the direct download reads real button names through Accessibility, while the App Store version falls back to OCR. Out of curiosity, how does it handle steps that aren't clicks, like keyboard shortcuts or hover menus that close before the screenshot is taken?
Good luck today from a fellow maker launching too 🙌
@erenasiroglu
Thanks, and good luck with your launch too!
Shortcuts are their own step. If you press something like Cmd+S or Ctrl+Shift+S, StepGrab takes a screenshot, puts a little keycap badge on it and writes "Press Cmd + S". Enter, Tab, Esc and the arrow keys work too, and you can switch each of them off if they make the guide noisy. On the Mac that needs the Input Monitoring permission, which is optional.
Menus were the annoying part. By the time a click lands, the menu is often already gone. So StepGrab keeps the last few frames in memory and uses the one from right before your click. You see the menu exactly how it looked when you clicked into it. On Windows that's always on. On the Mac it's a setting in Recording.
A pure hover with no click doesn't become a step. If a tooltip matters, I add a short note in the editor. Scrolling gets a small "scroll down" hint before the next step.
What are you launching?
Keeping the editable project usable on both Mac and Windows makes sense. The person updating a guide next month may be using a different machine.