Cron Calendar
Explain cron expressions and preview the next run times in any timezone.
OpenGet a quick glossary of the common symbols a regular expression uses.
Enter the regex without surrounding slashes or flags.
Thirteen common tokens are looked for anywhere in the text.
Each symbol found is listed with a plain-English meaning.
Use the Regex Tester for an exact, token-by-token reading.
A teammate's pull request adds ^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}$ and you want a reminder of what the symbols do before reviewing it. Regex Explainer lists the familiar building blocks in the pattern, each with a one-line meaning.
The explainer checks your pattern for thirteen common building blocks: the dot, \d, \w and \s, the ^ and $ anchors, the *, + and ? quantifiers, alternation with |, capturing groups, character classes and {} ranges. Each one is listed once with its meaning, under a copy of the pattern. Output refreshes as you type and can be copied or downloaded.
It is a glossary, not a parser. The check looks for each symbol anywhere in the text, so an escaped dot like \. is still listed as 'any character', and it does not describe token order, lookarounds, backreferences or what a particular class such as [A-Z] contains. For a breakdown of the actual pattern token by token, together with live matches, use the Regex Tester's token explanations. The regex quick reference card covers syntax this glossary skips, such as \b, non-capturing groups and flags.
Everything runs as simple string checks in the page, so private patterns from your codebase stay local.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
The explainer checks whether each symbol appears anywhere in the text, so it cannot tell an escaped dot from a real wildcard. In a pattern, \. matches a literal period. Use the Regex Tester when you need an exact reading.
No. It covers thirteen common symbols only. Lookarounds such as (?=...), backreferences like \1 and Unicode property escapes are not described here; the Regex Tester's token table gives a fuller breakdown.
They are the meanings shared by JavaScript, Python, PCRE and Java. Details differ between engines, for example whether $ matches before a trailing newline, so confirm edge cases in the language you use.