Free Find and Replace Text Tool
Something not working? Report a problem
About the Find and Replace
Find and replace text online — plain text or regular expressions, case-sensitive or not, with a live match count, all in your browser with no upload.
How to use the Find and Replace
- 1Paste your text into the box on the left — it's processed on your device.
- 2Type what to find and what to replace it with.
- 3Optionally match case, or switch on regex mode for patterns, line anchors and capture groups.
- 4The updated text appears on the right with a live match count — copy it with one click.
Frequently asked questions
Is this tool free?
Yes — completely free, with no sign-up and no watermark.
Is my text uploaded anywhere?
No. All find-and-replace happens in your browser — your text never leaves your device.
Does it replace all matches?
Yes — every match is replaced, and the match count shows how many were found. There's no need to click through matches one at a time.
What is regex mode?
Regular expressions let you match patterns instead of exact text — for example \d+ matches any run of digits. In regex mode you can also use $1, $2 and so on in the replacement to reuse captured groups.
Why doesn't ^ match the start of every line?
It does, as long as “^ $ match each line” is ticked — which it is by default in regex mode. Untick it and ^ and $ only anchor to the very start and end of the whole text. There's a matching option for whether . should match newlines, which it normally doesn't.
Why did I get an “invalid pattern” message?
That appears in regex mode when the pattern can't be understood. The message spells out the reason — an unterminated group, an unmatched bracket, and so on. Fix the pattern, or turn regex mode off to search for the text exactly as typed.
It says my pattern is too slow — what does that mean?
Some patterns take exponentially longer as the text grows, usually ones with a repeat inside a repeat such as (\w+\s?)+. Rather than let that freeze the page, the tool gives every pattern a moment to finish and stops it if it overruns. Making the pattern more specific — narrower character classes, fewer nested repeats — almost always fixes it.