What Can You Extract?

If you have a pattern, you can extract it. Common examples:

πŸ“§ Email Addresses

Pull every email from CRM exports, logs, or email threads. No regex needed.

Read guide β†’

πŸ”— URLs & Links

Extract API endpoints, config paths, and full URLs from text and config files.

Read guide β†’

πŸ” IP Addresses

Find all IPv4 and IPv6 addresses from logs, configs, and network traces.

Coming soon

πŸ“¦ Custom Patterns

Extract JSON properties, error codes, timestamps, or any regex pattern safely.

Coming soon

Real-World Scenarios

CRM Cleanup

You export 1,000 contacts from your CRM as raw text. You get a wall of text like:

Contact: Alice (alice@company.com, bob@company.com, charlie@example.com)...

Problem: Manually copy-pasting emails takes 30+ minutes.
Solution: Extract all emails in 3 seconds, paste into your new CRM.

Log File Debugging

Your app throws errors with URLs embedded in logs:

ERROR: Failed to reach https://api.service.com/v1/users at 14:32:15

Problem: Hunting through 500 log lines for URLs manually.
Solution: Extract all URLs at once, check which ones failed.

Config Audits

Your infrastructure team asks: "What IPs are whitelisted in this config file?"

allow_ips = ["192.168.1.5", "10.0.0.1", "203.0.113.42"]

Problem: Parsing nested configs manually is slow and error-prone.
Solution: Extract all IPs, load into your IP management tool.

Why Not Just Use Copy/Paste or Grep?

The Local Way

TextForge is a free Chrome extension that extracts data locally:

Quick Start

  1. Install TextForge from the Chrome Web Store
  2. Click the icon in your toolbar
  3. Paste your text
  4. Select the extraction type (emails, URLs, etc.)
  5. Copy the results

Privacy note: TextForge processes everything in your browser. Your text never leaves your machine, never reaches any server, never gets logged. It's the safest way to extract data from sensitive files, configs, and logs.