What does this ZIP junk file cleaner do?
This tool reads ZIP entry paths in browser memory and checks them recursively for known operating-system clutter: .DS_Store, __MACOSX, AppleDouble files beginning with ._, Thumbs.db, desktop.ini, .Spotlight-V100, .Trashes, .TemporaryItems, and .fseventsd. It shows each match with its path, size, and matching rule, then creates a rebuilt ZIP and a removal manifest.
Review entries before rebuilding
The cleaned preview updates automatically as you review entries and change removal settings. Detected junk and custom matches default to "Exclude". Encrypted entries are also locked to "Exclude" because they cannot be safely rebuilt. Other entries can be reviewed with the table checkboxes. Use Exclude all detected junk or Keep everything for bulk choices, and use Search entries by path… or the filter chips to find entries by status or warning.
Add custom removal patterns
Add a glob pattern using * and ?, then choose whether it matches the entry's file name or full path. Overly broad or too-short patterns are rejected. Custom matches are shown for review and default to "Exclude", but you can re-include them before rebuilding.
Warnings and rebuilding limitations
- Unsupported/encrypted archives - invalid ZIP files or archives whose central directory cannot be parsed are reported as unsupported. Encrypted entries are locked to "Exclude" and listed as skipped in the manifest.
- Duplicate paths - only subsequent case-insensitive duplicates are flagged. Treat this as a review warning; the controls do not guarantee reliable independent selection of each duplicate occurrence.
- Unsafe paths - absolute paths, Windows drive-letter paths such as
C:, and paths containing..segments are flagged for review. - Rebuild results - readable entries you keep are re-added with their path and content, but some entries can fail to copy. The result and manifest list those failures.
- Compression and ZIP metadata - the archive is freshly assembled, so ZIP-level compression settings may differ. Comments and some ZIP-level extras are not preserved verbatim.
How to get the cleaned archive
- Drop a ZIP file onto the drop zone or click browse file.
- Review the detected junk entries and any warnings; nothing is removed yet.
- Adjust individual keep/exclude choices, or add a custom pattern if you need to remove something else.
- Review the automatically rebuilt result, then download the cleaned ZIP and manifest.
- Download the cleaned ZIP and the removal manifest, which lists removals, skipped encrypted entries, and any copy failures.
Privacy and scope limits
Your ZIP is read, reviewed, and reassembled in browser memory. The source file is not overwritten, and the cleaned ZIP and manifest are separate downloads. The tool handles one archive at a time and detects filename and path patterns only; it does not scan for malware or guarantee that an archive is otherwise clean.
Frequently asked questions
What counts as "junk" here?
Only well-known OS-generated clutter - .DS_Store files, __MACOSX directories, AppleDouble files beginning with ._, Thumbs.db, desktop.ini, and the .Spotlight-V100, .Trashes, .TemporaryItems and .fseventsd directories - detected recursively anywhere in the archive. It never removes ordinary project files by default; anything else stays unless you add a custom pattern or manually exclude it.
Does it extract my ZIP to disk?
No. Entries are read into browser memory and a new archive is assembled there. Nothing is written to your filesystem except the two files you explicitly download: the cleaned ZIP and the removal manifest.
Will it overwrite my original ZIP?
No. Your source file is only read. The cleaned archive is downloaded separately as a new file; your original is left untouched on your device.
What about encrypted or unsupported archives?
Password-encrypted entries are detected and locked to "Exclude" because their content can't be safely read and rebuilt in the browser; they're listed in the removal manifest as skipped. Files that aren't valid ZIP archives, or whose central directory can't be parsed, are reported as unsupported.
Can I add my own removal patterns?
Yes, using simple glob patterns (* and ?) matched against either the file name or the full path. Overly broad patterns are rejected. Custom-matched entries are shown and excluded by default, but you can review and re-include them.
How is this different from Metadata Remover or a ZIP repair tool?
This tool only removes known OS clutter entries from inside an otherwise usable ZIP and hands back a rebuilt copy - it doesn't touch embedded file metadata, which is what Metadata Remover does, and it doesn't attempt to fix corrupted or malformed archive structures.