daniel_krieger's profile

7 Messages

 • 

2.1K Points

Thu, Oct 19, 2017 12:53 PM

203

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

Champion

 • 

6.7K Messages

 • 

111.8K Points

4 y ago

Right now it's just a version 1.0 product, so yes, it will probably be best suited to hobbyists at this stage. You're not missing those settings. You probably need to stick with Classic for now.

4 Messages

 • 

252 Points

4 y ago

I just thought the same.... maybe we need to wait until Lightroom CC 7 to get a professional cloud based LR... *it sucks*

4 Messages

 • 

244 Points

4 y ago

This reply was created from a merged topic originally titled Feature Request: Custom Export Configuration.

I would like to see the feature about the custom export. This will be super useful in order to export the files properly. I would like to see most of the option such as Quality Control, Color Space, Files Format, and Output Sharpening. This feature request is also apply to iOS Lightroom CC too. In future, I'm going to stop using Lightroom Classic and use the new Lightroom CC instead.

1 Message

 • 

140 Points

4 y ago

Yeah, this is extremely limited. It is like having a big block V8 with a straw for an exhaust...

1 Message

 • 

220 Points

4 y ago

What a letdown, we really need a proper export setting like we had in the 'classic' version ... 

48 Messages

 • 

1.1K Points

4 y ago

This reply was created from a merged topic originally titled More save export options.

We need more export / save options. And same in iOS version.
Currently only options are small (1048). Size , long edge and full. For jpgs output.
Plus importantly we need control for the compression/ quality and colour space to add Adobe RGB, as the jpgs are always sRGB., with some compression.
So I can give my clients full quality and colour space , in any size.

However , I noticed we can export to open in Photoshop . This opens a 16bit Adobe TGB TIFF in PS.
So there’s must be some decent output functionally and options behind the hood .

I’d be quite happy with a 8bit and 16bit TIFF (adobe RGB) options to save to be addded in to the save menu options.

55 Messages

 • 

1.5K Points

4 y ago

This reply was created from a merged topic originally titled Can’t export in a different format other than JPEG.

It seems that Lightroom mobile and CC desktop (new) can’t export to anything better than a lossy 8bit jpeg. This seems insane to me, especially for more advanced workflows which involve editing in other applications.

My usecase: initial RAW adjustments in Lr mobile, then continue working in Affinity Photo on an iPad. Currently this transfer to another application is lossy.

But no matter what other third party application I’d choose, or even if I just wanted to simply save an image, something better than JPEG is definitely required in many situations. I cannot understand the reasoning behind this limitation.

14 Messages

 • 

312 Points

4 y ago

+1 to getting more export options - I would particularly like to be able to choose filename, and JPG quality / compression level

6 Messages

 • 

130 Points

4 y ago

The ability to export to a lossless format such as tiff (or alternatively a very high quality jpeg) is urgently needed to enable proper to editing in other apps. Ability to specify parameters such as dpi is also required (as per OP original idea). This is basic stuff Adobe!!

2 Messages

 • 

122 Points

3 y ago

This reply was created from a merged topic originally titled Cannot export full res photos uploaded to Lightroom mobile directly to iPad.

Why can I not save a full size jpeg directly from a raw photo I put on my iPad with an sd card reader? The maximum jpeg size Lightroom mobile can save is 8bit 2560 x 1707 @ 72 dpi. On desktop/ classic Lightroom I can export a 16 bit 6720 x 4480 @ 600 dpi. What’s the point of Lightroom cc when I can’t save a full res image?

4 Messages

 • 

272 Points

3 y ago

This reply was created from a merged topic originally titled Ability to choose my export size, quality and format in lightroom mobile.

I want to be able to choose my file size, quality and format, I work for a sports photo Agency and they ask me for the file in a certain size and ppi but Lightroom mobile only gave the option of small size 2048px, and max available..

29 Messages

 • 

648 Points

3 y ago

I agree. We need better export options in Lightroom cc and mobile

2 Messages

 • 

130 Points

3 y ago

This reply was created from a merged topic originally titled Lightroom Mobile: Resize images in the app.

I am looking to download images from Lightroom phone app that are a 4:5 ratio and sized 1080px to the short edge to may phone so i can use for Instagram.

1 Message

 • 

100 Points

3 y ago

Add my vote to this issue.  I would prefer using LR mobile on the iPad Pro as my primary editing app but I keep having to return to my Macbook Pro to do any exports or to edit an image in another program.  I would like to see LR Mobile for iPad export at the full resolution of the RAW image to at least JPEG, TIFF, and PNG formats.  Thanks.

55 Messages

 • 

1.5K Points

3 y ago

I have a sneaky suspicion that saying things like "we need lossless export to continue editing in Affinity Photo on iPad" is only going to make things worse, and possibly one of the reasons why we don't have this obviously important feature in the first place. It might be in Adobe's business interest to prevent us from using competitor products, and lock us in the ecosystem. For example, Lr mobile has "Edit in Photoshop Fix", but no "Export with options". Similarly, Lr CC desktop can export as a 16bit TIFF to Photoshop, but nothing else.

Here's hoping I'm wrong.