ZIP Editor
Edit an existing ZIP without unpacking it: rename files and folders, delete entries, add new files, and change the archive comment. Untouched files are copied byte-for-byte, so editing is fast even for large archives.
ZIP Editor
Stage your changes, then save once. Nothing changes until you save, and the original file is never modified.
Drop the ZIP you want to edit
or choose one from your device
Files stay on your device. Nothing is uploaded.
How to use ZIP Editor
- 1
Open the ZIP
Drop the archive you want to change. Its files and folders appear as an editable tree.
- 2
Make your changes
Rename files or folders, delete what you don't want, add new files, and edit or clear the archive comment.
- 3
Save a new copy
A new ZIP is written with your changes. Everything you didn't touch is copied across byte-for-byte, then you download the edited archive.
Why use Aback ZIP's ZIP Editor?
No unzip, no re-zip
Edit the archive directly instead of extracting everything, changing it on disk and compressing it all again. Unchanged files are copied as stored, so even large archives save quickly.
Folder-aware renaming
Rename a folder and everything inside moves with it. Delete a folder and its contents go too, so the tree always stays consistent.
Add or replace files
Add new files anywhere in the tree. Adding a file at a path that already exists replaces the old version, which is the quickest way to update one file in a big archive.
The rest stays untouched
Files you don't change keep their exact compressed data. Editing is processed locally in your browser, and your files are not uploaded.
Common use cases
Remove something sent by mistake
Take out an .env file, internal notes or a draft before forwarding an archive to a client, without rebuilding it from scratch.
Update one file in a big archive
Replace a corrected PDF or a config.json inside a 2 GB delivery. Only the new file is compressed; everything else is copied as is.
Fix a plugin or theme folder name
WordPress installs a plugin into the folder name inside its ZIP. Rename my-plugin-main/ to my-plugin/ so updates land in the right place.
Add a README or LICENSE
Drop a missing README.md, LICENSE or changelog into a release archive at the right path.
Tidy names before delivery
Fix typos and inconsistent naming like final_FINAL_v3.docx so the client receives a clean, professional archive.
Patch a mod or asset pack
Swap a single texture, sound or config file inside a game mod or asset ZIP without unpacking hundreds of files.
About ZIP Editor
How editing a ZIP works
Each file in a ZIP is an independent compressed record, so an archive can be rebuilt without recompressing anything. The editor writes a new archive in which unchanged entries are copied byte-for-byte, renamed entries keep their data under the new name, added files are compressed as they go in, and deleted entries are simply left out. A fresh index is written at the end.
Browsers can't overwrite files on your disk, so the original ZIP stays exactly as it was. You download the edited archive as a new file.
Rules worth knowing
- Renaming a folder renames the path of every file inside it.
- Deleting a folder deletes everything inside it.
- Adding a file at a path that already exists replaces the existing file.
- Names are written as UTF-8, so accented, Cyrillic, CJK and emoji names display correctly in modern extractors.
- The archive comment can be kept, edited or cleared.
Removing lots of junk at once, such as __MACOSX/ or node_modules/? Clean ZIP does it with presets and patterns instead of one file at a time.
What is kept and what changes
| Item | Result | Notes |
|---|---|---|
| Unchanged entries | Preserved | Copied byte-for-byte without recompression. |
| Renamed entries | Changed | New path, same data. |
| Deleted entries | Removed | |
| Added files | Changed | Compressed and added; an existing file at the same path is replaced. |
| Archive comment | Optional | Kept, edited or cleared as you choose. |
| Archive file | Rebuilt | A new ZIP with a new index. Your original file is not modified. |
Limitations
- The editor changes the archive's structure, not file contents. To change text inside a file, edit it on your computer and add it back to replace the old version.
- Browsers can't save over the original file, so you download an edited copy.
- 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.
Related tools
ZIP Editor: frequently asked questions
No. The archive is opened and rewritten in your browser, and any files you add are read locally. Nothing is sent to a server and no account is needed.
Open the ZIP here, delete the file or folder in the tree, and save. The new archive contains everything else, copied without recompression, and the deleted entry is gone.
Open the ZIP, add files where you want them in the tree, and save. If a file already exists at that path, the new one replaces it. The rest of the archive is copied unchanged.
Yes. Renaming a folder changes the path of everything inside it, so old-name/src/app.js becomes new-name/src/app.js. This is handy for fixing the top-level folder name of plugins, themes and project downloads.
No. Entries you don't change are copied byte-for-byte, including their compressed data, so their contents are exactly the same as before.
No. Your original file is only read. The edited archive is a new file that you download and can keep alongside the original or use to replace it.
Not directly; this is an archive editor, not a text editor. Extract the file with Extract ZIP, edit it, then add it back here at the same path to replace the old version.