Local archive lab

Create an archive test file

Make a ZIP, TAR, gzipped TAR, or single-file gzip from safe text members. The browser worker encodes the output, reopens it to check every byte, and records the actual hashes before download.

Configure an archive fixture

Choose a versioned recipe, edit safe text members, then build and verify the real archive in a browser worker. ZIP uses stored entries so it works without a compression codec.

Archive formatTest scenario

Source files (2)

File 1Member pathText content

File 2Member pathText content

Limits: 100 files, 64 KiB per file, 512 KiB source, 2 MiB output. Paths cannot escape the archive.

Ready to generate.

Manifest preview

The listed member paths and UTF-8 byte sizes will be checked after encoding.

2 files · 47 uncompressed bytes

Path	UTF-8 bytes
README.txt	25
records.csv	22

ZIP entries are STORED for portable, byte-stable fixtures. TAR uses fixed timestamps. Gzip encoder bytes can differ by browser, so the sidecar records the actual hash and promises only content-equivalent round-trip output.