How to Open a Large Log File
- Drop a log file onto the box above, or click to browse — any size, any extension.
- Wait for indexing. A Web Worker scans the file in 50MB chunks to build a byte-offset index — this is typically close to disk read speed.
- Scroll, search, and jump to matches. Only the visible rows are ever decoded, so scrolling stays smooth regardless of file size.
How It Stays Fast at 10GB+
Most browser-based file tools read the whole file into a JavaScript string — fine for kilobytes, but a multi-gigabyte log file would either crash the tab or freeze it for minutes. This tool never does that. A Web Worker reads the file in 50MB chunks and records only the byte offset of every 128th line, off the main thread. That tiny offset table is enough to know exactly where any line starts, so the viewer can jump straight to the bytes for whatever rows are currently on screen — typically fewer than 100 at a time — decode just those, and discard everything else. The file itself is never fully loaded into memory.
Frequently Asked Questions
Does this upload my log file anywhere?
No. The file is read directly by your browser and never leaves your device — there is no upload and no server involved.
How large a file can it actually open?
It's designed for 10GB+ files. The chunked index and virtual scrolling mean memory use stays roughly constant regardless of file size.
Why does the scrollbar feel less precise on very large files?
Once a file has hundreds of millions of lines, one pixel of scroll necessarily represents many lines — the same tradeoff tools like VS Code's large-file mode make. Use the Go to line box or jump-to-match navigation for exact positioning.
Does search find matches across the whole file, or just what's visible?
The whole file. Search runs in a background Web Worker and streams matches back as it scans, so you can start jumping to results before the full scan finishes.