Read-only
It does not edit multi-gigabyte logs or perform regex replacements across them.
Large log file guide · read-only investigation
To investigate a multi-gigabyte log on Mac, use a viewer that reads bounded pages instead of loading the whole file into an editable buffer. ZapPad’s separate huge-file viewer pages UTF-8 content and searches literally across the file. It is read-only; normal editing supports files up to 16 MiB.
Currently offered to US customers only · Apple Silicon (M1+) · macOS 12+
The embedded player loads only when you choose to play it. YouTube processes playback data under its own privacy policy. Watch on YouTube ↗
A log may contain millions of lines, repeated payloads and a few important warnings. Opening every byte as one editable text document can demand far more memory than the file’s size, depending on the editor and its internal representation. For incident review, you often need to find an identifier and read surrounding lines, not edit the whole file.
Use an editor’s documented limits and test on a copy when the log is important. A paged viewer can limit each read to a small window, keep navigation responsive and search without materializing the full file in memory.
The viewer uses 256 KiB default pages and bounded-memory Rust processing. A recorded Apple M4 benchmark searched a synthetic 4 GiB file in three warm-cache runs of 286, 524 and 283 ms; this is not open time, cold-disk performance or a guarantee for other hardware. Read the complete benchmark conditions.
It does not edit multi-gigabyte logs or perform regex replacements across them.
The large-file viewer is for UTF-8 logs; legacy encodings belong in ordinary editing with an explicit encoding choice.
Viewer filters apply to the current displayed page; literal search covers the file.
Standard editable text is limited to 16 MiB in the current build.
For a live incident, Follow Tail refreshes the last page as new content is written. Check the ZapPad manual for exact controls and current behavior.