- ZIP archive and entry comments
- Variable entry timestamps
- Supported metadata in recursively selected embedded files
- Supported package properties when the ZIP is actually Office or EPUB
ZIP SHELL METADATA CLEANER
Remove ZIP comments and timestamps
A ZIP archive has metadata in its shell and may contain files with their own metadata. KillMetadata resets supported entry timestamps and comments, then optionally processes supported embedded files within strict depth, entry-count and compression-ratio limits.
THE CLEANING PLAN
Remove what exposes you. Keep what makes the file work.
Every field is shown before the rewrite and classified by action and coverage.
- File names and directory structure
- Entry contents by default
- Compression method where pass-through is safe
- Unsupported embedded files with a partial warning
- A guarantee for arbitrary embedded formats
- Encrypted archives
- ZIP bombs and unsafe paths
- Recursion beyond depth 3, 10,000 entries or 100:1 ratio
WHY THE ENGINE MATTERS
Cleaning the wrapper is not the same as cleaning every file
The default ZIP rewrite covers shell metadata only and therefore remains partial when embedded content is not inspected. Optional recursion invokes supported handlers for nested files.
Unsafe paths, encryption, excessive expansion ratios and entry counts are rejected. Any unsupported nested carrier keeps the result partial.
Explore the complete verification methodology →BEFORE YOU SHARE
A four-step privacy check.
Metadata cleaning is one part of a safe sharing workflow.
- 01Decide whether shell-only or recursive cleanup is needed
- 02Review unsupported embedded files
- 03Create the rebuilt ZIP
- 04Acknowledge partial only after reading every gap
QUESTIONS, ANSWERED
Know the boundary before you clean.
No vague “100% clean” claim.
Are my files uploaded?
No. The cleaner runs in your browser, has no upload endpoint, and only enables the file picker after its processor assets are available locally.
Is the original file changed?
No. KillMetadata reads the original and creates a separately named cleaned copy. It never overwrites the source file.
Does ZIP cleanup remove metadata inside every file?
Not by default. Shell cleanup resets archive metadata. Optional bounded recursion cleans supported embedded files; unsupported entries keep the result partial.
What safety limits apply?
Recursion stops at depth 3. The 10,000-entry and expanded-data budgets are shared across the whole operation, 100:1 is enforced per entry, and device-specific working-memory limits apply.
Runs locally in your browserReady to inspect your file?
Inspect this file type The picker opens only after offline protection is active.