macOS has a frustrating gap: you can select ten files in Finder, hold Option, right-click — and you'll either get just the last file's path, or nothing useful at all. The native "Copy as Pathname" doesn't support multi-file selection. It's a one-at-a-time operation.
This limitation hits in very specific but common scenarios. You want to feed a list of files into a script. You're building a manifest of assets. You're pasting multiple file references into an AI prompt. You need to log which files changed for a ticket. All of these require the same thing: the paths of multiple files, at once, on the clipboard.
macOS can't do this natively. The fastest solution is Pathly: select multiple files in Finder, right-click, choose your format — all selected paths are copied as separate lines. For a terminal-only approach, use ls -d "$PWD"/* | pbcopy from within the folder.
What Happens with the Native Method on Multiple Files
Let's confirm the problem. Select three files in Finder using ⌘+click or shift+click. Hold Option and right-click. You'll see "Copy 3 Items" in the menu — but the "Copy [filename] as Pathname" option changes behavior depending on macOS version:
- On some versions: the menu item doesn't appear when multiple files are selected
- On others: it copies only the path of the file you right-clicked on, silently ignoring the rest of your selection
- In all cases: there is no native way to get all three paths in one action
This is a deliberate macOS design limitation, not a bug. The native path copying feature was designed for single-file use. The workarounds below are the accepted solutions.
Method 1: Terminal with ls and pbcopy
If all the files are in the same folder, this Terminal one-liner is the fastest approach without extra software:
Each file path is on its own line, separated by newlines. You can paste the entire block wherever you need it.
To navigate to the right folder, you can drag it from Finder into the Terminal window after typing cd (with a trailing space) — macOS inserts the path automatically.
Method 2: Filter by File Type
If you only want paths for specific file types — say, all the .png files in a directory, or all .ts source files — you can filter with a glob:
Method 3: Recursive — All Files in a Folder Tree
If you need the paths of all files across a folder and its subfolders, use find:
The sed command converts the relative paths from find into absolute paths by replacing the leading . with the current directory. The last example uses git ls-files which is cleaner for getting paths within a git repository — it automatically excludes files in .gitignore.
Method 4: Pathly — Select in Finder, Right-Click, Done
All of the Terminal methods work, but they require switching to Terminal, navigating to the right folder, and typing or recalling the right command. That's fine for scripts and automation, but for ad-hoc use it's more friction than the task warrants.
Pathly handles multi-file selection directly from Finder's context menu:
In Finder, select multiple files using ⌘+click (individual files) or Shift+click (range).
Right-click the selection (no Option key required).
Choose Copy Path, Copy Filename, or any other Pathly format.
All selected files' paths are copied to the clipboard, one per line. Paste them into a text editor, a script, a prompt, or any other destination.
The format choice matters here — and this is where Pathly's five formats become especially useful with multiple files:
- Copy Path → all absolute paths, one per line
- Copy Filename → just the filenames, one per line (useful for a manifest or asset list)
- Copy Directory → the folder path of each file (useful if files span multiple directories)
- Copy Git Path → git-relative paths for all selected files (perfect for PR descriptions referencing multiple changed files)
When I'm describing a change to Claude Code that spans multiple files, I select all the affected files in Finder, right-click, and choose Copy Git Path. I get something like:
js/i18n.js
index.html
blog/blog.css
I paste this directly into my prompt: "I changed these files: [paste]. Review the changes for consistency." Claude reads the git-relative paths, correlates them with the files in its context, and gives me a focused review. This takes about 5 seconds. The Terminal equivalent would be 30+ seconds, minimum.
Use Cases for Multi-File Path Copying
Here are the scenarios where this capability actually matters:
Batch file processing scripts
You have 8 video files to transcode. You want to build the ffmpeg command list without typing each path manually. Select all files in Finder, copy their paths, paste into your script template.
Asset manifests
You're documenting what images are in a project's images/ folder. Select all, copy filenames (not full paths), paste into a markdown table or JSON manifest.
AI coding prompts with multiple file context
Select the files relevant to your question, copy their git-relative paths, paste them at the top of your prompt: "These are the files involved: [paths]. The issue is X." See our guide on using file paths with AI coding tools for more on this workflow.
Bug reports and tickets
You need to list which files are affected by a regression. Select them in Finder, copy paths, paste into the ticket. Much faster than right-clicking each one individually.
Code review preparation
Before a PR review, list all the files you changed using git-relative paths. Paste them into your PR description or a Slack message so reviewers know exactly what to look at.
Comparison: Methods for Copying Multiple File Paths
Shell Functions Worth Adding to Your Profile
If you frequently need multiple file paths in Terminal and prefer not to install anything, these shell functions are worth adding to your ~/.zshrc or ~/.bashrc:
Source your profile (source ~/.zshrc) and these become available as simple commands. copygitpaths is particularly useful before an AI code review session — it gives you the exact list of files you changed, ready to paste into a prompt.
For the Finder-centric workflow without Terminal, Pathly handles this with the familiar right-click menu you already use. For everything else, the Terminal one-liners above cover the power-user scenarios.