Private browser tool · No signup · No watermark

Combine Images Vertically

Stack screenshots and photos into one tall image. Most people arriving here have a set of phone screenshots and want them to look like a single continuous capture.

Drop photos here

or paste Ctrl/⌘ V, choose files, or take a photo

Your photos are processed in your browser. Nothing is uploaded.

Presets

Photos

Preparing your image…

Layout

Adjust

50%
100%
50%
50%
16px
0

Labels

Export

92
Output: —

Private export. No upload, no account, no watermark.

The giveaway is the repeated bar

Stacking screenshots is easy. Making the stack look like one continuous screen is the part that takes thirty seconds of preparation, and skipping it is what makes a long screenshot look obviously assembled.

Every phone screenshot carries the same furniture: a status bar with the clock and battery at the top, often a navigation or tab bar at the bottom. Stack three captures and the clock appears three times down the image, which immediately tells the viewer these are separate shots — and worse, it breaks the illusion exactly where you wanted continuity.

Crop that furniture out of every capture except the first before adding them. Keep the top bar on image one for context, then trim it from the rest. The same goes for any sticky header that stayed fixed while you scrolled.

STACKED AS CAPTURED the navigation bar appears twice CROPPED FIRST One continuous document, spacing zero.
Left: stacked as captured, with the navigation bar repeating. Right: furniture cropped from the second capture first.

Overlap is the other half of the problem. Scroll-and-capture usually repeats a few lines of content between shots. This tool stacks what you give it — it does not detect or remove duplicated rows, and there is no reliable way to do that automatically for arbitrary interfaces. Trim the repeated lines from the top of each following capture and the joins become invisible.

With the furniture and overlap removed, set spacing to zero. That is what makes the result read as one document rather than a strip of panels.

Matching widths

Equal width is the default and is almost always what you want for screenshots. Every image is scaled proportionally to a common width, so the column has straight edges and no image is cropped. Captures from the same device already share a width, so nothing is rescaled at all.

Original width keeps each image at its own size and lets you align them left, centre or right. This is only useful when mixing sources of genuinely different widths — a desktop screenshot alongside phone captures, say — and you would rather see the size difference than normalise it away.

Mixing a very wide desktop capture with narrow phone screenshots under Equal width makes the phone screenshots enormous and the desktop one unreadable. Crop the wide one down to the region that matters instead.

How tall is too tall

Vertical output grows fast, and people underestimate it. Six phone screenshots at a 1200-pixel output width land around 15 000 pixels tall — far beyond anything that displays at a readable size in one piece.

Two things follow. First, the maximum-width setting controls height too: narrower output means proportionally shorter, so it is the lever to reach for when a file gets unwieldy. Second, messaging apps and social platforms re-compress very tall images aggressively, and some refuse them outright — which is when carefully preserved screenshot text turns to mush.

Past roughly eight to ten screenshots, splitting into two images usually serves the reader better than one enormous file.

RESULTING HEIGHT — 6 PHONE SCREENSHOTS 800 px wide≈ 10 400 px tall 1200 px wide≈ 15 600 px tall 2000 px wide≈ 26 000 px tall Some apps re-compress or refuse extremely tall images. Narrower output keeps the file manageable.
Output height for six phone screenshots at three different output widths.

Keeping the text sharp

Use PNG. Screenshots are mostly flat colour and hard-edged text, which is exactly what PNG handles losslessly and what JPG handles worst — JPG leaves visible halos around lettering and smears thin UI rules, and those artifacts are permanent.

WebP is a reasonable second choice, noticeably smaller than PNG at similar quality for this kind of content, if the destination accepts it. Reach for JPG only when the stack is photographs rather than interface captures.

Do not enlarge past the original capture size. Scaling a 1170-pixel screenshot up to 2000 makes the file bigger and the text blurrier, because there is no additional detail to recover.

Stacking images vertically — questions

Does this remove duplicate overlap between screenshots automatically?

No. It stacks the images in the order you give it. Crop repeated rows, status bars and navigation bars from each capture before adding them — that is what makes the joins invisible.

How do I make it look like one continuous screenshot?

Crop the status bar and any navigation bar from every capture except the first, trim repeated content from the top of each following image, then set spacing to zero and keep Equal width.

Why is my result so tall?

The height is the sum of every scaled image plus gaps. Six phone screenshots at 1200 pixels wide is roughly 15 000 pixels tall. Reduce the maximum output width to reduce height proportionally, or split the set into two images.

Which format is best for screenshots?

PNG. It keeps interface text and thin lines crisp with no compression artifacts. WebP is a smaller alternative where supported. Avoid JPG for screenshots — it leaves halos around text.

Can I add space between the images?

Yes. Zero spacing reads as one continuous document; a gap of 8 to 24 pixels reads as separate panels, which suits step-by-step instructions where each stage is distinct.

Can images keep their original width?

Yes, switch to Original width and choose left, centre or right alignment. Equal width is the better default for captures from the same device.