Northern Commander

Finding files

Find files walks the folders under where you are and reads them, so it answers from what is on the disk now. Spotlight asks the index macOS keeps, and answers at once from what that has read. Either answer can become a pane of its own.

To find a name in the listing in front of you, start typing — see Panes.

At a glance

KeyAction
⌘PGo to file…
⌘FFind files…
⇧⌘FSpotlight…
⌘EGo to its folder in the other pane
⇧⌘EGo to its folder here

Going to a file by name

⌘P finds a file or folder whose name you know, anywhere under the folder the pane is in. Type part of the name and the matches are listed as you type, nearest first: a file directly in the folder comes before one three folders down, and a name that is what you typed, or starts with it, comes before one that only contains it. Below those come names found by their initials (gtf for go-to-folder.txt) or by letters in order with some skipped, and a small typo is forgiven when nothing else matches.

  • The folders are read while you type, however deep they go. The line under the list counts the files scanned so far.
  • Beside each name is the folder it is in, from the pane’s folder; a name directly in the pane’s folder says here.
  • A / matches folders in the path as well as the name: proj/main finds main.go in a folder called proj. A / at the end lists only folders — proj/ lists the folders whose names contain proj.
  • Hidden files are found only while the pane shows them. An application (.app) is listed as one item; what is inside it is not searched, and the same goes for anything else macOS shows as a single file. A link to a folder is listed but not searched, and so are other disks, network shares and disk images opened inside the folder.
  • ↑ and ↓ move in the list while you keep typing. Enter on a file takes the pane to its folder with the cursor on it; on a folder, the pane opens it. Until then the pane stays as it was.
  • It works in a folder on a disk. Inside an archive, or over the list of disks, it is unavailable (grayed out).

Finding files

⌘F asks where to look and what for, from any pane showing a folder. Over the list of disks, the Clipboard or a set of results it is gray.

Go and Markdown files holding TODO, but not the tests, changed in the last week. Both pages ask something, so both are marked.
  • Left empty, it lists every file under the folder.
  • Every box is read as you type. What will not read says why at the bottom, and Find stays gray. Under the rows, the box the cursor is in says how it is written.
  • Each box keeps its last five entries: [ ↺ ] at its end, or ⌥↓, opens the list.
Where
. is the folder the pane is in. It also takes a folder under that or beside it — docs, ../lib — a path from your home folder, ~/src, or a full path. The folder it comes to is written under it, and one that is not there is refused.
Simple, Advanced
The two pages of the form. A • marks a page that asks anything, so nothing narrows the search out of sight. Opened again, the form opens on the page its criteria are on.

The Simple page

Name matches
A wildcard pattern for the whole name: *.go. Several at once go apart by ; — *.go;*.md — and what follows a | is left out: *.go|*_test.go. *.* is every name, with a dot or without, and double quotes make ;, | and spaces part of a name. Searched with regular expression, it is found anywhere in the name. Either way, capitals and small letters are alike.
Look for
files, directories or both. A folder whose name matches is still searched inside. With directories alone, Containing and Size are gray, since a folder has neither.
Containing
Text the file holds, or with regular expression a pattern for it, within one line. Match case makes capitals and small letters differ.
Size
>1M at least, <500K at most, 1M..10M between, both ends included. K, M, G or T, counted in thousands as the panes count, so 10M and 10MB are 10,000,000 bytes; KiB, MiB, GiB and TiB count in 1024s. Files only. The two lines under the form give these examples while the field has the focus.
Modified
<7d in the last seven days, >1y more than a year ago — in h, d, w, mo or y — or 2026-01-01..2026-06-30, either end of which can be left off. An age is counted from when the search starts. The two lines under the form give these examples while the field has the focus.
Skip dirs
Folders neither listed nor searched: names apart by ;, such as .git;node_modules, or one regular expression.
Skip hidden files and directories
A name that starts with a dot, or one macOS hides. A hidden folder is not searched either.
Search in subdirectories
Off, only the folder itself is searched.

The Advanced page

The hint is for Depth, where the cursor is.
Created, Accessed
Written as Modified. When a file was last read is only as good as its volume keeps it — some keep it roughly, some not at all.
Depth
How far down: 1 is the folder’s own folders, 0 as far as there is. Gray while Search in subdirectories is off.
Read-only
yes for only what you cannot write to, no for only what you can.
Follow links
Off, links are passed over. On, a link is searched as what it points to, and found where the link is — so everything found is inside the folder searched. A link that leads back up is searched once; one that points at nothing is not found.
Inside
contains, or does not contain — and then the box on the Simple page says Not containing. A file that cannot be read is found by neither.
Whole words
What is typed must start and end where a word does.
Also look for the text in file names inside archives
The text is also looked for in the names of the files inside zip, tar, 7z and rar archives, and an archive holding a matching name is found — with the names that matched on the line under the results. Archives are listed, not unpacked, which takes longer; an archive inside an archive is not looked into. Unavailable without text to look for, and for bytes.
Pattern is bytes in hex
What is typed is bytes: 4D 5A or 4d5a. The one way to look for something that is not text; case, whole words and the encoding mean nothing to it.
Encoding
How files are read to look inside them: whatever it looks like, UTF-8, UTF-16 LE, UTF-16 BE or Latin-1.

What is searched

  • By name, only the folders’ lists are read, which is quick. Looking inside reads every file whose name, size and dates answered — ones that look binary too, so a string inside a program is found.
  • A macOS settings file (.plist), even in its binary form, is searched by its keys and values, so a name or a number in an app’s preferences is found though its bytes do not spell it.
  • A PDF or an office document usually keeps its text compressed, where reading the bytes cannot find it. Spotlight has read inside them.
  • A folder that cannot be opened is passed over, and the results say so. So is a pipe, a socket or a device when looking inside files: it has no contents to read, and is never opened.

The results

The results arrive as they are found, above a line that counts them — Searching… 12 found so far, 340 looked at, then 12 found, 512 looked at, with some of it unreadable where a folder could not be read. You can go to the first before the search has finished.

Go to file
Sends the pane to the file, in its own folder, with the cursor on it. Enter is Go to file.
Show all in a pane
Makes the results the pane — below.
Stop
Stops searching. What was found stays.
Change search…
Opens the form on everything you asked, to change and run.
Save
Keeps the search — see keeping a search.
Close
Closes, and stops the search.

Going to a result, closing and changing the search stop it; Show all in a pane and Save leave it running.

Results as a pane

Folder is where each was found, counted from where the search started.
  • The rows are the files themselves: view, edit, open, mark, copy, move, rename and delete them, or copy their paths, as anywhere else.
  • Nothing can be put into a set of results: no new folder or file, no paste, and a copy never goes there.
  • .. goes to the folder the search started from.
  • The search goes on filling the pane after it is there.
  • The results stay in the pane’s history while the application runs.

⌘E sends the other pane to the folder the file under the cursor is in, with the cursor on it, and makes that pane active — the results stay where they are. ⇧⌘E does the same in this pane. Both are in the context menu too, and work on the Clipboard’s rows as well.

Save on the form or on its results keeps the search under a name — what you asked, not the files it found — so running it again finds whatever answers it then. A search whose Where is . searches wherever the pane is when it runs.

Name
What to call it. A name already kept is replaced, and says so first. A name cannot start with a dot or hold a path.
Kept in
The folder the searches are in.

The form stays open, and says what it was kept as. From then on its title names the search and Save writes to it; Save as… keeps a copy under a new name.

Each with what it asks. The first nine have a number.
  • Saved searches in the places list lists them. Choosing one runs it straight into the pane; New search… opens the form.
  • Each search is a file, <name>.ncsearch, in the searches folder beside your settings — rename the file to rename the search. See Your files.
  • On a .ncsearch file anywhere, Enter runs it, and F3 or F4 opens the form on it, where Save writes back into that file. ⇧F3 and ⇧F4 show the file itself: JSON, holding what you typed.
  • A file that cannot be read is listed grayed, as cannot be read. One criterion in it that will not read costs only that criterion.

Finding duplicate files

Find duplicate files… looks for files with the same contents, whatever they are called. At the top of its form you choose what to look for.

Copies anywhere in a list of folders
Takes as many folders as you list, and any two copies under any of them count.
Files found in both of two folders
Counts a file only where a copy is in each, so two copies in one of them are not listed.

Under that, the size and the folder names to skip narrow which files are compared. Files of the same size are compared by a sample from each end, and those still alike by all that is in them, the largest first.

While you fill in the form, its last line counts the files under the folders, how many share a size with another and so may be duplicates, and the most that would be read to compare them. It lists the folders and opens no file, and counts again whenever you change what is looked at.

  • Empty files are never compared; the results say how many were left out.
  • A file kept in the cloud is never downloaded for this: it is left out and counted under the list.
  • Each folder keeps to its own disk, so add a disk’s own folder to look on it too.
  • Two names of one file are not two copies.

The results are a list like a search’s, which can also become the pane. Each group comes under a line saying its size and what else its files share, such as their type and how their names start, and a row can be viewed, opened or gone to in its folder. Nothing here changes a file: go to its folder to do that.

Asking the system’s index

⇧⌘F asks the index macOS keeps of your disks, rather than reading the folders.

More holds the rest. A query written by hand is the whole question.
Find
Words, looked for anywhere in a name and at the start of words inside files, capitals and accents alike. Not a pattern: * and ? are just characters.
Kind
anything, documents, images, film, sound, folders or applications.
Look in
this folder — the pane’s, and everything under it — or everywhere the index holds.
Tags
Finder tags, apart by spaces. A file must carry every one.
Size, Modified
Written as in Find files.
Query
A query in the index’s own language, such as kMDItemFSName == "*.pdf"c. While it holds anything it is the whole question: Find, Kind, Tags, Size and Modified are gray, and only Look in still counts.

The answer comes all at once, in a list like Find files’ — 12 found by the index, or The index found nothing — with Go to file, Show all in a pane, Change search… and Close. There is nothing to stop.

  • At most 10,000 are listed.
  • Each path is looked at before it is listed. One that is not there any more is left out, and the list says files gone since were left out.
  • A query the index cannot read is refused, with its reason.
Asked about a folder the index does not cover.

Asked about a folder that is not in the index, it says so rather than answering with nothing, and offers Find files instead. macOS indexes volume by volume, and folders can be left out. Asked everywhere, it says the same when the answer is empty and neither your home folder nor the startup disk is indexed.

Find files or Spotlight

Find files Spotlight
Answers from The disk, now What the index has read
Takes A moment by name, longer inside the files No time
Inside PDFs and documents No Yes
Hidden files, and what the index leaves out Yes No
What you type Wildcards, regular expressions, bytes Words
The answer Arrives as it is found All at once