How to use the Regex Explainer
1. Paste any regular expression — with or without surrounding slashes and flags.
2. Each part of the regex is broken down with a colour-coded explanation.
3. Use the quick-load examples to explore common patterns.
Tip: wrap your regex in /pattern/flags format to see flag explanations (g, i, m, s, u, y).
What is it?
Regular expressions are powerful but notoriously hard to read. A regex like /^[\w.+-]+@[\w-]+\.[a-z]{2,}$/i can be intimidating at first glance — this tool breaks it into individual components and explains each one in plain English.
Components are colour-coded by type: anchors (position), escapes (special characters), character classes (sets of characters), groups (capturing/non-capturing), quantifiers (repetition), alternation (OR logic), and literals (exact text).
Unlike a regex tester (which tests a regex against text), a regex explainer tells you what a regex means — useful for code review, documentation, and learning.
Example
/^\\d{4}-\\d{2}-\\d{2}$/^ → Start of string
\d → Any digit (0–9)
{4} → Exactly 4 times
- → Literal: "-"
\d → Any digit
{2} → Exactly 2 times
- → Literal: "-"
\d → Any digit
{2} → Exactly 2 times
$ → End of stringISO date pattern: matches YYYY-MM-DD format only.
Benefits
Generate accurate code from your actual data
TypeScript interfaces, Python dataclasses, and OpenAI function schemas are generated directly from your real JSON — accurate field names, correct types, no guesswork.
Control LLM API costs before you scale
Token counts and per-call cost estimates for GPT-4o, Claude 3.5, and Gemini let you optimise prompt size and model choice before a feature goes to production.
Ready-to-run code and configs, not boilerplate
Every tool produces output you can paste directly into your project — API request code, prompt templates, chunk configurations — adapt rather than write from scratch.
Purpose-built for AI engineering workflows
From RAG chunking strategy to prompt template selection to function calling schema design — tools built for the specific problems AI engineers encounter daily.
Frequently asked questions
What is the difference between a regex tester and a regex explainer?
A tester checks whether a regex matches a specific string — it tells you if it works. An explainer tells you what the regex means — it decodes the pattern into plain English. Both tools together help you build and understand regex patterns.
What are the regex flags and what do they do?
Flags modify how the regex engine works: g (global) finds all matches not just the first; i (case-insensitive) ignores upper/lower case; m (multiline) makes ^ and $ match line starts/ends; s (dotAll) makes . match newlines; u (unicode) enables full Unicode support; y (sticky) matches only at the current position.
What is a capturing group vs a non-capturing group?
A capturing group (abc) saves the matched text so you can reference it later (e.g. $1 in replacement or match[1] in code). A non-capturing group (?:abc) just groups the pattern for quantifier purposes without saving the match — more efficient when you don't need the capture.
What is a lookahead / lookbehind?
Lookaheads and lookbehinds are zero-width assertions — they check for a pattern without consuming characters. (?=abc) is a positive lookahead (must be followed by abc), (?!abc) is negative (must NOT be followed by abc), (?<=abc) is positive lookbehind, (?<!abc) is negative lookbehind.
What is the difference between greedy and lazy quantifiers?
Greedy quantifiers (* + ?) match as much as possible. Lazy/non-greedy quantifiers (*? +? ??) match as little as possible. For example, <.+> matches the whole string '<b>hello</b>' greedily, but <.+?> matches just '<b>' lazily.