Free tool · no signup
Step-by-step guide generator.
Rough notes in, clean how-to out.
Describe the process the way you would explain it to a colleague — “settings, team, invite, type the email, pick a role, send”. The AI turns it into a guide anyone can follow: a title, what it achieves, what you need first, short numbered steps, and tips and warnings — and tells you what is still missing instead of inventing it.
Generate a step-by-step guide
Anatomy of a good step-by-step guide
Six parts. If a guide has all of them, a new teammate can finish the task without asking anyone — that is the whole test.
- 01
Title
“How to <do the task>”. Searchable, specific, no jargon: “How to invite a teammate to the workspace”.
- 02
Purpose
One sentence: what the reader has achieved at the end. It tells them they are in the right guide.
- 03
Before you start
Access, role, data or files they need before step 1 — so nobody gets stuck halfway.
- 04
Numbered steps
One action each, verb first, UI names exactly as on screen: “Open Settings → Team”.
- 05
Watch out
Anything hard to undo, easy to get wrong, or with a side effect (billing, notifications, deletes).
- 06
Tips
Shortcuts and helpful asides — kept out of the steps so the steps stay short.
- auto
Or record it once
Do the task once in Chrome while SceneRecap records. Tutorial mode writes the same guide from what you actually clicked — with a screenshot per step and a timestamp that jumps back to that moment in the video — ready to export to your wiki or handbook. Tutorial mode is included on the Free plan.
How that works →
How to write step-by-step instructions
How do you write good step-by-step instructions?
Start from a place anyone can reach (“signed in to the admin”). One action per step, in the order it happens, starting with the verb: “Open Settings → Team”, “Click Invite member”. Name buttons and menus exactly as they appear. Put what to choose, or what happens next, in a short second sentence. List what the reader needs before step 1, and call out anything that is hard to undo. That is the structure this generator produces.
What is the difference between an SOP and a step-by-step guide?
A standard operating procedure (SOP) is a step-by-step guide with governance around it: an owner, a review date, a scope, sometimes a compliance reason. The core is the same numbered list of actions — generate it here, then add the SOP header your team uses.
Is there a step-by-step guide template I can copy?
Yes — generate a guide and copy it as Markdown; the headings (Before you start, Steps, Watch out, Tips, Still to confirm) are the template. Or use this skeleton: Title (“How to …”) · Purpose · Before you start · Numbered steps · Watch out · Tips.
Is the text I paste stored?
No. The description is sent to the AI model for this one request and is not logged or saved by SceneRecap. Don’t paste secrets anyway — leave passwords and tokens out of the steps.
Why does it list “Still to confirm”?
Because it never invents a menu name, a role or a setting your notes didn’t mention. When a reader would need a detail that isn’t in your description, the step stays generic and the gap is listed for you to fill in — a wrong button name in a guide is worse than a missing one.
Why is it free, and what are the limits?
It is a small taste of what SceneRecap does with a screen recording: there the AI watches the process and writes the same guide with a screenshot per step and a timestamp back to the video. The text tool is capped at 10 guides per day per visitor and the description at 4,000 characters.
More free tools
Skip the screenshots
Record the process once. Get the guide with a screenshot per step.
Every step links back to its second in the recording, so readers can watch the part they are unsure about. No narration needed.