How to turn copied paths into files on macOS
You can do this with Paste My. One shortcut turns path text on your clipboard into the actual files, so you can paste or attach them instead of hunting for each one.
Somebody sends you a list of file locations — in a message, in a ticket, in the output of something that ran. The files are on your Mac. You just have to go and get them.
Done by hand, that is a navigation exercise: read a path, open a Finder window, walk the folders, find the file, repeat. For four or five files it is genuinely irritating.
One shortcut turns the text into the files themselves, on the clipboard, ready to paste.
Turn the paths into files
Copy the path text
Select the paths wherever they are — a message, a note, a terminal — and press ⌘C.
One path or several. What is on the clipboard at this point is ordinary text.
Press ⌥⇧⌘F
The path text is turned into real file objects and put back on the clipboard — the kind the Finder accepts, not a description of them.
No window opens and it does not matter which app you are in.
This works on paths that point at files that actually exist on this Mac. A path to something that is not there cannot become a file, because there is no file for it to become.
Paste them wherever files go
Paste into a Finder window and you get the files. Paste into an email or a message and they attach. Drop them into an app that takes files and it takes them.
It is the same clipboard behaviour as if you had selected all of them in the Finder yourself — which is precisely the work you skipped.
Both versions stay in your history
The text you started with is still in your history as text, and it stays that way. Converting the clipboard does not rewrite what was saved.
So if you need the paths as text again later — to paste into a config, or send on to somebody else — press ⇧⌘V and take them.
Your history, newest at the top. The sources list is on the left; each entry carries a badge for the kind of thing it is.
The round trip, both ways
This shortcut is one half of a pair, and knowing both makes each more useful.
- Files to text. Copying files in the Finder records the plain text of their paths alongside the files, so you can take either.
- Text to files. ⌥⇧⌘F goes the other way, turning path text into the files themselves.
Between them, the awkward gap between “a file” and “where a file is” mostly stops existing. You copy once and take whichever form the destination wants.
The other clipboard conversions
| Shortcut | What it does |
|---|---|
| ⇧⌘C | Re-copy whatever is on the clipboard as plain text |
| ⇧⌘L | Copy a link with its tracking parameters stripped out |
| ⇧⌘B | Re-copy the clipboard as Base64 |
| ⌥⇧⌘F | Turn copied path text into real files |
All four act on the clipboard from anywhere and leave your history untouched.
Where this earns its keep
The shortcut looks niche until the first time it saves you ten minutes of navigating, and then it is one of the ones you keep.
- A list from a colleague. Five paths in a message become five files you can attach to a reply.
- Output from something that ran. A build, a script or a search prints locations; you want the things at those locations.
- A note to yourself. Paths you saved last week become the files again without you retracing where you put them.
- Anything with awkward folder names. Long paths with spaces are exactly where hand-navigation goes wrong.
Because the text stays in your history unchanged, you can convert, use the files, and still have the list to send on to somebody else.
If the conversion does not produce files
The files are not on this Mac
A path is a description of a location on a particular machine. If the file is not at that location here, there is nothing to convert it into.
This is the usual reason paths from a colleague do not work: the paths are valid on their Mac, not yours.
The path text has formatting on it
Paths copied out of a styled document, a chat app or a web page often arrive wearing that source's styling, and can pick up smart quotes or line wrapping along the way.
Press ⇧⌘C first to re-copy the clipboard as plain text, then ⌥⇧⌘F.
Some paths worked and others did not
Each path is only convertible if the file it names exists here. A mixed list produces the ones that do.
Check the ones that failed by pasting the text back and reading them — a typo, a truncated line or a renamed folder is usually the cause.
Questions people ask
Do the files have to exist already?
Yes. The shortcut turns paths into the files they name — it does not create anything. A path to a file that is not on this Mac has nothing to become.
Can I convert several paths at once?
Yes, and that is where it saves the most time. A list of paths becomes a set of files you can paste or attach in one go.
Does it work with paths that have spaces in them?
Copy the paths as they were given to you and convert. If the text has been through a styled document, flatten it first with ⇧⌘C so nothing unexpected is in the way.
Is the original text lost?
No. The text clipping stays in your history exactly as you copied it. Only the clipboard changes.
Can I go the other way?
Yes — copying files in the Finder records the plain text of their paths automatically, so the reverse needs no shortcut at all.
Will the files still work if I move them afterwards?
Once they are on the clipboard they are the files, so pasting them works. A path, by contrast, goes stale the moment the file moves.
Does it matter which app the paths came from?
No. It acts on the clipboard, so paths from a message, a note or a terminal all work the same way — flatten first with ⇧⌘C if the text arrived styled.
Get Paste My
Free on the Mac App Store. Everything you copy, kept on your Mac and ready the instant you need it again.