Extractors

Paste a messy block of text — a log file, an email thread, a scraped webpage — and pull out just the dates, IP addresses, hashes, UUIDs, or JWTs hiding inside it, without manually scanning line by line.

Most real-world text isn’t structured cleanly enough for a simple find-and-replace to help. Log files bury useful identifiers in a wall of timestamps and noise; a support email might mention a UUID or hash somewhere in a paragraph of prose. This tool runs pattern-matching against the whole input at once and returns a clean, deduplicated list of just the matched values, sorted by type.

To use it, paste your text and choose which pattern type to extract — dates, IPv4/IPv6 addresses, MD5/SHA hashes, UUIDs, or JWTs — or run all of them simultaneously to see everything the text contains across every category. Toggle deduplication if the same value appears multiple times and you only want it listed once, and export the results as a plain list or CSV if you’re feeding them into another tool.

Frequently asked questions

Can it extract more than one pattern type at once?

Yes — select multiple categories, and the results are grouped separately by type rather than mixed into one combined list, so you can still tell a UUID apart from an IP address at a glance.

Does it validate that a matched value is real, or just that it fits the pattern?

It checks structural validity — for example, confirming a matched IP address falls within valid octet ranges, or that a UUID follows correct formatting — but it can’t confirm the value is meaningful or currently active in whatever system it came from, only that it’s correctly formatted.

What if I need to extract emails or URLs specifically instead of the categories listed here?

That’s the Bulk Email & Link Extractor, a dedicated tool for exactly that pair of pattern types, since email addresses and URLs are common enough to warrant their own focused tool rather than being folded into this more general extractor.

Is there a limit to how much text I can paste in at once?

No hard limit — since matching runs locally in your browser, very large inputs (a full log file, for instance) may just take a moment longer to process than a short paragraph.