by Alexey Samoshkin

Why you should be using fzf, the command line fuzzy finder

Missing demo found

In this tutorial, I’ll help you take your command line habits to a next level with fzf . Start searching files like a pro. Learn less known features, like changing directory, searching through a command history, looking up the host name to SSH into, killing a process, having instant file’s preview with syntax highlighting, and more…

quick demo

Today I’m going to tell you about a tool that can change your tech life into “before” and “after” parts. Trust me — it’s not a hyperbole. Meet fzf, which stands for fuzzy finder. As the definition claims, it’s a general purpose command-line fuzzy finder. That doesn’t sound very descriptive and attractive for those who are hearing about it for the first time. But it’s a very popular project ranked at around 21,000 stars on the Github. So it’s time to clear the fog and get a deeper insight.

This post accompanies my recent screencast on the topic. So, if you’re a person who learns by watching, check it out. Otherwise, check it out too ?, because tools like fzf are best introduced with a live demo rather than tons of text.

As the fzf project page doesn’t have any demo video so far, I’ve called this post “missing demo found”. But now, this video has already been pulled into the fzf repo and has become a part of the project’s readme.

Searching for files

People who are used to a command line environment are likely familiar with the concept of Unix filters. This is when several independent utilities are composed together into a pipeline to produce the desired output step by step. For instance, this pipeline produces a list of strings:

$ yes | head -10 | awk '{ print NR, NR % 2 == 0 ? "even" : "odd" }'
1 odd2 even3 odd4 even5 odd6 even7 odd8 even9 odd10 even

Each program acts as a filter. In simple terms, fzf is just another Unix filter. It reads lines from stdin, launches an interactive finder dialogue, and finally writes selected items to stdout. The key point and difference from tools like GNU find, is its interactive finder dialogue that filters items instantly as you type.

“fzf” as a interactive unix filter

It might not sound too practical so far, but the primary use case for fzf is to search for files on the command line. With fuzzy matching and instant feedback, you’re only few characters away from finding the right file no matter how deeply it’s lost in the directory hierarchy. No need to jump back to your file manager, traverse the directory hierarchy, copy a file’s path and paste it back to the shell. Compare “file manager” vs “fzf” workflows below.

fzf vs file manager comparison

fzf supports fuzzy matching so you can just type several characters in a row and it will match lines with those characters scattered across the string. Alternatively, prefix a search term with a single quote, like 'string, to opt for exact matches only, or run as fzf --exact .

fuzzy vs exact match

It does not support regular expressions or glob patterns, so *.sh pattern would not work. But keep it simple — productivity and speed is your goal today. You don’t have spare time to compose and type correct regular expressions. Instead just type several words, or even parts of the words, delimited by a space, and that would cover >90% of the use cases. For the remaining 10%, use ^ and $ to match the start and end of the string respectively, and use ! to negate matching.

fzf matching syntax

Printing selected files to a command line is not super useful, so usually search is combined with some further action. For instance, you might open it with Vim, or pipe selected items to the next program.

# Open file in a Vimvim -o `fzf`
# Print info for each selected filefzf | xargs ls -l

Fuzzy completion for bash and zsh

To make it more convenient, fuzzy completion can be triggered if the word before the cursor ends with the trigger sequence which is by default **. For example, type vim ~/path/** and press TAB . Voilà, fzf steps in!

Double star fuzzy completion

** sequence triggers fzf finder and it resembles * which is for native shell expansion. At some point, you might even forget about fzf’s presence and get the impression it’s a native shell feature.

Format is as follows, where FUZZY_PATTERN is optional.


If you don’t like the ** sequence, you can use keyboard shortcuts. CTRL+T triggers fzf and pastes the selected file onto the command line, whereas ALT+C changes into the selected directory.

Changing directory

Ok, enough about searching files. Let’s talk about other useful applications. Changing your working directory is such a common operation. But nevertheless I’m always stuck a bit trying to recall and type the right directory’s path, making several mistakes along the way. It slows down my tempo. Even zsh completions do not compensate for it. But with fzf, changing directories is a breeze, no matter how deep and far it is. Just type cd ** and you’re almost there.

changing directory is like a breeze

Notice that while fzf is indexing your directory tree, you can start searching right away. Changing directories is my favourite use case, and fuzzy matching really excels here. It requires from you the same effort to change a directory whether it’s one level deep or ten levels deep.

ALT+C shortcut is an alternate way to trigger fzf in a change directory mode.

Command history

You might be using Ctrl+R keyboard shortcut to search through your command history. Great, but how about supercharging it with fuzzy finder? Look and compare.

Searching through command history

It pastes the selected item on the command line, so you can tweak it further.

Search the host name to SSH into

If you’re a backend developer and working with a number of remote servers, you might appreciate ssh+fzf combo. Use the same double star trigger sequence and type ssh ** . It pulls recently used IP addresses and host names from your ~/.ssh/config and brings up an interactive finder.

“fzf + ssh” combo

Send a signal to a process

Sometimes we want to send a signal to a process, but first we need to obtain its PID by name. Usually one uses pgrep <process_name> to resolve PID followed by a kill <process_pid> referring that PID. With fzf you can combine both steps. Type kill <TAB> and fzf steps in listing all your processes. No need to switch to a dedicated process monitor any more, like “Activity Monitor” on Mac.

Find a process and send a signal

Suppose you’re searching for files, but sometimes the file name itself does not tell you enough. So you might want to peek into a file’s content for a moment to make a decision. fzf covers you here as well.

Preview window

By default I have preview window off, but I toggle it on when I want to peek into the files. Plus, I’ve enhanced it with a coloured output and syntax highlighting using bat as a preview command.


There are two main ways to customize the stock version of fzf:

  • Change the behaviour of the finder dialogue (preview window, keyboard shortcuts, dimensions, custom actions, etc). See FZF_DEFAULT_OPTS environment variable.
  • Change the underlying find backend. By default it uses GNU find utility, but you can switch to the more advanced tools like fd or ripgrep. First, it’s faster than the stock find utility. Second, those tools respect .gitignore rules, so you don’t get node_modules or .git files in your search results. You can also use git ls-tree to list files when you’re in a Git repo. See FZF_DEFAULT_COMMAND environment variable.

Configuration is done through the environment variables. Here is the snippet from my setup. Not sure if it would work as is when copy-n-pasted, most likely there’re some other missing dependencies. But this is just to give you an idea of how the configuration looks.

Fzf and Vim

So far we’ve seen command-line usage only. But fzf is also shipped as a Vim plugin. And trust me, if you are a Vimmer, its worth adding to your vimrc. Vim usage is out of the scope of this post, otherwise no one would read it ?. But I talk about it thoroughly in the second part of the my video, also linked at the beginning of the post.

If you’re impatient, here is a small excerpt to draw your attention. Use :grep command for project-wide text search, open matches in fzf window in a full screen mode, further filter matches within fzf, and jump to the selected match. And don’t forget about instant file preview at the precise line position. That’s awesome, isn’t it?

fzf ❤️ vim


I hope you’re impressed of how super awesome fzf is. Chances are you already willing to install and give it a try.

Keep in mind that fzf is not only for file searching, although it’s the primary feature of it. As you can see, “search + action” is a general principle, but it’s abstract and powerful enough to work with any kind of list: files, directories, processes, host names, etc. Remember at the beginning of this post — fzf is just a Unix filter. Unlock your imagination, feed it any list, and tailor it for your own needs. You might take some inspiration from a wealth of examples.

BTW, appreciate how superior Unix philosophy is. fzf is a great example of a program that adheres to these principles.

  • let the program to do one thing and do it well (single responsibility principle)
  • make it abstract enough to be agnostic of irrelevant details or data types
  • compose separate individual programs using standard well-defined interfaces.

Stick with those principles in your software development career. Knowing fundamental principles that stand behind the rapid birth and death of multiple tools, languages, and frameworks out there is what differentiates professional developers from amateurs.


junegunn/fzf: A command-line fuzzy finder —

Vim universe. fzf — command line fuzzy finder — YouTube —

My Youtube channel. There’re only a few videos, as I’m taking my first steps into making screencasts. Be patient, I promise to make more videos. Alexey Samoshkin — YouTube —

sharkdp/fd: A simple, fast and user-friendly alternative to ‘find’ —

BurntSushi/ripgrep: ripgrep recursively searches directories for a regex pattern —

junegunn/fzf.vim: fzf vim —