Skip to content
aicoolies logo

ripgrep Review: Fast Recursive Search with Sensible Defaults

ripgrep is a fast, cross-platform command-line search tool that combines recursive regex search with practical defaults for source repositories, including automatic ignore-file handling, hidden-file filtering, binary-file filtering, globs, and file-type controls.

reviewed by Raşit Akyol September 12, 2026 updated September 28, 2026

The reproducibility fields and source checks for this review are complete.

Tested
Version
ripgrep 15.2.0 (rev e89fff89ac), official x86_64 musl release binary, PCRE2 10.45
Environment
Debian 13 (trixie) x86_64, Linux 6.12.94, shared 8-vCPU KVM cloud VM (Intel Xeon), 15.6 GiB RAM, overlayfs, warm page cache; corpus: kernel.org linux-6.12.tar.gz (sha256 1376ce98…7ca4), 86,618 files / 1.48 GB extracted; hyperfine 1.20.0, 3 warmup + 10 runs per query; GNU grep 3.11 baseline

Verdict

ripgrep is an excellent default recursive search tool for developers and automation working in source repositories. It earns high marks for speed, local execution, predictable file-type and glob controls, and repository-aware filtering. Its defaults are intentionally selective, so exhaustive audits must explicitly include hidden, ignored, or binary content when required.

92/100

overall

Speed96
Privacy98
Dev Experience91

What ripgrep does well

ripgrep searches directory trees for regular-expression matches while applying repository-friendly filtering by default. It respects ignore files such as .gitignore, skips hidden files and binary files unless asked otherwise, and provides explicit glob and file-type controls. Those defaults make common codebase searches concise without preventing deeper searches when the task requires them.

Search controls and predictable escape hatches

The command supports file-type filters, include and exclude globs, context lines, replacement output, compressed-file search, multiple regex engines, and machine-readable output. When default filtering hides relevant data, --hidden, --no-ignore, --text, and the cumulative -u flag provide explicit escape hatches. The trade-off is that users must understand which filter is excluding a file before broadening the search safely.

Measured search results

We ran ripgrep 15.2.0 (official x86_64 Linux release binary, PCRE2 enabled) on 28 September 2026 against the pinned Linux 6.12 source tarball from kernel.org (86,618 files, about 1.5 GB extracted), on a shared 8-vCPU cloud VM with a warm page cache. Timed with hyperfine (3 warmup runs, 10 measured runs per query), a repository-wide literal search for EXPORT_SYMBOL_GPL returned 20,182 matching lines across 3,481 files in a mean of 208 ms. A regex search with line numbers for probe functions averaged 219 ms, a C-only (-t c) regex search averaged 165 ms, a Rust-only glob search averaged 32 ms, a case-insensitive search averaged 208 ms, and listing the 11,305 files that contain a GPL MODULE_LICENSE line averaged 205 ms. On the same literal query, GNU grep 3.11 (grep -r) returned the identical 20,182 lines in a mean of 1.15 seconds. Commands, versions, output hashes, environment details, and every per-run timing are in the public test record. These are single-machine measurements, not universal benchmarks.

Privacy and deployment

ripgrep runs locally and does not require an account, hosted service, or network request for normal searching. That makes its default privacy posture easy to reason about: searched content stays inside the environment where the command runs. Teams still need normal shell and CI controls because command output, logs, and pipelines can expose sensitive matches independently of ripgrep itself.

Limitations

Repository-aware defaults can surprise users who expect every hidden, ignored, or binary file to be searched. ripgrep is also not a universal drop-in replacement for every historical grep pipeline, especially scripts that depend on exact POSIX behavior or platform-specific flags. Finally, our measured run covers one shared Linux VM with a warm page cache. It does not measure cold-cache I/O, macOS or Windows behavior, or searches inside git checkouts, where .gitignore rules can shrink the searched file set.

Verdict

ripgrep is an excellent default search tool for developers, maintainers, and agents working across source repositories. Its strongest quality is the combination of speed, relevant default filtering, and precise opt-in controls. Learn the ignore and hidden-file rules before using it for audits that require exhaustive filesystem coverage.

Pros

  • Fast recursive regex search with repository-aware ignore handling by default.
  • Strong file-type, glob, context, replacement, and output controls.
  • Local, cross-platform, open-source operation with no hosted account requirement.
  • Clear escape hatches for hidden, ignored, or binary content.

Cons

  • Default ignore, hidden-file, and binary filtering can omit data during exhaustive audits.
  • Not a universal drop-in replacement for every POSIX grep script or platform-specific pipeline.
  • Published measurements cover one shared Linux VM with a warm cache; cold-cache and other-platform performance were not measured.

View ripgrep on aicoolies

Pricing, platforms, and community stacks — explore the full tool page

Alternatives to ripgrep

Command-line fuzzy finder

General-purpose command-line fuzzy finder written in Go that adds interactive filtering to any list — files, command history, processes, Git branches, and more. Blazing fast even on millions of entries. Integrates with bash, zsh, fish, and vim/neovim for history search (Ctrl+R), file finding, and directory jumping. Supports preview windows, multi-select, and custom key bindings. 67K+ GitHub stars. One of the most essential CLI productivity tools in the modern developer toolkit.

Open Source

A cat clone with wings

Modern replacement for the Unix cat command with syntax highlighting for 200+ languages, automatic paging, line numbers, Git integration showing file modifications, and themes including integration with terminal color schemes. Supports plain text output mode for piping. Extremely fast with Rust-based implementation. Can be used as a drop-in cat replacement via aliasing. 51K+ GitHub stars. Part of the modern CLI toolkit alongside fd, ripgrep, and eza.

Open Source

FAQ

Does ripgrep search hidden and ignored files by default?

No. ripgrep normally respects ignore files and skips hidden files. Use explicit flags such as --hidden, --no-ignore, or cumulative -u levels when the task requires broader coverage.

Can ripgrep search only selected file types?

Yes. It supports built-in file-type filters with -t and -T, custom type definitions, and include or exclude globs for precise repository searches.

Does ripgrep send source code to a cloud service?

No network service is required for normal searches. ripgrep executes locally, although shell history, CI logs, and downstream pipelines can still expose output and should be governed separately.

Is ripgrep a complete replacement for grep?

It covers most interactive recursive code-search needs, but scripts that depend on exact POSIX grep behavior or platform-specific options should be tested before migration.

Sources & verification

Sources checked
Content verified

Verification dates are editorial checks. Routine CMS saves and automatic updatedAt timestamps do not advance them.