Mac file paths explained, slash, tilde, Volumes and containers

A Mac path is read left to right, with slashes between each folder. The first character tells you where it starts. A slash means the top of the disk, a tilde means your home folder. Everything else is just folder names in order.

Support articles hand out paths constantly and almost never explain the notation. Learn the four opening characters and every one of them becomes readable.

The first character is the whole trick

Apple states the first two directly. A slash at the beginning means the starting point is the top level of your computer's folder structure. A tilde means your home folder.

A slash at the end means the path points at a folder rather than a file. Nothing enforces that, but it does tell you what to expect when you arrive.

The slash on its own

A path beginning with a slash starts at the top of the startup disk, above your account and above everybody else's.

This is where /Applications lives, along with /Library and /System. Anything here is shared by every account on the Mac, which is why changing something in /Library affects everyone and changing something under your home folder affects only you.

The slashes between folder names are separators, not part of any name. /Applications/Utilities/Terminal.app reads as Applications, then Utilities inside it, then Terminal.

The tilde

A tilde is shorthand for your home folder, so it stands for something different on every Mac and for every account.

On a Mac where the account is called sam, ~/Documents and /Users/sam/Documents are the same folder written two ways. Support articles use the tilde precisely because they do not know your account name.

This is why a path copied from a forum works for the person who posted it and for you, without either of you editing anything.

The tilde is the reason paths look wrong. Someone reports a folder as /Users/sam/Library and you go looking for a folder called sam. Read it as your own name and it resolves.

/Volumes and the drives that are not the startup disk

An external drive, a disk image or a network share does not get its own letter the way it would on Windows. It gets mounted into the same tree, under /Volumes.

Plug in a drive called Backup and its contents are at /Volumes/Backup/. Finder shows it in the sidebar as a separate item, which hides the fact that it is a folder like any other.

Two things follow. A drive named with a space works fine in Finder and needs quoting in Terminal. And two drives with the same name mount as Backup and Backup 1, which is how a script written for one ends up writing to the other.

Container paths, the ones that look like nonsense

Some paths carry a run of reversed domain names or a block of random capitals. Those are sandboxed applications and app groups.

Read the bundle identifier backwards and it makes sense. com.apple.Notes is Apple, then Notes. The random capitals in a group container are the developer's team identifier, assigned by Apple, which is why they look meaningless and never change.

What lives inside those folders is a separate question from how to read the path to them.

Typing a path instead of clicking

Finder takes a path directly. Press Shift and Command and G. Choose Go then Go to Folder if you prefer the menu, then type or paste.

Three things make this the fastest route on the Mac.

It reaches hidden folders. Library does not appear in Finder. Typing the path opens it anyway, with nothing switched on first.

It completes as you type. Apple says suggestions ignore small typing errors, so an approximate spelling still lands. Press Tab to accept one.

It accepts either notation. A tilde path and a full /Users/ path both work.

Getting a path out of Finder

The reverse job comes up just as much. Something asks you for a path and you have the file in front of you.

Apple documents one route. Right click the file and hold Option. The menu changes to offer Copy as Pathname. The full path lands on the clipboard as plain text.

Two others help. Option and Command and P shows the path bar along the bottom of every Finder window, which is a display rather than something you can copy. Dragging a file into a Terminal window types its path for you.

The two dots

Paths sometimes contain a single dot or two dots. Apple defines both.

One dot means the folder you are already in. Two dots mean the folder above it. So ../Documents reads as go up one level, then into Documents.

These only appear in Terminal instructions and scripts, never in Finder. A path containing them cannot be understood without knowing where it was meant to start.

Case, spaces and the characters that bite

Three details break paths that otherwise look correct.

Case. A Mac disk normally ignores capitals, so ~/documents and ~/Documents reach the same folder. Terminal is stricter than Finder about this. A disk formatted case sensitive treats them as two different places entirely.

Spaces. Finder handles them without comment. Terminal reads a space as the end of the path, so /Volumes/My Backup has to be quoted or the space escaped with a backslash.

Quotes from web pages. Copying a path out of an article brings a curly quote or a non breaking space with it more times than you would expect. Both look identical on screen and neither works. Retyping the path by hand is faster than hunting for the character.

Why a pasted path lands nowhere

Four causes cover nearly all of it.

The version number one turns up more than the rest combined. Mail paths carry a V number that changes with macOS releases, which is why the Apple Mail path has to be read rather than copied blindly. Outlook does the same with its profile folder. Thunderbird generates eight random characters in the name of every profile.

Read the path, match the shape, then substitute what is different on your machine. That is the whole skill.