b2KIT

ZIP File Creator

Create ZIP archives from multiple files entirely in the browser with compression level control.

Tested tool guide Tested browser tools Checked August 16, 2026

What ZIP File Creator does, with a checked example

A ZIP file is a container: a list of entries, each holding a filename, a CRC-32 checksum, and data that is either copied verbatim or deflated. This tool builds that container from files you drop in, lets you set a compression level from store to maximum, and downloads the finished archive. Everything runs in the browser, so the files never leave your machine. The surprise most people hit: compression is lossless and per-file, so already-compressed formats such as JPEG, PNG, and MP4 shrink almost nothing, and cranking the level up for them only costs time.

Worked example

A concrete input and expected output from the current implementation.

Input

One text file named hello.txt of exactly 1000 bytes, with the compression level set to Store (0).

Expected output

archive.zip of 1116 bytes, containing hello.txt byte-for-byte unchanged.

At level 0 the file data is copied, not compressed, so the archive is the original 1000 bytes plus fixed structural overhead: 39 bytes for the local file header and filename, 55 for the central directory entry, and 22 for the end-of-central-directory record (39 + 1000 + 55 + 22 = 1116). This assumes the minimal layout with no extra fields; some creators add timestamp extra fields, which shifts the total by a few dozen bytes.

How the result is produced

1

Archive layout

Each file is compressed with DEFLATE at the chosen level, or copied unchanged at level 0, and a CRC-32 checksum is computed over the original bytes. The output follows the ZIP layout: a local header and data per file, then a central directory listing every entry with offsets, then an end-of-central-directory record. Extractors verify each entry's checksum, so a damaged archive fails loudly instead of producing silently wrong files.

2

Compression levels

Level 0 stores data as-is and is effectively instant. Levels 1-9 run DEFLATE with increasing matching effort; higher levels usually yield smaller output with diminishing returns, and level 9 never guarantees beating level 6. Files are compressed in isolation - ZIP is not a solid archive - so one large text file beats ten small similar ones, and repetitive text, CSV, and logs shrink the most.

Good uses

  • Collecting a batch of loose files - invoices, scans, export files - into one named archive for a single email attachment or upload.
  • Shrinking text-heavy payloads like CSV exports, JSON dumps, logs, or source folders before transferring them, where the size drop is usually dramatic.
  • Zipping files on a locked-down or shared computer where no compression software can be installed; the browser is sufficient and the files never leave the machine.

Limits and checks

  • Levels cannot shrink what is already compressed: JPEG, PNG, MP4, and most PDFs zip to nearly their original size at every level. Judge the tool with text, not photos.
  • A ZIP here is an archive, not a vault - the tool offers no password or encryption, and nothing about the format hides the contents from anyone who receives the file.
  • The size you see is the compressed archive; extraction restores the originals. If two files share the same name and folder path, both entries are stored but the unzip tool decides the collision, usually keeping the later one.

Common questions

Why did a 10 MB folder of photos come out as a 9.8 MB zip?

Because the photos are already compressed. JPEG and PNG data is heavily compressed by its own format, and DEFLATE cannot meaningfully compress compressed data, so the archive gains almost nothing at any level. This is the format working as designed; text files, CSVs, and logs are where ZIP produces large savings.

Can I add a password to the archive?

No - this tool writes a plain ZIP with no encryption, so anyone who gets the file can open it. If you need protected archives, use software that writes AES-encrypted ZIPs and keep the password elsewhere. Traditional password-protected ZIPs use a separate, weaker scheme, so they are not a substitute for real encryption either.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools