How to Open Huge Text Files Without Crashing Your PC

Before choosing a tool, ask yourself what you need to do with it. If you need to edit the file, you need an editor, but to work effectively, it must keep everything under control. If you only need to read and search—as is almost always the case with system logs—a viewer does much better because it keeps almost everything on disk.

Why normal editors freeze #

Windows Notepad has improved significantly, but it is still designed for small files. Notepad++ handles up to a few hundred megabytes well and starts to struggle beyond one gigabyte: the scroll bar becomes slow, searches take minutes, and sometimes you get an “out of memory” error.

This isn’t a flaw in the program. An editor needs to know where every line begins to handle edits, undos, and syntax highlighting, and all this information is stored in memory. With massive files, you simply run out of memory.

Viewers that work #

Large Text File Viewer does one thing and does it very well: it opens the file and lets you scroll and search, even using regular expressions. It doesn’t modify anything and has no extra features. It is portable, so there is no installation required: just extract the archive and run the executable, even from a USB stick. It can even read a log while another program is still writing to it.

The original developer’s website no longer exists, and the program hasn’t been updated in years. You can download it from the archived copy of the official page on archive.org, and it still runs without issues on Windows 10 and 11.

klogg is the best if you work with logs. It opens files of any size, and additionally, it lets you apply a regular expression filter to see only the matching lines in a separate pane—for example, all those containing ERROR—while the file continues to grow.

EmEditor is the only one on the list that also allows you to edit files dozens of gigabytes in size, and it handles massive CSVs with columns, sorting, and filters. It is a paid software, but if you spend your days working with these kinds of files, it pays for itself quickly.

The command line #

If you only need to see the beginning or end of a file, or search for a word, you don’t even need to open a program.

On Windows, using PowerShell:

# Le prime 100 righe
Get-Content registro.log -TotalCount 100

# Le ultime 50 righe
Get-Content registro.log -Tail 50

# Seguire il file mentre cresce
Get-Content registro.log -Wait -Tail 20

# Cercare una parola e contare le occorrenze
Select-String -Path registro.log -Pattern "ERROR" | Measure-Object

On Linux and macOS:

head -n 100 registro.log
tail -n 50 registro.log
tail -f registro.log
grep -c "ERROR" registro.log

To extract a chunk and work on it calmly—for example, from line 50,000 to 60,000:

sed -n '50000,60000p' registro.log > estratto.log

On Windows, you can use the same commands by installing the Windows Subsystem for Linux (WSL): if you work with it every day, this is the most convenient solution.

Splitting a file that is too large #

If a file needs to be fed into a program that cannot handle its size, split it up.

On Linux and macOS, in chunks of one million lines:

split -l 1000000 registro.log parte_

With PowerShell, you can read the file in blocks and write them out as separate files, but for CSVs, there is a better way: import them into a lightweight database like SQLite, or process them with a Python script that reads them block by block.

Character encoding #

Sometimes, when you open a file, strange symbols appear instead of accented letters. This is an encoding issue: the file uses a different character set than what the program expects.

Viewers allow you to change the encoding on the fly. Try UTF-8 first, which is the modern standard, and then Windows-1252 (or ISO-8859-1), which is still common in logs generated by older applications.

FAQ #

What is the limit of Notepad++? #

There isn’t a precise threshold; it depends on your memory and the file content. It works well up to a few hundred megabytes, but beyond one gigabyte it becomes slow, and near two gigabytes you start seeing memory errors. For large logs, go straight to a viewer.

How do I open a text file that is 10 GB or larger? #

Use a viewer that reads the file in blocks, such as Large Text File Viewer or klogg: it will open in seconds regardless of the size. If you only need to search for something, the terminal commands mentioned above are even faster.

Can I edit a massive file, not just read it? #

Yes, but your options are limited. EmEditor can do it directly. Alternatively, extract the part you need to correct, edit it, and put it back together using the command line. In any case, always make a copy of the file first.

Why has the log file become so large? #

Usually, this happens because of a lack of rotation—the mechanism that closes the file once it reaches a certain size, archives it, and opens a new one. On Linux, logrotate handles this; on Windows, it depends on the application writing the log. Setting up rotation prevents you from ending up with a 50 GB file.

Can you search through a massive file without opening it? #

Yes, and it’s actually the fastest method: grep or Select-String search the file directly without loading it into memory. On a log file dozens of gigabytes in size, they take only seconds, whereas a program with a GUI would take minutes.

Can you read compressed files directly? #

On Linux and macOS, yes, using zcat, zgrep, and zless, which decompress on the fly without writing anything to the disk. They are incredibly convenient for archived logs, which are usually kept compressed in .gz.