Skip to main content
Adobe Photoshop Family

7 Messages

 • 

2.1K Points

Thu, Oct 19, 2017 12:53 PM

Implemented

201

Lightroom Desktop: Additional options needed when exporting

I ask because when you export in Lightroom CC, called "save to," the only parameter you can adjust is the pixels. Nothing else that I can see. In other versions of Lightroom you get a whole bunch of parameters to adjust, including DPI. Clients specify sometimes the settings that they want. Or another possibility is that I'm doing it wrong, and if so, could someone let me know how to export and adjust things like DPI.

Responses

12 Messages

 • 

530 Points

3 years ago

Can we please have export as tiff?Please?
Thanks

55 Messages

 • 

1.5K Points

3 years ago

Exporting as tiff would be everything I would need as well, but at least with customizable bit depth. 16bit would be nice.

2 Messages

 • 

192 Points

3 years ago

Ok, guys...6 month and no changes to the exporting feature. I cancel my subscription and go to Luminar. Sorry Adobe, but you clearly do not see what a fast upgrade cycle is. The last changes made to Lightroom CC have been marginal and only to do with your auto filters...get the basics right before being fancy.

1 Message

 • 

62 Points

3 years ago

I`m using LR CC as a professional. I wanted to uprgad to the 1TB plan. But then i realized I can ́t choose DPI and Color Range? Please put a serious export on the very top of your todo list!!

3 Messages

 • 

172 Points

2 years ago

I can't believe that this FR has only 35 votes. There are so less LRCC users out there? Or are they happy with the limited options here? I do not understand why Adobe did not implement such a basic feature.

55 Messages

 • 

1.5K Points

Contrary to what Adobe probably assumes, most users don't visit these forums at all. I doubt that the vast majority even cares about expressing their satisfaction or dissatisfaction in a forum like this one at all. They're angry and talk about it with their friends or just switch to a different product.

Getting useful feedback from your users is hard. But Adobe is worse at doing it that many other companies (perhaps intentionally).

If they added a more streamlined way for people to request for features (like an obvious button in the application's UI), the signal would increase dramatically... along with the noise.

Champion

 • 

5.9K Messages

 • 

104K Points

> Contrary to what Adobe probably assumes, most users don't visit these forums at all.

Adobe knows only a small number of their users visits the forum, but the percentage of votes compared to other requests still provides useful feedback, rather than focusing on the actual number of votes. In my experience, the percentages are fairly accurate when compared against the feedback I hear from a wide range of sources. 

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

5 Messages

 • 

208 Points

Came here solely with the hope that the export limitations are known and other people care. Of all possible features, the lack of control on export types/quality is the most crippling.

4 Messages

 • 

148 Points

2 years ago

This reply was created from a merged topic originally titled Add Export Options!!!.

I'm currently testing Lightroom CC on iOS and staggered about the non-existing export options. I really like the possibilities for the basic editing. But I don't understand that I can't define the export details like format/compression (JPG, TIFF, ...), ICC-Profile or dimensions of the photo. Please add these very basic options in the near future to keep up with your claim to be the best mobile editing app ...

55 Messages

 • 

1.5K Points

The fun part is that Adobe likes to pretend like this particular forum isn’t about Lightroom on iOS or Android at all (despite the fact that it’s called Lightroom CC on all platforms).

There are two product forums for Lightroom (not counting Classic):
Lightroom CC: https://feedback.photoshop.com/photos...
Lightroom for Mobile: https://feedback.photoshop.com/photos...

People post in either one of these product forums, referring to mobile products inside “Lighroom CC” and vice-versa. And of course they do, this product is called “Lighroom CC” everywhere. Adobe seems to be taking advantage of (or ignoring) this confusion when prioritizing features, blaming users for not knowing where to voice there opinion.

For example, they‘ve implemented “sync settings” on desktop but not mobile, claiming that people haven’t voted for the mobile feature. However, it’s clear that comments have been referencing all platforms extensively: https://feedback.photoshop.com/photos...

Another example: Adobe has been merging requests marked for both “Lightroom mobile” + “Lightroom CC” (desktop) into desktop-only threads, without a corresponding topic or vote in the mobile-only thread: https://feedback.photoshop.com/photos...

To do these things, yet also claim that more people vote for desktop but not mobile is either disingenous or proof that Adobe doesn’t know how to receive feedback. They’re doing a lot of great things, but I’m baffled at their continuous refusal to treat mobile as a first class platform.

So I guess you’ll have to more actively voice your opinion in the other product forum if you want to get something on iOS, then hope that Adobe listens to you in a few years :)

Champion

 • 

5.9K Messages

 • 

104K Points

> Adobe seems to be taking advantage of (or ignoring) this confusion when prioritizing features, blaming users for not knowing where to voice there opinion.
For example, they‘ve implemented “sync settings” on desktop but not mobile, claiming that people haven’t voted for the mobile feature.

Don't worry, all of the feature requests get considered, whether they're showing as mobile or desktop.

Mobile is considered a first class platform, but each team has its own features to be working on, so the different platforms tend to leapfrog each other. Each platform has its own strengths and weaknesses, for example, the mobile team has camera improvements to fit into their development time, which doesn't apply to desktop, and mobile operating systems and devices have different limitations to desktop ones.

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

55 Messages

 • 

1.5K Points

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 :)

Champion

 • 

5.9K Messages

 • 

104K Points

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 Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

1 Message

 • 

100 Points

2 years ago

Absolutely crazy that this has not been solved, finally decided to give lightroom cc mobile a go, upgraded to the 1tb plan, imported 2000 photos, spent hours editing a selection, now I wish to make further edits in affinity for example, but there is no point in making any further edits to a lossy jpeg! Wished I had done further research into the export options before investing a lot of time and money into this! Will need to look for an alternative solution, maybe scrap adobe all together, and stick to capture one on desktop too.

2 Messages

 • 

80 Points

2 years ago

Export limitations are a bad Thing for all platforms. It limits the users in their workflow and does not allow further editing without loosing Qualität. Sure, a high quality jpeg ist not bad at all but there are many use cases you need loosless exports like tif or psd. I am sure this would be very easy to implement because these formats are state of the art and maybe just export parameters.

Additionally, if you want to print photos, you may need a quality that is somewhere betweend the two offered options. You may not believe it, but in many regions upload speed is still limited. However, let the user define the compression rate and size of the picture would and should also not be a big thing. I am sure you use existing libraries for that and they all allow to export with parameters (type, compression, size, etc). So how long would it take to implement and test? 1 day? Maybe 2

39 Messages

 • 

646 Points

2 years ago

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

55 Messages

 • 

1.5K Points

2 years ago

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.

39 Messages

 • 

646 Points

2 years ago

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.

55 Messages

 • 

1.5K Points

2 years ago

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.

39 Messages

 • 

646 Points

2 years ago

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.

176 Messages

 • 

3.7K Points

2 years ago

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?

Go for C1, succeed your cloud by yourself 

5 Messages

 • 

262 Points

2 years ago

This reply was created from a merged topic originally titled Export TIFF from Lightroom CC.

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

12 Messages

 • 

530 Points

Yup. So much for having LR mobile being a professional tool. :-(