Multi-File Log Search

When the answer is scattered across files, Multi-File Log Search finds it in one pass. Paste several logs marked with file separators, type a query, and every match appears grouped by file with per-file counts.

Plain text or regex, case-insensitive, fully in the browser — the fastest way to hunt a token across a merged set of logs.

• Multiple files — separated in one paste.
• Plain or regex — search either way.
• Per-file counts — summary + detail.
• Case-insensitive — no exact-match surprises.
• Copyable results — keep the evidence.

1. Mark each file with a separator line before its content — either === FILE: name === or a simpler --- name ---. Anything pasted before the first separator is collected into a (default) file, so a single un-separated log still works.
2. Type your search term in the search box, or tick Regex and write a pattern instead — the search is always case-insensitive either way.
3. Optionally tick Whole word to match the plain-text term only at word boundaries — useful when searching for a short token like id that would otherwise match inside longer words like valid.
4. Click Search. Every file section shows its own match count, even zero, so you immediately see which files were clean and which need attention.
5. Copy the grouped results for a bug report or incident writeup.

Example 1 — Error hunt. Paste app, worker and cron logs as three sections and search ERROR to see, at a glance, which service is throwing and which are silent — the per-file summary line makes the split obvious even before reading a single matched line.

Example 2 — User trace. Search a user id or request id across auth, API and billing logs in one query to reconstruct what happened to a specific request as it moved through your stack, without opening three separate files.

Example 3 — Slow path. Regex-search (slow|timeout) across several service logs at once to map where latency problems are concentrated — a file with a high match count is your starting point for investigation.

Example 4 — Merged support bundle. Many support-bundle exports concatenate several component logs into one text blob with simple --- filename --- headers between them; paste the whole bundle as-is and search once instead of splitting it into separate files first.

• One query, many files — scan them together.
• Attributed results — know which file hit.
• Regex power — when substring is not enough.
• Private — nothing leaves the browser.