Inspect ZIP entries and compressed and expanded sizes
Inspect entry names and sizes before extracting a ZIP to review what it contains. The report describes archive structure and does not function as an antivirus judgment about the content of each file.

How to use this tool
- Choose files in ZIP format. Maximum files per batch: 1.
- Review Report format, then start processing.
- Download the output, open it, and check its content and quality.
Choose the right settings
Choose one ZIP and select CSV, TXT or JSON for the report. Read compressed size, expected expanded size and method together to distinguish the different measurements.
- Supported input
- ZIP
- Output
- Files
- Available settings
- Report format
Before you start
Distinguish bundling from compression
Keep a list of the source files and decide whether you need one bundle, separate compressed files, extracted contents or an inspection report. These are different outcomes. ZIP entry names and folder paths also differ from the contents of the files themselves; check what this tool will preserve before processing.
Where an output or report choice is offered, choose it for the next step rather than by extension alone. Do not assume that an archive will be smaller: already compressed files may change little, and bundling without compression adds archive structure. Review the supported archive types and restrictions instead of expecting a password or bypass control that is not provided.
Record the selected source files, their names and which measurement matters for delivery. A report can describe entries without proving that each can be extracted, while a successfully extracted file still needs a content check. If a later program cannot open the result, compare its actual format with that program’s supported input before blaming the archive step. Preserve any intermediate archive separately, so the original compressed input and a newly produced package are not confused during another attempt.
Verify names, contents and sizes
Compare the result with the source list. For an archive, inspect entry names and open an extracted sample; for separate outputs, match each file to its input. Read compressed size, expanded size and whole-archive size as different measurements. If paths become safe filenames, verify that similarly named entries can still be distinguished.
If processing stops, check for a damaged stream, unsupported encryption or structure, unsafe paths and the stated expansion limits. Do not bypass a blocked input by assuming it is harmless. Structural inspection does not scan file contents for malware, and decompression may reveal another archive that needs its own extraction step.
Example input and output
archive.zip → entry information reportExamples describe the workflow. Results depend on the source file and settings.
Check the saved result before using it
Review required document names and expected expanded data. The whole archive size differs from individual entry sizes, so check the byte units and the scope of each value you compare.
If the result is different from what you expected
Encrypted, split, unsupported ZIP64 or structurally damaged archives may not be analyzed. When a dangerous path blocks inspection, review the source archive's construction instead of bypassing the check.
Limits to keep in mind
- This is a structural report, not an antivirus scan or a guarantee that archived files are safe to open.
Continue with a related tool
This guide explains the public browser tool. Keep a copy of the original and inspect the result before sharing it.