grepWin review: free regex search and replace across whole folders

Who grepWin is for

grepWin is built for anyone who edits text at scale: developers renaming a function across a project, sysadmins fixing a path in dozens of config files, writers swapping a term through a folder of Markdown notes, webmasters updating a URL in hundreds of HTML pages. If you've ever opened twenty files one by one to make the same edit, this tool exists for you.

It's the work of Stefan Küng, best known as the developer of TortoiseSVN — the near-ubiquitous Windows Subversion client. That pedigree shows: grepWin is the kind of focused, reliable utility you'd expect from someone who has maintained serious Windows tooling for decades, and the source is public on GitHub if you want to verify what it does.

It is not the right tool for searching Word documents, PDFs or email — grepWin reads raw text only. For that job, see Agent Ransack or DocFetcher.

Key features

Full regex search — and replace

grepWin supports full regular expressions for both the search pattern and the replacement string. Crucially, replacements can use capture-group backreferences: search for version="(\d+)\.(\d+)" and replace with version="$1.$2.0", and every match is rewritten with its own captured values. That single capability separates grepWin from nearly every other tool we cover — most can find; almost none can transform. If regex syntax is new to you, start with our regex file search guide and its copy-paste patterns.

Backup before replace

Tick "create backup files" and grepWin writes a copy of every modified file before changing it. For an operation that can alter hundreds of files in one click, this safety net matters — and we recommend leaving it on until a pattern has proven itself.

File masks, include and exclude

Limit a search to *.cs;*.csproj, exclude node_modules or .git by pattern, cap file sizes, and filter by modification date. These controls keep big searches fast and stop replacements from straying into folders they shouldn't touch.

Presets and shell integration

Frequently used search/replace pairs can be saved as named bookmarks and recalled in two clicks. grepWin also registers a right-click "Search with grepWin" entry in Explorer, which pre-fills the folder — in daily use this is how you'll launch it almost every time.

Dark mode and a portable build

A proper dark theme is built in, and a portable version runs from a USB stick or network share with no installation — handy on machines where you can't install software.

Performance in our testing

On our reference rig (Ryzen 7, 32 GB RAM, NVMe SSD), grepWin chewed through a source tree of roughly 60,000 text files in well under a minute for a literal-string search, with regex patterns adding modest overhead depending on complexity. That's brute-force scanning, so speed scales with how much text it has to read: tight file masks and excluded folders make a bigger difference than anything else.

Replace operations performed in our testing exactly as advertised — backreferences substituted correctly, backups appeared alongside originals, and a test run with deliberately greedy patterns showed why you should always search first, inspect the match list, then replace. grepWin shows you every match with surrounding text before you commit, and counts matches per file, which makes sanity-checking easy.

Because there's no index, there's also no background process, no RAM cost when idle, and no first-run wait. The flip side: repeating the same search re-reads the same files every time. If you search the same large corpus daily, an indexed tool may suit you better.

Ease of use

The single-window UI is utilitarian: folder picker, search and replace boxes, a wall of checkboxes, results grid below. Nothing is animated and nothing is hidden, which experienced users will appreciate and newcomers may find dense. Switching between "regex search" and "text search" modes is one radio button, so you can use it as a simple literal-string finder without ever writing a pattern.

The honest caveat is the regex learning curve itself. grepWin can't protect you from a pattern that matches more than you intended — the backup option and the preview-before-replace workflow are your guardrails. Budget twenty minutes with a pattern reference the first time and you'll be fine.

Pricing

grepWin is completely free and open source (GPL), with no paid tier, no nags and no telemetry games. Downloads — installer and portable, 64-bit and ARM64 — are on the official site at tools.stefankueng.com. Donations are welcome but never solicited inside the app. Among the best free file search tools we've tested, it's one of the very few with zero commercial angle at all.

Alternatives worth considering

• Agent Ransack — the better free pick for finding text inside Office files and PDFs, with a rich preview pane, but it can't replace anything. We compare the two directly in Agent Ransack vs grepWin.
• DocFetcher — open-source indexed content search across many document formats; the right call when you query the same library repeatedly.
• Everything — if your problem is finding files by name instantly rather than by contents.

For the full ranked field across every use case, see our roundup of the best file search software.

Final verdict

grepWin earns its 8.5/10 by owning a niche outright: free, auditable, regex-powered search and replace across entire folder trees, with backups and presets that make it safe to use at scale. The plain-text limitation and spartan UI are real, but they're the cost of a tool this focused. Every developer and admin's Windows toolkit has room for it.