{{ summaryTitle }}
{{ summaryValue }}

{{ summaryLine }}

{{ badge.label }}{{ badge.value }}
One archive up to 16 MiB, 500 entries, and 64 MiB of selected expanded content.
{{ sourceReady ? sourceFile.name : 'Drop one archive here' }}
{{ sourceFileSummary }}
Reviewed entries

Select safe regular files with unique normalized relative paths. Extraction never writes directly into your filesystem.

{{ selectionStatus }}
SelectNormalized pathTypeExpandedDecision
{{ entry.safe_path || entry.path }}
From: {{ entry.path }}
{{ entry.type === 'file' ? 'File' : entry.type }}{{ entry.type === 'file' ? formatBytes(entry.expanded_bytes) : '—' }}{{ entry.selectable ? 'Safe' : (entry.type === 'directory' ? 'Directory' : 'Blocked') }}
{{ entryStatus(entry) }}

{{ workflowMessage }}

Archive order is neutral and preserves the package identity.
Verified local output
{{ computation.values.package_name }}
Files included{{ computation.values.selected_count }}
Expanded size{{ formatBytes(computation.values.selected_expanded_bytes) }}
ZIP size{{ formatBytes(packageBytes.length) }}
Blocked{{ computation.values.blocked_count }}
PathExpandedCRC-32DecisionCopy
{{ row.path }}{{ row.sizeDisplay }}{{ row.crc32 }}Included
Online File Compressor Compress one local file into a compatible archive or stream and review size change with split delivery plus SHA-256 integrity before downloading.
Gzip Text Decompressor Decompress gzip, zlib or raw deflate into readable text in your browser with wrapper checks, byte counts and strict encoding options.
File Encryptor & Decryptor Encrypt a local file into an authenticated .stenc envelope or recover it in your browser with AES-GCM, PBKDF2 or Argon2id, and no upload.
File Hash Generator Hash one local file in your browser and compare its full digest with SHA-2 or SHA-3 plus required RIPEMD-160 and legacy references.

An archive combines stored names with file data so a set of files can travel as one object. ZIP normally combines packaging and compression. TAR records a directory tree and file data in fixed-size blocks, while GZIP is a compressed stream that usually represents one file. A .tar.gz or .tgz file applies GZIP compression to a TAR archive.

Extraction is a write operation, not merely decompression. Every member name can become an output path, so a hostile archive may try to write outside the intended directory with an absolute path or .. segment. Links, device nodes, colliding normalized names, and ambiguous legacy filename encodings can also make the restored tree differ from the list a person reviewed.

HazardWhat can happenUseful control
Path traversalA member targets a parent or absolute directoryRequire normalized relative paths
Path collisionDifferent stored names resolve to one output nameBlock every colliding entry
Link or special entryExtraction creates an indirect or non-regular filesystem objectPackage regular files only
Expansion bombA small archive expands to excessive memory or storageLimit per-entry ratio and total expanded bytes
Corrupt dataDecompressed bytes do not match the stored integrity valueVerify size and CRC before packaging

Selective extraction reduces exposure because only reviewed regular files are decompressed and repackaged. It does not make their contents trustworthy. A valid CRC confirms accidental corruption was not detected; it does not identify the author, prove authenticity, or scan documents and programs for malware.

A safe handoff keeps the stored path visible, explains why blocked entries were excluded, and writes accepted files under a fresh destination or package. Permissions, owners, executable bits, extended attributes, and links should not be assumed to survive a safety-focused rewrite.

How to Use This Tool:

Inspect the archive first, choose only entries marked safe, and treat the generated ZIP as a new reviewed package.

  1. Choose one ZIP, TAR, TAR.GZ, TGZ, or single-file GZIP archive no larger than 16 MiB.
  2. Review the normalized paths and blocked reasons. Sorting paths alphabetically changes review order only; archive order preserves the original listing order.
  3. Select one or more safe regular files. At most 200 files and 64 MiB of selected expanded content can enter one output package.
  4. Start extraction. If a selected ZIP member fails size or CRC-32 verification, discard the stale result and choose a valid source or different reviewed entries.
  5. Check the package name, included paths, expanded sizes, and CRC-32 values before downloading the generated ZIP.

Interpreting Results:

Safe file means an entry passed the tool's path, type, encoding, encryption, method, size, ratio, collision, and integrity rules. It does not mean the content is harmless or appropriate to open. Scan or inspect unfamiliar output with controls suitable for the file type.

Blocked entries remain outside the generated package. A mixed archive can still produce a reviewed ZIP from accepted files, but the omitted paths should be noted when completeness matters. Directory markers are not packaged separately; accepted file paths recreate the necessary directory structure inside the ZIP.

The expansion ratio compares selected expanded bytes with the source archive size. It helps describe the job but should not be read as a compression-quality score because unselected members and archive headers are still part of the source size.

Technical Details:

The archive is parsed into bounded entry records before selected content is packaged. ZIP uses its central directory, TAR uses checksum-verified 512-byte headers and end markers, and GZIP exposes one decompressed member name. Format detection follows the byte signature rather than trusting the filename alone.

Rule Core:

CheckAccepted ruleBlocked case
PathRelative, normalized, 1 to 240 characters, at most 20 segmentsAbsolute paths, drive paths, control characters, .., or excessive depth
Entry typeRegular fileSymbolic links, hard links, and special entries
ZIP nameSafely normalized filenameUnsupported non-UTF-8 legacy filename
ZIP methodStored or Deflate, unencryptedEncryption or another compression method
Expanded fileAt most 32 MiB and expansion ratio no greater than 100:1Oversized or unusually expanding member
Normalized identityOne stored entry per normalized pathTwo names resolving to the same output path
Selection1 to 200 files; total expanded size at most 64 MiBEmpty, duplicated, oversized, or blocked selection

Formula Core:

The displayed selection ratio divides the total expanded bytes of the selected files by the complete source archive size.

Rs=∑i=1nEiS

Ei is the expanded byte count for selected file i, and S is the source archive size in bytes. Entry safety uses a separate ratio, expanded bytes divided by compressed bytes; values above 100 are blocked, while exactly 100 is accepted.

Transformation Core:

Accepted paths are normalized to forward-slash relative names. Only selected data is decompressed, and every selected ZIP file must match its declared expanded size and CRC-32 value. The files are then written into a new ZIP package with a fixed timestamp and a bounded output size of 72 MiB. The generated package is reopened and compared with the reviewed path, size, and CRC list before it is offered for download.

ZIP64 and split or multi-disk ZIP archives are rejected. TAR owners, modes, link semantics, and extended attributes are not carried into the reviewed ZIP, and a standalone GZIP input becomes one regular file.

Privacy and Safety Notes:

The archive bytes, entry names, decompressed content, and generated ZIP stay in memory in the active browser tab. They are not uploaded or stored by the service.

  • Path and expansion checks reduce extraction risk but do not scan for malware or unsafe document content.
  • CRC-32 verifies accidental corruption, not authorship or cryptographic authenticity.
  • Encrypted ZIP, RAR, 7z, split archives, sparse TAR, links, and special filesystem entries are not supported.
  • Use a dedicated destination when unpacking the downloaded ZIP, especially when the source came from an untrusted sender.

Worked Examples:

TAR with one traversal path

Suppose a TAR contains ../outside.txt, a symbolic link, and folder/report.csv. The traversal path and link are blocked, while the regular CSV can be selected and written to the new ZIP as folder/report.csv. The result is a reviewed subset, not a complete restoration of the TAR.

References: