Export Formats
Note: Exporting explanations requires an account on a deployment that enables these features.
Export your regex explanations in multiple formats for documentation, code reviews, and team sharing.
Available Formats
Markdown
Standard Markdown format, perfect for:
- README files
- Wiki pages
- Documentation sites
- Note-taking apps
Example output:
# Email Validation
## Pattern
\`\`\`regex
/^[\w.+-]+@[\w.-]+\.[a-zA-Z]{2,}$/gi
\`\`\`
## Explanation
1. Start of string
2. One or more word characters, dots, plus, or hyphens
3. Literal @ symbol
4. One or more word characters, dots, or hyphens
5. Literal dot
6. Two or more letters (TLD)
7. End of string
---
*Generated by [RegexLens](https://regexlens.dev)*PR Comment
GitHub-friendly format with collapsible details:
<details>
<summary><strong>Email Validation</strong></summary>
**Pattern:**
\`\`\`regex
/^[\w.+-]+@[\w.-]+\.[a-zA-Z]{2,}$/gi
\`\`\`
**Explanation:**
| Step | Description |
|------|-------------|
| 1 | Start of string |
| 2 | One or more word characters, dots, plus, or hyphens |
| 3 | Literal @ symbol |
| 4 | One or more word characters, dots, or hyphens |
| 5 | Literal dot |
| 6 | Two or more letters (TLD) |
| 7 | End of string |
</details>
*Generated by [RegexLens](https://regexlens.dev)*This renders as a collapsible section in GitHub PRs and issues.
Notion
Notion-compatible format with callouts and toggles:
# Email Validation
## Pattern
\`\`\`
/^[\w.+-]+@[\w.-]+\.[a-zA-Z]{2,}$/gi
\`\`\`
## Explanation
1. Start of string
> Anchors the match to the beginning
2. One or more word characters, dots, plus, or hyphens
> The local part of the email
3. Literal @ symbol
4. One or more word characters, dots, or hyphens
> The domain name
5. Literal dot
6. Two or more letters (TLD)
> Top-level domain like .com, .org
7. End of stringPlain Text
Simple text format for any context:
Email Validation
================
Pattern: /^[\w.+-]+@[\w.-]+\.[a-zA-Z]{2,}$/gi
Explanation:
------------
1. Start of string
2. One or more word characters, dots, plus, or hyphens
3. Literal @ symbol
4. One or more word characters, dots, or hyphens
5. Literal dot
6. Two or more letters (TLD)
7. End of stringHow to Export
- Enter your regex pattern
- View the Explanation tab
- Click the Export button
- Select your format
- Copy to clipboard or download
Including Warnings
When exporting, you can optionally include warnings detected in your pattern:
## Warnings
### 🟡 Unescaped Dot
The `.` in your pattern matches any character, not just a literal dot.
> **Tip:** Use `\.` to match a literal dot.API Access
Export explanations programmatically:
POST /api/export
Authorization: Bearer <your-token>
Content-Type: application/json
{
"format": "markdown",
"title": "Email Validation",
"pattern": "^[\\w.+-]+@[\\w.-]+\\.[a-zA-Z]{2,}$",
"flags": "gi",
"steps": [
{ "label": "Start of string", "depth": 0 },
{ "label": "One or more word characters...", "depth": 0 }
],
"warnings": []
}Response:
{
"content": "# Email Validation\n\n## Pattern\n\n..."
}Use Cases
Code Reviews
Add regex explanations to your PRs:
- Export as PR Comment format
- Paste into your PR description or comment
- Reviewers can expand to see the full explanation
Documentation
Document your regex patterns:
- Export as Markdown
- Add to your project's README or docs
- Keep explanations in sync with code
Team Knowledge Base
Share patterns with your team:
- Export as Notion format
- Paste into your team's Notion workspace
- Build a searchable regex library
Learning Materials
Create educational content:
- Export explanations for example patterns
- Use in tutorials, blog posts, or courses
- Help others understand regex concepts
Rate Limits
| Plan | Exports per Hour |
|---|---|
| signed-in | 10 |
Exports are rate-limited to prevent abuse. If you need higher limits for automation, contact support.