Showing the folder path inside Finder

A Finder window is generous about what is inside a folder and almost silent about where that folder sits. The title says src. There are four windows open and three of them say src. The file that needs moving is in one of them, the terminal is sitting in a fourth location entirely, and the only way to be certain which is which is to click around until something looks familiar. Searching for mac finder show path bar usually happens at that exact moment. The setting takes one keystroke to turn on. What is worth knowing is what it fixes, what it quietly does not fix, and which of the other three ways to see a location is the right one for the job at hand.

Turning the path bar on

The path bar lives in the View menu. Open a Finder window, choose View, then Show Path Bar. The keyboard shortcut is Option+Command+P. A strip appears along the bottom of the window showing the chain of folders from the volume down to the one currently open, read left to right.

This is a Finder setting, not a window setting. Switch it on once and every Finder window has it, including new windows and windows restored after a restart. The same is true of its neighbors: Show Status Bar (Command+/) adds the item count and free space, Show Tab Bar adds the tab strip, and Show Preview (Shift+Command+P) opens the preview pane on the right. The path bar costs roughly the height of one line of text at the bottom of the window, which is the entire price.

The bar is interactive, and this is the part most people miss after switching it on. Double-clicking any folder in the chain opens it in the same window, which makes moving up two levels a single action rather than a repeated Command+Up. Dragging a selected file onto a folder in the chain moves it there when the destination is on the same volume, and copies it when the destination is on a different one, the same rule that applies anywhere else in Finder. Control-clicking a folder in the chain opens a contextual menu for that folder rather than for the file you have selected.

The strongest reason to leave it on has nothing to do with navigation. Run a search in a Finder window and the results arrive as a flat list from all over the disk, with no indication of origin. Click a result and the path bar fills in with its actual location. Without the bar, answering "where is this thing" means Get Info or File, Show in Enclosing Folder, on every candidate.

Four ways to see where you are

The path bar is one option among several, and they are not interchangeable. Each answers a slightly different question.

Method	How to enable	What it shows	Can you copy it as text
Path bar	View > Show Path Bar (Option+Command+P)	The whole chain, always visible at the bottom	No
Title bar menu	Command-click the folder name in the title bar	The enclosing folders as a pop-up menu	No
POSIX path in title	defaults write com.apple.finder _FXShowPosixPathInTitle -bool true, then killall Finder	The full path in the window title	No
Column view	Command+3	The chain as columns, one per level	No
Get Info	Select the item, then File > Get Info	The location under Where	Yes, but not as a POSIX path

The title bar menu is worth knowing because it needs no setup and works in any Finder window. Command-clicking the folder name in the title bar drops a menu of every enclosing folder up to the volume, and choosing one opens it. It answers the question once, on demand, instead of taking up permanent space.

The defaults command in the third row changes the window title to the full path. It is a long-standing setting and it is not documented by Apple, which means it is not covered by any promise to keep working. Undocumented settings occasionally stop functioning after a system update, so it is a reasonable thing to try and a poor thing to build a habit on. Setting it back to false and running killall Finder again reverses it.

Column view deserves a mention because it makes the hierarchy the main interface rather than an annotation. For a deep tree that gets browsed constantly, Command+3 does more than the path bar does. For a shallow tree it wastes horizontal space.

The path bar shows a picture of a path, not a path

This is the limitation that catches people, and it is worth being precise about. What the path bar displays is a chain of display names. What a terminal, a script, or a chat window needs is a POSIX path. The two are frequently not the same string.

Localized system folders are the clearest case. On a Mac set to Japanese, the Documents folder appears in the path bar under its Japanese name, while the directory on disk is still Documents. The same applies to Desktop, Downloads, Movies, Music, Pictures, and Applications. Typing what the bar shows into a terminal produces a path that does not exist.

iCloud Drive is the second case. It appears in the path bar as a single tidy item, and on disk it sits at ~/Library/Mobile Documents/com~apple~CloudDocs. Nothing in the bar hints at that. Network shares are the third: a mounted share shows under the server or share name, while the path on disk starts at /Volumes. External drives with spaces or non-ASCII characters in their names are the fourth, and those characters need quoting or escaping before any shell will accept them.

The path bar is a navigation aid and an orientation aid. It is not a source of text. For text there is one built-in answer: select the item, hold Option, and the Copy entry in the Edit menu and the contextual menu becomes Copy as Pathname. The shortcut is Option+Command+C, and it copies the real POSIX path.

Reading the path once it is text

A copied path is only useful if its shape is understood, and macOS has a few shapes that surprise people who came from other systems.

A user's own files live under /Users/ followed by the short account name, which is not always the same as the full name shown on the login screen. The tilde shorthand expands to that directory in a shell and in the Go to Folder field, but it means nothing in most application text fields, so a path pasted into a form or a note should usually be the absolute form.

Anything that is not the startup disk mounts under /Volumes, including external drives, disk images, and network shares. The name that appears there is the volume name, and it changes when the volume is renamed, which is why scripts that hard-code a drive name break the day someone tidies up their labels.

Since the introduction of the read-only system volume, some tools report paths beginning with /System/Volumes/Data in front of an otherwise ordinary path. Both forms refer to the same file. Finder never displays the longer form, but a path pulled out of a log or a backup tool may carry it, and stripping the prefix leaves a path that still works.

One more property matters when a path leaves the machine. The default macOS file system is case-insensitive, so Notes.md and notes.md are the same file locally. On a Linux server, in a Docker image, or in a Git repository shared with other systems, they are two different files. A path that is correct on the Mac and wrong once deployed is almost always this.

Getting from the path bar to a terminal

The path bar has one capability that most of its users never find, and Apple documents it in the Terminal user guide rather than anywhere near the Finder documentation.

You can use the path bar in a Finder window to open a new Terminal window or tab with the working directory set to a folder's location. If you don't see the path bar at the bottom of the Finder window, choose View > Show Path Bar. Source: support.apple.com

In practice: control-click a folder in the path bar and choose Open in Terminal for a new window, or Services, then New Terminal Tab at Folder for a tab in the existing one. The Services entries are listed under System Settings, Keyboard, Keyboard Shortcuts, Services, in the Files and Folders group, and they can be switched on and given a shortcut there if they do not appear in the menu.

This removes the most common reason for copying a path at all. A path gets copied so it can be pasted after cd, and a shell that already opened in the right directory skips both steps. Going the other way, open . in a terminal opens a Finder window at the shell's current directory, and open -R followed by a filename opens Finder with that file selected.

What remains after all of this is the round trip. The Finder window sits in one place, the terminal in another, and the two are synchronized by a menu command each time either one moves. Nothing about the path bar makes that shrink. It makes the current position legible, which is a real improvement over four windows all called src, and it stops there.

Where the path bar runs out

Three situations expose the boundary clearly.

Open and Save dialogs have no path bar. When an app asks where to save something and the sidebar does not list the destination, the answer is Command+Shift+G, which opens a Go to Folder field that accepts a typed or pasted path and expands ~. That field is also the fastest route to any directory that Finder hides by default.

Search results across volumes are the second. The path bar reports the location of a selected result, but if that result lives on a volume where indexing is off, it never appears in the list to be selected. Location display and search coverage are separate problems.

The third is the one that brought most readers to this page without their naming it. A path in the path bar cannot be handed to anything. To reference a file in a chat window, a prompt, a note, a script, or a message to a colleague, it has to become text, which means Option+Command+C, then a switch to the other application, then a paste, then a check that the spaces survived. That sequence repeats dozens of times a day, and it is the reason a category of tools exists that puts a folder view and a shell in the same window instead of two. The details of what that arrangement covers are set out under Features, and the practical differences between the available options are laid out in Compared with other file managers.

What to change first

Turn the path bar on with Option+Command+P and leave it on for a week, then add Option+Command+C to muscle memory for the moments when the path needs to become text. If the round trip between a folder window and a shell is still the thing eating the day, the setting was never the bottleneck, and Atriens exists for that specific version of the problem.