How do I use screenshots in instructions without making the steps depend on guesswork?
Quick answer
Give each screenshot a specific job: support one step or a clearly identified group of steps. In the instruction, name the action and the visible control or area; in the caption, number the image to match the step and say what to look for. Keep essential directions in words, not just in the picture. Before publishing product instructions, check that the screenshot and labels match the current interface.
The question, the details, the next step.
I’m writing instructions for a task in a software interface. How do I decide which steps need screenshots?
Start with the step, not with whatever screenshots you happen to have. Add an image when it helps readers recognize a control, distinguish between similar-looking areas, or understand where an action takes place. Give each image a defined job, such as “show where to open the settings panel.”
A useful test is: if someone followed the written instruction without seeing the picture, would they still know what to do? If not, improve the words as well as adding the image. W3C describes visual illustrations as helpful in explaining step-by-step product documentation and gives numbered captions as an example of identifying illustrations. That supports connecting an image to identifiable instructions; it does not mean a screenshot alone is always sufficient or prescribe one required format. [S1]
How do I connect each screenshot to the right instruction and point out the relevant area?
Number the steps and use the same number in the image caption. In the step text, name the action and the control or area using the wording readers can see in the interface. In the caption, describe what the image helps them notice; avoid a vague label like “Screenshot.”
For example, if step 2 asks readers to open a panel, the caption could say, “Step 2: Find the Settings control in the upper navigation.” If needed, add a simple callout to the relevant area, but don’t let a circle or arrow carry information the written instruction omits. Check product-specific names, labels, and screenshots against the current interface before publishing; the cited guidance does not verify any particular product’s current appearance. [S1]
Can you show me a planning format I can use before I capture or place images?
Use a screenshot-to-step planning table with one entry per image. This hypothetical example shows the fields to fill in; replace the interface labels with the exact ones in your product and confirm them in the current interface.
Screenshot 1 Step: Open the settings panel. Area to notice: Settings control. Caption: “Step 1: Locate Settings in the navigation.” Text-only instruction: “Select Settings in the navigation.”
Screenshot 2 Step: Choose a display option. Area to notice: Display options. Caption: “Step 2: Find the display options in the panel.” Text-only instruction: “In the panel, choose the display option you need.”
The text-only instruction should explain the action without requiring readers to infer meaning from color, position alone, or a callout. If a screenshot shows several controls, state which one matters and why. Keep each image close to its corresponding step so readers do not have to guess which instruction it illustrates.
What should I review before I publish the instructions?
Review the relationship between the step, the image, and the caption—not just whether the screenshot looks tidy. Confirm the numbering matches, the image shows the state the step describes, and the caption directs attention to the intended area. Check labels against the current product interface, and remove or replace images that no longer match it. Then read the written steps without looking at the screenshots: they should still say what action to take and identify the relevant control. This approach can help reduce guesswork, but it cannot guarantee that every reader will interpret an image the same way.
A practical checklist
Assign each screenshot to one numbered step or a clearly stated group of steps.
Name the action and visible control or area in the instruction text.
Use a matching step number and informative caption for each image.
Add a callout only as extra guidance; keep essential meaning in words.
Check product-specific screenshots and labels against the current interface.
Read the instructions without the images to find missing directions.
A few more useful answers
Should every instruction step have a screenshot?
No. Use an image when it clarifies a location, visual distinction, or process. An image for every simple action may add clutter rather than clarity.
Is a caption such as “Step 3” enough?
It links the image to the step, but may not tell readers what to notice. Add a brief description of the relevant control or area.
Can a screenshot replace the written directions?
Avoid relying on the image alone for essential actions. Explain the action and identify the relevant area in text so readers are not left to infer the step from appearance.
Sources
References used for this guide.