Skip to main content
Known Participant
January 19, 2012
Open for Voting

P: Support Common Image Formats (EPS, GIF, PDF, BMP etc.)

  • January 19, 2012
  • 275 replies
  • 9772 views

Feature request: Please add Lightroom support for common Adobe publishing and Web image formats, such as EPS, AI, PDF, GIF, and PNG.

Many of us use Lightroom to manage client images in NEF, JPG, PSD and other formats. But the clients' associated images, which are used on their Websites and in their logos and publications, are invisible to Lightroom. If Adobe Bridge can display these other image formats, why can't Lightroom?

Even if Lightroom did not provide direct editing support for these other image formats, it would still be extremely useful if Lightroom could catalog and display them.

It would also elevate Lightroom from being "just" a photo editor into the realm of being a true Digital Asset Manager (DAM). Now that Lightroom includes basic video support - isn't it time to support all the common image formats that our other CS applications use?

Please vote for, as well as reply to, this request if you would also like to see Lightroom support these additional common image formats...

275 replies

Participating Frequently
May 3, 2012
I would like LR to behave with unsupported formats
just as it did with video files :
Insert a placeholder in the catalog and redirect to
"associated" program on access.
Raffisys
Known Participant
May 3, 2012
Ok, lets make a LR(standard, and LRPro. standard the way it is...Pro would have LRLibrary, and Dev as 2 apps that work together yet are individual....Much like ACR/PS
Inspiring
May 3, 2012
Oh, are you saying you want to be able to buy each module separately? Given LR's relatively low cost already, what good would that do?
Inspiring
May 3, 2012
I don't understand what you are talking about.

I'm a user. I use Lightroom. I don't own or use Bridge or Photoshop. That's why I don't want Lightroom "stripped down".
Raffisys
Known Participant
May 3, 2012
Lee Jay, You speak from the business model mindset that each subgroup being its own business entity. And you'd do ALL possible to protect it. While that may work for your departments numbers and statistic for what it is planned out to do... It doesn't translate to users! Very loyal, long time vested users... authoritative users in the industry, trend setters, teachers. NOR does it translate to Adobe as a whole. Just look at the Recent Activity topics, and the numbers. This is HIGH on the list. (Besides new users still learning how to remove a background in PS). You being vehemently opposed is stuck in the box thinking. I'm sorry. if its not your way its the highway...and that's just not good business practice. But what can we mere mortals do? sit on hands and hope it sees a financial stream and benifit for this...but you'd have to look past the 1-2 year forecast on your charts.
Raffisys
Known Participant
May 3, 2012
On that note...WHY in the world would we have different color coding, Rating and metadata standards across viewers...WHY shouldn't I see what I rated X photo in ACDSee as I rated it in LR? Same with my Metadata info. Just no excuse for this type of un-professionalism.
Raffisys
Known Participant
May 3, 2012
I totally agree, and have mentioned...Why not make a Raw Dev viewer?!! Have the DAManager read the preivew with the recipe used in LR or Capture One, or other developers ...And I don't mean this as a DNG solution. there are reasons not to us DNG. The developer makes a preview file in sidecar or someplace. Other viewers should be able to see this. period. This is 2 years nowI have been asking..I guess after buying over 5 pieces of software that SHOULD work somehow...they all lack this...COORDINATION as ummm, the sanscript name guy put it above. Its almost as bad if not worse in ways than the construction industry!
Raffisys
Known Participant
May 3, 2012
To have a proper image manager. besides it would only be in the marketablility.

The interface would be the same, It would act as a module .

example.

"LR" is open..
click Develop Tab, and pops up the installed Develop module.
(the result is as we see in LR4).
Inspiring
May 3, 2012
"I would expect to strip down LR to a DEV app only program. "

I would be vehemently opposed to that, and I don't see why you'd be interested in that.
Raffisys
Known Participant
May 3, 2012
I have gone and removed all the files it makes the 2 cache files in each folder and left it at that. ACDSee is much better at this, as it the Batch Resize tool alone , other than Batch Export is leaps ahead.