Skip to content

Guides

How to create a step-by-step guide with screenshots for free

A free template to copy, seven rules that make guides easy to follow, and three ways to make the screenshots for free: by hand, with a Chrome extension or with a script.

  • November 2, 2026
  • 9 min read
  • The AtriumKit team
  • Updated November 12, 2026
Click the highlighted spot in each step to follow along. Made with AtriumKit, from a click-through of the app.

Sooner or later someone needs a step-by-step guide with pictures from you: a customer stuck on a setting, a new hire learning how billing works, a colleague covering for you next week. This article shows how to create a step-by-step guide with screenshots that people can follow without asking you. You get a template to paste, the rules that make a guide work, three ways to make the pictures for free, and the same guide made in AtriumKit as a worked example.

The walkthrough above, an AtriumKit demo, shows how to publish one and where its written guide lives. We make AtriumKit, so weigh what we say about it accordingly.

What a good step-by-step guide contains

A guide can list every click and still leave the reader stuck, because what’s missing is the information around the steps. Readers need to know:

  • Is this the right guide? A title that names the task, and who it’s for.
  • Can I do it? The role, plan or data they need before they start.
  • What do I do? Numbered steps, one action each, in the words on the screen.
  • Did it work? What they should see after each step that changes something.
  • What if it didn’t? The two or three things that usually go wrong.
  • Is this still true? When someone last checked the guide against the product.

A step-by-step guide template you can copy

It’s Markdown, so it drops into a docs repo and works as an outline in any other editor. Replace everything in brackets.

# [Verb + object, the way readers say it: "Send an invoice"]

- **Who it's for:** [role, team or plan]
- **Time:** [about N minutes]
- **Last checked:** [YYYY-MM-DD], on [app version or release]

## Before you start

- [The permission or role the reader needs]
- [What to have ready: a file, an ID, a test account]

## Steps

1. **[Verb] [the label, exactly as the screen shows it].**
   [Where to find it, only if it's hard to find.]

2. **[Verb] [the label].**

   ![What the picture shows, and what's highlighted](images/02-short-name.png)

   [What the reader sees now, e.g. "A blank invoice opens."]

3. **[Verb] [the label].** [One detail the reader needs, if any.]

   [What the reader sees now.]

## If something goes wrong

- **[What the reader sees].** [Why it happens, and what to do.]
- **[What the reader sees].** [Why it happens, and what to do.]

## Related

- [The task readers usually do next](link)

Steps 1 and 3 have no picture on purpose. Rule 5 explains why.

Seven rules that make a guide easy to follow

1. One action per step

“Open Settings, click Billing and then Edit” is three steps. When a reader gets lost, they can tell you which step failed, and you know which one to fix.

2. Use the words on the screen

Write each label exactly as the product shows it, in bold: New invoice, not “the create button”. Readers scan for those words. And when a label changes, searching your docs for the old word finds every guide that needs fixing.

3. Say what happens next

After any step that changes the screen, add one line on what the reader should now see: “A blank invoice opens.” A reader who doesn’t see it knows to stop before the next step makes things worse.

4. Crop to the action and highlight it

A full-screen capture from a large monitor shrinks until it’s unreadable in an article column. Crop to the area around the control, leaving enough context for the reader to find it on their own screen. Then highlight one thing per picture, with a box or ring in a color your interface doesn’t use. In the words of one Hacker News commenter: “Make sure that ‘the point’ of the screenshot is clear.”

5. Don’t screenshot every single step

The same commenter: “Don’t screenshot Every. Single. Step.” A picture under every line splits the instructions apart. Add one when the control is hard to find, when the screen changes a lot, or when readers need to compare their screen with yours. Skip it for “Open Invoices in the sidebar.”

6. Write alt text that says what matters

“Screenshot” tells a screen reader user nothing. “The Invoices page with the New invoice button highlighted” tells them what the picture is for. The W3C’s alt text decision tree covers the edge cases.

7. Date it

A “Last checked” line with the date and the app version tells readers whether to trust the guide, and tells you which guides to check after a release.

How to create a step-by-step guide with screenshots: three ways

Whichever way you choose, use a test account with sample data, so no real customer’s details end up in your docs.

1. By hand: a screenshot tool and a doc

On a Mac, Shift-Command-4 captures part of the screen and Shift-Command-5 opens the Screenshot app (Apple). On Windows, Windows logo key + Shift + S opens the Snipping Tool’s capture overlay (Microsoft). Paste each picture under its step, draw the highlight, and write the steps around it.

This suits short guides, desktop apps and anything else a browser recorder can’t reach, and guides that rarely change. The cost comes later: every picture is its own crop, and an interface change means retaking them one by one.

2. With a Chrome extension that records your clicks

Install a recorder, click through the task once, and each click becomes a step with a screenshot and a line of drafted text. AtriumKit works this way, and so do others:

  • Scribe has Chrome and Edge extensions and a desktop app, and “will automatically capture screenshots and text as you navigate” (scribe.com).
  • Tango is a Chrome extension that “captures screenshots and autogenerates descriptions in real time” (Tango help).
  • Stepsy is a Chrome extension that publishes guides to Google Docs in your Google Drive (stepsy.co).
  • Guidejar says that with its extension “every click becomes a step with its own annotated screenshot” (guidejar.com).

On the desktop, Snagit’s Step Capture does a similar job, though TechSmith notes it “does not capture non-click actions”, such as typing (TechSmith).

A recorder suits web apps, guides longer than a few steps, and teams that write guides every week. Before you install one, check what it can read on your pages and what it blurs before upload. Then edit the drafted text: a recorder knows what you clicked, not why.

3. Scripted, for docs-as-code

If your docs live in a Git repository as Markdown, a browser automation script can take the pictures. Playwright, for example, saves a picture of a single element with await page.locator('.header').screenshot({ path: 'screenshot.png' }). The script signs in to a test account, walks through the steps and saves a fresh image at each one.

Scripts suit products that change often, with someone on the team to maintain them. That maintenance is the cost: when the interface changes, selectors break and someone has to fix them. AtriumKit’s own help center pictures are made this way, from a short spec per picture: the page, what to ring and what to crop to.

By hand Chrome extension Script
First guide Capture, crop and mark up each picture Click through once, then edit the text Write the script, then the text
After a UI change Retake each picture that changed Record again, or edit the capture if the tool allows it Run it again, fixing any selectors that broke
Best for Short, stable guides and desktop apps Web apps, many guides Docs in a repository, maintained by engineers

Create step-by-step instructions with screenshots for free

All three ways have a free option. What each one gives you, and where the free version stops:

Free option What you get Where it stops
Your computer’s screenshot tool Shift-Command-4 on a Mac, the Snipping Tool on Windows No limits, but every crop, highlight and step is yours to make
Playwright An open-source library: a script takes the pictures Someone has to write the script and fix it when the interface changes
Scribe Basic Capture in Chrome and Edge; share by link, embed or video No file exports, Scribe branding, and up to 10 guides shared at a time, per Scribe’s help center
Tango Free Capture in Chrome and Edge; share by link, embed or Copy HTML; up to 10 users 5 workflows in the Team Library; PDF, Markdown and HTML exports are on Pro
AtriumKit Free Capture in Chrome; every published demo is also a hosted guide; copy it as rich text or Markdown, download it as .md, or print it to PDF 3 demos published at a time, 1 creator, and “Made with AtriumKit” on the guide page

Scribe’s and Tango’s plans were checked on November 12, 2026, on Scribe’s pricing page and Tango’s pricing page and their help centers. Free plans change, so check the vendor’s page before you build a library of guides on one.

Create step-by-step instructions automatically from your clicks: a worked example

Here’s the template’s task, sending an invoice in a sample invoicing app, made from one AtriumKit recording. Each click becomes a step with its own screenshot and a drafted line of text.

  1. Record it. Open the app in Chrome, click the AtriumKit button, choose Guided demo and click Start recording. Click through the task: Invoices, New invoice, the customer, a line item, Send. Then click Done. With Auto-blur emails and names on (the default), emails, phone numbers and names it recognizes, such as a customer’s, are blurred in your browser before upload. It misses some things, such as a card number on screen, so drag a Blur area over those before you click and check every screen (what auto-blur covers).
  2. Trim it. A review panel lists one row per click, titled from what you clicked: Open Invoices, Click “New invoice”, Enter description. Remove misclicks with the × on their row, then click Open in editor.
  3. Publish it. Click Publish. The demo is now also a step-by-step guide at its own address (the demo’s, with /g/ in place of /d/). It has one numbered step per tooltip, each with a picture of the screen.

How that measures up against the rules:

  • One action per step, in the screen’s words. Each click is a step, and the drafted titles use the label of what you clicked.
  • Cropped and highlighted. Each picture is cropped like the demo, with the clicked spot highlighted. To cut a screen down further, use Crop in the editor.
  • Alt text. Each picture’s alt text is the step’s heading, such as “Step 2: Click New invoice”.
  • What happens next. Add it in Text in the guide on the Guide tab, or let Write guide copy draft it for every step with AI (1 AI credit per 20 strings). Title in the guide and Text in the guide change the guide only, so the demo keeps its tooltips.
  • Fewer pictures. AtriumKit gives every step a picture, so the fix is fewer steps. Check Hide from guide on an obvious step and mention it in the next step’s text.
  • The rest of the template. The guide page doesn’t show a date. Put “Last checked”, who the guide is for and what to have ready in the intro card, which opens the guide, and troubleshooting in the closing card or the doc you paste the guide into.

Then get it to readers:

  • Send the link. On the Share tab, click Copy on the Step-by-step guide card. The guide follows the demo’s Who can view setting: search engines can index a public guide, and unlisted ones ask not to be.
  • Paste it into your docs. On the Guide tab, Copy → Rich text pastes the guide with its pictures into editors such as Notion and Google Docs. Copy → Markdown and Download .md give you Markdown. Copy and download use your latest draft; Print / PDF opens the published guide in your browser’s print dialog.
  • Put the walkthrough above it. The demo itself has an embed code (Share → Embed). In a help article, embed the walkthrough at the top and paste the written steps underneath.

Here’s a step from the Markdown export, after its guide text was filled in. The highlight is drawn into each exported picture, and the export ends with a link back to the interactive demo.

### Step 2: Click New invoice

It's at the top right of the Invoices page. A blank invoice opens.

![Step 2: Click New invoice](https://media.atriumkit.com/media/demos/…/guide/….webp)

When the product changes, edit the demo and publish again, and the hosted guide follows. A renamed button doesn’t need a new recording: change the text on the captured page with Edit text, or on every page of the demo at once with Find & replace…, then fix any step text that names it. A changed flow needs a new recording. Copies you pasted elsewhere don’t update, so paste them again. How to keep help center screenshots up to date covers the rest, scripted screenshots included.

Guides come with every published demo on every plan, Free included. On Free you can have 3 demos published at a time, and the guide page shows “Made with AtriumKit”.

Which way to start

If you write one guide a month, the template and your computer’s screenshot shortcut are enough. If you document a web app every week, try a recorder. Record your first demo and publish it, and the step-by-step guide comes with it. For help articles with the walkthrough on top and the steps underneath, follow the interactive help center playbook.

Your next demo is one click-through away.