HeartbeatHocusFocusFilesMacHyperTile
Guide

Finder, the app that draws your desktop

The file manager that also draws your desktop icons, remembers every window frame and empties the Trash. Measured: 52 MB, six minutes of CPU a day, one run since login.

By Chethan Kumar S N · Updated

You have used this one more than any app on your Mac. Every file window, the desktop underneath them, the little progress bar when you copy something, the Trash you empty on Fridays: all of it is one app, and the app is a process, and the process has a name in Activity Monitor that nobody ever introduces.

This page is a measurement of Finder on a Mac running macOS 27.0.1 with 29 days 21 hours of uptime, 10 cores, 32 GB of memory. Every fact below was read off the system. Nothing was installed, nothing was killed, no setting was written.

The household name with no manual page

The series always starts at the manual, and Finder is the starkest case yet:

$ man Finder
No manual entry for Finder

Apple documents the app everywhere. The user guide chapter opens with the sentence “The Finder is your Mac’s home base for everything you’ve stored” and explains that you open it “by clicking its icon in the Dock”, with a sidebar holding your Desktop, Documents, Downloads and iCloud Drive, and four ways to view a folder: icon, list, column and gallery. Not one of those pages mentions that any of this is a process, or what it costs, or what happens when it restarts. The app is documented. The machinery never is. That gap is the reason this page exists.

A birth certificate like the Dock’s

Finder is not a daemon. Its launch file sits in /System/Library/LaunchAgents, the user-level folder, and reads like an app’s file, not a daemon’s:

Label             => com.apple.Finder
Program           => /System/Library/CoreServices/Finder.app/...
POSIXSpawnType    => App
RunAtLoad         => false
KeepAlive         => { AfterInitialDemand => true,
                       SuccessfulExit    => false }
ThrottleInterval  => 1
EnablePressuredExit => false

launchd’s live report fills in the behaviour: state = running, runs = 1, last exit code = never exited, minimum runtime = 1 second, immediate reason = non-ipc demand. In other words launchd did not start it from a schedule, it started it because the session asked for an app, and in 29 days it has never had to start it twice.

The contrast showed up in the same ps sweep. The Dock, born at the same login moment, has an elapsed time of 26 days and 11 hours on a session that is 29 days 21 hours old: it restarted, once, three and a half days in. Finder’s report still reads runs = 1. The file manager outlasted the taskbar.

Two more keys earn their space. ThrottleInterval = 1 means a restarted Finder is allowed back immediately instead of sitting out the usual cool-down, and EnablePressuredExit = false means the memory system never reclaims it the way it trims the daemons in this series. Finder is meant to be always there, instantly replaceable, and never shuffled out of memory.

Your desktop is one of its folder views

This is the fact that reorganises how you picture the screen. The desktop is not a place, it is a view Finder draws, and its settings are not in System Settings, they are in Finder’s own preferences file. Measured on this Mac:

DesktopViewSettings => IconViewSettings => {
    iconSize      = 64
    gridSpacing   = 54
    arrangeBy     = none
    showIconPreview = 1
    textSize      = 12
    labelOnBottom = 1
}

The icon size of everything on your desktop, the spacing of the invisible grid they snap to, whether previews render inside the icons: a folder view configuration, exactly the kind Finder stores for any folder, just pointed at Desktop. The binary backs it up with 29 class names that all begin TDesktop, from TDesktopIconView and TDesktopGridLayout to TDesktopIconSelectionView and TDesktopInlinePreviewController. There is even a per-volume key, FXDesktopVolumePositions, remembering where the icons sit on each drive you plug in.

So the screen you see after login is four apps’ work, and the crew splits cleanly:

ProcessMemoryCPU over the sessionOwns
Finder52 MB183 minutesfile windows, desktop icons, Trash contents, copy dialogs
Dock12 MB40 minutesthe Dock, and the Trash’s icon
SystemUIServer3 MB17 secondsthe right end of the menu bar
WallpaperAgent9 MB56 secondsthe desktop picture

When people say “the desktop crashed”, what usually happened is Finder restarted: the icons vanish, the wallpaper stays, and both come back. The wallpaper staying is the tell, because it was never Finder’s to lose.

The Rosetta stone of Finder keys

Reading the preferences file is like finding the app’s diary. The keys with an FX prefix are Finder’s own classics, and they name features you have met as settings:

The keys with an FK prefix belong to FinderKit, the framework layer, which is the quiet announcement that the app you think of as one thing is at least two: a front and a library behind it.

The 10 kilobyte telltale

On this Mac’s Desktop sits a file called .DS_Store, 10,244 bytes, invisible in Finder itself. That is the folder-view settings from the section above, written back to disk, and Finder drops one in nearly every folder you open. It is why your view settings follow you around, and it is also the file the internet complains about: it rides along when you zip a folder on a Mac and hand it to someone on Windows. It is Finder writing down where you left the furniture.

Spotlight reads what Finder writes

The file diary has a second reader. Every change Finder makes is noted by fseventsd and picked up by Spotlight’s workers, the mdworker_shared processes this series covered earlier. Worth being precise about the family tree, because it is measured: the mdworker_shared processes on this Mac are parented by launchd, pid 1, not by Finder. Finder writes, launchd’s children index. When a Finder window’s search is slow, the question is whether the workers have caught up with the writing, not whether Finder is searching well.

And the Trash belongs to Finder too. The folder is yours, ~/.Trash on this Mac, holding 16 items behind permissions only you can read, drwx------. Apple’s own words for the division of labour: “You start by dragging items to the Trash in the Dock, but the items aren’t deleted until you empty the Trash.” The Dock draws the icon. Finder owns the folder and does the emptying.

The bill

Two readings, minutes apart:

ReadingValue
Memory (RSS)53,360 KB, then 47,952 KB
Virtual size489,660,288 KB, about 466 GB
Processor time183 minutes 14 seconds across 29d 21h
Per dayabout 6 minutes 8 seconds, 0.4 percent of one core
CPU right now0.0 to 0.1 percent
Runs1, never exited, same age as the session

Six minutes a day is the honest price of the desktop, every file window, the icon previews and the Trash, and it is the number to hold in your head when the column misbehaves. A Finder sitting at 40 percent is not a Finder problem in itself, it is a Finder doing something: churning previews in a folder of thousands of images, sorting a monster directory, feeding a copy, or waiting on a slow network volume. None was mounted on the measured Mac, so the idle readings above are the true floor.

The reset, when you want one, is the oldest keyboard remedy on the Mac that still means what it meant in 2001:

killall Finder

Your file windows close, the desktop icons blink out and return, and a fresh Finder takes over in about a second, with the receipts for that speed sitting in its own launch file.

If it climbs straight back, stop watching Finder and watch what it is reacting to. A process that creates and deletes files in a loop, a cloud sync client arguing with a folder, or an indexer walking a huge library will all show up as Finder’s CPU first, because Finder is the one drawing the pictures of it.

Questions

What is the Finder on my Mac?

It is the file manager, the app that shows your files, and it is also more of the screen than most people realise. Every file window, the desktop with its icons and grid, the copy dialog when you move files, and the Trash are all Finder work, drawn by one process that starts when you log in and stays alive until you log out. Apple's own user guide introduces it as the app you open from the Dock: The Finder is your Mac's home base for everything you've stored. On the measured Mac the process is pid 1651, parented by launchd, running as your own account out of /System/Library/CoreServices/Finder.app, and it has not exited once in 29 days. Like loginwindow and SystemUIServer before it in this series, it is a household name with a process nobody documents: man Finder returns no manual entry.

Why is Finder using so much CPU?

A healthy Finder bills about six minutes of processor time a day, which was the exact measured figure on a Mac with 29 days of uptime, 0.1 percent of one core while idle. When the column climbs well past that, the work is almost always real: generating icon previews for a folder of photos or videos, sorting a folder with tens of thousands of files, running a copy, or browsing a network volume that answers slowly. The preview setting is on by default and lives in Finder's own preferences, recorded as showIconPreview = 1. The classic reset is safe: killall Finder closes your file windows, the desktop icons blink out and back, and launchd starts a fresh copy in about one second, because its launch file asks for exactly that. If it climbs again immediately, look at what is feeding it, usually a process creating and deleting files in a loop.

Why is Finder using so much memory?

Real memory was 52 MB in the first reading and 47 MB in the second, taken minutes apart, on a Mac that had been up 29 days. A falling number is the healthy pattern for Finder, not a leak, and unlike the daemons in this series its launch file sets EnablePressuredExit to false, so the system never trims it on purpose. The number that alarms people is the virtual memory column, which reads about 466 GB. That is address space the process reserved, not RAM it is holding, the same pattern loginwindow and audiomxd showed earlier in this series. Judge Finder by Real Mem, not Virtual Mem.

Is it safe to quit or killall Finder?

Yes, and unlike loginwindow, where killall ends your session, this one is designed to be restarted. The launch file says KeepAlive with SuccessfulExit = false, meaning launchd brings it back if it ever goes away, ThrottleInterval = 1, and launchd's own report shows a minimum runtime of one second and runs = 1, never exited. What you lose is your open file windows, and the desktop icons disappear for the moment it takes to relaunch. Nothing else on the screen belongs to it: the menu bar is SystemUIServer, the wallpaper is WallpaperAgent, the Dock is its own app. The old trick of adding a Quit item to Finder's menu with a defaults write command predates this Mac and is not needed, killall Finder does the same job with no settings.

Can Finder be a virus or malware?

The genuine process runs from /System/Library/CoreServices/Finder.app on the sealed, read-only system volume, is signed by Apple as part of the OS with library validation enabled, and on this Mac its binary is 26 MB and built only for Apple silicon. A process named Finder running from a downloads folder or a temp folder would be a costume, and the way to check is the same as for every process in this series: open Activity Monitor, select the process, click the info button, and read the path. There is no known malware family that impersonates this name. One honest note: the word Finder is generic, and utilities that call themselves file finders are ordinary apps, not this process.

Ready? Buy Ribbon for $15, or read all the guides.