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

A good how-to is a few screenshots with numbers on them and one sentence per number. The slow part is usually the assembly: paste, annotate, number, write, reformat for wherever it ends up. Here is a way to cut that down.

The structure that works

1. One goal per guide. "Reset your password" is a guide. "Account settings" is a menu.
2. One screenshot per screen, not per click. If three clicks happen on the same screen, mark all three on one image.
3. Number the marks, write one sentence per number. Start each with a verb: "Click Settings", "Paste your key".
4. Hide anything private before you save: email addresses, names, account numbers.
5. Keep screenshots consistent. Same arrow color, same font, same size across the whole guide.

Doing it by hand

With a normal screenshot tool the workflow is: capture, open an editor, draw numbered circles, save, paste the image into a document, type the numbered list beside it, and repeat for each screen. If a step is added later, the numbers on the image and in the text have to be fixed separately.

Doing it in GrabCanvas

1. Capture a region (Ctrl + Shift + 1, or ⌘ + ⇧ + 1 on macOS). The editor opens straight away.
2. Place numbered steps by clicking where each action happens. Each marker gets a line in the steps list beside the image.
3. Write the instruction for each step. Drag a step earlier or later and the numbers on the image follow.
4. Use blur to hide private details; it finds email addresses and offers to blur them in one click.
5. Export the image and steps together as Markdown, Word (.docx), HTML or PDF. The image is also saved as a PNG with the markers drawn on, so it still reads when it is pasted elsewhere.

Captures stay in the Library with their annotations as separate layers. When the interface changes, reopen the capture, move a marker and export again.

Where the export goes

• Markdown for a wiki, README or static help center.
• Word for a colleague or client who wants a document they can edit.
• HTML for a snippet to drop into a knowledge base.
• PDF for a customer or for onboarding.

Keep it current

Guides go stale quietly. Put the product version or the date on the guide, and when a release changes the screen, replace the one affected capture rather than rebuilding the guide.