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

Known Participant
May 5, 2014
Precisely. If Photoshop can do it, so can Lightroom. Adobe already has all the code they need to implement extra file formats, which includes non-maximized PSD, as well as several oddballs.

The only challenge would be animated GIF and APNG, since those files are "video" and picture at the same time.

I'm not so sure about vector format, though. Lightroom works on pixels, not vectors.
Known Participant
May 5, 2014
Thank you, Kim, for agreeing that Lightroom needs expanded image format support.

...pt
Participating Frequently
May 5, 2014
The need to at least acknowledge most common formats in the catalog is blindingly obvious. LR's catalog is used by many as the sole source of information about our images, and that includes EXIF, tags, location and so on. Only supporting the easy formats makes sense only to those who might not want to poison the "purity" of their product philosophy. But the real world demands solutions that work, and don't hide data.
Raffisys
Known Participant
November 11, 2013
I wish the Library section worked like a regular browser, and users can manually add content they want in the catalog. This would help me see files that are new from other apps. Sync Folders is when you know there is something in it. This of course would be most useful when other image formats are visible.
Legend
November 8, 2013
Inspiring
November 8, 2013
At least it would mean that we don't have to surrender to *only* Adobe's mercy when asking for new features. This is very important with such a complex product.
Inspiring
November 8, 2013
Related to this: I also find it rather weird that in order to catalog PSD files, they need to be stored with "maximum compatibility" switched on. That feels like one Adobe product has trouble reading another Adobe product's file formats. This needs fixing too.
Inspiring
November 7, 2013


Allow cataloging GIF files in the next Lightroom, please. GIFs are used for animation, and folks who want to create those neat anigifs from pieces of video, can keep those GIFs in the catalog using this feature.

Lightroom would have to support *animated* GIF as well as non-animated. Animation is technically already supported in the form of video support.
Known Participant
July 11, 2013
I agree it is a non-trivial undertaking. In fact, I suspect it would be more difficult than anything else in LR development. My experience using javascipt with photoshop and bridge shows Adobe is not that good at engineering and supporting the SDK. A good example of this is the bridge SDK, where the ScriptUI is riddled with bugs since CS6 and has not been fixed even though it works in photoshop and the ESTK.

The LR SDK has been asked for before (several times)... and sort of promised at the beginning of LR. Personally I think Adobe should concentrate on the develop module, core library capabilities and a robust SDK, instead of creating almost good enough modules like mapping and books.
Known Participant
July 11, 2013
That's a fine idea, and one that could lead to many new capabilities, including better image format support. However, as someone who is involved with an SDK development team (I write the documentation), it is not a trivial undertaking. But I'd love to see Adobe pursue this. Though it is related to this topic, perhaps you should start a new feature request for a robust Lightroom SDK?