Photo Merger

Add your photos and pick a layout to see the merged result and file size right away

Photo Merger puts several photos together, in order, into a single image file. The four cards at the top (Stack vertically, Side by side, Grid, and Justified rows) each show a live preview of your current photos, so you can choose by looking at the shape and pixel size of the result. To change the order, drag photos in the strip below or use the Move earlier and Move later buttons.

If your screenshots capture one long chat or web page in several parts, Stack vertically finds the overlap and removes it. The top bar and bottom input bar that repeat on every screen are kept only at the start and the end, and any rows that appear in both the previous and the next capture are kept once, so the result reads as if it had been captured in one go. Your photos are processed only inside this browser and are never sent to a server.

When to use it

• Saving a chat or an order history as one image: stacking scrolled captures vertically keeps the context unbroken. Repeated rows and repeated top bars are removed, so the same message doesn't show up twice.
• Comparing before and after: Side by side scales every photo to the same height. Place before-and-after photos of a tidy-up, a treatment, or a renovation from left to right and the difference is clear at a glance.
• Collecting product or trip photos on one canvas: Grid uses same-size cells, and Justified rows fills each row to the same width without cropping. Use them for a blog cover image or a social post that shows several photos in one.
• Photographing a document in parts: stack photos of a receipt or a notice top to bottom and send one file, so the recipient never mixes up the order.

How to merge photos

1. Add photos: click Add photos or drag files onto the stage. You can also paste a copied image (Ctrl+V, ⌘V). The first photos you add replace the examples, and later ones are added at the end.
2. Choose a layout: each of the four cards shows your photos merged that way, with the result size. If the first photos you add are two or more vertical captures of the same width, the layout switches to Stack vertically automatically.
3. Order and direction: drag photos in the strip (mouse), or select a photo and press Move earlier or Move later (phone). Rotate 90° turns a photo clockwise, and Remove takes it out of this session only.
4. Size and styling: the size starts at Original size, so no photo is enlarged. Then set Gap between photos, Outer margin, Rounded corners, and Background.
5. Save: check the pixel size and the actual file size in the result line, then save as PNG, JPG, or WebP. On a phone, Share sends the image straight to a messaging app.

How do the four layouts differ?

None of the four layouts distorts a photo. They differ in which length they match, whether photos are cropped to fit, and whether empty space can appear.

In Grid, Fill cell enlarges each photo until it covers the cell completely and then crops what spills over. It keeps the center at first, but you can move the part that stays by dragging the photo on the stage, or by selecting it and pressing the arrow keys. With Justified rows set to Auto, the number of rows is the one that brings the result closest to 4:3 landscape; setting 1 row gives the same shape as Side by side.

How the saved size is determined

The number in the size field means something different for each layout. In Stack vertically it is the photo width, in Side by side the photo height, in Grid the cell width, and in Justified rows the total width without the outer margin. Add the gap between photos and the outer margin on both sides, and you get the saved size. Lengths scaled up or down to keep the ratio are rounded to the nearest whole pixel.

• Original size: the starting value is the largest size that doesn't enlarge any photo. In Stack vertically that is the width of the narrowest photo, and in Side by side the height of the shortest photo. Enlarging a small photo doesn't create detail that wasn't there; it only blurs.
• Result limits: if a result made at Original size goes over the limits below, it is reduced to the largest size within the limits. If you enter a size yourself and it goes over, it is not reduced; saving is blocked and the largest value you can enter is shown.

A rotated photo is calculated with its rotated proportions. Rotating a 100 × 50px photo by 90° makes it 50 × 100px, and in Stack vertically with the width set to 100px, that photo becomes 200px tall.

What does Remove capture overlap look for?

Screenshots taken while scrolling overlap in two ways. One is the rows that stay fixed in place, such as the top bar at the very top and the input bar or menu at the very bottom. The other is content that appears at the bottom of one capture and again at the top of the next. The tool compares the pixel rows of each neighboring pair, top to bottom, to find both.

1. Fixed rows: it compares the same positions in the two captures from the very top and from the very bottom, and treats the run of identical rows as the top bar and bottom bar. A row where only one corner differs, like a clock or a battery icon, still counts as the same row.
2. Repeated content: it looks for the largest number of rows for which the end of the previous capture's content matches the start of the next one. A match counts as overlap only if the average color of each row is nearly the same (JPG compression differences are ignored) and several of the rows contain changing patterns, so a stretch of plain background alone isn't treated as overlap.
3. Trimming: from the previous capture it cuts the bottom bar, and from the next one it cuts the top bar and the repeated content. The first capture's top bar and the last capture's bottom bar are kept.

Each seam it finds appears on the stage as a dotted line with an "overlap removed" marker showing the pixels cut. Click a marker to go to that photo's Trim top and Trim bottom fields and change the values yourself, and click Use auto value to return to the detected value. Overlap is only searched between captures of the same width. Photos taken on a different device, rotated photos, and horizontally scrolled captures are joined as they are.

Photos you can add and the limits on the result

When a canvas goes over the size limit, the browser doesn't raise an error; it just produces a blank picture. That is why the tool checks, right before saving, that the bottom-right pixel of the result is actually drawn, and tells you to reduce the size if it isn't. Even within the limits, a phone may fail to save depending on its memory, so close other tabs, reduce the size or the number of photos, and save again.

PNG, JPG, or WebP: which to save as?

• PNG: suits captures with lots of text. It leaves no compression artifacts and supports a transparent background. If every photo you added is a PNG, the starting format is PNG.
• JPG: gives a much smaller file than PNG for photo-heavy results. It can't store transparency, so transparent areas are filled with white. Quality runs from 50 to 100%, starting at 90%.
• WebP: lossy compression with a quality setting that also supports transparency. It can't be used when a side goes over 16,383px, and if the browser can't create WebP, the image is saved as PNG and you are told.

The file size in the result line is not an estimate; it is measured by actually creating the file with your current settings. For large results over 16 megapixels the calculation takes long, so the size is set when you save. Even 100% quality doesn't mean identical to the original, because the photos are resized, redrawn, and compressed again.

Common mistakes

• Reading the size field as the final size: in Stack vertically, 1080 is the photo width. With a 20px outer margin the saved width is 1,120px. The number in the result line is the real saved size.
• Scrolling too far between captures: if two captures share no rows, there is nothing to remove, so they are joined as they are and the content in between is missing. When you take the next capture, make sure a few rows from the bottom of the previous one show again.
• A moving ad or video sits in the overlapping area: its pixels differ between the two captures, so the overlap may not be found. If no seam marker appears, enter a value in Trim top yourself.
• Faces or text cut off by Fill cell: drag the photo on the stage to move the part that stays, or switch to Show whole photo. Justified rows never crops.
• Choosing a transparent background but saving as JPG: JPG has no transparency, so the background turns white. Save as PNG or WebP if you need transparency. A white background painted into the original photo does not become transparent.

Where are my photos processed?

Reading the photos, merging them, and creating the file all happen inside this browser. Photos are not sent to a server to be merged, and your original files are never changed or deleted. Remove and Clear only take photos out of this session. The work is not saved automatically, so save the result before you close the page.

Captures of chats and order histories often contain names, phone numbers, and addresses. Merging photos doesn't hide personal information, so open the result and check it before you share it. The saved file is a newly created image and doesn't carry over the photo information (EXIF).

Limitations

• It doesn't warp overlapping parts to fit, as a panorama does. Remove capture overlap only finds captures where the same rows appear unchanged above and below; it doesn't search for horizontal overlap or for photos taken at a different angle.
• It doesn't do free editing such as layering photos or placing text and stickers on top. Add text first with a tool like a text-on-photo tool.
• If you add an animated GIF or WebP, only the first frame is used and the result is a still image.
• If you refresh or close the page, the work is gone.
• Result limits and supported save formats differ by browser, and the tables above show values checked on 2026-10-20.

As of 2026-10-20, the relevant statements in the documents below were checked. The photo count, file size, and 50-megapixel limit are this tool's own limits.

Sources

• 01MDN — <canvas>: Maximum canvas sizeThe maximum size differs by browser; iOS devices allow 4,096 × 4,096 pixels, and drawing commands stop working beyond it
• 02canvas-size — Test ResultsChrome 73+ allows 65,535 per side and Firefox 122+ 32,767; area 268,435,456; mobile Safari 16,777,216
• 03Google for Developers — WebP FAQThe maximum pixel size of a WebP image is 16383 × 16383
• 04WHATWG — HTML Living Standard, toBlob()The default format is PNG, and requesting an unsupported format also gives PNG; quality is 0.0 to 1.0
• 05MDN — createImageBitmap()imageOrientation defaults to from-image: the image is rotated according to its EXIF orientation
• 06WebKit — WebKit Features in Safari 17.0Safari 17.0 added support for HEIC images
• 07MDN — Using files from web applicationsHow a web page reads, inside the browser, files that the user chose or dropped

Frequently asked questions

Tools to use with it