Directory Tree Artifact Builder

How to use Directory Tree Artifact Builder

Create a README-ready Unicode or ASCII directory tree and inventory from an explicit relative-path list. Add implied folders, catch file/directory conflicts, and keep supplied byte counts separate from unknown sizes. No directory is scanned and no original file is changed.

1. Provide optional hierarchy-model json file, relative file/directory inventory as json.
2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
3. Copy the result or download a separate output; reset to clear the current form.

Good to know

• One UTF-8 JSON object {root?,entries:[{path,type,bytes?}]} up to 200,000 bytes; 1–2,000 explicit records and 5,000 explicit plus implied nodes. Paths are relative slash-separated strings, at most 2,048 UTF-8 bytes, 32 levels and 192 UTF-8 bytes per component.
• Dot/parent/empty components, leading/trailing slash, backslash, controls, malformed Unicode and duplicate explicit paths are refused. An explicitly supplied directory may complete an already implied directory; file/directory conflicts or file descendants are refused regardless of source order.
• Paths are case-sensitive, preserve Unicode spelling and hidden names, and sort by UTF-16 code-unit name order. This deterministic order is not locale collation or actual filesystem case sensitivity. Connectors are text, not terminal control sequences or clickable paths.
• Only a file may supply an optional nonnegative whole byte count up to 1,000,000,000,000. Known values sum exactly; omitted values stay unknown and are not substituted as measured zero. This inventory does not read or verify file contents, metadata or disk usage.
• Root is an 80-byte display label. Tree text is capped at 250,000 characters; the structured report at 500,000. No directory discovery, symlink/hard-link behavior, shell expansion, environment access, globbing, script execution or GNU tree CLI parity is claimed.
• Structured text output is limited to 500,000 characters. Reduce the supplied source when that separate output budget is exceeded.
• Inputs are processed on this device and are not automatically saved or uploaded.