Lightroom
Client Picks in Two Lightroom Classic Catalogs: What Carries Over
A laptop catalog on location, a desktop catalog at the studio, and one client choosing photos in between. Here is exactly what the pick import does when the shoot lives in more than one catalog.
Updated 18 September 2026
Short answer: the ClientGallery pick import does not sync two catalogs with each other. It writes the client's picks into the catalog that is open when you run it. If the shoot lives in two catalogs, you run the import once in each, and the same picks land on the matching photos in both.
That is a narrower thing than catalog sync, and it is worth being precise about. Your own star ratings, your develop settings and your keywords do not travel from one catalog to the other through the plugin. Only the client's picks do, and only because the same gallery is read twice.
This page covers the setups where two catalogs come up, what the import writes each time it runs, what it overwrites, and what it never touches. Everything below was checked in the plugin source, version 3.2.0, on 18 September 2026.
What the import reads and where it writes
The pick import lives in the Library menu, under Plug-in Extras, as Import ClientGallery Picks. It asks for two things: your studio key and the gallery link.
The gallery is the single source. The picks are stored on the gallery, not in any catalog. So every catalog that runs the import reads the same list of likes, loves and labels.
The target is the active catalog only. The plugin asks Lightroom Classic for the catalog that is open and searches that one. A second catalog sitting on the same drive is never opened, read or written by the import.
The match is by file name. For each photo the client picked, the plugin searches the open catalog for that file name and writes to every photo the search returns. The search is a partial match, not an exact one, so a short name can also catch longer names that contain it.
What lands on each matching photo
Each run writes the same values, whichever catalog is open. This is the full list of fields the import sets.
| Client action in the gallery | Written to the matching photo in the open catalog |
|---|---|
| Like | Rating set to 3 stars. The Pick flag is not touched. |
| Love | Rating set to 5 stars and the photo flagged as a Pick. |
| Color label | The same color label (red, yellow, green, blue or purple), when labels are switched on for that gallery. |
| Comment | Nothing by default. With the caption option ticked, and comments switched on for the gallery, the comments are written into the IPTC caption, replacing what was there. |
| Any of the above | Added to a collection named after the gallery, inside a ClientGallery collection set in that catalog. |
Nothing else is written. Develop settings, keywords and every other field are left alone. The import never sets a photo to Rejected.
The setups where two catalogs come up
The rule is the same in every case: run the import in each catalog that holds the shoot. What changes is whether you need to.
| Setup | What to do with the client's picks |
|---|---|
| Laptop on location, desktop at the studio | Run the import in the catalog you will edit in. If the shoot is imported into both and you want the picks in both, run it once on each computer. |
| Working catalog plus an archive catalog | Run it in the working catalog while you edit. Run it again in the archive catalog once the shoot has been imported there, so the archive carries the client's picks too. |
| One catalog per year or per client | Open the catalog that holds this shoot before running it. The import never looks in a catalog that is closed. |
| Two people, each with their own catalog | Each person runs the import in their own catalog, with the studio's one key. Both get the same picks on their matching photos. |
If the shoot is in only one of your catalogs, there is nothing to sync. Run the import there and ignore the other.
Setting up the second computer
A second catalog on a second computer needs the plugin installed on that computer too. The plugin is a free download from the clientgallery.io Lightroom page. Our own install steps are: unzip it, move the folder ending in .lrplugin somewhere permanent, add it through File, Plug-in Manager, then restart Lightroom Classic. The plugin install guide walks through each step.
The studio key is per account, not per computer. The same key works on the laptop and the desktop. You find it at the bottom of your studio page on clientgallery.io.
Paste it once on each computer. The plugin remembers it after that, and the pick import dialog opens with it already filled in. In the ClientGallery export settings, the Check button confirms which studio the key signs in to.
One thing to know before you regenerate the key on the dashboard. A new key kills the old one. Both computers then need the new key pasted in before the next import.
The plugin works in Lightroom Classic only. It does not run in the cloud Lightroom app.
Overwrite and never-clear: the two rules that matter with two catalogs
It overwrites what it touches. The import sets the rating and label without checking what was there. A frame you rated 5 stars in one catalog, which the client only liked, drops to 3 stars in that catalog. An existing color label is replaced by the client's label.
With two catalogs, this means your own ratings can differ between catalogs before the import and match after it, on the photos the client picked. On the photos the client never touched, each catalog keeps whatever you had.
It never clears anything. A re-run adds and overwrites. It does not remove a rating, flag or label from a photo the client later un-picked. A love that the client later turns into a like drops to 3 stars on the next run but keeps its Pick flag, because a like never sets the flag. The collection is reused on each run and nothing is ever removed from it.
The practical order. If the client changes their mind between your two runs, the two catalogs can end up with different picks. The clean way is to wait for the client's final picks, then run the import in each catalog. If one catalog already carries picks from an earlier round, check the photos the client dropped by hand, since the import will not reset them.
Publishing from either catalog
On the upload side, a gallery is identified by its name on your account. Exporting from either catalog to a gallery name that already exists adds to that gallery. This works on a free account too.
A gallery holds one photo per file name. If you export the same frame again from the other catalog, the new upload replaces the old one in place and the client's picks on it stay. So a proof re-exported from the desktop after a laptop edit does not reset the client's choice.
Plugin uploads carry the catalog photo's own file name. That is the name the pick import later searches for. Keep the same file names in both catalogs and the picks find their photos in both. If one catalog holds renamed copies, the import will not find them there.
Rating changes made by the import do not queue anything for re-upload. The plugin does not treat a metadata change as a reason to republish, so running the import in a catalog never pushes new proofs to the client.
Two people, one account
There is no seat model. clientgallery.io has no multi-user accounts, no roles and no per-assistant logins. A two-person studio shares one account and one studio key.
For the pick import that is enough. Both people read the same galleries with the same key and write into their own catalogs. What it does not give you is a record of who ran what, or separate access per person. If you need that, this is the wrong tool for it.
When the import finds nothing in the second catalog
If none of the picked file names exist in the open catalog, the plugin says so with this message: "None of the N picked filenames were found in this catalog. Import the shoot folder first, then run this again." N is the number of names it searched for.
With two catalogs, check these three causes.
- The wrong catalog is open. The import only searches the active one. Open the catalog that holds the shoot and run it again.
- The shoot is not in this catalog yet. Import the photos first, then run the pick import.
- The file names differ between catalogs. The search is by file name, so renamed copies in one catalog will not match the names stored in the gallery.
When the import does find photos, a summary dialog reports the counts, so you can compare the two catalogs side by side.
Who should not rely on this
You want your own ratings and edits synced. The plugin moves the client's picks, nothing else. Merging your own work between two catalogs is a Lightroom Classic job, not a plugin job, and this page does not cover it.
You need picks to clear when the client changes their mind. The import never removes a rating, flag, label or collection entry. If you re-run it after a change, the dropped frames need a manual check.
You work in the cloud Lightroom app. The plugin is Lightroom Classic only.
For studios that do fit, the plan is simple. A free account holds one gallery and 5 GB, and the pick import is not limited by plan. The paid plan is $10 a month or $100 a year for unlimited galleries under fair use. The full pick workflow is in the guide to getting client picks back into Lightroom, and the two-person view of the product is in client gallery software for a small studio.
Limits at a glance
| Item | Value |
|---|---|
| Catalogs searched per run | 1 (the open one) |
| Studio keys per account | 1, usable on any number of computers |
| Like / love | 3 stars / 5 stars plus Pick flag |
| Photos per gallery | 1,000 |
| Proof storage per paid account | 250 GB |
| Free account | 1 gallery, 5 GB |
| Paid plan | $10 a month or $100 a year |
Sources
No outside source is used on this page. Adobe's help pages could not be fetched on 18 September 2026, so nothing here describes how Lightroom Classic handles catalogs internally.
- clientgallery.io product facts, checked in code 18 September 2026: Lightroom Classic plugin version 3.2.0 (active catalog only, partial file name match, 3-star likes, 5-star loves with a Pick flag, label and optional caption writes, overwrite without clearing, collection reuse, the not-found message, studio key remembered in the plugin, metadata changes not triggering republish), the plugin upload routes (gallery identified by name, one photo per file name, 1,000 photos per gallery, 250 GB per account), the pick import route (not limited by plan), and the plan terms ($10 a month or $100 a year, free account of one gallery and 5 GB, no seat model), https://clientgallery.io/lightroom
Frequently asked
Does the ClientGallery plugin sync star ratings between two Lightroom Classic catalogs?
No. It writes the client's picks into the catalog that is open when you run it. Running it in each catalog applies the same picks to the matching photos in each, but your own ratings, develop settings and keywords do not move between catalogs.
Can I import client picks into a catalog that is not open?
No. The import searches only the active catalog. Open the catalog that holds the shoot, then run Import ClientGallery Picks from the Library menu under Plug-in Extras.
Does the same studio key work on my laptop and my desktop?
Yes. The key belongs to the account, not to a computer. Install the plugin on each machine and paste the key once on each; it is remembered after that. If you regenerate the key on the dashboard, the old one stops working on both.
What happens if I run the import in a catalog where I already rated the photos?
It overwrites the fields it touches on the photos the client picked. Likes become 3 stars, loves become 5 stars with a Pick flag, and the client's color label replaces yours. Photos the client never touched keep your ratings.
If the client changes their picks, does a re-run clean up the other catalog?
No. The import adds and overwrites but never clears. A photo the client un-picked keeps its rating, flag and label, and stays in the collection. Check dropped frames by hand in each catalog.
Can two photographers in one studio each import picks into their own catalog?
Yes, with the studio's one shared key. There is no seat model: no separate logins, no roles, no multi-user accounts. A two-person studio shares one account.
Why does the import find the photos in one catalog but not the other?
The match is by file name in the open catalog. Check for the wrong catalog being open, the shoot not yet imported into that catalog, or the photos carrying different file names there.
Your client galleries, under your name
Unlimited galleries, your branding, one-click Pixieset import, and a Lightroom plugin, all on a flat 10 $/month with everything included. Your first gallery is free.
See the Lightroom plugin