Guides

Text editors for one big .txt file

Updated: October 27, 2026

Not every editor is a good fit for one large .txt. A 5–50 MB file with thousands of lines needs fast search, careful encoding handling, and predictable behavior without syntax highlighting.

Selection criteria

• Speed on large files. The editor should not freeze when opening, searching, or replacing.
• Search and regular expressions. Regex search, replace, and go-to-line are valuable.
• Encoding and line endings. UTF-8, CRLF/LF, and correct display of non-Latin text.
• Cross-platform support. The ability to open the file on another OS without conversion.
• Mobile support. Separate apps for iPhone, iPad, and Android.
• Price and license. Free, freemium, and paid options.
• Extensibility. Plugins, macros, Git integration, and terminal access.

Desktop editors

Sublime Text

A fast cross-platform editor with excellent search, regular expressions, multi-cursor editing, and a large plugin ecosystem. It handles large text files well. The license is paid, but there is an unlimited evaluation mode.

VS Code

A free editor with a huge extension ecosystem. For large files, the files.maxMemoryForLargeFilesMB setting matters; at tens of megabytes, disable the minimap, syntax highlighting, and unnecessary extensions. It is convenient if you already work in VS Code and want notes next to code.

BBEdit

A macOS editor with strong large-file support, regex search, and macros. There is a free mode with limitations and a paid full version. A good choice for a native macOS tool.

Notepad++

A free Windows editor with many plugins, regex search, and support for multiple encodings. A familiar option on Windows when a full IDE is unnecessary.

TextEdit and Notepad

Built-in OS editors work for quick edits but can struggle with very large files and offer weaker search. For daily OBTF use, an editor with file history and regex search is a better fit.

Terminal editors

Vim and Neovim open large files almost instantly and support regex, macros, and work without a graphical shell. The learning curve is steeper, but for a file that lives in a terminal and Git, it is a strong option.

Emacs offers comparable flexibility and extensibility. Like Vim, it takes time to learn, but it works equally well locally and over SSH.

nano is a minimal editor without extra features. It is fine for a quick fix, but not for complex search and replace.

Mobile editors

• iA Writer — macOS, iOS, and iPadOS, clean plain text and Markdown editing with a focus mode. Paid.
• Textastic — iOS and iPadOS, a code and text editor with highlighting, search, and Files access. Paid.
• Working Copy — an iOS Git client that can edit files. Useful when sync runs through Git.
• Markor — a free Android editor for Markdown and plain text with local file access.
• Acode — a free Android editor with highlighting and file management.
• Obsidian — Markdown-oriented; less suitable for a single .txt than dedicated editors.

Comparison

Settings for large files

• Disable syntax highlighting and the minimap: they are the most common sources of slowdown.
• Check the encoding: the file should open as UTF-8 without broken characters.
• Fix line endings: LF for macOS/Linux, CRLF for Windows tools when needed.
• Use rg or grep for search if the editor struggles.
• Archive old entries by year so the active file stays compact.
• Keep a backup before bulk replacements.

How to choose

• macOS. BBEdit or Sublime Text; TextEdit for a minimal setup.
• Windows. Notepad++ or Sublime Text; VS Code if you need project integration.
• Linux. Neovim, Sublime Text, or VS Code.
• Terminal only. Vim, Neovim, or Emacs; nano for quick edits.
• iPhone and iPad. iA Writer, Textastic, or Working Copy.
• Android. Markor or Acode.

If the file syncs across devices, set up sync first: how to sync one text file across devices. If you are still deciding whether OBTF is right for you, start with the comparison: OBTF vs Notion vs Obsidian.