Clean
Clean ZIP — Remove Hidden System Files
When you create a ZIP on a Mac or Windows computer, system metadata files are automatically included. These clutter the archive and can cause issues with upload portals and recipients. This tool finds and removes them, then rebuilds a clean ZIP.
Input formats
Output formats
Common uses
- Clean a ZIP before sending to a client
- Remove __MACOSX before uploading to a form or portal
- Prepare a ZIP for professional delivery
- Remove Thumbs.db before sharing with Mac users
- Clean up a ZIP downloaded from a Mac user
Limitations
- Only ZIP files are supported in the browser. For RAR or 7Z, convert to ZIP first.
- Custom hidden files not matching standard patterns must be removed manually.
When a clean ZIP actually matters
Mac and Windows quietly inject metadata into archives: macOS adds a __MACOSX folder and .DS_Store files, Windows leaves behind Thumbs.db and desktop.ini. Inside your own machine these are invisible, but the moment a ZIP leaves it they become visible clutter — and sometimes a real obstacle. This tool strips that junk and rebuilds a clean archive, so the recipient opens exactly the files you meant to send and nothing else.
The use cases that genuinely fit are sharing and delivery scenarios. Sending a deliverable to a client where a stray __MACOSX folder looks unprofessional; uploading to a submission portal or web form that rejects or chokes on hidden entries; preparing a source-code or asset bundle for a Windows or Linux colleague who has no use for Mac resource forks; or tidying a ZIP you received from someone else before passing it on.
It is equally useful for cross-platform handoffs in office and dev work — a Mac designer sending assets to a Windows team, or a Windows user removing Thumbs.db before a ZIP reaches Mac reviewers. The goal is modest and concrete: a smaller, tidier archive whose contents match what a recipient on any operating system can actually use.
The flow, the options, and the boundaries
Drop or select a .ZIP file (up to roughly 300 MB), and the tool reads the archive in your browser. You then see a checklist of what to remove: .DS_Store, __MACOSX, Thumbs.db, and desktop.ini are enabled by default, with two optional toggles for all dot-prefixed hidden files and for empty folders. A separate, off-by-default section offers filename cleanup — replacing special characters, converting spaces to hyphens, and lowercasing names — with long names truncated to 80 characters. Click Clean ZIP and a rebuilt <name>-clean.zip downloads automatically, alongside a summary of how many entries were removed or renamed and the before/after size.
Supported input and output are both ZIP only. RAR and 7Z are not handled — convert those to ZIP first. The four standard categories match by exact pattern (for example, any path ending in .DS_Store, or anything inside __MACOSX/), so they are conservative and predictable.
What it does not do: it will not edit, recompress, or re-organize your real files, it does not preserve the original archive (it generates a fresh one), and it cannot read inside password-encrypted ZIPs — encrypted entries are unreadable, so cleaning is not possible without first removing the password. Anything that does not match a standard junk pattern must be removed with a dedicated remove-files tool instead.
Pitfalls worth knowing before you click
The biggest trap is the optional Hidden files checkbox. It removes every entry whose name starts with a dot — which sweeps up legitimate files such as .gitignore, .env, .htaccess, and .editorconfig, not just metadata. Leave it off unless you are certain the archive contains no dot-files you need; the four default categories already cover ordinary system junk.
Filename cleanup is powerful and therefore easy to over-apply. Lowercasing and special-character replacement change the actual stored paths, which can break things that depend on exact names — case-sensitive servers, code imports, or links between files inside the bundle. The 80-character truncation can also collide two long names into the same result. Treat these toggles as deliberate choices, not defaults.
Two smaller points: the rebuilt ZIP is a new file with standard compression, so the byte size may differ slightly even beyond the junk you removed, and the on-screen list of removed paths shows only the first twenty. And because only ZIP is supported, feeding a RAR, 7Z, or already-encrypted archive will simply fail to load rather than clean.
Checking the result before you send it
Open the downloaded <name>-clean.zip and confirm the structure first: the __MACOSX folder and any .DS_Store, Thumbs.db, or desktop.ini entries should be gone, while every document, image, and code file you intended to keep is still present and in the right folder. Cross-check the removed/renamed counts in the summary against what you expected — a surprisingly high number is a sign the Hidden files or cleanup toggles caught more than you wanted. If you enabled filename cleanup, scan for renamed files and make sure nothing your project references by exact name was altered.
If hidden files you needed are missing, or names changed in ways that broke something, simply re-run from the original ZIP with those toggles off. The original on your disk is untouched, so you can iterate freely.
For official, financial, or legal deliverables, do a manual verification pass: extract the cleaned archive fully and confirm file count, names, and contents by hand rather than trusting the summary alone. This tool removes system metadata only and makes no guarantee about the correctness or completeness of your underlying documents — that responsibility stays with you before the archive goes out.
Frequently asked questions
__MACOSX is a folder Apple's Archive Utility adds to ZIPs created on macOS. It stores Mac-specific resource forks and extended attributes. Windows and Linux users cannot use this data, so it is safe to remove.
.DS_Store files are macOS directory metadata files that track folder appearance settings. They are harmless but useless outside macOS and are safe to remove from ZIPs before sharing.
Thumbs.db is a Windows thumbnail cache file. It stores small preview images for folders. It is useless outside Windows and safe to remove.
No. Only system metadata files are removed. Your documents, images, code, and other files are untouched.
Yes. The tool shows checkboxes for each junk file category so you can control exactly what is removed.
Related tools
Tool last reviewed: June 30, 2026 · Report a problem