Loading page
About this tool
Selectively remove, reorder and recompress entries inside a ZIP or TAR archive.
The ZIP/TAR Archive Surgeon opens a ZIP file in your browser, lists every entry with its uncompressed size and readability status, and rebuilds the archive without the entries you name — recompressed with DEFLATE at level 6 and downloaded as altftool-rebuilt.zip. Entries are verified with a CRC32 check as they are read, so anything encrypted or corrupt is flagged rather than silently dropped. Note that the current build reads ZIP containers only; TAR archives are not parsed.
Open ZIP/TAR Archive Surgeon on AltFTool — it loads instantly in your browser.
Choose your ZIP under Local file(s) — it is parsed in the browser with JSZip and every entry is CRC32-checked as it is read.
Paste the exact entry paths to drop into 'Archive entry names to remove', comma- or newline-separated, then press Run local workbench.
Review the entry table of name, byte size, Readable or Encrypted-or-unreadable status and Keep/Remove; the rebuilt archive downloads as altftool-rebuilt.zip at DEFLATE level 6.
Paste the exact entry names to drop, comma- or newline-separated, and get a rebuilt ZIP back; everything else keeps its original path inside the archive.
Each member is decompressed and checksummed, so damaged or password-protected entries surface as 'Encrypted or unreadable' in the table rather than failing quietly.
Every entry is listed with its byte size, whether it is a directory or a file, and whether this run will keep or remove it — a review pass before anything is written.
No — despite the name, the current implementation loads ZIP containers only. TAR, tar.gz and 7z files are not parsed, so use a ZIP or repackage first.
Load the archive, then paste the exact entry names into the removal box, separated by commas or line breaks. Names must match the path as stored inside the archive, including any folder prefix such as docs/old.pdf, and the rebuilt ZIP downloads automatically.
No. The ZIP is parsed and rebuilt entirely in your browser with JSZip, and the output is generated as a local blob download. Nothing is transmitted, which is why large archives are limited only by your own device memory.
Yes — every kept entry is recompressed with DEFLATE at level 6, a balanced middle setting, rather than preserving each entry's original compression method. Stored (uncompressed) members and already-compressed media may therefore come out at a slightly different size.