Bulk Captures
Windows 10 & 11 Buy license · $39.95
Workflows

How to Take Screenshots for Step-by-Step Instructions and Guides

Take clean screenshots for step-by-step instructions and help articles: capture in order, keep sizes consistent, name files by step and add a watermark.

Updated 5 minute read The Bulk Captures team

Good screenshots for step-by-step instructions share four things: they show only what the reader needs (a window or region, not the whole desktop), they are the same size and style throughout, they are captured and named in step order, and they are saved as PNG so text stays sharp. Getting there is mostly about preparation and a capture setup that numbers files for you. This guide walks through the whole process, from setting up your screen to dropping the finished images into a manual or help article.

Before you capture: prepare the screen

Ten minutes of preparation makes every screenshot in the guide look better.

  • Use a clean test account with realistic but fake data. No real customer names, emails or figures.
  • Close everything you do not need and turn on Do not disturb so notifications do not appear mid-capture.
  • Set a fixed window size. Restore the app from maximized and size it so the important controls are visible without wasted space. Many guides work well at around 1280 by 800.
  • Pick a display scaling and stick to it. Changing scale between captures makes text sizes inconsistent across steps.
  • Use the default theme (light or dark) your readers are most likely to see.
  • Write the steps first, at least in rough. You will know exactly which screen each step needs.

Window, region or full screen?

Capture typeUse it for
WindowMost steps: a dialog box, a settings page, the app at its working size
RegionZooming into one part of the window, such as a toolbar or a single setting, with the same framing each time
Full screenRarely: steps involving the taskbar, Start menu or several windows at once
Delayed captureOpen menus, dropdowns and tooltips that close when you press a key

Full-screen captures on a large monitor shrink to unreadable sizes in a document. Capture the window and readers can actually see the text. Our guides to capturing the active window and capturing menus with a delay cover the techniques.

Capturing in step order

The built-in approach, Windows+Shift+S, paste, save, rename, breaks your concentration at every step. By step 15 it is easy to lose track, overwrite a file or save one in the wrong folder.

A better setup is a hotkey that saves each capture immediately with a running number. Bulk Captures does this: set a naming pattern such as setup-guide_step-{n} and an output folder for the guide, then work through the process pressing the window or region hotkey at each step. Files come out as setup-guide_step-001.png, step-002 and so on, in exactly the order you captured them, ready to drop into your manual. If you need a capture you are not sure about, take it anyway; deleting an extra file later is easier than going back.

For a region you return to repeatedly, such as one panel of the app, draw it once as a saved region in Bulk Captures, so every close-up has identical dimensions.

If you retake a step, the counter moves on and the new file sorts after the old one. Delete the old file and renumber at the end, or just note the extra number in your draft.

Keeping screenshots consistent

Inconsistent screenshots make a guide look thrown together, even when the instructions are good. Check these as you go:

  • Same window size for every full-window capture.
  • Same width when published. Resize to one width, such as 800 or 1000 pixels, rather than letting each image display at its own size.
  • Same border or shadow. A thin border separates a white dialog from a white page. Apply it to all images or none.
  • Same pointer policy. Either show the pointer where the reader should click in every image, or in none.
  • Same format. PNG for interface captures.

Bulk Captures can apply the border or drop shadow, resize to a fixed width and add a small logo watermark to every capture as it is saved, so consistency happens automatically rather than in a long editing session at the end. Keep any watermark small and in the same corner on every image, so it never covers the control a step is pointing at.

Annotating screenshots

Highlighting where to click helps readers, but keep it restrained:

  • One highlight per screenshot, usually a rectangle or arrow around the control the step mentions.
  • One color for all annotations across the guide, with enough contrast against both light and dark interfaces.
  • Numbered callouts only when a single screenshot covers several sub-steps.
  • Blur or cover private data that slipped into a capture, even in a test account.

Snipping Tool's pen and highlighter work for quick markup, and most image editors and documentation tools have arrow and box tools. Annotate copies, so the clean originals are available when the guide needs updating.

Placing screenshots in the guide

  1. Text first, image second. Write the step, then show the result or the control. Readers scan the instruction and use the image to confirm.
  2. Add alt text describing what the screenshot shows, for readers using screen readers and for when images fail to load.
  3. Do not rely on the image alone. Name the button or menu in the text too, such as Settings → Account → Security.
  4. Skip obvious screenshots. Not every step needs one. Use images where the reader might get lost.
  5. Check on a phone. Many readers open help articles on a phone. Make sure the key detail in each image is still visible when the page shrinks, and crop tighter if it is not.

If the guide is going out as a single document rather than a web page, a multi-page PDF with one step per page is easy to print and share. Our guide on how to combine screenshots into one PDF covers that.

Updating guides when the software changes

Interfaces change, and outdated screenshots are the first thing readers notice. Keeping your capture setup makes updates fast:

  • Keep the original, unannotated captures in a folder per guide, named by step.
  • When the interface changes, run through the process again with the same window size and naming pattern, into a new dated folder.
  • Replace only the steps that changed, comparing old and new folders side by side.

For sizing advice specific to manuals and help centers, see our guide to the best screenshot size for documentation.

Frequently asked questions

What size should screenshots for instructions be?

Capture at the size the reader needs to see, usually a single window or region rather than the whole screen, and keep the same size across a guide.

How do I keep screenshots in the right order?

Use a running counter in the file name, such as step-001, step-002, so files sort in the order you captured them.

Should I capture the full screen or just the window?

Usually just the window or a region. Full-screen captures include the taskbar and other apps, which distract the reader and shrink the useful detail.

Get three guides like this every month, plus software update notices.Subscribe →