ZIP Creator
Create a ZIP locally with editable archive paths, Store or Deflate compression, and exact file bytes.
This tool runs entirely in your browser. Your data is never uploaded, never stored, and never leaves your device.
Create an unencrypted ZIP from local files, with editable relative paths and Store or Deflate compression, preserving each file's exact bytes.
How to use it
- 1Choose up to 100 local files, at most 8 MiB each and 32 MiB combined.
- 2Review and edit archive paths; remove unwanted entries.
- 3Choose compression, create the ZIP and download it.
Example
- Input
- a.txt: ABC (3 bytes) empty.txt: 0 bytes Store mode
- Output
- a.txt extracts as ABC (3 bytes) empty.txt extracts as 0 bytes
Archive headers add overhead; empty files are retained.
What happens to your data
Files and archive paths are processed in browser memory. No contents are uploaded; downloaded ZIPs retain your data and are not encrypted.
Last updated October 2026
Create a standard ZIP archive from local files without uploading their contents. Review the file list, edit each archive path, then choose Deflate compression or Store mode before downloading. This is useful when an application portal, email recipient or project handoff needs several files packaged together.
The creator keeps file contents byte-for-byte, including empty files and binary data. It checks names before writing the archive so one file cannot silently replace another. It does not add passwords, encrypt contents or preserve filesystem metadata.
How it works
Choose one or more local files. Every new selection replaces the current list rather than appending implicitly. You may remove individual files or edit their archive paths before building. A path such as reports/summary.txt places the file under a folder when extracted; folders are represented by file paths, without separate empty-directory entries. Folder picking and an archive with zero files are not supported.
Choose Deflate to compress at level 6, or Store to bundle without compression. Deflate is lossless: decompressing an entry restores its original bytes. Already compressed images, videos and archives may shrink little, stay similar in size or become slightly larger. There is no guaranteed compression percentage. Archives use a fixed 1 January 2000 timestamp and standard non-executable file permissions. Numeric-only paths may be enumerated before other names, and ZIP readers can display entries in a different order; use explicit names when order matters. Original modification times, permissions, extended attributes, symlinks and empty directories are not retained. ZIP metadata and filename interpretation can vary among extraction applications; test your recipient's workflow when names or structure are important.
Paths must use forward slashes and contain 1–240 UTF-8 bytes. Absolute paths, backslashes, drive prefixes, empty segments, dot and parent-directory segments, control characters, reserved Windows device names and characters unsafe on common Windows filesystems are rejected. Leading or trailing segment spaces and trailing dots are rejected too. Names that differ only by case or NFC Unicode normalization cannot coexist, because they can collide on a receiving filesystem. A file named reports cannot coexist with reports/summary.txt. These checks prioritize portable packaging over accepting every name your operating system allows; rename an incompatible entry explicitly. Original accepted spelling is retained.
Limits are 100 files, 8 MiB per file and 32 MiB of combined uncompressed contents. The output budget adds up to 1 MiB of archive overhead. File contents are read and archived in memory; large jobs can still consume more memory than their input size. Use a desktop archive utility for larger datasets, directory trees, metadata preservation, encryption or a different archive format. ZIP64, split archives, TAR and 7z are outside this tool's workflow.
For example, a.txt containing the three ASCII bytes ABC and empty.txt containing zero bytes produce two ZIP file entries. Extracting a.txt returns ABC, and empty.txt remains present with zero bytes. Store mode does not compress these contents; Deflate may add overhead on such tiny inputs.
Creating an archive does not make its contents safe or confidential. The file names and bytes remain available to anyone with the ZIP. Review the source files, protect sensitive downloads and scan untrusted files using appropriate software. Toolvore does not inspect documents for malware or provide password protection.
Processing happens in your browser. No file contents or archive paths are submitted by the tool. Editing names, removing files, changing compression or selecting a new input removes the previous download. Late file reads or archive builds cannot replace newer edits. Closing the page releases the in-memory working copy; downloaded files remain on your device.
Worked example: Keep an empty file while packaging two entries
- Input
- a.txt: ASCII bytes ABC (3 bytes) empty.txt: no bytes (0 bytes) Compression: Store
- Result
- a.txt → 3 extracted bytes: ABC empty.txt → 0 extracted bytes
ZIP headers add overhead. This example describes the independently verified extracted entries, not an estimated archive size.
Common use cases
- Packaging several application documents into one upload
- Creating a project handoff with explicit relative paths
- Bundling binary fixtures together with empty-file test cases
- Grouping local files without sending their contents to an archive server
Frequently asked questions
Are my files uploaded?＋
The archive is created in browser memory. The tool does not send file contents or archive paths to a server. Downloaded ZIPs still contain your information and should be handled accordingly.
Can I password-protect or encrypt the ZIP?＋
No. The creator produces an unencrypted standard ZIP. Use an appropriate desktop archive tool when confidentiality requires encryption.
Why is my ZIP larger than the input?＋
ZIP adds headers and file-name metadata. Compression also has overhead, and already compressed files may not shrink. Store mode bundles exact bytes without attempting compression.
Can I add folders or duplicate names?＋
You can edit a file's relative path, such as reports/a.txt. Empty directories and folder picking are unsupported. Duplicate or conflicting paths, including case and NFC-normalization collisions, are rejected rather than overwritten.
Are original dates and permissions preserved?＋
No. Entries use a fixed timestamp and standard non-executable permissions. This is a file-packaging tool, not a full-fidelity filesystem backup.
What are the limits?＋
Up to 100 files, each at most 8 MiB, with at most 32 MiB of combined contents. The archive is built in memory; use desktop software for larger jobs or metadata-sensitive backups.
Related tools
ZIP Extractor
Inspect supported ZIP archives and extract files with explicit path, integrity and expansion limits.
File Hash Checker
Get SHA-1, SHA-256 and SHA-512 checksums for a file, then paste the expected value to confirm a match.
GZIP Compress / Decompress
Compress a file to GZIP or decompress a supported .gz file, then download the exact output bytes.
File Type Checker
Inspect recognized file signatures, extensions and browser MIME without opening or uploading the file.