Lightroom hides JPEGs when there is an accompanying RAW file. The majority of photographers - even amateur - import JPEGs alongside the RAW files. This will need to be supported for a lot of people to consider the switch.
Di you try checking "Treat JPEG files next to RAW files as separate photos"? If not, try checking the box. By default, it is disabled. Lightroom -> Preferences -> General -> Treat JPEG files next to RAW files as separate photos
Thanks for the reply. I'm not seeing it in CC. Are you referring to Lightroom Classic, or CC? I just noticed I accidentally added Classic category to this post as well...
Thanks for the input, Berry. We hesitated on this one, not knowing how people would want to handle the storage. Given that there are limits on cloud storage, would you want the sidecar JPEGs backed up?
I personally would like the JPEGs backed up and hidden in the interface. If I really were to run out of capacity then I would be forced to rethink my storage strategy. Until then I really would like to have the JPEGs backed up.
Could this not be controlled by the same setting that Lightroom Classic has: `Treat JPEG files next to RAW files as separate photos`?
It's worth noting that Adobe's own DNG format embeds JPEGs in the file itself, so you wouldn't have a reasonable option to save space in the way you have mentioned.
Also, for those who do not want to backup the JPEGs it would be very useful to have the option to exclude JPEGs during the import, so users don't have to go through all the files selecting only the RAWs.
I just discovered this issue (sidecars are apparently either absent by default or hidden when a catalog is migrated). Fortunately, I found it before importing a huge batch of with-sidecar files and can take steps to mitigate the issue when dealing with the rest of my (large) planned imports.
For me, shooting the RAW+JPEG combination has been one of many backups. Once things are in Lightroom, it's probably unnecessary to have both, and I can see myself hitting my current 1 TB cap within 18-24 months from now, so I'm happy to exclude them.
But I agree fully with Berry on having an in-app method for excluding JPEGs. The files I'm importing are currently in folders sorted by month and, even if it's just because I'm a creature of habit, I'm probably not going to stop shooting with sidecars any time soon. That means I'm going to have to put extra steps into my workflow to exclude the jpgs - sort by file type to select only RAW files, and double check to make sure there weren't any times in the session/month when I was shooting JPEG-only.
The main problem we encountered here is that lightroom cc will offer importing jpeg and raw separately. We'd love if we could just instruct lightroom cc to ignore jpeg files during import if there is raw counterpart.
Can somebody please follow up on this issue? Either enable users to import JPEG/RAW only, or at least enable filter by file-type so it can be easier to delete all JPEGs post-import.
I have to shoot RAW+JPEG because of WiFi/Smart device transfer requirements for JPEG files, but any time that I actually want to interact with photos in LR, it's almost always RAW.
I was trying out the new Lightroom CC today. The import feature is just kinda weak now. My camera takes a normal quality jpeg and a raw for each pictures. So in the file explorer, there will be a FILE_NAME.jpg and a FILE_NAME.raw. In Lightroom CC, the import window would automatically omit the .jpg files and just show me the raw files. But since the new CC directly calls the File Explorer api, this feature is gone. Can we please have this feature on the new CC 🙂 Thanks!
Realize that Lightroom desktop is NOT the new version of Lightroom. It is a port of the mobile os version of Lightroom to desktop operating system. It has all the many limitations of something running on a phone or tablet. It has the nice feature of syncing everything to the cloud but misses many really important features of the 'real' Lightroom. The real new version of Lightroom is called Lightroom classic. It has the full featured import panel, can print, full featured keywording, etc etc etc and stores all your images locally. Adobe's very unfortunate naming causes endless confusion. The cloud based version is meant to present a very simplified interface so as to retain feature parity between it running on mobile operating systems vs on the desktop. So if you want powerful features use classic. If you want simple interface and your images appear the same on every device use Desktop (the cloud based version)
13
Replies
AdChoices