3032

How can I recursively find all files in current and subfolders based on wildcard matching?

0

19 Answers 19

4296

Use find:

find . -name "foo*"

find needs a starting point, so the . (dot) points to the current directory.

If you need case insensitive search use :

find . -iname "foo*"
25
  • 37
    I know this is tagged as linux but this is worth mentioning: the path is required for on other *nix variants that aren't linux. On linux, the path is optional if you want to use dot.
    – IslandCow
    Commented Nov 16, 2013 at 0:14
  • 7
    @Seatter "foo*" tells find to look for all files that start with "foo". It is just his example. You could use "gpio*" to find all files who's names start with gpio, or just "gpio1" to find all files named gpio1. Commented Apr 2, 2014 at 18:00
  • 59
    note that the "foo*" is in quotes so the shell doesn't expand it before passing it to find. if you just did find . foo*, the foo* would be expanded AND THEN passed to find.
    – grinch
    Commented May 19, 2014 at 14:29
  • 87
    Worth stressing that " " is very necessary for recursive searching.
    – WesternGun
    Commented Oct 21, 2016 at 11:43
  • 36
    Also useful: If you don't want to be notified about directories you don't have permission to (or other errors), you can do find . -name "foo*" 2>/dev/null
    – Jobbo
    Commented Aug 15, 2017 at 10:54
318

Piping find into grep is often more convenient; it gives you the full power of regular expressions for arbitrary wildcard matching.

For example, to find all files with case insensitive string "foo" in the filename:

find . -print | grep -i foo
6
  • 114
    find also has the -iname, -regex, and -iregex flags for case-insensitive wildcard, regex, and case-insensitive regex matching, so piping to grep is unnecessary.
    – iobender
    Commented Aug 4, 2015 at 16:54
  • 10
    I don't think it is about being unnecessary, but being more convenient. Commented Feb 8, 2017 at 16:57
  • 4
    However, piping to grep -v can allow you to use simple strings or regexes to remove entries you don't want. Commented Apr 6, 2017 at 3:15
  • 8
    @iobender - Sadly, I can tell you from experience that not all systems come with a find command that supports those options. Sometimes grep becomes the only option.
    – Mr. Llama
    Commented Jul 5, 2018 at 17:36
  • 3
    One important caveat here is that if you're using find on a directory that contains A LOT of files (eg; ``) then this can be quite slow. Commented Jul 22, 2022 at 16:38
219

find will find all files that match a pattern:

find . -name "*foo"

However, if you want a picture:

tree -P "*foo"
3
109

fd

In case find is too slow, try the fd utility - a simple and fast alternative to find written in Rust.

Syntax:

fd PATTERN

Demo:

Homepage: https://github.com/sharkdp/fd

1
  • I went to the GitHub link to get the details on it, but it would be worthwhile to edit your post and mention why fd is faster than find. The reason: "Very fast due to parallelized directory traversal" Commented Jan 19 at 20:29
82
find -L . -name "foo*"

In a few cases, I have needed the -L parameter to handle symbolic directory links. By default symbolic links are ignored. In those cases it was quite confusing as I would change directory to a sub-directory and see the file matching the pattern but find would not return the filename. Using -L solves that issue. The symbolic link options for find are -P -L -H

1
  • 6
    L switch is very helpful. Many times user do not have any idea about underlying directories, whether they are softlinked or are normal directories. So in case of doubt, it always good to use L option. At least, it has always helped me.
    – Ritesh
    Commented Jan 3, 2018 at 16:21
73

Use

find <directory_path>  -type f -name "<wildcard-match>"

In the wildcard-match you can provide the string you wish to match, e.g., *.c (for all C files).

3
  • 5
    Your answer is the first most correct here as it only searches files as specified. The others not specifying type will return directories.
    – wilsotc
    Commented Nov 23, 2017 at 1:15
  • 1
    if you wish to search for a directory "-type f" could be changed to "-type d "
    – XYZ_Linux
    Commented Sep 11, 2019 at 7:02
  • By default, find detect symbolic file links (but not the ones in symbolic directory links). -type f will cause find to not detect symbolic file links. If you also want to include symlinks that point to a file, use -L: find -L <optional_directory_path> -type f. Don't use -type f,l since it will also include symbolic directory links. Commented May 17, 2022 at 11:54
64

If your shell supports a new globbing option (can be enabled by: shopt -s globstar), you can use:

echo **/*foo*

to find any files or folders recursively. This is supported by Bash 4, zsh and similar shells.


Personally I've got this shell function defined:

f() { find . -name "*$1*"; }

Note: Above line can be pasted directly to shell or added into your user's ~/.bashrc file.

Then I can look for any files by typing:

f some_name

Alternatively you can use a fd utility with a simple syntax, e.g. fd pattern.

4
  • 2
    This just goes into a single level. Not recursing into the sub directories for me
    – Broncha
    Commented Jun 7, 2017 at 16:29
  • 5
    @Broncha Because you need to activate the extended globbing by shopt -s globstar command. This is supported in Bash, zsh and similar shells.
    – kenorb
    Commented Jun 7, 2017 at 16:30
  • bash-3.2$ shopt -s globstar gives bash: shopt: globstar: invalid shell option name
    – drewish
    Commented Oct 17, 2017 at 5:09
  • @drewish You need to upgrade your Bash to 4.x
    – kenorb
    Commented Oct 17, 2017 at 10:30
44

Use

find path/to/dir -name "*.ext1" -o -name "*.ext2"

Explanation

  1. The first parameter is the directory you want to search.
  2. By default find does recursion.
  3. The -o stands for -or. So above means search for this wildcard OR this one. If you have only one pattern then no need for -o.
  4. The quotes around the wildcard pattern are required.
20

You can use:

find . -type f  -name 'text_for_search'

If you want use a regular expression, use -iname:

find . -type f  -iname 'text_for_search'
20

The default way to search for files recursively, and available in most cases is

find . -name "filepattern"

It starts recursively traversing for filename or pattern from within the current directory where you are positioned. With the find command, you can use wildcards, and various switches. To see the full list of options, type

man find

Or if man pages aren't available at your system:

find --help

However, there are more modern and faster tools than find, which are traversing your whole filesystem and indexing your files. One such common tool is locate or slocate/mlocate. You should check the manual of your OS on how to install it, and once it's installed, it needs to initiate the database. If the install script doesn't do it for you, it can be done manually by typing

sudo updatedb

And, to use it to look for some particular file, type:

locate filename

Or, to look for a filename or pattern from within the current directory, you can type:

pwd | xargs -n 1 -I {} locate "filepattern"

It will look through its database of files and quickly print out path names that match the pattern that you have typed. To see the full list of locate's options, type: locate --help or man locate

Additionally, you can configure locate to update its database on scheduled times via a cron job, so a sample cron which updates the database at 1 AM would look like:

0 1 * * * updatedb

These cron jobs need to be configured by root, since updatedb needs root privileges to traverse the whole filesystem.

0
15

For file search

find / -xdev -name settings.xml → the whole computer
find ./ -xdev -name settings.xml → the current directory and its subdirectories

For files with an extension type:

find . -type f -name "*.iso"
14

I am surprised to see that locate is not used heavily when we are to go recursively.

I would first do a locate "$PWD" to get the list of files in the current folder of interest, and then run greps on them as I please.

locate "$PWD" | grep -P <pattern>

Of course, this is assuming that the updatedb is done and the index is updated periodically. This is much faster way to find files than to run a find and asking it go down the tree. Mentioning this for completeness. Nothing against using find, if the tree is not very heavy.

1
  • 2
    locate "$PWD*.mp4" Just to remind that you may be able to skip the grep Commented May 14, 2020 at 22:37
13

The following command will list down all the files having the exact name "pattern" (for example) in the current and its sub folders.

find ./ -name "pattern"

2
  • 2
    Downvote. This repeats a 2017 answer. Commented Aug 31, 2021 at 11:03
  • 1
    @Brian New answers are expected to provide some new info or an alternative solution, repeating what already has been said is not useful. Just like when asking a question, before writing an answer you should search first to make sure your answer will add something useful. Especially when there are lots of other answers, as in such case the possibility of this approaches 0. It's not hard at all, only a single Ctrl+F away.
    – EvgenKo423
    Commented May 28, 2022 at 7:56
10

The below command helps to search for any files

  1. Irrespective of case
  2. Result excluding folders without permission
  3. Searching from the root or from the path you like. Change / with the path you prefer.

Syntax:

find <FromDirectory> -iname '<FileName wild char allowed>'   2>&1 | grep -v "Permission denied"

Example

find / -iname 'C*.xml' 2>&1 | grep -v "Permission denied"
1
  • 5
    why on earth do you use grep for that? Just redirect stderr to null find / -iname '*C*.xml' 2>/dev/null
    – phuclv
    Commented Mar 23, 2019 at 5:51
10

This will search all the related files in current and sub directories, calculating their line count separately as well as totally:

find . -name "*.wanted" | xargs wc -l
8

Try with the fd command if installed. Install instructions.

Find all files that start with 'name':

fd "name*"

This command ignores all .hidden and .gitignoreed files.

To include .gitignoreed files, add the -I option as below:

fd -I "name*"

To include hidden files, add the -H option as below:

fd -H "name*"
8

If you want to search special files with a wildcard, you can use the following code:

find . -type f -name "*.conf"

Suppose, you want to search every .conf files from here:

. means search started from here (current place)
-type means type of search item that here is file (f).
-name means you want to search files with *.conf names.

1
1

You can also use ripgrep.

Example:

Search all the filenames contain substring psql,

rg --files | rg psql
-4

With Python>3.5, using glob, . pointing to your current folder and looking for .txt files:

 python -c "import glob;[print(x) for x in glob.glob('./**/*txt', recursive=True)]"

For older versions of Python, you can install glob2

4
  • 3
    Can someone explain the downvotes? If there is something wrong with my answer, I would like to know what it is. – This question asks a native solution for Linux shells and you provide an answer in Python. So your answer is off-topic here.
    – EvgenKo423
    Commented Nov 12, 2021 at 9:34
  • I don't understand part of your comment @EvgenKo423, since this answer was answered by Katu and not by you. Commented Nov 16, 2021 at 15:57
  • 1
    @ValerioBozz Look at the revision history. I had quoted their question and answered it.
    – EvgenKo423
    Commented Nov 17, 2021 at 14:38
  • 1
    I have seen plenty of questions about sed with accepted answers that use awk and similar. [...] It feels like this is getting downvoted by people following the trend instead of thinking about it. – But both sed and awk are command line tools, while the Python is a full-featured programming language. Downvoting answers costs rep which discourages doing so for no reason, but if you still think it's a voting fraud, have a read of this post. P.S.: Please use comments or Stack Overflow Chat for discussions, they don't belong in answers.
    – EvgenKo423
    Commented Jan 19, 2022 at 7:50

Not the answer you're looking for? Browse other questions tagged or ask your own question.