Linux/Mac Terminal Tutorial: The Grep Command - Search Files and Directories for Patterns of Text

Grep is a fast way to search for text patterns across files and directories from the Linux or Mac terminal, and mastering its options turns a simple “find this word” task into practical debugging and code-navigation work. At its core, grep scans files for lines that match a pattern and prints the matching lines—so the immediate payoff is knowing exactly where a string appears, not just that it exists.

A basic workflow starts with searching a single file. For example, running grep with a pattern like “John Williams” against names.txt returns every line containing that text. Grep is case-sensitive by default, which means “john” and “John” won’t match unless case-insensitive mode is enabled. The -i flag fixes that by matching regardless of letter case.

When partial matches are a problem, grep’s -w option helps enforce whole-word matching. That’s useful when searching for a full name but avoiding near-matches like “John Williamson” when only “John Williams” should count. Once matches are found, additional flags add the context people usually need for follow-up work. The -n option prints line numbers, making it easier to jump straight to the exact location in a file. For context around a match, grep supports several “window” options: -B shows lines before the match, -A shows lines after, and -C shows both sides (with a configurable number of lines). This is especially handy when searching source code, because the surrounding lines often reveal what the match refers to.

Grep becomes more powerful when applied to multiple files. Using a wildcard like * with grep lets it search everything in the current directory, while adding a file extension filter such as *.txt limits results to text files. If the goal is to search through an entire project—including subdirectories—grep’s -r recursive option is the standard approach. That said, recursion can be slow in large directory trees, so it’s worth being deliberate about where the search starts.

For large codebases, many users don’t need the matching lines themselves; they need to know which files contain the pattern. The -l option lists only filenames with matches, and -c reports how many matches each file contains. These switches help triage quickly before opening files.

Finally, grep’s pattern matching can go beyond plain text into regular expressions. By default, grep uses POSIX regular expressions, but Perl-compatible regular expressions (PCRE) require different handling—especially on macOS. On Linux, the -P option enables PCRE directly. On macOS, grep is typically BSD grep, so PCRE support may not work as expected; the workaround is installing GNU grep via Homebrew (brew install grep) so that -P behaves correctly. With GNU grep in place, PCRE features like \\d with quantifiers can be used to find phone-number-like patterns, and the same combination of -w, -i, -r, and -l can be layered on to search recursively and report only the relevant files.