How Archive Inspector reads an archive
Choose or drop a ZIP, TAR, GZIP, or TAR.GZ/TGZ file to see its entry metadata in a searchable table. The report includes paths, file types, sizes, methods, timestamps, compression ratios, and warning flags. Archive Inspector reads the selected file in your browser and does not write extracted files to disk.
How to inspect an archive
- Drop a ZIP, TAR, GZIP or TAR.GZ file into the drop zone, or click
browse file. - Review the summary cards and the Size distribution (uncompressed, files only) chart.
- Search with
Search entries by path, then choose anEntry typeor tick an entry flag. - Click
Reset filterswhen you want the complete list again. - Click
CSVorJSONto save the full entry report.
What archive entries show
Each row reports Path, Type, Depth, Uncompressed, Compressed, Ratio, Method, Modified, and Flags. ZIP rows can include a CRC value in the exported report. TAR rows do not have per-entry compressed sizes or ratios because compression applies to the whole TAR stream. Directory size fields can be unavailable.
Flags identify duplicate paths, encrypted entries, unsafe paths, malformed entries, and nested archives. Archive Inspector marks a path as unsafe when it starts with a slash, contains a Windows drive letter, or includes a .. segment.
Path: ../notes.txt
Type: File
Flags: unsafe path
How to inspect nested archives
Archive members with ZIP, TAR, GZIP, or TGZ-style names can be checked for nested content. Archive Inspector follows up to 3 nesting levels. ZIP members use compressed size for eligibility; TAR and GZIP members use stored or reported uncompressed size. The threshold is 75 MB.
Eligible Deflate or GZIP members are decompressed in browser memory so their entries can be listed. Other nested methods are skipped. The entry list stops at 50,000 entries, and parser notes identify truncated or malformed input.
How to search archive paths and filter entries
Search entries by path matches text inside each path. The Entry type menu contains All entries, Files only, and Directories only. The flag checkboxes filter Encrypted, Unsafe path, Duplicate, Malformed, and Nested archive entries. Reset filters clears the search, type choice, and flags.
Summary cards count entries, files, directories, uncompressed total, maximum depth, nested archives, duplicate paths, encrypted entries, unsafe paths, and malformed entries. Compressed total and Overall ratio show N/A when compressed-size data is unavailable. The chart groups files by uncompressed size.
Search and export archive reports
Search entries by path matches path substrings, and you can combine an entry type with any flag checkboxes. Reset filters returns to the complete entry list while keeping the archive loaded. CSV and JSON export the full entry report.
Where this comes up
Before unpacking a build artifact, search for paths such as ../notes.txt and review the Unsafe path or Duplicate flags. Export JSON when another check needs the entry metadata.
For a TAR archive with a large directory tree, filter Directories only to inspect its layout, then switch to Files only to review sizes and modified timestamps.
For a bundle that contains another archive, choose Nested archive and check the Depth column. Members above the size threshold or nesting limit are not followed.
When to use Archive Inspector
Use Archive Inspector for a read-only structural report. Archive Analyze Tools lists the other archive-analysis tasks. This page reads the selected file with File.arrayBuffer(), sends no request containing its contents, and does not write extracted files to disk.
RAR, 7z, and BZIP2-compressed tarballs are reported as unrecognized formats. Archive Inspector does not scan file contents for malware or verify overall archive integrity. ZIP CRC values can appear without verification, while TAR header checksums are used during TAR parsing.
Frequently asked questions
Can I inspect a TAR archive without extracting it?
Yes. Archive Inspector reads TAR headers and lists paths, types, depths, sizes, and timestamps. It does not write extracted files to disk.
Why does a ZIP entry show an unsafe path?
An entry is marked Unsafe path when its path starts with a slash, contains a Windows drive letter, or includes a .. segment.
How many nested archives can Archive Inspector inspect?
It follows up to 3 nesting levels when a recognized nested member meets the size and format checks. The full entry listing stops at 50,000 entries.
Does Archive Inspector verify ZIP CRC values?
ZIP CRC values may appear in the exported report, but Archive Inspector does not verify them or perform an overall archive integrity check.
Which archive formats can I inspect?
It recognizes ZIP, TAR, GZIP, and TAR.GZ/TGZ files. RAR, 7z, and BZIP2-compressed tarballs are reported as unrecognized.