Regex Extractor

1. Add source records. Paste representative logs, notes, exports, or semi-structured lines.
2. Define the extraction pattern. Use boundaries so adjacent punctuation does not enter the result.
3. Choose a capture group. Select 0 for full matches or the numbered group containing only the needed field.
4. Handle duplicates. Keep every occurrence for traceability or enable unique output for a distinct list.
5. Validate the collection. Check the returned count, values, and offsets before importing the data elsewhere.

Turn matching text into a structured list

Regex Extractor scans the source for repeated records and emits only the chosen values. It does not include the complete diagnostic tree produced by Regex Tester and it does not create transformed prose like Regex Replace. The result is intentionally compact: selected group, count, match number, value, and source offset.

This workflow fits log identifiers, version numbers, dates, URLs, email-like strings, reference codes, and labels in semi-structured exports. Regex works best when every desired token has a repeatable boundary.

Examples for extracting regex matches

Collect all email-like values

Pattern: \b[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,}\b
Flags: iu
Group: 0

Return only order identifiers after a label

Pattern: \border=([A-Z]{2,5}-\d{3,8})\b
Input: order=API-2048 status=paid
Group: 1
Output value: API-2048

Collect distinct software versions

Pattern: \bversion[=: ]+v?(\d+(?:\.\d+){1,3})\b
Flags: iu
Group: 1
Unique values: enabled

Extract ISO-shaped dates

Pattern: \b\d{4}-(?:0[1-9]|1[0-2])-(?:0[1-9]|[12]\d|3[01])\b
Group: 0

Collect the value inside quoted ID fields

Pattern: \bid=["']([^"']+)["']
Group: 1

Complete matches versus selected groups

Use group 0 when boundaries are excluded from the pattern and the full match is already clean. Use a numbered group when a stable label such as order= is needed to locate the value but should not be exported. Non-capturing parentheses (?:...) organize a pattern without increasing the group number.

If the selected group does not exist, the tool stops with a clear error. If an optional group does not participate in a particular match, that row is skipped. Test every alternative branch so the chosen group remains present and meaningful.

Duplicates, occurrence numbers, and offsets

Keep duplicates when each occurrence matters, such as repeated events in a log. Enable unique values for a compact set of domains, identifiers, or versions. Deduplication preserves the first occurrence, so its offset still points to a real location in the source.

Offsets are measured in UTF-8 bytes. For human-facing Unicode character offsets, line numbers, and columns, open the same expression in Regex Tester PRO. A byte offset is still useful for server-side processing and tracing values back into the exact source payload.

Validate extracted values after collection

A regular expression can confirm shape without confirming meaning. An ISO-shaped date can still name a nonexistent calendar day, an IPv4-shaped candidate can contain an invalid octet if the pattern is broad, and an email-like value can reference no working mailbox. Apply domain validation before database import or automation.

Compare the returned count with an expected range. An unexpectedly large count often means a permissive boundary or an empty-string-capable expression. Review the PHP preg_match_all reference and PCRE2 documentation for engine behavior.

Related Trexmi tools

Inspect every group and position with Regex Tester PRO, generate a starting expression with Regex Builder, or modify matching source text with Regex Replace.