A long image is useful for a short walkthrough, conversation excerpt, or multi-part receipt. Its value comes from readable text and an understandable sequence. Simply stacking everything can create a huge file with repeated headers, overlapping lines, or text too small to read after sharing.
Prepare a sequence before combining
Capture every screen at the same device zoom and orientation when possible. Keep a separate copy of the original screenshots. Remove irrelevant notifications and private information before making the image public. Cropping is not a substitute for checking the saved result: inspect the final file for names, account numbers, and other details you intended to exclude.
If adjacent screenshots overlap, crop repeated content manually with an image editor. The merger does not detect scrolling overlap or remove duplicate lines. Leave enough context that a cropped sentence or receipt total is still understandable.
Stack three equal-width screenshots
For a concrete example, use three screenshots measuring 1080 × 1920 pixels. In the homepage merger, select Vertical, Original sizing, Free aspect ratio, and zero outside margin. Use an 8-pixel gap to distinguish separate screens.
There are two gaps between three images. The result is 1080 × 5776 pixels: 1920 × 3 + 8 × 2. Reorder the screenshots in the image list so the first step is at the top, then download PNG.
| Setting | Why it matters for screenshots |
|---|---|
| Original sizing | Keeps the captured text at its source size |
| Free aspect ratio | Avoids extra background for a fixed shape |
| PNG export | Avoids lossy encoding around letters |
| Small visible gap | Distinguishes separate screens |
| Correct image order | Makes the workflow or conversation readable |
When one screenshot has a different width
Suppose the third screen is 720 pixels wide. Original sizing keeps that width and leaves background beside it inside the 1080-pixel canvas. Reduce instead matches the smaller width, shrinking the 1080-pixel screens and their text. Magnify enlarges the 720-pixel source, which cannot add new letter detail.
For documentation, consistent captures are preferable to resizing a mixture. If you must use unequal sources, preserve them at Original size and use a clear background. Read each screen at the actual sharing width before deciding whether the combined image is usable.
Avoid making the image too tall
Five 1080 × 1920 screens with four 8-pixel gaps would produce 1080 × 9632 before the export limit. The homepage's 8000-pixel longest-side cap shrinks that composition, reducing text detail. Device memory may also become a problem before any advertised pixel limit is reached.
Split a long sequence into two images when a single export becomes hard to read. For an extended manual, separate screenshots with text in a document or webpage are often easier to search and navigate. Do not force an entire long conversation into one image just because the tool can stack it.
Template editor differences
The template editor can also stitch vertically at source dimensions. Its stitch export includes the selected gap and annotations. Template and free layouts have an 800-pixel longest-side export, making them unsuitable for a full-resolution long screenshot master. Use the homepage when you need visible separators and configurable export formats.
Check the recipient's version
Open the downloaded PNG at 100%, verify the first and last lines of each screen, and check every join for repeated or missing text. Then inspect the copy after uploading or sending it: a messaging app may reduce a tall image. Share the file as a document when that destination offers a way to avoid photo resizing, or provide the original screens separately if precise readability matters.
Plan a tutorial sequence
For an app walkthrough, use the three-step screenshot workflow. It distinguishes useful repeated interface context from duplicate scrolling content and calculates how display width affects small labels.