Skip to main content
Adobe Photoshop Family

Champion

 • 

5.1K Messages

 • 

92.8K Points

Tue, Apr 28, 2015 3:20 AM

Solved

Lightroom CC: JPEG format tripping up other programs

Lightroom CC writes JPEGs in an atypical layout that trips up other programs. While they appear to be strictly conforming to industry standards, the unusual layout has caused problems for at least two users: one who had problems uploading photos to real-estate services, and another whose own software tripped over the layout.

LR writes the APP1 header as: TIFF header, 114 unused bytes, ExifIFD, IFD1, IFD0. Whereas Photoshop CC uses a more traditional layout: TIFF header, no unused bytes, IFD0, ExifIFD, IFD1. Here's an Exiftool dump of the beginning of a LR JPEG:

And here's a dump of the beginning of a Photoshop JPEG:

I've tested LR JPEGs with 12 Mac and Windows programs and 2 online services, all of which read them just fine:

Mac: Preview, Photoshop CC 2014, ColorSync Utility, Firefox, Chrome, Lattice, Paintbrush, Safari, Word
Windows 8.1: File Explorer Preview, Irfanview, Paint, Windows Photo Viewer
Online services: Flickr, Zenfolio

Even though LR's JPEGs may be strictly conforming, if it wrote the JPEGs without the unused header bytes and it put IFD0 immediately after the TIFF header, as Photoshop does, then there would be fewer problems with other programs choking on LR's JPEGs.

Responses

Official Solution

Employee

 • 

474 Messages

 • 

10.7K Points

5 years ago

This has been fixed in Lightroom 6.2, which is available today.

Thanks,
Ben

Champion

 • 

5.1K Messages

 • 

92.8K Points

5 years ago

Also, I seem to recall that years ago, LR 4 Beta had a similar issue, and the final release changed the layouts of JPEGs to be more traditional.

427 Messages

 • 

7.7K Points

You are right - but I think it was LR 5 beta (or perhaps both?)

115 Messages

 • 

1.6K Points

I checked my email, and yes indeed it was the LR 5 beta. Unfortunately, Adobe has restricted access to the beta discussion forum, but one of the emails contains a link to a JPEG exported by LR 5 beta showing the exact same atypical layout. One of the users affected was complaining about Wordpress choking on LR 5 Beta JPEGs:

________________________________________
From: Les Bessant2 [mailto:forums_noreply@adobe.com]
Sent: Tuesday, May 14, 2013 7:23 AM
To: John R. Ellis
Subject: [Photoshop Lightroom 5] Lightroom 5 exported images and EXIF information, Camera Make points to keywords instead

Re: Lightroom 5 exported images and EXIF information, Camera Make points to keywords instead
created by Les Bessant2 in Photoshop Lightroom 5 - View the full discussion

Thanks for following this up. This is a sample image exported from LR5:

https://www.dropbox.com/s/3sqj3nr66rg...

10 Messages

 • 

238 Points

5 years ago

I've encountered the very same issue: I publish a photo to Picasaweb/Google+ and the metadata isn't displayed. Been doing this for years via LR and it's always worked perfectly - stopped working as soon as I started using LR CC.

No metadata displayed in other applications is a BIG issue for me. The bugs are stacking up...

10 Messages

 • 

238 Points

5 years ago

I just did some testing: if I use an exported JPEG created by LR CC or PS CC 2014 (so ACR 9) then the metadata seems to work OK and is displayed in Google+ as it should be. However, if I use a publish service then it still fails to display the camera metadata.

So what gives? Bug with the publish services?

Champion

 • 

5.1K Messages

 • 

92.8K Points

Which publish service/plugin are you using?

10 Messages

 • 

238 Points

Jeffrey Friedl's "Export to PicasaWeb" plugin.

115 Messages

 • 

1.6K Points

Unfortunately, I'm not able to reproduce the problem using that plugin, on either Mac or Windows. It would have been nice to narrow down the problem and confirm whether or not it is caused by the atypical JPEG format.

115 Messages

 • 

1.6K Points

This problem with Picasa is caused by the XMP bug: http://feedback.photoshop.com/photosh....

115 Messages

 • 

1.6K Points

5 years ago

The problem seems to strike TIFF files as well (which use the same representation of metadata). In this thread:

https://forums.adobe.com/message/7493633

a user reports that HP MediaBin (HP's enterprise digital-asset management product) is not able to display the metadata of TIFFs exported from LR 6.

115 Messages

 • 

1.6K Points

5 years ago

LR 6 can write invalid XMP metadata (a true bug), as described here: http://feedback.photoshop.com/photosh...

To distinguish that bug from the issue here, you'll have to use a photo with and without a large number of develop settings.

115 Messages

 • 

1.6K Points

5 years ago

To work around the problem described here, you can use the Run Any Command plugin: http://regex.info/blog/lightroom-good...

Use this command line in the Command To Execute box of the Run Any Command post-process action:

exiftool -all= -tagsfromfile @ -all:all -unsafe "{FILE}"

This idiom deletes all of the existing metadata from the image and rewrites it from scratch using a more typical layout that doesn't confuse software that doesn't strictly obey the industry standards. Make sure you have Exiftool version 9.94 or later -- earlier versions would choke on LR images containing large numbers of brush strokes from the adjustment brush.

115 Messages

 • 

1.6K Points

That command line should have the "-m" option to handle XMP metadata with large numbers of brush strokes:

exiftool -m -all= -tagsfromfile @ -all:all -unsafe "{FILE}"

115 Messages

 • 

1.6K Points

The maintainer of Exiftool pointed out the command line should be:

exiftool -m -all= -tagsfromfile @ -all:all -icc_profile -unsafe "{FILE}"

Champion

 • 

5.1K Messages

 • 

92.8K Points

The latest version of the command line:

exiftool -m -all= -tagsfromfile @ -all:all -icc_profile -unsafe -overwrite_original "{FILE}"

This will avoid creating backup files of the originals, which aren't needed in this case.

115 Messages

 • 

1.6K Points

5 years ago

PHP's exif_read_data() appears to be incompatible with LR 6 JPEGs. PHP, of course, powers a huge number of Web sites. See this thread: https://forums.adobe.com/thread/1835290

115 Messages

 • 

1.6K Points

That user was using PHP 5.6.

7 Messages

 • 

100 Points

I'm using 5.6.8 and since upgrade to LR6 my EXIFs are messed up on my site!

4 Messages

 • 

110 Points

5 years ago

Yes indeed, we use Lightroom 6.01 to export our photos as JPEG for Piwigo under PHP 5.6. Und here you can see http://s.edv-tipp.de/fpvth that

COMPUTED.Copyright: efan Uchrin, (C) by St
COMPUTED.Copyright.Photographer: efan Uchrin
COMPUTED.Copyright.Editor: (C) by St

are broken. OK, we go back to LR 5.7.1 and wait for a better LR 6!

12 Messages

 • 

200 Points

5 years ago

Interesting. It seems that the unused bytes are an aborted attempt at IFD0. It contains most of the information from IFD0, except for the orientation (in my sample), then IFD0 is rewritten at the end of the EXIF APP1 segment.

115 Messages

 • 

1.6K Points

5 years ago

Another LR user can't upload LR 6 JPEGs to his client's Web site: https://forums.adobe.com/thread/1842441

427 Messages

 • 

7.7K Points

5 years ago

This seems to look exactly like a similar problem some time ago in Lightroom 5 beta.

Champion

 • 

5.1K Messages

 • 

92.8K Points

5 years ago

Dave Palmetto reports that the JPEGrescan plugin also works around the problem:

http://www.capturemonkey.com/lrjpegre...

https://forums.adobe.com/message/7540...

You need to set the Strip Metadata option in the plugin, so this solution is only useful for those, like Dave, who were uploading to sites that choked on LR 6's JPEGs and don't care about transmitting the metadata.

1 Message

 • 

60 Points

5 years ago

I'm the user who had the problem John R Ellis is reporting on May 13, 2015. When I switched from LR-5.7 to LR-CC, my jpgs began showing up very blurry after being uploaded into my client's reporting software. Apparently the client's report software that worked fine with my LR-5.7 jpgs was ignoring the full uploaded resolution from LR-CC jpgs, and instead magnifying the embedded thumbnail. This produced a low-resolution image that appeared out of focus. This is a high-volume client with multiple uploads daily and hundreds of photos every month, so a reliable, clerically simple solution that required minimal additional labor was needed.

Due to the assistance of the LR/PS/CC community, I can report four workarounds:

1. Export TIF files. For my user reports, these worked fine but of course were much larger than the JPEG files I had been using.

2. Use the Lightroom Web module to export, thereby producing classic jpgs in the "Large" folder. The jpgs created this way do not have the problem with mis-interpretation by my client's web reporting system. The disadvantage to this is that a multitude of unnecessary files are also created every time the jpg is exported.

3. Use the Run Any Command plug-in to execute an exiftool command line to edit the metadata back to classic style. The first command line I used created a duplicate copy of the original jpg with a ".original_jpg" suffix, but I am advised that using the command line

exiftool -m -all= -tagsfromfile @ -all:all -icc_profile -unsafe -overwrite_original "{FILE}"

would eliminate this unnecessary duplicate file, leaving only the LR-5.7-compliant jpg. This works but requires installing two pieces of software (exiftool and Run Any Command), plus having some expertise with scripting. On the plus side, this can be easily added to an export preset so it's very set-it-and-forget-it.

4. Use the JPEGrescan plugin. This requires installing only one piece of code, the plugin itself. Its disadvantages are that all metadata is stripped (not a concern in my situation) and there is a quirky pop-up every time the plug-in runs. This can also be included within an export preset.

I would like to see Adobe provide an export option that supports exporting in the "classic" format used by LR-5.7.

Champion

 • 

5.1K Messages

 • 

92.8K Points

5 years ago

Here's another person whose Android app(s) on a Sony Xperia phone and tablet can't read metadata in LR-exported JPEGs:

https://forums.adobe.com/message/7544...