Download Cheat sheet PDF 12 pages · syntax, editors, patterns, Unicode, performance, debugging

Contact us.

Reach us at contactus@regexguide.com — we read every message.

Or send a message right here

This form opens your email client with the message pre-filled. We don't run a server — nothing leaves your device until you hit Send in your mail app.

0 characters

What we love hearing about

  • Patterns our explainer mishandles — paste the regex and describe what you expected vs. what you got
  • Wrong, broken, or unsafe patterns in our library — these are the most valuable bug reports; we'll prioritize them
  • Patterns you'd like added to the library — tell us the use case, we'll add it
  • Explanations that aren't clear enough — be specific about what confused you
  • Bugs — what you did, what you saw, what you expected

What we probably won't do

  • Add user accounts or "save to cloud" features — we're committed to client-side-only
  • Build a Chrome extension — we want everyone to land on a regular web page
  • Add AI features — we're explicitly the human-curated alternative to AI regex tools

Response time

One developer reads this inbox. Responses usually come within a few days. Bug reports about the regex engine or library get top priority; "what about [feature]" requests get answered when there's time.

For privacy-related requests

If you're exercising GDPR or CCPA rights, mention that in your subject line and we'll respond within 30 days as required by law. See the privacy policy for details on what data exists.