Metric | Value |
---|---|
Original size | {{ formatBytes(originalSize) }} |
Compressed size | {{ formatBytes(compressedSize) }} |
Saving | {{ savingPercent }} % |
File compression reduces the storage footprint of data by reorganising repeated patterns and eliminating redundancy, allowing the same information to occupy fewer bytes without altering its content. Modern archive formats also bundle multiple items so they travel together, streamlining distribution and backup workflows across email, cloud drives, and version-control systems.
This tool accepts one or more local files, groups them into a portable archive, and then applies a selectable algorithm—lossless deflate, gzip, or Brotli—to squeeze the byte stream. A level slider fine-tunes the balance between processing time and space saving, while a filename field styles the resulting package for easy identification.
Compressing a quarterly report folder before emailing, for example, can cut its 25 MB size to under 8 MB, saving upload time and bandwidth for all recipients. Very large videos, photographs, and already-compressed formats may show minimal improvement and could even grow when re-archived. Always review the savings figure after processing to confirm benefits.
Lossless compression encodes binary data so that decompression reproduces the exact original bit sequence. The algorithms offered here analyse repeating byte patterns, sliding windows, and statistical frequency to emit shorter symbol codes. Tar creates a raw concatenated stream with headers, while deflate, gzip, and Brotli then apply dictionary coding and entropy stages to shrink size further. These methods honour file boundaries, preserve timestamps, and deliver platform-agnostic archives that open on any modern system.
Algorithm | Transformation | Extension | Typical Use |
---|---|---|---|
ZIP (Deflate) | Dictionary + Huffman | .zip | General sharing |
ZIP (Store) | None | .zip | Bundling already-compressed media |
TAR | None | .tar | Unix backup streams |
TAR + GZIP | Deflate after TAR | .tar.gz | Source-code bundles |
TAR + Brotli | Brotli after TAR | .tar.br | Web-optimised assets |
Parameter | Meaning |
---|---|
Files | One or more items selected from local storage. |
Algorithm | Compression method and container format. |
Compression level | Numeric quality from 1 (fast) to 9 (compact). |
Output name | Stem used for the generated archive file. |
Worked example (three files totalling 10 485 760 B, TAR.GZ, level 6):
Deflate is formalised in RFC 1951; gzip in RFC 1952; Brotli in RFC 7932. Tar specifications derive from POSIX ustar and GNU extensions.
The algorithms operate solely within the local runtime, aligning with GDPR data-minimisation principles for client-side processing.
Follow these steps to create an efficient archive.
The tool emits ZIP, TAR, TAR.GZ, and TAR.Brotli archives, each compatible with mainstream extraction utilities.
Yes. All computations run locally; you can disconnect from the internet once the page has loaded.
No. Files remain in local memory and disappear when you close or refresh the page.
The application subtracts compressed bytes from original bytes, divides by the original size, then multiplies by 100.
If content is already compressed—such as JPEG images or MP4 videos—adding headers can offset negligible gains, resulting in a larger file.