Regex & Text Tools

Regular expressions are a small programming language for matching text, and they are powerful exactly because they are compact: one expression can validate an email, extract a URL or find every log line for a given service. The compactness is also the problem - a regex that looks right fails on an edge case, and debugging a pattern by trial and error in a terminal is slow.

The tester is the center of the category. It runs a pattern against sample text with live results: which strings match, where the match starts and ends, and what each capture group holds. Because you see the result on every keystroke, the tester turns regex debugging from guesswork into a loop of change-and-check.

The builder and the escaper attack the two ways patterns go wrong. The builder assembles a regex from parts - literal, character class, quantifier, group - so a pattern is constructed from the same units a regex engine parses, which catches the structural mistakes early. The escaper handles the opposite case: text you want to match literally, like a file path or a version string, gets every special character escaped so it matches itself instead of acting as syntax.

The text diff completes the category for the non-regex half of text work. It compares two strings and shows the additions and removals line by line, which is the fastest way to see what changed between two versions of a config, a payload or a template.

A note on regex flavors. Patterns behave differently across engines: JavaScript, Python and PCRE differ in lookbehind support, in how named groups are written, and in what counts as a word boundary. The tester here uses JavaScript semantics, so patterns validated here match what a browser or Node.js will do - write for your engine and test in its dialect.

As everywhere on the site, processing is local. Your sample text and pattern never leave the browser, which makes the tester a safe place to paste production log lines or a real email list.