Client picks to Lightroom: filename workflow without the hunt
Direct answer
Getting client favorites back into Lightroom Classic usually means a filename handoff: the client hearts proofs in a gallery, you get a list of basenames, then you filter your catalog and flag picks. Lightroom has no native CSV import for client selections. Library → Metadata → Text → Filename → Contains, with a space-separated paste, is the standard path.
That path breaks when lists arrive with line breaks, spaces inside names, substring collisions (IMG_1 vs IMG_101), or duplicate basenames across folders. Fix the list and filter by shoot folder first. At higher volume, inbound sync plugins (Pic-Time Sync Gallery, Gallerina-style metadata sync) beat paste. Most gallery "Lightroom plugins" are upload-only and do not sync favorites back.
Grain Issue copies space-separated filenames from the studio today. A Lightroom Classic OAuth plugin (publish proofs/finals + sync selections) is on the product roadmap; this page documents the paste workflow that works now.
The paste workflow (Lightroom Classic)
- Get a clean list from the gallery (copy filenames) or from the client (one line of text).
- In Library, filter to the shoot folder or collection first.
- Open the filter bar → Metadata → Text → Filename → Contains.
- Paste a space-separated list of basenames (extensions optional if names are unique).
- Review results for false positives and duplicate basenames.
- Flag picks: color label, pick flag, or add to a "Client selects" collection.
For a full portrait proofing arc (upload → favorites → retouch → deliver), see proofing gallery workflow.
Paste rules checklist
| Rule | Why it matters |
|---|---|
| Space-separated, not one filename per line | Contains expects one paste string |
| Filter by folder or collection first | Same basename in two shoots selects wrong files |
| Watch substring collisions | IMG_1 can match IMG_101 and IMG_10 |
| Match the export basename | Virtual copies and re-exports may not match copy-list names |
| Keep naming consistent at export | Spaces vs underscores should match what the client saw |
| Re-paste after client revisions | Treat each submit as a new list |
Capture One shortcut
Capture One users paste into Select By → Filename List (clipboard). The same filename pains apply. Grain Issue is Lightroom-first for plugin sync; Capture One export handoff is planned after the Classic track ships.
DIY proofs without a gallery SaaS
If proofs live in Drive, Dropbox, or a static folder, clients often send picks in email or WhatsApp. The free picks tool reads filenames locally, gives clients a heart UI, and outputs one paste line for Lightroom. No upload, no account.
When sync beats paste
| Situation | Paste | Inbound sync |
|---|---|---|
| Under ~30 picks, clean filenames | Usually fine | Optional |
| 100+ wedding selects | Slow, error-prone | Worth paying for or switching tools |
| Messy archives / second shooters | High collision risk | Sync + ambiguity UI helps |
| Shared studio Mac | N/A | OAuth beats token paste |
| Client revises selections | Re-copy list | Revision-aware sync (roadmap) |
Publish ≠ sync: Pixieset and ShootProof Lightroom plugins upload proofs to the site. Client favorites still need a copy-list or a platform with inbound sync. See Pixieset vs Pic-Time vs ShootProof for stack context.
Honest Grain Issue gaps
- No Lightroom plugin shipped yet. Studio copies filenames from the shoot today; OAuth publish + sync is in development.
- Basename matching only. Duplicate filenames in one catalog need human resolution.
- Not a lab marketplace. Pixieset and Pic-Time still lead integrated print fulfillment.
- Not Adobe Lightroom Web. Clients use a branded portal link, not an Adobe ID.
FAQ
Can I import a CSV of client picks into Lightroom?
Lightroom Classic does not offer a built-in CSV import for client selections. Power users sometimes use third-party list plugins (Extended Search, Photo List Importer). Most studios paste into Filename → Contains.
Why does Lightroom filename search break when filenames have spaces?
Contains matches substrings. A list pasted with wrong separators, or names that share prefixes, returns extra photos. Normalize to space-separated basenames and narrow the folder filter.
Does the Pixieset Lightroom plugin sync client favorites?
No. The Pixieset plugin is primarily for publishing photos to Pixieset. After the client picks, use Pixieset's copy filename list and the paste workflow above.
What is the fastest path if I use Grain Issue?
Client favorites in the branded gallery → studio copies filenames from shoot detail → paste into Lightroom. When the Classic plugin ships, you can publish from LR and sync favorites back with OAuth sign-in.
Should I use Lightroom Web collaborative proofing instead?
Lightroom Web proofing targets the cloud workflow: clients often need an Adobe account, and picks do not automatically flag local RAWs in Classic the way a Classic-native sync plugin would. Many portrait studios stay on Classic plus a third-party proofing portal.