In this article
Check which item you have selected
Start in Finder, with the suspected alias selected but unopened. Choose File > Get Info or press Command-I. Check the item's kind and the original location shown for an alias. Then use File > Show Original, or Control-click the alias and choose Show Original, to reveal its target.
Pay attention to the selection after Show Original: Finder has now selected the original. Return to the alias's location before removing the shortcut. This small change of selection is easy to miss when the two items have the same icon and similar names.
Apple's alias guide explains that opening an alias opens the original item. The practical consequence is that an alias provides another route to something; it does not give you an independent working copy.
Once you have identified the shortcut, move that alias to the Trash. Open the original from its actual folder to confirm it is still there. There is no reason to empty the Trash as part of this check. Apple's Trash instructions describe File > Put Back if you moved the wrong item and it remains in the Trash.
Removing a shortcut and deleting through it are different actions
Imagine a folder named Project with a document inside it. You place an alias to Project on the desktop. There are now two convenient ways to open Project, but still only one original folder.
| What you select and remove | What you are acting on |
|---|---|
| The unopened Project alias on the desktop | The shortcut itself |
| A document inside the window opened through that alias | A document in the original Project folder |
| Project after choosing Show Original | The original folder |
| An independent duplicate of Project | That separate copy |
The distinction matters most when cleaning up a desktop. An alias to a large folder may look like a second copy of the folder. Opening it, selecting everything, and deleting the contents is not a way to empty the shortcut. You have reached the original contents.
Use the same care when editing a document opened through an alias. Changes saved to that document are changes to the original. If your aim is to keep an untouched version while experimenting, create a separate copy and verify its location before working on it.
What our disposable-file test showed
On October 7, 2026, we tested this distinction on macOS 15.7.5, Apple Silicon. We created one temporary text file, an alias made with Apple's Foundation bookmark-file APIs, a symbolic link, and an independent copy. No existing user documents or installed apps were involved.
The test resolved the alias to its target before editing that target. It also created a separate folder alias and removed a disposable child through the resolved folder location.
| Test action | Observed result |
|---|---|
| Edit the file reached by resolving the alias | The original text changed; the independent copy kept its earlier text |
| Remove the alias file itself | The original and copy both remained |
| Remove the symbolic link itself | The original remained |
| Remove a child through the resolved folder alias | The original child disappeared; the folder and its alias remained |
These were actual file operations through Foundation APIs, not a Finder interface test. The experiment supports the distinction between a reference and its target; it does not prove that every application handles links identically. The temporary test directory was removed afterward.
The useful checkpoint is the object being changed. A familiar icon, a convenient location, or the word “alias” in a filename cannot replace checking the selected item and the target you have opened.
Alias, symbolic link, or copy?
A Finder alias and a symbolic link both refer elsewhere, but they are different mechanisms. An ordinary duplicate contains a separate copy of the data.
Apple's archived aliases and symbolic links documentation describes the path-based nature of symbolic links and the additional information used by aliases. That document discusses older file systems, so do not turn its examples into a promise that an alias will always find a moved or replaced item on every modern storage service.
For this cleanup decision, you do not need to manipulate either mechanism in Terminal. Identify the reference, reveal its destination, and remove only the reference if that is your intention. A broken alias is also not proof that its target was deleted: the target might be unavailable, such as on a disconnected drive.
Watch the Finder selection change
MacMost's 10 Uses For Mac Finder Aliases, published January 14, 2026, provides a current visual walkthrough. The relevant sections begin with Show Original at 2:17, followed by deleting an alias at 2:45. Watch which object Finder selects before repeating the steps on your own files.
The video demonstrates Finder behavior; our table above separately records the controlled API experiment.
A desktop cleanup is not an app uninstall
Removing a shortcut to an application leaves the application in place. Similarly, Apple documents that removing an item from the Dock or Finder sidebar removes its reference without removing the original from the Mac.
If you actually want to uninstall an app, identify the installed application and follow the developer's uninstall instructions when provided. Do not begin by deleting everything with the app's name from Library. Our Application Support cleanup guide explains why settings, databases, and other retained files need separate decisions.
If the goal is reclaiming storage, distinguish the shortcut from the app and its data before estimating the benefit. Finder size and Storage totals measure different things. Deleting an alias cannot reclaim the original's stored contents while also keeping those contents intact.
Before moving anything to the Trash, answer three questions: Is this the reference or the original? Which folder am I actually viewing? Do I want to remove a shortcut, a copy, or the underlying data? Those checks make the next action much clearer.
