Archive path traversal checker

Edge cases

• Unsupported, encrypted, corrupt, or unusually structured files may be rejected.

Accuracy

• Browser-readable file structure and metadata can vary by format and producer.

Privacy

• Supported inputs are processed on your device.
• Convurter telemetry avoids raw file bytes and pasted content.

Best for

• Local file and archive workflows where packaging, extraction, listing, type checks, metadata, or hashes help before sharing.
• Inspecting what a file appears to be before using it in a larger workflow.
• A focused inspect task where the expected output is path-risk-report.

Before you start

• This tool runs in the browser, so keep the tab open until the result is created and downloaded or copied.
• Treat files and archives from unknown sources as untrusted, even when the extension looks normal.
• List archive contents before extraction when you only need to inspect what is inside.
• Keep source files until the ZIP or TAR output has been opened and checked.
• Use the report as a decision aid, then route to cleanup, conversion, or verification tools if it finds something notable.

Quality checks

• Treat inspection output as a signal report, not as a guarantee that every possible issue was checked.
• Verify file count, names, sizes, checksums, and detected type against what you expected.
• Remember that file type and metadata inspection are not malware scanning.
• Checksum final artifacts when exact byte identity matters.
• Copy or download the result only after confirming the displayed output matches the task you intended.

Common mistakes

• Opening extracted files automatically is risky; inspect and download deliberately.
• Assuming an extension proves file type. Byte signatures and browser metadata can disagree.
• Using checksum output as proof that a file is safe. Checksums prove identity, not safety.
• Closing the tab before downloading or copying a browser-generated result.
• Treating the first result as final without checking the destination requirement.

Continue the workflow

Use these when the current result is only one step in a longer task.

Verify or clean up

Use these when the output needs checking, cleanup, comparison, compression, or a final share-ready pass.

Good uses

• Inspect a ZIP before extraction.
• Find parent-directory, absolute path, hidden/system, nested archive, or executable-looking entries.

Bad inputs

• Password-protected ZIPs.
• Assuming clean paths mean files are safe.
• Expecting archive extraction or malware scanning.

Output checklist

• Review flagged paths.
• List contents before extracting.
• Inspect extracted file types before opening unfamiliar entries.

Failure modes

• Unsupported ZIP features can fail parsing.
• Very large archive entry counts are rejected.
• Nested archives require separate inspection.

Runtime limits

• Browser-local.
• No extraction.
• No malware verdict.

Use this instead if

Help