Folder Tree
Draw a folder's files and subfolders as a tree, like the tree command, in Unicode or ASCII lines, a Markdown list or indented text. Choose or drop a folder, or paste a list of paths.
About this tool What it's for, how to use it and an example
What it's for
Show what’s in a folder as a tree of branches and leaves, the way the tree command does on Windows, Linux and the Mac (with Homebrew), ready to paste into documentation, a README, an email or a support ticket.
For example, when you’re writing instructions for a project and want to show where each file goes, choose the project folder, untick Sizes, set Levels to 2 and copy the tree into the README.
How to use it
Choose a folder, or drop one anywhere on the page. You can also paste a list of paths instead, one per line,
such as the output of find . -type f or dir /s /b: backslashes count as slashes, a leading ./ is dropped,
and a path ending in / is an empty folder.
- Style: Unicode lines (
├──), plain ASCII (|--, astree --charset=asciidraws), a Markdown nested list, or indented text. Markdown and indented styles end folder names with/. - Levels limits how deep the tree goes (
0for every level), Folders first lists folders before files at each level, Folders only leaves files out, and Sizes adds each file’s size and each folder’s total (chosen or dropped folders only). - Ignore leaves out anything whose name matches, separated by spaces or commas;
*stands for any characters, so*.loghides log files. Ignored folders aren’t read at all when dropped.
The message gives the count of folders and files shown. Copy copies the tree. Settings are remembered in this browser, and Copy a link keeps pasted paths and settings, never a chosen folder.
Example
Paste these paths:
project/README.md
project/src/main.js
project/src/lib/util.js
project/docs/guide.md
With the Lines style and Folders first, the tree is:
project
├── docs
│ └── guide.md
├── src
│ ├── lib
│ │ └── util.js
│ └── main.js
└── README.md
The message reads “3 folders, 4 files.”
Good to know
Only names and sizes are read, never the files’ contents. Browsers leave empty folders out when a folder is chosen with the button, but include them when it’s dropped. Hidden files such as .env are included unless ignored. Names are sorted alphabetically with numbers in order (file9 before file10), ignoring case, so the order may differ a little from your file manager’s. A very large folder (tens of thousands of files) may take a while to read.
Guide: Documenting a project's files, tables and links
Private: this tool runs in your browser. Nothing you type, paste or choose leaves this page.
Saved you a few minutes? Say thanks with a coffee.
Something wrong with this tool, or missing from it? Report a bug or suggest a feature.