Folder Tree Generator
Generate a text folder tree diagram - free, no upload.
Only file and folder names and paths are read - files are never uploaded or opened.
What this tool does
Choose a folder to generate its tree from real file and folder names, or switch to pasting a list of paths, and copy or download the resulting text diagram.
Builds a text tree diagram (using the same connector characters as the Unix tree command) from a chosen folder's real structure.
Also accepts a manually pasted list of paths as an alternative input, for planning a structure before it exists.
Sorts folders before files at each level, alphabetically within each group.
Draws the tree with the same ├──, └── and │ connector characters as the Unix tree command, so branch lines continue correctly past folders that aren't the last item at their level.
Infers a path as a folder rather than a file whenever something else in the list needs it as a parent, even if a shorter pasted path first listed that same name without a trailing slash.
How to use it
- Choose "Choose a folder" or "Paste a list of paths".
- Select a folder, or paste your paths (one per line).
- Copy or download the resulting tree diagram.
Why use this generator
Documentation and READMEs often need a folder diagram, and typing one by hand is slow. Generating the tree from a real folder or list gives an accurate one.
Why we built it
We built the folder tree generator to read only file and folder names, never contents, from the folder you choose. Tidy names with the file name cleaner and rename files with the batch file renamer.
Who this tool is for
- Developers documenting a project structure
- Teachers and writers explaining a folder layout
- Support staff describing a setup
When to use it
- Documenting a project structure.
- Writing a README.
- Sharing a folder layout.
- Teaching or reviewing structure.
Why folder contents aren't uploaded
Building a tree diagram only needs the names, not the files themselves.
A browser's folder picker gives a page access to file names and their paths within the folder, which is all a tree diagram actually needs - it never opens, reads or uploads the contents of the files themselves. This tool only ever touches those names, generating the diagram entirely in your browser.
Why the chosen folder's own name isn't shown as the top line
A small, deliberate choice that keeps folder mode and paste mode consistent.
Every path a browser's folder picker returns already begins with the chosen folder's own name - that's built into how the browser reports it - so the tree built from those paths already shows that folder as the top-level entry on its own. Printing the folder's name again as a separate header above the tree would show it twice. This tool prints a plain "." as the header instead, in both folder mode and pasted-paths mode, which keeps the output identical in shape regardless of which input method produced it.
At each level, folders are always listed before files, and each group is then sorted alphabetically by name - matching the ordering convention most directory-listing tools use, rather than sorting everything together or preserving whatever order the folder picker or your pasted list happened to supply.
What you give it, and what you get back
| Item | Details |
|---|---|
| Input | A chosen folder, or a pasted list of paths. |
| Output | A text tree with connectors. |
| Export | Copy or download. |
Issues you may run into
| What you see | Why it happens | What to do |
|---|---|---|
| Large folder is slow | Every path is read. | Choose a subfolder. |
| Empty folders are missing | Folders without files are not always seen. | Add them to a pasted list. |
| Characters look wrong | A proportional font is used. | Paste into a monospace area. |
Assumptions and limitations
- Very large folders (many thousands of files) may render slowly, since every path is read to build the tree.
- Empty folders that contain no files can't always be distinguished from a file with no extension when using the pasted-paths method - the folder browser method doesn't have this ambiguity.
Frequently asked questions
How do I generate a folder tree diagram for free?
Choose a folder, or paste a list of paths, and the tree diagram is generated instantly.
Are my files uploaded when I choose a folder?
No - only file and folder names and paths are read. File contents are never opened or uploaded.
Can I generate a tree before the folder actually exists?
Yes - switch to "Paste a list of paths" and type out the structure you're planning.
What format is the output in?
A plain text tree using the same box-drawing style as the Unix tree command, ready to paste into documentation.
Is my data uploaded anywhere?
No. Everything happens in your browser.
Why does the tree start with a "." instead of my folder's name?
Because the paths from a chosen folder already include that folder's own name at the start of each one, so the tree already shows it as the top-level entry - printing the name again above would show it twice. "." is used as a plain, consistent header in both folder mode and paste mode.
Are folders and files listed in a particular order?
Yes - folders are always listed before files at each level, and each group is then sorted alphabetically, matching the convention most directory-listing tools use.