Skip to content
Aback ZIP

Merge ZIP

Merge two or more ZIP archives into one. Choose how duplicate names are handled (rename, keep first, keep last), skip identical duplicates, or keep each archive in its own folder. Entries are copied without recompression.

Merge ZIP

Combine ZIP archives into one. Order matters for conflict handling: earlier archives come first.

Processed locally

Drop two or more ZIP files

You can add more and reorder them next

Files stay on your device. Nothing is uploaded.

How to use Merge ZIP

  1. 1

    Add the archives

    Drop two or more ZIP files, or choose them with the file picker. You can add more at any time.

  2. 2

    Set the order

    Drag archives into the order you want. The order decides which archive counts as “first” and “last” when names clash, and the order entries are added in.

  3. 3

    Choose conflict handling

    Rename duplicates (default), keep the first copy or keep the last. Optionally skip identical duplicates or put each archive in its own folder.

  4. 4

    Merge and download

    Download the merged ZIP along with a report of every entry that was renamed or skipped.

Why use Aback ZIP's Merge ZIP?

No recompression

Entries are copied from the source archives exactly as they are stored, never decompressed and compressed again. Merging is quick and file data is untouched.

Predictable duplicates

When two archives contain the same path, you choose what happens and the result is always the same for the same inputs. Nothing is overwritten silently, and every rename or skip is listed.

Folder per archive

Put each source ZIP's contents in a folder named after it, so a.zip and b.zip become a/ and b/ and nothing can collide.

Encrypted entries stay encrypted

Password-protected files are copied as they are and keep their original password. You don't need to unlock them to merge.

Common use cases

Multi-part photo exports

Cloud photo and account exports often arrive as several numbered ZIPs. Merge them into one archive so the library is in one place.

CI artifacts from several jobs

Windows, macOS and Linux build jobs each produce a ZIP. Merge them with one folder per archive to get a single release bundle.

Collected submissions

Combine the ZIPs each student or team member sent into one archive, each kept in its own folder, for marking or archiving.

Incremental backups

Merge backups from different days. “Skip identical duplicates” drops files that didn't change, and “keep last” keeps the newest version of those that did.

Monthly document bundles

Turn twelve monthly invoice or statement ZIPs into one archive for your accountant, with any same-named files renamed rather than lost.

Reassemble split parts

Got project.part01.zip, project.part02.zip… from Split ZIP? Merge them back into one archive with all the files.

About Merge ZIP

How name conflicts are resolved

Say docs/report.pdf exists in both a.zip and b.zip, with a.zip first in the list:

OptionResult
Rename (default)docs/report.pdf from a.zip and docs/report (1).pdf from b.zip
Keep firstOnly the copy from a.zip
Keep lastOnly the copy from b.zip
Folder per archivea/docs/report.pdf and b/docs/report.pdf, no conflict at all

Skip identical duplicates (on by default) handles the common case of the same file appearing twice: if both copies have the same path, size and CRC-32, they are treated as the same file and only one is kept. Every rename and skip appears in the report.

Why merging is fast and lossless

A ZIP stores each file as an independent compressed record. Merging copies those records into a new archive and writes a fresh index, without touching the compressed data. File contents come out exactly as they went in. The merged archive itself is a new file, so it is not byte-identical to any of the inputs.

Have .001, .002 or .z01 pieces of a single archive rather than separate complete ZIPs? Those need joining, not merging: use Join ZIP Parts.

What is kept and what changes

ItemResultNotes
File contentsPreservedCompressed data is copied without recompression.
Folder structurePreservedPrefixed with the archive name when “folder per archive” is on.
Modification timesPreserved
EncryptionPreservedEach encrypted entry keeps the password it had.
Duplicate pathsChangedRenamed or skipped according to your choice, and listed in the report.
Archive fileRebuiltA new ZIP with a new index; contents are equivalent, the file is not byte-identical.

Limitations

  • Encrypted entries keep their original passwords. If the source archives used different passwords, the merged ZIP will need different passwords for different files, which many extractors handle poorly. Consider removing the passwords first and protecting the merged result with one password.
  • Entries are copied without being decompressed, so damage in a source archive is carried over. Run Test ZIP Integrity on sources you don't trust.
  • All inputs are processed in browser memory. There is no fixed limit on size or count, but merging several gigabytes may fail on phones and low-memory devices.
  • Only ZIP archives can be merged. Convert TAR or TAR.GZ archives with TAR to ZIP first.

Processing happens locally in your browser. Your files are not uploaded, and closing the tab discards everything.

Merge ZIP: frequently asked questions

No. The archives are read and combined in a Web Worker in your browser, and the merged ZIP is created on your device. Nothing is sent to a server and no account is needed.