A three-screen walkthrough should show the starting state, the action, and the result. Simply stacking captures can repeat navigation, omit the state between steps, or create an image that becomes unreadable when shared. This workflow focuses on an app tutorial. For the general size and export settings, see the screenshot merging guide.
Capture a complete sequence
Before capturing, write a one-sentence goal such as “Change the notification setting and confirm it is off.” Then capture the setting's starting state, the control being changed, and the resulting state. Those are example steps; use the real states of the app you are documenting.
Keep the device orientation, app zoom, and capture method consistent. Remove notifications and private account details before publishing. A crop that hides the selected tab or the relevant setting name can make the remaining screen harder to understand, so retain enough interface context for each step.
Distinguish overlap from useful repetition
A repeated app header can help readers recognize each separate screen. Repeated lines in scrolling content can instead make a conversation or instruction look duplicated. The merger does not detect overlap, remove repeated content, or create a seamless scrolling capture.
If two screenshots overlap, compare the last visible line of the first with the first lines of the second. Crop source copies in an image editor before merging if you need to remove duplicates. Avoid cutting through a sentence or deleting a control that explains the next action. Keep the originals so you can recover context.
Calculate a three-screen output
For three 1080 × 1920 screenshots, choose Vertical, Original sizing, Free aspect ratio, zero outer margin and border, and 12px spacing in the homepage editor. The result is 1080 × 5784: 3 × 1920 + 2 × 12.
At 360px display width, each screen appears one third of its original pixel width. A 30px-high label in a source is only about 10px high in that view. Adding more screenshots below it does not enlarge the label. If the tutorial is a webpage, separate images with selectable instructions often work better than a single long image.
Know when to split the walkthrough
Five of the same screenshots with four 12px gaps make 1080 × 9648 before the homepage export limit. The 8000px longest-edge cap reduces that to about 896 × 8000. PNG avoids lossy encoding but cannot prevent this resizing. A lower configured limit can shrink it further.
| Delivery | Useful approach |
|---|---|
| Short three-step reference | One vertical PNG with a caption |
| Many steps with explanations | Separate screenshots in a document or webpage |
| Exact text must remain inspectable | Provide source screenshots alongside the overview |
| Sending through a chat app | Check the received copy for resizing |
The template editor's Stitch mode uses source dimensions and includes its spacing and annotations in the PNG download. The homepage offers configurable export formats and outer margins. Add short labels afterward with Add Text, and put the full instructions outside the image.
Review from top to bottom
Confirm that the first capture establishes context, every action leads to the next visible state, and the final capture demonstrates the result. Check each join for repeated or missing content and reopen the actual exported file. Then review the version after sharing; a long image that is readable locally may be reduced by the destination. Keep the source screenshots with the tutorial so a future interface update can replace one step without reconstructing the whole sequence.