Screenshots to step-by-step guide

How to turn screenshots into a step-by-step guide

To go from screenshots to a step-by-step guide, take one screenshot per action, put them in the order the task happens and write a short instruction under each one, plus a title and a line on what the guide achieves. This tool does the writing: it turns screenshots into instructions by reading what each screenshot shows, working out the action and writing a step title and instruction next to the image. You check the wording instead of writing it.

A screenshot guide works because readers can compare their screen with yours at every step. Most “I’m stuck” moments come from not finding a button, and a picture answers that faster than a sentence.

How to take screenshots for a guide

• One screenshot per action. Capture the screen where the reader has to click, type or choose something.
• Show where to click. Leave the cursor on the button or open the menu before you capture.
• Crop to the window. A full desktop with ten open tabs makes the important part tiny.
• Keep the same window size. Consistent screenshots look like one guide, not a collage.
• Hide personal data. Blur names, emails and account numbers before you share or upload anything.

Screenshot guide, video or plain text?

Each format suits a different kind of task and reader.

Many help centers use both: a screenshot guide to skim and a short video for people who prefer to watch.

A short example

Three screenshots of an admin panel, with the context “Setting up two-factor login”, could become:

1. Open your security settings. Click your profile picture, then choose Security.
2. Turn on two-factor login. Click Enable next to Two-factor authentication and scan the QR code with your authenticator app.
3. Confirm with a code. Enter the six-digit code from the app and click Verify.

In the result, each step sits next to its screenshot, and the Word and Markdown downloads keep the images in place.

Tips for a better screenshot to guide result

Use the context field

A line like “Creating an invoice in our billing app for new accountants” tells the AI the goal and the reader, so the steps explain why, not only where to click.

Check the order before you upload

The guide follows the order of your files. Rename them with numbers, or drop them in one at a time, so step three doesn’t end up first.

Name the exact labels

If a button label is hard to read in the screenshot, mention it in the context. The guide is only as precise as what the AI can see.

What makes a good step in a screenshot guide

Each step should do three things: say what to do, show where to do it and tell the reader what they should see next. Start with a verb (“Click”, “Choose”, “Enter”), name the button exactly as it appears on screen and keep it to one action. If a step needs a value, such as a setting or a field entry, write it out so readers can copy it. The generator writes steps this way; your job is to check that the labels match your app.

Common mistakes

• Skipping a screen because it seems obvious. Beginners get lost exactly there.
• Screenshots from two different versions of the app in one guide.
• Tiny, uncropped screenshots where the button can’t be seen.
• Not re-taking screenshots after the interface changes.

Read every step against the real app before you publish. AI can misread a screen, especially with small text or similar-looking buttons.