Archive Member Path Preflight
Check a pasted archive manifest for unsafe relative names, case aliases, duplicate members and file-parent conflicts. Only the list you paste is checked: no archive is read, nothing is renamed, nothing is uploaded.
Input
One member per row: write F (file) or D (directory), then one Tab, then the relative path. At most 500 rows; each path is 1–240 characters with at most 16 segments.
Portable relative-path rules
- Each row: F or D, one Tab, then the path. Paths have no trailing slash; the kind marks directories.
- Paths are 1–240 characters with at most 16 segments; each segment is 1–64 characters and only accepts
A–Z a–z 0–9 . _ -. - Absolute paths, drive letters, backslashes,
.or..segments, empty segments, and trailing dots are rejected. - Reserved device names are rejected:
CON PRN AUX NUL COM1–COM9 LPT1–LPT9(case-insensitive, compared before the extension). - Comparison folds ASCII case: paths that differ only in capitalisation conflict.
- Declaring the same member twice, or a file occupying another member’s ancestor directory, is a conflict.
- No archive is read or extracted, nothing is renamed, and no repair commands are produced.
Paste a manifest, or load the example.
The example is sample data, not your files.
Invalid rows and tree conflicts
Invalid rows
No invalid rows.
| Row | Code | Segment | Detail |
|---|
Tree conflicts
No tree conflicts.
| Kind | Normalized path | Source rows | Detail |
|---|
Frequently asked questions
- Does a clean report guarantee safe extraction?
- The audit checks this manifest against its stated naming policy.
- Why flag a case-only difference?
- The portability policy compares paths with ASCII case folded.