Julian Belting's profile on Product Hunt

About

Student in Germany. Built StepGrab because I kept explaining the same Mac tasks to my boss and rebuilding the same screenshot guides by hand. Most of what's in it came from people telling me what was missing.

Badges

Tastemaker

Gone streaking

Gone streaking 5

Maker History

StepGrabTurn any Mac or Windows task into a step-by-step guide

🎉

Joined Product HuntJuly 16th, 2026

Forums

•

4d ago

StepGrab - Now on Windows, with redaction and a real editor

New since our first launch: StepGrab runs on Windows, and projects open on Mac and PC. Black out emails, names or prices, and the box is burned into every export so nobody can lift it off. Every guide opens in an editor: rewrite steps, add arrows, boxes and text, reorder, undo. The direct Mac download reads the real name of every button you click. Still the core: every click becomes a screenshot, arrow and sentence. No account, nothing uploaded. 5 free Lifetime licenses: see the comments :)

p/stepgrab

•

10d ago

StepGrab 1.6: now on Windows, reads button names on the Mac, plus codes up to 100% off

Hey everyone, Julian here. It's been a while since my last update in here, so here's what happened since.

As a thank you for following: codes up to 100% off Lifetime. Four levels from 10% to 100%, the page shows how many are left, and there are only five 100% ones. They're for the license from my website (Mac download and Windows), not the Mac App Store.

StepGrab is on Windows now. It's in the Microsoft Store (Windows 10 22H2 and 11), and projects open on both, so you can record on the Mac and finish the guide on a PC or the other way round.

On the Mac you can now also download StepGrab directly as a notarized .dmg. If you give it Accessibility access, it asks the app what you clicked and gets the real name of the button or menu item, so the step says "Click Save" instead of guessing from the screenshot. The App Store version can't do that because of the sandbox, so it keeps using text recognition.

p/stepgrab

•

3mo ago

How do you document repeatable tasks today?

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.