If you need to find file by name on a Linux computer, the good news is that Linux gives you several fast, reliable ways to do it. Whether you remember the exact filename, only part of it, or just the folder it might be in, you can find file by name from the terminal in seconds. This guide walks through the main commands step by step, explains what each option does, and shows how to search safely within your own files only, so you never accidentally dig through system folders you should not touch.
Before you start, it helps to know one thing: Linux commands are precise. A search that looks for “report” will not match “Report” unless you tell it to ignore case, and a search that looks in your home folder will not find a file stored somewhere else. Once you understand those two ideas, learning how to find file by name becomes straightforward, and you can repeat the same patterns every time you lose track of a document, a photo, or a downloaded file.
How to Find File by Name With the Find Command
The most flexible way to find file by name is the find command. It walks through a directory tree, folder by folder, and prints every path that matches your rule. The basic shape is simple: you name the place to start, then the test to apply. For example, to find file by name in your home folder, you would search your home directory for an exact filename. If the file exists anywhere below that starting point, the command prints its full path.
One of the most useful habits is to start narrow. Searching your whole computer takes much longer than searching one folder, and it often produces long lists of system files you do not care about. If you believe the file is in your Documents folder, start there. If you are not sure, start in your home folder. Only widen the search when the narrow search comes up empty. This habit also keeps your search fast and your results readable.
Another habit worth building is to quote patterns that contain special characters. Characters such as the asterisk act as wildcards, and your shell may expand them before the search command ever sees them. Putting the pattern in quotes hands it to the search tool unchanged, which is what you want. So when you find file by name using a partial name plus a wildcard, quotes keep the pattern intact and the results accurate.
Searching for an Exact Filename
An exact-name search is the simplest case. You give the starting directory and the exact name, and the tool returns matching paths. This works best when you remember the filename precisely, including its extension, such as a document ending in a familiar suffix or a photo with its usual extension. If nothing is returned, do not assume the file is gone. Check your spelling, check whether the extension differs, and then try a partial-name search.
Exact searches are also case-sensitive by default. That means a file called “Notes” and a file called “notes” are treated as different names. If you are not sure about capitalisation, use the case-insensitive option instead. It is a small change that often turns an empty result into the file you wanted, and it is one of the first things experienced Linux users try when a search fails.
How to Find File by Name When You Only Remember Part of It
Most of the time, you will not remember a filename perfectly. You may remember a word from the middle, the first few letters, or the file type. That is where wildcard patterns earn their keep. An asterisk stands for any characters, so a pattern with an asterisk at the start matches anything ending in your remembered word, and a pattern with an asterisk at the end matches anything starting with it. Used well, wildcards let you find file by name even from a fuzzy memory.
Partial searches work best when the fragment you remember is distinctive. A fragment like “budget” will return a manageable list, while a fragment like “a” will return almost everything and bury the file you want. If a partial search returns too many results, add more of the name, add the file extension, or narrow the starting folder. Each extra clue shrinks the list quickly, and a short list is far easier to scan than a long one.
It is also worth searching by extension when you know the file type but not the name. A pattern that matches every file with a given extension in a folder can jog your memory, because seeing the list of similar files often reminds you which one you wanted. Combine that with sorting or paging the output, and you can work through a long list without it scrolling past before you can read it.
Ignoring Capitalisation in Your Search
Case-insensitive searching is a simple switch on the standard search command, and it is worth using whenever you are unsure about capitals. Many files arrive with mixed capitalisation from downloads, cameras, or other people, so a search that insists on exact case will miss them. Turning on case-insensitive matching removes that whole class of failure, and it costs nothing in speed for an ordinary home-folder search.
One caution still applies: case-insensitive searches return more results, because names that differ only in capitals now count as matches. That is usually a good trade, but if the list grows too long, add another clue, such as the extension or a second word from the name, to bring it back under control.
A Faster Way to Find File by Name With Locate
The locate command offers a faster way to find file by name, because it searches a database of filenames rather than walking the filesystem live. On a large drive, that difference can be dramatic: results appear almost instantly. The trade-off is that the database is only as fresh as its last update, so a file you created minutes ago may not appear until the database is refreshed. For older files, though, it is an excellent first try.
If your system does not have the locate database set up, your first run may return nothing or report that the database is missing. In that case, fall back to the live search command, which always reflects the current state of your folders. And if you do use locate regularly, remember that refreshing the database is a system task; on a shared machine, leave that job to the administrator rather than changing system settings yourself.
Many users keep both tools in their routine: locate for a quick first attempt, and the live search when locate comes up empty or the file is very new. That pairing covers nearly every everyday case, and it means you rarely need to wait through a slow full-disk scan.
Narrowing Results by Type, Size, and Date
Once you can find file by name, the next skill is narrowing a long result list. The standard search command lets you add tests for file type, so you can ask for regular files only and skip directories that happen to share the name. You can also filter by size, which helps when you remember that a video was large or a note was tiny, and by modification time, which helps when you know roughly when you last worked on the file.
Date filters deserve a little care. A file modified “in the last seven days” is a different test from a file modified “more than thirty days ago,” and mixing them up produces confusing results. Start with a broad window, such as the last month, and tighten it only if the list is still too long. The same principle applies to size: start broad, then narrow. Each filter you add should answer a question you genuinely know, not a guess, because a wrong guess filters out the very file you want.
| What you know | Best approach | Why it helps |
|---|---|---|
| Exact filename | Exact-name search in a narrow folder | Fastest, most precise result |
| Part of the name | Wildcard pattern search | Finds files from a fuzzy memory |
| File type only | Extension pattern search | Lists similar files to jog your memory |
| Old file, large drive | Database search first | Near-instant results |
| Very new file | Live search in the likely folder | Reflects files created minutes ago |
| Too many results | Add type, size, or date filter | Shrinks the list to something scannable |
Staying Inside Your Own Files
On your own computer, it is wise to search your own home folder rather than the entire system. System folders contain thousands of files with similar names, and searching them wastes time and clutters your results. More importantly, some system areas are not yours to change, and poking around in them can lead to accidental changes if you later act on a result without checking it. Keep your searches in folders you own, such as your home folder, Documents, Downloads, or Pictures, and you avoid both problems.
If you share a computer, the same rule protects other people’s privacy. Search only your own account’s folders, and do not use elevated privileges to look through someone else’s files. A file search is a powerful tool, and using it only within your own space is the respectful and safe way to work.
Finding Files Without the Terminal
If you prefer not to use the terminal, your desktop file manager also lets you find file by name. Most file managers include a search box that looks through the current folder and its subfolders, and many let you filter by type or date. The terminal commands are faster and more flexible, but the graphical search is perfectly good for everyday use, especially when you already have the likely folder open.
Graphical search has the same core lesson as terminal search: start in the most likely folder, use a distinctive fragment of the name, and narrow the results if the list is long. The interface differs, but the thinking is identical, so everything you learn with the terminal transfers directly, and vice versa.
Frequently Asked Questions About How to Find File by Name
Why does my search return nothing?
The most common reasons are a spelling mistake, wrong capitalisation, a different extension, or searching the wrong folder. Try a case-insensitive partial search in your home folder before concluding the file is missing. Also check the Trash or Recycle Bin area of your file manager, since a deleted file will not appear in a normal search.
Which command should I try first?
Try the database search for speed if the file is not brand new, and the live search if the file was created recently or the database search returns nothing. For most home-folder searches, the live search is fast enough that either order works, so pick the one you remember and switch only if it fails.
What do I do with too many results?
Add one more clue at a time: more of the filename, the extension, the file type, or a date range. Avoid adding several guesses at once, because one wrong guess can hide the file. Narrow step by step until the list is short enough to scan comfortably.
For related how-to reading, see our guide to Linux commands and our explainer on extracting files. Both cover everyday file and system tasks that pair well with searching.
Conclusion: Find File by Name Quickly and Safely
Learning to find file by name on Linux is mostly about choosing the right starting folder, using a distinctive fragment of the name, and narrowing step by step when the list is long. Start with an exact or partial search in your home folder, ignore case when you are unsure about capitals, try the faster database search for older files, and filter by type, size, or date when you need to. Keep your searches inside your own files, and you will locate documents, photos, and downloads quickly without wading through system clutter. Practice the patterns above on a file you already know, and the next time one goes missing, you will know exactly how to find file by name and get back to work.
