find Command Builder Guide
Assemble a find command with name, type, size, age and depth tests, then choose to print, delete or exec on each match.
A short companion for find Command Builder: when it is useful, what it expects, and what to check before using the result.
What it does
Build a find command from plain choices instead of remembering the test order. Filter by name, type, size, age, permissions and depth, exclude noisy directories, and then decide what happens to each match: print it, print it with a null separator, delete it, or run a command on it.
Use the tool
Open find Command Builder, add the input the tool asks for, run it, and check the output before using it elsewhere.
Input and output
- Input: text.
- Output: text.
- Category: DevOps.
Privacy and processing
Processing happens locally in your browser. This tool does not upload the input to ilham.dev.
Questions
Why does -delete deserve caution?
It removes matches immediately and asks nothing. Run the same command with the print action first so you can see the exact list, then switch to delete.
What is the null-separated option for?
-print0 ends each path with a null byte instead of a newline, so a name that contains a space or a newline is still one item. Pair it with xargs -0.
Does the order of the options matter?
Yes. -maxdepth is a global option and has to come before the tests, and -delete has to come last. The builder already places them in a working order.
Related guide
For broader background, see Linux Command Line Tasks Without Surprises.