Regular Expressions (Regex) Cheat Sheet & Quick Reference

Overview

Regular expressions (Regex) provide concise syntax for searching, matching, and manipulating text strings across log files, input validation forms, and data parsers. Mastering core metacharacters, character classes, quantifiers, and lookaround assertions eliminates brittle string manipulation loops.

This reference sheet organizes standard ECMAScript and PCRE patterns into structured syntax tables for instant lookup during coding and debugging rounds.

Syntax Tables: Character Classes & Anchors

Quantifiers & Groups

Practical Patterns for Daily Work

Standard patterns frequently required across application input validation and log parsing:

# Email Validation (Pragmatic RFC 5322 approximation)
^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$

# ISO 8601 Date String (YYYY-MM-DD)
^\d{4}-(?:0[1-9]|1[0-2])-(?:0[1-9]|[12]\d|3[01])$

# Slug / URL Safe Identifier
^[a-z0-9]+(?:-[a-z0-9]+)*$

# IPv4 Address Extraction
\b(?:(?:25[0-5]|2[0-4]\d|[01]?\d\d?)\.){3}(?:25[0-5]|2[0-4]\d|[01]?\d\d?)\b

Common Mistakes & Pitfalls

• Unescaped Metacharacters: Forgetting to escape literal dots (`.`) in domain matching (`example.com` matches `exampleXcom`). Always write `example\.com`.
• Catastrophic Backtracking: Nested greedy quantifiers like `(a+)+$` on non-matching strings can freeze regex engines. Avoid nested quantifiers on overlapping character sets.
• Ignoring Anchors: Omitting `^` and `$` during form input validation allows malicious strings embedded within larger payloads to slip through.

Best Practices

• Use Non-Capturing Groups: Default to `(?:...)` instead of `(...)` when grouping alternatives unless you specifically need to extract the submatch. This improves memory performance.
• Test Edge Cases: Always verify regex behavior against empty strings, unicode characters, and long inputs using live browser testing utilities.

Related Interactive Tools

Related Engineering Guides

Frequently Asked Questions