Why Standard JSON Tools Crash on Large Files
Every browser tab runs inside a V8 JavaScript engine instance with a hard heap memory limit — typically around 1.5GB on desktop Chrome and significantly less on mobile. When you paste a 500MB JSON file into a standard online formatter, the browser must allocate memory for the raw string, the parsed AST (Abstract Syntax Tree), and the DOM elements to render it. This triple allocation means even a 300MB file can consume over 1GB of heap, triggering an ERR_OUT_OF_MEMORY crash.
Database exports from PostgreSQL, MySQL, and MongoDB routinely exceed several gigabytes. Backend engineers frequently need to search these dumps for specific records — a particular user_id, a malformed email field, or a timestamp range. Until now, the only option was command-line tools like jq or grep, which lack visual feedback and require terminal proficiency.
How Stream Search Works (No RAM Required)
This tool takes a fundamentally different approach. Instead of loading your file into JavaScript memory, it uses the browser's native File System Access API (window.showOpenFilePicker) to establish a direct read stream to your hard drive. The file is never fully loaded — instead, it flows through a ReadableStream pipeline connected to a TextDecoderStream.
Each chunk (typically 64KB) is decoded from bytes to UTF-8 text, scanned against your search pattern (plain text or regex), and then immediately discarded from memory. The browser's RAM usage stays flat regardless of file size. You could search a 50GB log file and your browser would use the same amount of memory as searching a 1KB file.
When to Use This Tool
- Database Exports: Searching through
pg_dumpormongodumpJSON exports for specific records without loading them into a database first. - Application Logs: Scanning JSON-structured log files (e.g., from Winston, Pino, or structured logging pipelines) for error patterns or specific request IDs.
- Data Migration Validation: Verifying that specific fields exist across millions of records in a JSON Lines (
.jsonl) export before triggering an import. - Incident Response: During production incidents, quickly searching audit logs for compromised credentials or suspicious activity patterns.
Browser Compatibility
The File System Access API is currently supported in Chromium-based browsers (Chrome, Edge, Brave, Opera) on desktop. Firefox and Safari do not yet support showOpenFilePicker. For cross-browser compatibility, consider downloading the file and using our standard JSON Formatter for files under 100MB, or use command-line tools for non-Chromium environments.
Security and Privacy
Your file never leaves your computer. The File System Access API provides a read-only handle to the file on your disk — the data streams directly from your hard drive into the browser's JavaScript runtime and is immediately discarded after scanning. No data is uploaded, cached, or transmitted to any server. This makes it safe to use with production database exports containing PII, credentials, or proprietary business data.
Related Tools
For files under 100MB, our JSON Formatter provides full beautification with syntax highlighting. To find specific keys in complex nested structures, try the JSONPath Evaluator. For visual exploration of JSON topology, use the Node Graph Viewer.