How to open a large text file on Mac
You can do this with Note My: a hundred-megabyte log opens as a document you can scroll, search and edit like any other. Here is how to open one, and what to reach for once it is in front of you.
A "large" text file on a Mac starts causing trouble somewhere around ten megabytes and becomes genuinely painful past a hundred. A web server access log, a database dump, a crash report, a CSV export, an application log that has been running since March — they are all just text, and they should all just open. Often they don't.
This guide covers how to open a file that size in Note My, what you can do with it once it is open, and what to reach for when a log is still being written while you read it.
Everything below happens on your Mac. Nothing is uploaded, there is no account to make, and a file you open never leaves the machine — which matters more than usual when the file is a production log.
What to expect from a large file
A large file behaves like any other document here. It opens into its own tab, it scrolls, you can search it, and you can edit it and save it. Our large-file engine keeps that true at a hundred megabytes as well as at a hundred kilobytes: the window comes up quickly and stays responsive, so a file you were bracing yourself for turns into a document you can simply get on with. It all happens on your Mac, so a production log is readable in seconds without leaving the machine.
Three things are worth knowing before you double-click anything.
You can start reading the moment it opens. Scroll, select and search as soon as the window appears — you work in the document while the rest of it settles into place, and the counts in the status bar catch up with you as you read.
Work on a copy of anything live. If a service is still writing to the file, duplicate it in the Finder before you edit, or use View ▸ Follow Tail to read the original without touching it.
Editing is real editing. A huge file is not a read-only preview: you can delete a hundred thousand lines of noise, fix a broken record in the middle of a dump, and save with ⌘S as you would in a short note.
Open the file
-
Open it the ordinary way
Press ⌘O and choose the file, or drag it from the Finder onto the tab bar. With the Finder extension turned on, files also open by right-clicking in the Finder and choosing Note My ▸ Open, which is worth knowing when the file lives somewhere awkward.
You can select several files at once; each arrives in its own tab.
-
If macOS says it is not a text file, force it
Press ⇧⌘O for File ▸ Open Anything as Text…. This is the one to reach for when a file has no extension, or an extension the system has assigned to something else —
.dump,.dat,.bak, a rotated log calledaccess.log.1.Note My opens those files whenever you ask and leaves your Finder set-up exactly as it was — nothing is taken over behind your back, so double-clicking a file in the Finder keeps behaving the way you expect it to.
-
Start working straight away
There is no import step, no progress bar to sit through and nothing to configure. Our large-file engine looks after a document this size so you can scroll, search and edit it the moment it is open. It all happens on your Mac — nothing is uploaded, and the file never leaves the machine.
…08114:02:11.048 203.0.113.7 GET /api/v2/sync 200 12 ms…08214:02:11.052 198.51.100.23 GET /api/v2/state 200 9 ms…08314:02:11.201 203.0.113.7 POST /api/v2/commit 201 44 ms…084WARN queue depth rising — 1 208 pending…08514:02:12.114 192.0.2.41 GET /api/v2/manifest 500 310 ms…08614:02:12.119 203.0.113.7 GET /api/v2/sync 200 11 ms…08714:02:12.500 198.51.100.23 GET /healthz 200 2 msChars 326 004 118 Lines 2 004 111 ↵ LF Aa UTF-8 Plain TextA 326-million-character log, open and idle. The Large File badge is the editor telling you it has shifted into its heavy-lifting mode — it is display-only, and there is nothing to click. -
Check the counters
The status bar counts characters, words, spaces and lines for the whole document, not just the part you can see — so you can say how many lines that dump really runs to, and quote the figure to whoever asked for it. The footer always shows the counts for the tab you are looking at, so switching between yesterday's log and today's switches the numbers with them.
Chars 2 411 908 Words 318 442 Spaces 402 117 Lines 51 204 Sel 0 Occ 0 ✓ Clean ↵ LF Aa UTF-8 {} Plain Text ⌘ IdentifySix counters, live: characters, words, spaces, lines, the size of the selection, and how many times the selected word occurs. They are cached on the document, so a keystroke does not recount two million characters.
What you can do once it is open
A hundred-megabyte log is a document here, not a preview of one, and the table below is what that means at your desk. Our large-file engine keeps the window responsive while you work, so none of this arrives with a wait attached to it.
| What you want to do | How it works here |
|---|---|
| Edit and save | Type, delete, paste and save with ⌘S, exactly as in a short note |
| Search and replace | Our find and replace, across this file or every open tab, with regular expressions and a live match count |
| Read code and config | Our syntax engine colours the document wherever you are in it |
| Read a log | Severity levels, status codes, timestamps and addresses picked out for scanning |
| See how big it is | Characters, words, spaces and lines counted for the whole document, not just the part on screen |
| Finish a long word | ⌃Space opens the completion popup whenever you want it |
| Keep unsaved work | Held as you type by our auto-recovery safety net |
Colour is the thing people expect to lose first at this size, and you keep it. Our syntax engine goes on working as you type, so a stack trace or a config dump stays readable however far into the file you have scrolled. Everything you came for behaves the same at a hundred megabytes as at a hundred kilobytes: you can select across the whole document, retype a line in the middle of it, run our find and replace over the lot, and save the result.
Unsaved work in a very large document is looked after by our auto-recovery safety net, which brings the document back with your uncommitted text if the app or the Mac stops unexpectedly. It works quietly in the background and asks nothing of you. Pressing ⌘S before you walk away from an edit is still the habit worth keeping, on a file of any size.
Pasting a lot of text at once
Opening a big file is one job; dropping an enormous block of text into one is another. ⌘V is all it takes, however much is on the clipboard, and there is no separate command to learn for a big paste.
| What you are pasting | What you see |
|---|---|
| A few lines, or a few pages | It lands immediately. |
| A large block | It lands without the window locking up, so you can keep reading while it arrives. |
| A very large block | A progress sheet appears with a Cancel button, so a paste you did not mean to start is one you can stop. |
| Styled text from a browser or word processor | Plain characters — fonts, colours and sizes are left behind. |
Paste here is always plain text, so a snippet from a web page or a word processor arrives as characters and nothing else — no formatting to strip afterwards, no styling carried into a config file by accident. If what you pasted still holds characters you cannot see, such as a non-breaking space or a smart quotation mark in a command, Clean ▸ Clean Invisible / Special Characters… finds them with our hidden-character scanner and shows you each one before anything changes.
Following a file that is still being written
A log that is still growing is a different job from a file that is finished. Choose View ▸ Follow Tail and the editor pins itself to the end of the file, appending new lines as they are written.
Three things make this usable rather than annoying:
- Scrolling up releases it. Read as far back as you like; scroll to the bottom again and it resumes. You do not have to switch following off to look back, and on again to catch up — useful when you are chasing the lines just before an error.
- Size does not slow it down. Following a multi-gigabyte log feels the same as following a small one, so you can leave it running against a busy service.
- Rotation does not derail it. When the log rotates out from under you, the view picks up the new file instead of showing you nonsense.
Lines that arrive while you are following are not treated as edits you made: ⌘Z still undoes your own typing and nothing else.
Reading a log once it is open
Turn on View ▸ Enable Log Highlighting, or click the Log pill in the status bar, and a wall of text becomes something you can scan. Severity keywords, HTTP status codes, timestamps, IP addresses, UUIDs and URLs each get their own treatment, so a red run of 5xx responses or a cluster of ERROR lines stands out from a screen away. None of it is written into the file: the colour is for reading, and the file on disk stays exactly as you found it.
| Pattern | Treatment |
|---|---|
| FATAL, CRITICAL, SEVERE, ERROR, WARN, WARNING, NOTICE, INFO, DEBUG, TRACE, VERBOSE | A colour per level |
| HTTP status codes | 2xx green, 3xx teal, 4xx orange, 5xx red |
| ISO-8601 timestamps | Muted, so they do not compete with the message |
| IPv4 addresses | Purple |
| UUIDs | Indigo |
| http, https and file URLs | Link colour |
To move between problems rather than scrolling for them, use ⌥⌘E and ⌥⇧⌘E — jump to the next and previous error. They match on FATAL, CRITICAL, SEVERE, ERROR, WARNING and WARN, case-insensitively, and wrap around at the end of the file. ⌘L goes to a specific line number, and the field arrives pre-filled with the line you are on, selected — so it also answers "where am I?".
Searching inside a very large file
Open Find & Replace from the magnifying-glass button in the toolbar. It is a pop-over, not a bar: two fields, a This File / All Tabs scope switch, and Case Sensitive, Whole Word and Regular Expression options. Type, and every match highlights live with a running count; ↩ steps forward, ⇧↩ back, ⎋ closes.
Reach for Regular Expression when you are working through a log rather than a document. A pattern such as ERROR.*timeout takes thousands of lines down to the handful you actually want, and ↩ then walks you through them one at a time.
Our find and replace stays live as you type on a file this size, counting matches while you refine the query. That running count is the useful part of a big search: type ERROR and watch the number, then add a service name or a status code and watch it fall to something you can read through in a sitting. ↩ walks you from one match to the next however far apart they sit in the file, and ⇧↩ takes you back again.
Scope is yours to choose. Replace in All Files sweeps every tab you have open, which is the quick way to make the same correction across a set of rotated logs you have opened together. To reach a whole directory tree, use Search ▸ Find in Folder… (⇧⌘F), which reads files and never writes them — so you can point it at a folder of logs with no risk to their contents.
Troubleshooting
The file opens but the encoding is wrong
Garbled accents, or a stray  in front of every non-ASCII character, mean the file was opened as the wrong encoding. Use File ▸ Encoding ▸ Reload with Encoding… and pick the one the file was written in — Windows-1252 for a lot of older Western text, Shift JIS or GB18030 for CJK. Our encoding handling covers the long list, so an old export is usually one menu choice from being readable. Reloading changes nothing about the file itself; if the first choice is wrong, reload again with another. Only Convert to Encoding… changes what will be written when you save.
The line count keeps rising after the document appears
The document is ready before the counting is, which is the point of it. Our large-file engine hands you a usable window straight away, and the counts arrive by themselves a moment later. Read, scroll, search and edit while the number climbs — none of it waits on the counter, and nothing you do while it runs is lost or interrupted. When you want the exact line count to quote to someone, give it that moment and it will be there in the status bar.
Applying a change to every line at once
Two jobs deliberately reach every line of the document in a single pass, which is exactly what you want them to do on a file this size. The first is re-indentation. The toolbar Indent button never reformats anything on its own — it opens the Indentation sheet, and nothing changes until you press Apply, at which point our indentation engine applies your choices to the whole file. The second is the Review All sheet under Clean ▸ Clean Invisible / Special Characters…, where our hidden-character scanner covers every line rather than only the part you have scrolled to — which is the point of it, since the stray character you are hunting is rarely on screen. Both are doing in one pass what would otherwise be an afternoon of scrolling.
Press ⌘S before you re-indent a large document. Applying the Indentation sheet rewrites every line, and having saved first means File ▸ Reload from Disk (⌘R) puts the document back exactly as you saved it, ready to try the sheet again with different settings. Reloading never changes the file on disk, so it is a safe move to make as often as you like.
The file was changed by another process while I had it open
You will be told. When something outside the app changes a file you have open, you get a sheet offering Reload or Keep My Version; nothing is overwritten behind your back either way. If the tab is in the background the prompt waits until you switch to it, so nothing pulls you out of the file you are working in, and you are never asked about a change that no longer matters by the time you get there. On a log this is routine: choose Reload to see what has been written since, or Keep My Version if you have edits you are not finished with.
The file was deleted from under me
Also handled: you are told once, calmly, and offered Keep in Editor or Close Tab. Choose Keep in Editor and the text in front of you becomes the surviving copy, held by our auto-recovery safety net until you save it somewhere of your own choosing. On a rotated log that is often the only copy left, so save it before you carry on.
Five things worth trying
Once the document is in front of you, these are the moves that turn a wall of machine-written text into something you can work with:
- Cut it down to the part that matters. Every file you open is a document you can edit, so select a run of a hundred thousand uninteresting lines, delete them, and save with ⌘S. The practical ceiling on size is your Mac rather than any number set in the app.
- Collapse the block you are not reading. Double-click a brace to fold the block it opens — the quick way to get a long payload or a nested config section out of your way while you read what surrounds it.
- Put two files side by side. Multi View gives each open tab its own pane, so yesterday's log and today's can sit next to each other while you work out what changed between them.
- Jump instead of scrolling. ⌘L goes to the line number someone has quoted at you, and ⌥⌘E walks from one error to the next, wrapping round at the end of the file.
- Tidy what you are about to hand on. An excerpt bound for a ticket or a colleague reads better without the invisible characters it collected on the way; our hidden-character scanner shows you every one of them before a single thing changes.
Frequently asked questions
How large a file can Note My actually open?
There is no maximum file size. Multi-megabyte logs and dumps are ordinary work here, and so are the ones an order of magnitude larger: the window comes up, the document scrolls, our find and replace runs over the whole of it, and you can edit the result and save it. The practical limit is your Mac rather than any number in the app, and what you get is an editable document rather than a preview of one.
Why do the apps already on my Mac fail on the same file?
Most of them are built for documents a person writes — a letter, a note, a page or two of prose — and a hundred-megabyte log is not that. The difference is not effort, it is what each application was designed for. Note My is built for the file a machine wrote.
Can I open a file that macOS insists is not text?
Yes — ⇧⌘O, File ▸ Open Anything as Text…. If the file turns out to contain binary data you will be warned; that check is on by default and can be turned off in Settings.
Can I leave a log following for hours?
Yes, and it is a good way to watch a deploy or an overnight job. Size does not slow following down, so a busy service can write to the file all night and the view keeps up with it; in the morning you scroll back through what arrived, or use ⌥⌘E to go straight to the first thing that went wrong. Following is per tab and is not remembered when you quit, so it never quietly keeps running on a file you have forgotten about.
Will my unsaved changes survive a crash in a file this large?
Yes. Our auto-recovery safety net keeps unsaved work as you type, whatever the size of the document, and the next time you open the app your tabs come back with that text still in them — the edit you were part-way through is where you left it. Pressing ⌘S before you step away is still the habit worth having.
Where does the file go when I open it?
Nowhere — it stays exactly where it is on your Mac. Opening, searching, colouring, cleaning and saving all happen there. Nothing is uploaded, there is no account, and the file never leaves the machine — so a production log or a customer export can be opened here without a conversation about where it went.