Finder on a Mac computer: what it is and what it is not

Searching for Finder on a Mac computer usually starts with something that did not behave like an application. There is no Quit in its menu. It is not in the Applications folder. A window went grey while listing a network share and there was nothing obvious to force quit. None of that is a fault. Finder is a different kind of process from the apps installed next to it, and once that difference is clear, most of the odd behaviour stops being odd.

What follows is the shape of the thing: where it runs, what it is responsible for, what it deliberately keeps out of view, and the point at which it stops being the right window for the work in front of you.

The one application that never quits

Finder launches at login and stays running for the whole session. The Finder menu has no Quit item, and pressing the quit shortcut while it is frontmost does nothing. That is by design, because Finder is not only a file browser. It draws the desktop, mounts and unmounts volumes in the sidebar, handles drag and drop between applications, and owns the Trash.

The practical consequence shows up in the Force Quit window. Select any other application there and the button says Force Quit. Select Finder and the same button says Relaunch. There is no state in which the Mac runs without it.

You can use the Finder to view, access, and organize almost everything on your Mac. Source: support.apple.com

That single sentence explains a second thing people notice: almost every complaint about "the Mac being slow with files" is really a complaint about one long lived process doing several unrelated jobs at once. A stalled network share, a folder with tens of thousands of items, and a sync client rewriting metadata all land on the same process. Windows that have nothing to do with the stall go grey with it, because they are windows belonging to one application rather than separate programs.

Where it lives, and why it cannot be moved

Finder is at /System/Library/CoreServices/Finder.app, not in the Applications folder where installed software goes. Since macOS Catalina, the system content sits on a separate, cryptographically signed volume that is mounted read only, so that copy cannot be edited, renamed, or replaced even by an administrator.

This is worth knowing for two reasons. First, when a guide tells you to reveal something in the Applications folder and Finder is not there, nothing is broken. Second, Apple's own documentation is direct about leaving system items alone.

App folders and any items that came with your system, such as the Library folder. Source: support.apple.com

The Dock slot behaves the same way. The Finder icon on the far left cannot be removed, and dragging it out does nothing, because there is no state where the Dock has no Finder. Third party file managers install into Applications like ordinary software and run alongside it. None of them take over the desktop or the Trash, which is the main reason "replacing Finder" is never a clean swap. A comparison of what a separate file window can and cannot take over is set out on the comparison page.

Relaunching Finder without losing anything

When a window stops redrawing, the fix is a relaunch rather than a restart of the Mac. There are three routes to the same result.

• Hold Option and right click the Finder icon in the Dock, then choose Relaunch.
• Open Force Quit with Option, Command and Escape, select Finder, then click Relaunch.
• Run killall Finder in Terminal.

All three kill the process and let the system start it again within a second or two. Open Finder windows come back, the desktop redraws, and no file is touched. What does not survive is anything in flight: a copy operation that was running is cancelled partway, so check the destination folder afterwards rather than assuming the copy finished.

A relaunch is also the step that makes a written preference take effect. Settings changed with the defaults write command are read when the process starts, so the change appears to do nothing until Finder is restarted. If the beachball came from a network volume that went away, unmount it first, because relaunching into the same dead mount reproduces the stall immediately.

The desktop is a Finder window

The desktop is not a special surface. It is the contents of ~/Desktop drawn full screen by Finder, and every icon on it is a real file in that folder. Deleting an icon deletes a file. Sorting the desktop sorts a folder.

That explains a common slowdown. A desktop holding several thousand items forces Finder to compute icons and previews for all of them on every redraw, and those previews compete with whatever else the process is doing. Moving the pile into a dated folder is a faster fix than any maintenance utility.

It also explains why a file saved to the desktop by one application appears instantly in a Finder window pointed at the Desktop folder, and why a folder dragged there from an external drive is copied rather than moved. The desktop follows the same rules as any other folder, including permissions and the behaviour of drags between volumes.

Two settings control what else appears there. In Finder Settings under General, four checkboxes decide whether hard disks, external disks, removable media, and connected servers show on the desktop. Under View, Use Stacks groups desktop items by kind or date without moving them, which keeps the folder contents unchanged while reducing the number of icons drawn.

What it is doing when nothing appears to be happening

A window that has gone quiet is usually waiting on work that Finder started but does not report. Four things account for most of it.

After a large copy, the Spotlight indexer reads the new files so they can be found by name and content later. Until that pass finishes, search results in the destination folder are incomplete, and the fans on a laptop may run without any visible cause. The work is done by a separate helper process rather than by Finder, so quitting or relaunching the window changes nothing.

Thumbnails are generated on demand as icons scroll into view. In a folder of raw photographs or video, that generation is the slowest thing in the window, which is why switching to list view makes the same folder feel instant. Gallery view forces the opposite: it renders a full preview of the selected item every time the selection changes.

Folder sizes, when the option is enabled, are calculated by walking every descendant. On a project tree with a hundred thousand small files, that walk continues in the background while the numbers fill in one row at a time.

Anything on a network share or a cloud placeholder has to travel before it can be shown. A share that has dropped off the network is the single most common cause of a window that never finishes drawing, because the request has no answer and no timeout that the user can see.

The practical test is whether the rest of the Mac is responsive. If other applications are fine and only file windows are stuck, the cause is one of the four above rather than a system fault, and the ordinary response is to unmount the share, switch view, or wait for the index rather than to restart the machine. Activity Monitor shows which helper is busy, listed under names such as mds_stores for indexing and QuickLookUIService for previews.

What Finder shows, and what it keeps out of sight

A fair amount of the file system is hidden from the default view. This is not obstruction, it is a decision about what an ordinary session needs to see, and each piece has a way back.

Hidden by default	Why	How to reveal	Does it stay revealed
Files starting with a dot	Configuration, not documents	Shift, Command and period in any window	Yes, until toggled again
The Library folder in your home	Application support data	Hold Option and open the Go menu	No, the menu entry appears only while Option is held
Filename extensions	Visual tidiness	Finder Settings, Advanced, show all filename extensions	Yes, and it overrides the per file setting
Folder sizes in list view	Calculating them is expensive	Command and J, then calculate all sizes	Per folder, not global
Any path you know but cannot see	Depth	Shift, Command and G, then type the path	Per use

Two of these rows behave differently from the rest and catch people out. Extensions have both a global switch and a per file one, so a single file can stay hidden even after the global setting is on, and the fix is the checkbox in that file's Get Info window. Folder size calculation is stored with the view options of the folder it was set on, so turning it on once does not apply it anywhere else unless the same options are used as the default for all windows.

The last row is the one worth building a habit around. Go to Folder accepts a typed path, expands a leading tilde, and completes with the Tab key, which makes it faster than clicking through five levels even when nothing is hidden.

One more thing is invisible for a different reason. Files stored in iCloud Drive but not downloaded locally appear with a cloud icon and occupy almost no space. They are listed, searchable by name, and open on demand, but a command line tool pointed at that folder sees a placeholder rather than the content until it is fetched.

Three jobs Finder does not take on

The boundary matters more than the feature list, because it tells you when to stop looking for a setting that is not there.

It does not act on rules. Smart Folders answer a question continuously, showing everything matching a set of criteria, but they never move, rename, or delete a thing. Anything that runs automatically has to come from a separate application: Folder Actions, Shortcuts, or Automator.

It does not run commands. There is no output pane. The Services menu can open a Terminal window at the selected folder, but that option is off by default in Keyboard settings, and it opens a second application rather than showing the result in place. Every check on the state of a project, from disk usage to version control status, means leaving the window.

It does not read inside every file. Finder search is a front end to the Spotlight index, and that index is built for documents. Source trees, dependency folders, and anything on a volume excluded from indexing return nothing, which is why a search that works for a PDF fails for a string inside a repository.

None of these are missing features waiting to be added. They mark where a file window ends and other tools begin, which is the honest way to decide whether a different window would help. The features overview sets out what a file manager built around the terminal handles instead, and the pricing page shows what that costs.

What to change first

Turn on filename extensions and learn Go to Folder before installing anything, because those two remove most of the friction people blame on Finder itself. Then count how many times a day the work moves from listing files to running a command on them. If that number is high, the fix is a window where both happen, which is what Atriens is built for.