P: Additional options needed when exporting

Yup. So much for having LR mobile being a professional tool. 😞

I find very annoying that I cannot export photos in TIFF format from Lightroom CC after one year or more it has been released, and I am still paying for it. Am I supposed to use JPEG on other editing software that are part of my workflow? Isn't it time to add export settings? It looks like a bad joke to photographers that prioritize uncompressed format.
Thank you

11 months later, nothing happen with this underpowered feature.
Adobe prioritize in very confusing

I've discover iOS is able to embed copyright in the photo. Seems not ti be able in LR CC 1.5, do I'm wrong or right?

Thanks Victor, I don’t know unfortunately because I’m battling to get info on the image once created, non of the software I own can read the metedata on it. When I loaded it into classic and bridge it seems to give less info then the original RAW and the high quality lossy jpg, I think FIX losses some of the metadata when saving. One thing is for sure, it’s far less compressed. From what I’ve heard PNG is also a decent file type for many applications. Hoping someone with particular skills can give us info on the created PNG.

Editing in Photoshop Fix on iOS, going back to Lightroom Mobile, then exporting that as PNG is a pretty nice hack indeed, I haven't thought of that! Less than ideal for sure though.

Is this an 8-bit or 16-bit PNG? The crucial thing for me is being able to continue editing in other apps such as Affinity, without lossy compression.

Yes I wrote that it’s only to control the image pixel value, not compression, bit depth or file type. I believe the only way to export an uncompressed file from lightroom mobile is unfortunately one at a time. But I would suspect most people would not need all images exported this way, only one or two, just when required for particular uses. I haven’t been able to determine the bit depth or compression level, but what you can do is select an image, “edit in” then choose a app like Fix, it will open in fix, then save straight back into mobile without editing it and it creates a duplicate PNG file uncompressed. You then just select it and export original, now you have a edited uncompressed image. For example, the image I did the other day when exported high quality jpg was a 12mb image, with this method, the same image PNG was 45mb. Again I don’t know the full specs around what lightroom generates for fix, but far less compression if not any at all. By the way the workflow app also batch renames on export or can both do a batch rename and resize at the same time.

I printed three 8x12in images the other day, one a 16bit uncompressed file, one 8bit lossy from lightroom mobile and one 8bit jpg from classic set to 300dpi, couldn’t tell the difference.

For me batch export was the biggie, any special scenario where I need higher quality, I’d be on my Mac.

I suspect that your workflow hack simply re-converts the lossy compressed image exported from Lightroom to the format you want. This doesn’t mitigate the lossy compression artifacts and loss of quality at all.

I picked up on this thread linked to another relating to CC mobile. I use IOS, so I cannot comment on Android.


Firstly I wanted to say how happy I am to finally be able to export or share all images instead of the limited 15 at a time we had before, thank you adobe.


I noticed many still frustrated by the two available quality export options, high quality and 2048px quality. I cannot offer a bit depth or file type change solution for export, but I do have a way of changing pixel values on export to whatever I want below that of the original image pixel value.


I use the workflow app and have designed an extension which pops up after rendering (same place it asks you for a location). Before you share your files, set the pixel width or length in workflow, then when you choose the workflow extension, it will save all your images set to your pixel count.


Lastly, many people are concerned about the 72dpi Lightroom sets on all exported images in cc mobile. If you have a high res camera, which most people have, this really does not make much difference when printing. If you have for example a 6000 x 4000 image, like what my camera generates and Lightroom mobile exports not cropped, but with 72dpi, is the equivalent, once converted to 300 dpi to a 20x13.3 in print, which is bigger then most need. If anyone needs larger then that, just take the image you need printed manually or through the cloud into photoshop and set it correctly. If I printed 6000x4000px image on a 72dpi printer setting, it would give a 83in (length) print. It’s hard to even tell the difference between a 200 dpi and 300 dpi image when printing. If you set a 6000x4000px 72dpi image to print at 200 dpi, you get a 30in (length) print. 72dpi shouldn’t be a concern for most. It’s your pixel value that really matters and with the workflow app, you can set it on export.


Hope this helps

Threads get merged so all of the votes are combined into one place. If a thread is for both desktop and mobile, it should end up tagged as both Lightroom CC and Lightroom for mobile, so it shows up in both forums, although occasionally that doesn't happen.

> why aren’t all feature requests treated the same way? Why are some cross-platform threads merged but others are not?
Sometimes it simply depends on who's doing it! Or sometimes, they're features that would need to be implemented in completely different ways depending on whether it's desktop or mobile. Syncing settings across multiple photos is a great example, since the selection mechanism is completely different on a desktop vs. a mobile device.

> Why ask people to continue voting on mobile topics *after* a feature becomes under consideration or even implemented on desktop
When a feature is implemented on one platform, it's automatically a priority for other platforms as Adobe's aiming for feature parity long-term. Where there's a separate thread for mobile, like in the case of that sync feature, I recommended people vote on the mobile one so that they'd be notified when it was also implemented on mobile. However, the votes are still useful because some features may be used more on one platform than another. For example, how much do you need HDR merge on mobile, when it would be 10x quicker to do on the desktop.

It is a little fuzzy, but don't worry too much about the mechanics of how they gather the information. Just know that the people making the decision get a good overview from this forum.

Victoria, if all platforms are first class citizens and all features get considered regardless of which product forum they’re posted in, that indeed explains why requests on one platform get merged into threads from another platform, for example this one: https://feedback.photoshop.com/photos... (and there’s plenty of other examples).

But then why aren’t all feature requests treated the same way? Why are some cross-platform threads merged but others are not? Why did the above feature request get merged from mobile into desktop, but the “sync settings” feature request didn’t? I can’t figure out the rule for all of this, as these actions send mixed signals.

Why ask people to continue voting on mobile topics *after* a feature becomes under consideration or even implemented on desktop: https://feedback.photoshop.com/photos...

More importantly, I’m asking because I’m really struggling to understand how all of this works 🙂 I want to contribute by helping Adobe accurately weigh feature requests, but the current multiple-product forum setup is confusing: some cross-platform threads get merged together but others don’t, some features get released on multiple platforms at the same time but others don’t, some features are marked as “implemented” cross platform but others are marked in the same way but require continued voting on desired platforms.

Thank you for being patient with my questions 🙂