Skip to main content
Inspiring
October 19, 2017
Released

P: Ability to sync Lightroom Classic keywords with the Lightroom Ecosystem

  • October 19, 2017
  • 375 replies
  • 17478 views

Keywords do not sync correctly: When added on the mobile app (iOS), they do not appear in LR classic and not in LR Web (I deleted the new LR CC immediately, this version does not make sense to me).
Same problem into the other direction: Keywords from LR classic do not appear on the mobile app. 
Attention: At this stage the whole keywording within the iOS app should not be used!

375 replies

Community Expert
January 27, 2021

>but not sure you can keep the folder/album structure on your local drive or even if you can choose the location.

You indeed cannot keep your preferred folder structure if you go full cloudy. It files local copies of your files in a single location using a simple dated folder structure. You can choose the location however but Lightroom Cloudy keeps the files organized in a strict structure in that single location. The important thing to realize is that this is not a strategy for backup but is only meant to provide quick access to your files and you won't have to download copies all the time in order to edit them. If you delete a file in the cloud, it will also immediately get deleted from this local storage!

Antoine HLMN
Inspiring
January 27, 2021

That wouldn't be needed because of how the different versions of LR work together. In short:

1) Classic and cloudy

* No keywords sync (so are stacks, color labels, ...)

* Only smart previews synced from Classic to the cloud, but they do not take storage 🙂

* Only way to have full res images in the cloud is via mobile, ...

2) Full cloudy:

* Keyword sync

* Ability to have full res in the cloud

* Limitations of cloudy compared to classic

* To be verified, but not sure you can keep the folder/album structure on your local drive or even if you can choose the location. That's a big no for me for several reasons. First reliability, pictures were lost in the cloud with no backup (!) and having them locally is a must. Then not having the folder structure on a local hdd (and the edits) would be a major barrier to migrate to another solution. The biggest no go for me.

    Participating Frequently
    January 26, 2021

    So I already pay for an individual subscription to the entire Creative Cloud.  The only way Adobe can get more money from me would be if keywording worked well between the Lightroom versions - I would then move my entire massive photo collection into the cloud and happily pay for the needed cloud storage.  Maybe there’s just not enough of people in my situation.  

    Participating Frequently
    January 26, 2021

    Same here. This and the poor handling of Fuji .raf files means that I am pointing people towards Capture One. It is a bit trickier for me to change with 14 years of images in Lightroom.

    Antoine HLMN
    Inspiring
    January 26, 2021

    @max_l_g5zfjo4iqqgaf 

    For what it's worth, I'm already at a point of NOT recommending Lightroom to anyone ever, but this is pushing me to migrate away myself. The team just keeps making one bad software design decision after another and when they are pointed out, the response is borderline offensive. 

    Amen 🙏
    I could not phrase it better.

    LR used to be the best DAM, and by far. But development decisions the last years are terrible and customer are treated as excrements. Bugs are too often referred as « feature requests » if not referred to as « by design ». The updates are either marginal or for the social side of LR.

    I too stopped recommending LR, sadly. LR used to be the best in its class. It’s not and by far!

    Max LTV
    Known Participant
    January 26, 2021

    But there is syncing of keywords, it's just badly broken. Keywords sync to the files stored in Lightroom CC, but Lightroom CC stays unaware of them. That is just bad software design and poor user experience. 

    Why can't this be fixed? The simplest way to address it would be for Lightroom CC to re-read keywords on file change just like it does on file import. It will still be infinitely better than the current mind-blowingly poor design decision. 

    For what it's worth, I'm already at a point of NOT recommending Lightroom to anyone ever, but this is pushing me to migrate away myself. The team just keeps making one bad software design decision after another and when they are pointed out, the response is borderline offensive. 


    Rikk Flohr_Photography
    Community Manager
    January 26, 2021

    This thread is being merged into an existing authoritative thread for better tracking and response. 

    Rikk Flohr: Adobe Photography Org
    Rikk Flohr_Photography
    Community Manager
    January 26, 2021

    Keywords do not sync between Classic and the Cloud.

    Rikk Flohr: Adobe Photography Org
    Max LTV
    Known Participant
    January 26, 2021

    When I change metadata fields in Lightroom Classic, some metadata update in Lightroom Cloud and some do not. For example, changing the Title or Caption fields in Classic does propagate to Cloud but changing some other fields does not. Or rather the changes propagate to the photo that's in Lightroom Cloud but Lightroom Could does not "see". 

    For clarity, let's say in Classic I change photo title, caption, and keywords from black to "Frustration". Then I update metadata in file and sync, and look at the photo in Lightroom Cloud - Title and Caption metadata updated but keywords field is till blank. But when I save the file from Lightroom Could, all 3 fields are actually updated to "Frustration". So, frustratingly, lightroom could actually gets out of sync with the actual file it stores in the could. 

    This is very inconvenient because editing metadata is easier to do in Lightroom Classic, but then all that work is lost because there seems to be no way to get the Could to be aware of some of the changes. 

    Califdan2
    Inspiring
    January 17, 2021

    Apparently the LR product manager is "married" to this idea of only having minimal metadata sync capability between the two ecosystems and is oblivious to the customer base frustration, convoluted machinations, expense, and inconvenience people are going through because of this one synchronization failure point. 

    Only hope seems to be if the LR Product Manager at Adobe leaves and a new person takes over who cares about what their customer base needs and want.