How to Add Shortcuts to Finder: Five Routes That Work

Somewhere on the disk there is a folder that gets opened twenty times a day, and the route to it runs through four or five clicks every single time. Adding a shortcut to Finder is the obvious fix, and the reason it often does not stick is that the word covers at least three unrelated things. One of them is a row in a list. One of them is a small file that points at another file. One of them is a key combination that triggers a menu command. They are set up differently, they break differently, and picking the wrong one is why a shortcut added last month is already gone. Below is each route, what it survives, and which one is worth the setup.

Three different things called a shortcut

The first is a pointer to a place. A row in the sidebar, an icon in the Dock, an alias sitting on the desktop. Nothing moves when one is created. The original file or folder stays where it is and the shortcut simply names it.

The second is a route with no object at all. Shift-Command-G opens a field that accepts a typed path, and Command-Up Arrow goes to the enclosing folder. There is nothing to add and nothing to maintain, which makes these the shortcuts that never break.

The third is a key that performs an action rather than moving anywhere. Renaming, compressing, converting an image, running a script against a selection. These come from Quick Actions and from custom key assignments, and they are the only category that can save time on work rather than on navigation.

Most articles about adding shortcuts cover the first category and stop. That is also the category with the least payoff, because navigation is rarely where the minutes actually go.

The sidebar and the Dock are two lists that behave differently

Adding to the sidebar takes one key. Select a folder in a Finder window and press Control-Command-T, or drag it into the Favorites section directly. Dragging is the more precise route, because the drop position decides the order and the order is worth thinking about. A list of fifteen favourites gets scanned rather than aimed at, which is slower than the four clicks it replaced.

The Dock takes a different key. Control-Shift-Command-T adds the selected Finder item to the Dock, where a folder becomes a stack that can be set to fan, grid, or list. A stack shows the contents without opening a window, which makes it the better choice for a folder that gets read from rather than navigated into. Downloads is the obvious example.

One list is shared by every Finder window and every save dialog, and one is not. The sidebar appears inside Open and Save panels, so a folder added there is reachable at the moment a file is being saved, which is when the wrong destination usually gets picked. The Dock is not present in those dialogs at all. If the goal is to stop saving things to the desktop by accident, the sidebar is the list that matters.

Neither list holds files well. Both are built around folders and applications, and a single document added to either tends to be the entry that gets removed first.

There is also a layer above manual entries that gets overlooked. Finder settings has a Sidebar tab listing every item macOS is willing to show automatically, including the home folder, iCloud Drive, the Applications folder, external disks, and connected servers. Several of these are switched off by default. Turning on the home folder there removes the need for a manual favourite pointing at the same place, and turning off the categories that are never used shortens the list without deleting anything. Working through that tab once is usually worth more than adding three shortcuts by hand, because it is the only part of the list that maintains itself.

The toolbar is the route most people skip

The row of buttons at the top of a Finder window accepts folders and applications, not just the built in controls. Hold Command and drag a folder onto the toolbar, and it drops in when a green plus sign appears. Hold Command and drag it back out to remove it. Holding Command while dragging an existing item rearranges the row.

What makes this different from the sidebar is that a toolbar item is also a drop target. Files can be dragged onto it to move them there, which turns a two window operation into one drag. For a folder that receives things rather than one that gets opened, this is the better place for it.

The rest of the toolbar is configured through View then Customize Toolbar, where items can be dragged in and out, spacers added, and labels turned on or off. The path control and the Get Info button are the two that repay their space most often. The toolbar is per window in appearance but the configuration is shared, so a change made in one window applies everywhere.

Aliases and symbolic links look identical and are not

Select an item and press Control-Command-A to create an alias next to it. An alias can be dragged anywhere, and Command-R opens the original from it. The important property is that an alias tracks its target: move or rename the original and the alias keeps working, because it stores a file identifier rather than only a path.

A symbolic link is the shell equivalent, created with ln -s, and it stores a path and nothing else. Move the original and the link breaks silently.

Route	Survives moving the original	Visible to shell commands	Setup
Sidebar entry	Yes	No	One key
Dock item	Yes	No	One key
Toolbar item	Yes	No	Command-drag
Alias	Yes	No	One key
Symbolic link	No	Yes	One command

The row that decides most cases is the third column. Aliases are a Finder construct. A shell command pointed at an alias reads a tiny file, not the folder it stands for, so scripts and command line tools cannot follow one. Symbolic links are the opposite: the shell follows them transparently and Finder displays them like aliases. For anything that will be touched by both a window and a terminal, the symbolic link is the one that works in both places. That is the practical reason to reach for ln -s even when the destination is a graphical workflow.

The shortcut that needs no setup at all

Shift-Command-G opens the Go to Folder field in any Finder window, and it also works inside Open and Save dialogs. Typing a path completes as it goes, ~ expands to the home folder, and pressing Return moves the window there. Recently used paths appear in the same list.

This route is worth more than it looks because it scales. A sidebar with thirty entries is unusable, but a typed path is equally fast for the thirtieth folder as for the first. It also transfers directly to and from a terminal, since the string being typed is the same string a shell command would take. Dragging a folder from a Finder window into a terminal pastes its path, and pasting a path into Go to Folder does the reverse.

For anyone who already lives partly at the command line, this pair covers most of what sidebar entries were being asked to do, without any list to maintain.

The same idea has a shell side. Setting CDPATH in a shell profile makes cd search a list of parent directories, so the name of a project folder is enough from anywhere. The two halves complement each other: typed paths in the window, a short name in the terminal, and no icons added to anything.

Shortcuts that do something rather than go somewhere

The Finder right click menu ends with Quick Actions, and that list can be extended. The Shortcuts app builds workflows that accept files as input, and setting one to appear as a Quick Action puts it in that menu for any selection. Automator services and Folder Actions do the same job through an older interface, with Folder Actions running automatically whenever an item lands in a watched folder.

This is the category that saves real time, because it acts on the selection rather than moving the window. Converting a batch of images, stripping metadata, or moving anything older than a month out of a working directory happens without a single drag.

Two details decide whether one of these gets used again. The first is where it appears. A workflow marked as a Quick Action shows up in the right click menu and in the Preview pane at the right edge of a Finder window, and the Preview pane version is the one that gets noticed, because it sits next to the file that was just selected. The second is naming. The menu shows the workflow name and nothing else, so a name like Resize To 1600 is usable a year later while a name like Image Workflow 2 is not.

A custom key can be attached on top. System Settings, then Keyboard, then Keyboard Shortcuts, then App Shortcuts accepts Finder as the target application and any menu command typed exactly as it appears, which includes Quick Actions once they are in the menu. That combination, a workflow plus a key, is the closest thing on a Mac to a one press operation on a selection.

The limit is what the Finder can express. Anything conditional, anything that needs to read output and decide what to do next, ends up as a shell command anyway. At that point the workflow is: find the files in one window, carry the path to another window, run the command, then go back and check the result. Removing that carry is the whole argument set out in Features, and the comparison against other approaches is laid out in Compared with other file managers.

Where adding more stops helping

Every route above shortens the distance to a place. None of them shortens what happens after arrival. If the pattern is open folder, look, then run something against a subset of what is there, then the number of clicks to reach the folder was never the expensive part.

A useful test is to count the windows rather than the clicks. A task that touches one window is already fast. A task that bounces between a file list, a terminal, and an editor is slow no matter how many sidebar entries exist, and it stays slow after the twentieth one is added. Details on how that applies across languages and regions are in Languages.

What to change first

Add exactly one sidebar entry, for the folder that receives files rather than the one that is browsed, and learn Shift-Command-G instead of adding a second. Then look at whether the step after opening the folder is a shell command, because if it is, a file manager with a terminal in the same window such as Atriens removes a cost that no shortcut list can touch.