Preview an archive's folder tree

Show a ZIP or TAR archive's folder structure as a navigable tree without extracting anything.

archivetreepreviewstructure

Questions people ask

How is this different from the other archive tools?: This one draws the folder shape across ZIP and TAR variants without opening a single member: timestamps, compression details and CRC checks belong to the other inspectors, and the size accountant reports extraction footprints. Here the tree is the product, both as a rendered download and as a structured listing.
Is anything extracted or opened?: No. The listing comes from the archive's directory records: names, types and the sizes the records declare. Nothing is written to disk, and no member's contents are read, so the report is safe to run even on an archive you have no intention of unpacking.
What do the flags mean?: A small set of structural oddities is counted and sampled: absolute paths, parent-directory segments, drive-qualified paths, Windows device names, control characters and mixed separators, plus duplicate paths and unusually deep nesting. They are observations, not verdicts, and the dedicated archive-traversal-audit tool examines member paths and link targets in depth.
What are the declared sizes?: The sizes the archive's own records state for each member. They are statements, not measurements: the report says so next to the figures, and no member was opened to verify them.
How large can the listing be?: Up to 4096 entries are listed individually; anything beyond is counted and stated rather than hidden, and paths deeper than 64 segments are counted as a class. The report itself is capped at 4 MB. An empty archive answers with an empty tree rather than an error.
What happens to my file?: The upload is deleted as soon as processing finishes; the tree and report stay downloadable for about 10 minutes, then are deleted automatically.

About this tool

A folder-shape viewer that keeps its honesty in plain sight: the listing comes from the archive's own directory records, sizes are labelled declared rather than measured, and nothing is extracted while the report is built. Duplicate paths, unusual Unicode, absolute paths, parent-directory segments, control characters and over-deep nesting are counted with a few named samples, and the report is explicit that these are observations, with the dedicated traversal audit named as the place for a deeper look. Technical details: the tool reads the ZIP central directory or the TAR header records (including gzip, bzip2 and xz compressed variants), 100 MiB of archive at most, sorts the listing lexicographically for reproducible output, and renders a deterministic tree download. Caps: 4096 entries listed, 64 segments of depth, 4 MB of report, with the overflow counted and stated. Honest limits: the tool cannot verify declared sizes without opening members, which it deliberately never does; it does not follow links or audit their targets (the traversal audit does); and nesting deeper than 64 components is counted as a class rather than drawn. An empty archive is a successful inspection that reports an empty tree.

File limits

Exactly 1 file per job
Each at most 100 MiB
Result at most 8 MiB

Supported formats

Any file type

Capabilities

archivetreepreviewstructureziptar

Privacy & processing

Your file is processed in an isolated job on Tooley's own infrastructure. No third-party services are involved and nothing is stored beyond the result window.

Uploads are removed as soon as processing finishes. Results stay available for about 10 minutes, then they are deleted automatically.