Skip to content
Aback ZIP

Clean ZIP

Strip clutter from a ZIP: macOS metadata (__MACOSX, .DS_Store, ._ files), Windows Thumbs.db and desktop.ini, version-control folders, editor files, dependency folders, empty folders, or anything matching your own patterns. Optionally unwrap a single top-level folder.

Clean ZIP

Strip clutter that other operating systems and tools leave behind. Preview exactly what goes before you run it.

Processed locally

Drop the ZIP you want to clean

or choose one from your device

Files stay on your device. Nothing is uploaded.

How to use Clean ZIP

  1. 1

    Open the ZIP

    Drop the archive you want to clean, or choose it with the file picker.

  2. 2

    Choose what to remove

    Tick presets for macOS, Windows, version control, editor files, dependencies and empty folders, or add your own patterns such as *.log.

  3. 3

    Preview the removals

    See the exact list of files and folders that will be removed before anything changes.

  4. 4

    Clean and download

    A new ZIP is written without the junk. Everything you keep is copied without recompression.

Why use Aback ZIP's Clean ZIP?

macOS clutter, gone

Removes __MACOSX/, .DS_Store, ._ AppleDouble files and Spotlight folders, the things Windows and Linux users see as junk in archives made on a Mac.

Preview before removing

Every matched file is listed before you clean, so a pattern never removes something you wanted to keep.

Developer presets and patterns

Strip .git/, node_modules/, __pycache__/, .idea/ and similar in one go, or write patterns like *.log or build/** for anything else.

Unwrap the extra folder

Archives that contain one folder holding everything else can be flattened by one level, so extracting doesn't create project/project/.

Common use cases

Mac to Windows handoffs

You zipped a folder in Finder and the Windows recipient sees a __MACOSX folder full of ._ files. Clean the archive before sending it.

Sending source code

Remove node_modules/, .git/ and .venv/ before submitting an assignment or sharing a project. They are often most of the archive's size, and the recipient can reinstall dependencies anyway.

Plugin, theme and extension packages

Upload validators and store reviewers can flag hidden files like .DS_Store or editor folders. Strip them so the package contains only what it should.

Professional client deliveries

A delivery with Thumbs.db, desktop.ini and .DS_Store scattered through it looks careless. Clean it in one pass.

Fix the double folder

Extracting report.zip gives report/report/…? Unwrap the single top-level folder so files land one level higher.

Consistent timestamps

Set every entry to one date so archives built from the same files don't differ only because file times changed.

About Clean ZIP

What each preset removes

PresetRemoves
macOS__MACOSX/, .DS_Store, ._* AppleDouble files, .Spotlight-V100 and similar system folders
WindowsThumbs.db, desktop.ini, $RECYCLE.BIN
Version control.git/, .svn/, .hg/
Editor files.idea/, .vscode/, *.swp, *~
Dependencies & cachesnode_modules/, __pycache__/, *.pyc, .venv/
Empty foldersFolders with nothing left in them after cleaning

Custom patterns use familiar glob syntax: *.log for log files, build/** for everything under a build folder. Check the preview to confirm a pattern matches what you expect.

Where __MACOSX and ._ files come from

macOS keeps some file information, such as Finder tags, custom icons and download quarantine flags, outside the file's own data. When Finder's “Compress” creates a ZIP, it saves that information as ._filename files in a __MACOSX/ folder so Archive Utility can restore it later. Other systems don't use it and show it as clutter. .DS_Store files store Finder window settings for each folder.

Removing them doesn't change any file's contents. The only loss is that Finder-specific metadata, such as tags, won't be restored when a Mac user extracts the cleaned archive.

What is kept and what changes

ItemResultNotes
Files you keepPreservedCopied without recompression.
Matched junk files and foldersRemovedExactly the entries shown in the preview.
Folder structurePreservedMoved up one level if you unwrap the top-level folder.
Modification timesOptionalKept, or all set to one date if you choose.
Archive fileRebuiltA new ZIP; your original is not modified.

Limitations

  • Presets and patterns match names and paths, not contents. Junk with an unusual name needs a custom pattern.
  • Removed items are gone from the cleaned copy, including version history in .git/. Your original archive is not changed, so keep it if you might need them.
  • Mac users extracting the cleaned archive won't get Finder tags or custom icons back.
  • The archive is processed in browser memory. There is no fixed size limit, but multi-gigabyte archives may fail on phones and low-memory devices.

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

Clean ZIP: frequently asked questions

No. The archive is read and rewritten in your browser, and the cleaned ZIP is created on your device. Nothing is sent to a server and no account is needed.