Code · Made a little simpler

Duplicate File Finder in Archives

Scan local ZIP and TAR.GZ files for byte-identical entries. Compare archive paths, SHA-256 hashes and repeated logical bytes in a JSON report.

Free to useNo account neededProcessed on your device
Your workspaceProcessed on your device

Add this tool to your website

Paste this code into your page to add the tool and a visible ToolMellow credit link.

HTML embed code
Preview embed

Duplicate File Finder in Archives: how to use it

  1. Select one or more local ZIP or TAR.GZ files, or load the two-archive example.
  2. Scan for duplicates. Review each confirmed group and its source archives and paths.
  3. Read any failed-source findings and download the duplicate JSON report.

Limits and notes

Use up to eight archives, 65 MB of input, 1,000 entries and 60 MB of indexed file data combined. Each member is limited to 30 MB. Expanded TAR containers share a 64 MB cap. Uses safe paths, Stored or Deflate ZIP and locally readable TAR.GZ.

How your privacy works →

Duplicate File Finder in Archives: common questions

Can files with different names be duplicates?

Yes. Both the SHA-256 and every expanded byte must match. Names and paths identify where each copy appears.

What does repeated logical bytes mean?

It counts the expanded size of copies after the first one in each group. Actual archive savings depend on compression and archive overhead.

What does a partial scan mean?

At least one source or member failed to read. Groups cover the successfully read files, and the report labels the failures.

Guides