How to open a 10 GB log file on a Mac

Download Caxton for Free · 7-day free trial of Caxton Pro, no credit card required · 7 MB · macOS 13.0+

How do I view a huge log right now?

Terminal, zero installs. These four cover most on-call moments:

less -S app.log        # opens instantly; /text searches, G jumps to end, q quits
tail -n 1000 app.log   # the last thousand lines, now
tail -f app.log        # stream the file as it grows
grep -n -C 3 "ERROR" app.log > errors.txt   # matches with line numbers and 3 lines of context

less is the right first move because of what its own manual documents: it does not have to read the entire input file before starting. Inside it, F follows a growing file the way tail -f does, and &pattern shows only matching lines.

Often a slice is genuinely all you need. If the incident happened in the last hour, tail -c 200m app.log > tail.log carves the final 200 MB into a file any tool can open, and head does the same for the beginning. The grep-with-context pattern above turns a 10 GB haystack into a few thousand lines around the needles.

less already scrolls, searches, and moves between matches. Caxton adds an editable document, filters you can see, bookmarks, and incident tools in one Mac app.

Why can't my editor open a big log file?

Most editors, from TextEdit to the mainstream code editors, read the entire document into their own memory structures before rendering the first line. The cost of opening scales with what the file weighs, not with what you look at, and somewhere past a few gigabytes that means a stuck main thread, the beachball, and sometimes a machine deep in swap. Force-quitting is safe: the editor has only been reading. If the editor in question is VS Code, its large-file behavior and the ways around it are in file too large for VS Code.

The two designs that survive this size are streaming (read only the visible window, the way less does) and memory-mapping (let macOS page pieces of the file in on demand). Which mainstream editor was designed for what, with each vendor's own documentation as the record, is a survey of its own: large file text editors on a Mac.

This page is about logs. If your giant file is a CSV, the workflow is different enough to have its own guide: open a large CSV file on a Mac.

How do I search, filter, and edit the whole log?

Caxton's document model is a memory-mapped piece table: opening copies nothing and loads nothing up front. The published 10 GB benchmark log (80,610,954 lines) is scrollable and searchable immediately, while the full line index finishes in the background in 3.7 s. Memory stays under 160 MB through every measured operation on the 50 GB log, so an 8 GB MacBook is not the limiting factor. That memory figure is the 50 GB text benchmark on macOS 15.7; CSV grids and other macOS versions use more.

The 10 GB benchmark log with a literal search across all 80.6M lines: 1,613,344 matches in 1.0 s.

The working numbers, measured on an M1 Max with 64 GB RAM (methodology and the full table on the benchmarks page): a literal search over the 10 GB file returns 1,613,344 matches in 1.0 s, and filtering the view down to just those matching lines takes 1.0 s, with the noise gone and original line numbers preserved. A two-condition OR filter over the same file runs in 1.8 s. The filtering workflow end to end, from grep to multi-condition chains, has a guide of its own: filter a large log file on a Mac.

It is an editor, not a viewer, so the fix-it half of log work is on the table: a keystroke applies in about 1 ms at this scale, Replace All rewrites 1,613,344 sites in 1.7 s as one undo step (the whole replacement story, batch pairs and folders included: find and replace in a huge file on a Mac), and saving writes the same file back atomically in 11.3 s. For a log that is still growing, follow-tail pins the view to the end while search and filters keep working above. And when the "log" turns out to be one enormous line (JSON event streams do this), a search across a one-line 500 MB file still returns in 0.5 s.

Which approach fits which job?

Two more jobs on the same log: compare it against another copy side by side, and find and replace across a folder of logs without opening them.

Frequently asked questions

The incident won't wait for a progress bar. Download Caxton for Free and have the log open before the next page-out: 7-day free trial of Caxton Pro, no credit card required.