Escape regex special characters for a literal match

Literal text cannot always be inserted directly into a regular expression. Characters such as a period, question mark, bracket, or backslash are instructions in regex syntax, so an unescaped value can match the wrong text or even make the pattern invalid. This capability converts a string into an ECMAScript pattern fragment that treats every regex metacharacter literally. It is useful when search terms, filenames, identifiers, labels, or other user-provided values must become part of a larger regular expression without changing their meaning.

Turn literal text into a safe pattern fragment

Send the exact value you want a regular expression to match in the text field. The result contains escaped, a pattern fragment in which every ECMAScript regex metacharacter has a preceding backslash. Ordinary letters, digits, spaces, punctuation without regex meaning, line breaks, and Unicode characters remain unchanged.

For example, a period normally means any character in a regular expression, while an escaped period means an actual full stop. Parentheses normally create a group, square brackets open a character class, braces can introduce a repetition count, and question marks or asterisks control repetition. Escaping those symbols preserves the literal meaning of the original value.

The returned fragment does not include slash delimiters or flags, so it can be passed directly to a RegExp constructor, embedded in a larger pattern, or stored as a pattern body. An empty input string is valid and produces an empty escaped value because there are no characters to transform.

Compose the escaped value with deliberate regex syntax

Escaping is most useful when part of a pattern comes from data and another part is intentionally written as regex syntax. Suppose an application needs to find a user-supplied product code only at the beginning of a line. Escape the product code first, then add the start anchor and any deliberate boundary logic yourself.

This separation keeps trusted pattern structure distinct from literal content. Do not escape an entire pattern after composing it, because doing so would also neutralize the anchors, groups, alternatives, or quantifiers you intended to keep active. The output targets an ECMAScript pattern body rather than JavaScript source-code notation.

That distinction matters: slash characters are not special to the RegExp constructor and therefore are preserved. If you place the result inside a slash-delimited regex literal in generated JavaScript source, source-level delimiter escaping is a separate concern. In ordinary application code, prefer passing the returned escaped string to new RegExp along with separately selected flags.

Know the guarantee and validate the surrounding design

The transformation is deterministic and linear: it scans the supplied string and prefixes the characters that control ECMAScript regular-expression syntax. It does not use a network, execute the resulting expression, choose flags, add anchors, or decide whether matching should be case-sensitive. Those choices belong to the surrounding application because they change matching behavior rather than literal safety.

Each of those formats has its own escaping rules, and combining them with regex escaping requires applying each layer at the correct boundary. After composition, test the complete pattern against representative positive and negative examples, especially when adding optional sections or alternation around the escaped fragment.