SimpleLogSearch

Frequently Asked Questions

The fourteen questions users ask most — privacy first, then file types and limits, browsers, WebMCP, and how to reach the author.

Is my data sent anywhere?

No — your file never leaves your browser; everything is searched locally and forgotten when the page closes. Only your interface language is stored.

Can I search CSV, JSON, or XML files?

Yes — any line-based text file: app logs, syslog, access logs, Windows Event exports, CSV, JSON lines, XML dumps. Matching is case-insensitive substring per line; binary files not supported.

Why is there no account or server?

Because neither is required — a file that never leaves your machine needs no database, upload pipeline or login. Only your interface language is remembered.

What browsers are supported?

Any evergreen browser — Chrome, Edge, Firefox, Safari all run the app. Only the WebMCP agent tools need a newer client: Chrome 149+, Edge 150+, ChatGPT Desktop.

What is WebMCP, and how do I use it as a user?

WebMCP is a W3C standard that lets AI agents use a web page's capabilities as tools; SimpleLogSearch registers four. In a WebMCP-capable browser, ask your assistant in natural language and it runs searches for you.

How big a file can I open?

Up to 50 MB; larger files are rejected before reading. The results window is virtualized — only visible rows exist — so a 10 MB log with 100,000 lines scrolls smoothly.

Can I search across multiple files?

Not yet — v1 holds one log at a time; a second upload replaces the first. Multi-file search is on the roadmap; meanwhile: search one file, note matching line numbers, load the next.

How do line numbers work?

Every result keeps its original line number from your file — filtering never renumbers. A match labeled 4,182 is line 4,182 in the file: jump straight there in an editor or SIEM.

What happens to my file when I reset or upload a new one?

Reset clears the search box and errors — the file stays loaded. A new upload discards the old one completely; closing the page forgets everything.

Is it mobile-friendly?

Yes — responsive down to phone width, verified at 390 pixels. Large files work on a phone too; a desktop screen is more comfortable for long result sets.

Is the search case-sensitive?

No — case-insensitive substring: error, Error and ERROR find the same lines. Subtlety: no word boundaries, so 192.168.1.1 also matches a line with only 192.168.1.10 (the syntax reference covers the fix).

Why is it free?

Nothing to charge for — no server or tiers, just a few dollars of GitHub Pages hosting. Google AdSense ads cover that; no paywall, and your files are never shared with advertisers (see the Privacy Policy).

Who makes this?

Chris Pardue, a certified cybersecurity professional, also runs CEHStudy, a free CEH exam prep site. He built this for himself first — private log triage without sending files anywhere; via WebMCP, AI agents get the same.

How do I contact the author?

Use cehstudy.com/contact — bug reports, feature requests and feedback are read personally (multi-file search is the most requested addition); no ticket system exists because there are no accounts.