Jeffrey’s Lightroom Goodies (Plugins and Tools)

This page lists my Lightroom-related plugins and posts.

Note: everything here is for Adobe's venerable photo-workflow app started in 2006, named at various times “Lightroom”, “Lightroom CC”, and now (as of Oct 2017) “Lightroom Classic” or perhaps “Lr7”.

Nothing here applies to Adobe's new desktop app, debuted in Oct 2017 and given the old app's “Lightroom CC” name.


Plugins for Lightroom:   (All-Plugin Update Log via RSS )

Export & Publish:

Export Plugins:

Other Publish Plugins:

Export Add-Ons:

Geoencoding Plugins:

Utility Plugins:

Plugin-related Info:

Tools for Lightroom:

Etc...

Old Plugin Resources for Lightroom 1 (no longer supported)

Other notable sources of Lightroom plugins include:


The 30 most-recent comments (out of 484; see all), most recent last...

Have you given any consideration of support for ZenPhoto?

thanks for what you do!

No, I’ve never heard of them. —Jeffrey

— comment by Loyd Craft on February 6th, 2017 at 4:42am JST (8 months, 17 days ago) comment permalink

I have Lightroom cc 6.5

Do you have a plugin or solution for the Nikon D500 without upgrading to LR 6.7 ?

Thanks !

I perhaps don’t understand the question, but if you’re looking to get raw photos from an unsupported camera into an old version of Lightroom, you can usually use Adobe’s free DNG converter to make DNGs that you then import. —Jeffrey

— comment by WeBr on February 7th, 2017 at 5:30am JST (8 months, 15 days ago) comment permalink

Hello, Wondering if you can offer some advice. I have posted to the Google Photos forum without any replies.

I’m on LR version 6.8 and using plugin jf PicasaWeb

Up until yesterday it was publishing to my google photos account without issue. I have uninstalled and reinstalled the plugin. I have also removed LR preferences and reset.

Here is the screen shot of the error :
Unexpected HTTP status from Google: 501
Update is no longer supported

Thank you for any help in this issue, as I am unable to publish. I would gladly contribute to the plugin, if I can get it to work for me.

Lots of folks are getting this. I think the error message is pretty self evident… Google is shutting PicasaWeb down. But who really knows besides those in the black hole of Google? It’s still working for me at the moment, but many folks are seeing this error. —Jeffrey

— comment by Deborah Hinter on February 8th, 2017 at 12:12pm JST (8 months, 14 days ago) comment permalink

Hi Jeffrey,
Big fan of your Facebook and Zenfolio plugins.

Do you have a plugin or other recommendation for exporting to multiple sizes at once? I have presets, but it’s a little cumbersome to run many export presets for the same photo set.

It looks like Rob Cole’s Export Manager might do this, but unfortunately it’s no longer available.

Unfortunately, it’s not possible to do properly, given the limitations of Lightroom’s plugin infrastructure. A plugin can do a vanilla render, but a plugin doesn’t have the ability to invoke a preset or otherwise do anything more than a vanilla render (e.g. it can’t do a render that involves another plugin, for example). If one just needs multiple sizes of the same image, it’s possible a plugin could make reduced copies of whatever image had been produced by Lightroom, but then you just have these copies sitting around on disk…. that’s fine if that’s all you want, but if you wanted them uploaded by a plugin, you’re out of luck. Adobe could make it all so easy by allowing a plugin to invoke an export preset. Until then, it’s just a huge can of worms that’s not worth the trouble trying to address, I think. )-: —Jeffrey

— comment by Nathan Carter on February 14th, 2017 at 4:04am JST (8 months, 9 days ago) comment permalink

Have you a plug-in to export photos from Lightroom to google photos ?

No, Google has not made an API for third-party apps. —Jeffrey

— comment by Eric Lefebvre on March 1st, 2017 at 6:30am JST (7 months, 21 days ago) comment permalink

Hi Jeffrey,
as with many others I am a big fan and user of some of your plugins (Zenfolio mostly). I am trying to find a plugin for tracking my time spent on the jobs within Lightroom. I cant find it anywhere nor under your plugins. Some sort of punch in punch out either automatic whenever I am working inside a collection or forlder in question. I presume its possible to check the current open folder/collection from the history log. On the other hand if you havent attepted to create such there is a good reason. How do you deal with tracking of your time on the jobs? I do 2 hour photoshoot but it feels like ages sitting behind my computer on selecting / rating / post processing.

Thanks a lot for your time.

A plugin can tell what source is currently selected (e.g. what folder or collection is active), but it can’t tell when work is actually being done. There are a lot of stand-alone time-tracking apps (for both desktop and phone) that cater to this kind of need. —Jeffrey

— comment by Pavel on March 13th, 2017 at 3:33am JST (7 months, 10 days ago) comment permalink

Hi Jeffrey,
At one time Lightroom would put the RAW FILENAME in the metadata. It no longer does that. There was a plug-in that did it for a while, but I don’t know who made it. I’d like to keep the file’s original name in the metadata that gets exported, so if you rename the file, the original .NEF name can be found. Do you have a plug in that does that?
Thanks!
Stan in Boston

You should be able to do this with the Metadata Wrangler —Jeffrey

— comment by stan on April 6th, 2017 at 11:16pm JST (6 months, 16 days ago) comment permalink

Hi Jeff:

I just found out about you, and am hoping you can help. I work for a non profit that cares for the environment, and we have a large collection of images in a Lightroom folder structure of about 75 carefully organized folders and subfolders. I have an exact duplicate structure in Smug Mug, which works quite well for my users. The issue is I have to manually drag and drop every time I add images to a collection, and manually search and republish in Smug Mug every time I make a metadata or develop change to an image. Could you create a “publish all” plugin that would recognize changes in my LR collection, and force them onto the Smug Mug collection and then publish them automatically? I can’t tell you how much time this would save me.

Looking forward to hearing from you-

Alison Taggart-Barone
Photo Editor
Golden Gate National Parks Conservancy

I don’t quite understand everything you’re asking, but my Bag of Goodies plugin includes a publish all feature. —Jeffrey

— comment by Alison Taggart-Barone on April 7th, 2017 at 12:55am JST (6 months, 16 days ago) comment permalink

Thanks for the above answer to my request for putting the file’s original name in the meta data. I can see how I can add it as a keyword., caption, or title areas. But can you tell me a way just to dump it into the RAW DATA box that Photoshop uses in the File Info area, and not in the keyword or areas?
Thanks again!

Sorry, I’m not familiar with Photoshop or what field that might be. I took a look around in my copy of Photoshop and couldn’t find anything appropriate. Maybe save some specific text to that field, load the file into Lightroom, and view with my Metadata Viewer plugin to look for the specific text to see what field it landed in. —Jeffrey

— comment by stan on April 11th, 2017 at 12:41am JST (6 months, 12 days ago) comment permalink

Re: Original File Name.
I dug up an old file, and in Photoshop’s RAW DATA area Lightroom posted the original file name as:
_DSC5737.NEF
Meanwhile Metadata Viewer calls it “Filename.”
I guess what I’m asking for is to just have the original filename exported, which Lightroom doesn’t currently do, but I don’t see a field named “Filename” in Metadata Wrangler to turn on. So what am I missing?
Thanks for your patience.

It may be something that Photoshop keeps track up, but as far as I know it’s not something that Lightroom keeps track of. If you change the name of a file, the original name is lost forever. As far as I know. —Jeffrey

— comment by stan on April 11th, 2017 at 10:59am JST (6 months, 11 days ago) comment permalink

Hi Jeff,

Wondering if you have a tool/utility that would let me update custom metadata fields using tokens? These are not the standard IPTC fields I want to change/set but ones added to Lr by third-party publish plug-ins. Format.com has a publish plug-in that adds two fields ‘Caption’ and ‘Alt-Text’. I want to populate these with the ‘standard’ Title and Headline fields before I publish.

Unfortunately, Lightroom prohibits any plugin but the owner plugin from updating a plugin’s custom metadata, so it’d have to be something they support directly. —Jeffrey

— comment by Mark on April 19th, 2017 at 7:41am JST (6 months, 3 days ago) comment permalink

Hello again:

I’m still hoping you saw my last message about a plug in that will automatically match my LR catalog with an identical Smug Mug catalog, and automatically publish to the web.

Thanks!

Alison

I replied the other day via email. In short, it’s exactly what Publish is supposed to do, but Lightroom is full of bugs so it doesn’t always work right. )-: —Jeffrey

— comment by Alison Taggart-Barone on April 21st, 2017 at 6:43am JST (6 months, 1 day ago) comment permalink

Hi Jeffery,

I use your plug-ins all the time thank you for the excellent tools. Recently I have been experiencing a problem with window focus specifically when using the Plug-in Manager to download and install updates and when using your Geoencoding plug with the One-By-One dialog. In both cases when I click the button to install or to apply location data when the operation is completed the window is popped behind the main window and you cannot even bring it forward by clicking on the title bar. The I have to slide the main window out of the way to get to the button to complete the action.

This has been happening for me for a while. I am on MacOS 10.12.4 and LR 2017.9

tks, louie

Unfortunately, I don’t have much hope here… Lightroom (or the OS) handle that and don’t give the plugin any say in the matter. It usually works, but sometimes I have to do what you do as well. I don’t know a way around it. )-: —Jeffrey

— comment by Louie on April 30th, 2017 at 11:42pm JST (5 months, 22 days ago) comment permalink

Hello Jeffrey,

I’m writing from Germany. After upgrading the “Geoencoding Support” plugin today it is deactivated due to an error “Could not find namespace: LrApplicationView”. I’m using Lightroom 3.6 64-bit on Windows 8.1. Following the steps in FAQ (I get “An error occurred while reading the schema …) didn’t help.

Best regards,
Theo

Ooops, sorry, sloppiness on my part. I’ve just released an update that should fix it. —Jeffrey

— comment by Theo Ingenerf on May 6th, 2017 at 5:00am JST (5 months, 17 days ago) comment permalink

I know others have asked about an instagram plugin and it’s not allowed, etc, etc. I recently stumbled on something called LRInstagram. Works well enough but not nearly so slick as it would if it had all your bells and whistles. I had been using gramblr to upload from my computer and it worked nicely except it was completely unintegrated with LR so I found it frustrating.

So, if LRInstagram (https://www.lrinstagram.com) and gramblr (http://gramblr.com) are able to do this, could you not consider it for your suite?

No, sorry. It’s enough work to keep a plugin going with the support of the remote provider; doing it expressly against their wishes and against the terms of their service is both not my style, nor my idea of fun. Sorry. —Jeffrey

— comment by Larry Williamson on May 7th, 2017 at 10:07pm JST (5 months, 15 days ago) comment permalink

Hi Jeffrey,

Have you written a LR keyword management program that would allow editing in a larger window/panel than LR affords? My keywords are a CF, and reorganizing them directly in LR is an onerous task at best. I understand that it is possible to edit by exporting as a text file and then reimporting, but that strikes me as a formula ripe for disaster.

Best,
Jerry (in torrid Tucson, AZ)

No, I’ve not done much with keywords, sorry. Perhaps check out Jerry Cagle on May 15th, 2017 at 12:30am JST (5 months, 8 days ago) comment permalink

Hi Jeffrey,

Thank you for your plugins, very helpful on many fronts.

I am trying to set up a shortcut for “View selected locations as KML in Google Earth”, have been trying though the normal route of setting it up through the zprefercens on my mac to no avail. Any tips? Directions for this?

Many thanks

Jacob

Lightroom prefixes plugin commands with three spaces, so be sure to include those in the System Preferences dialog when setting up the shortcut. —Jeffrey

— comment by Jacob McIntyre on June 23rd, 2017 at 9:08pm JST (3 months, 29 days ago) comment permalink

Hi – I’m from the Margaret River region in West Australia.

I saw an earlier comment from Manuel asking about exporting face frame images from Lightroom. I have (badly) written a python script that does that using Imagemagick and Exiftool. I have looked into writing a LR plugin to do this but until the LR SDK supports accessing the associated metadata it would be difficult. The script reads the xmp files in a directory and outputs a batch file that uses Imagemagick and Exiftool to crop the face regions found from the images and place the results (as small jpg files) in a “faces” subdirectory.

In order to use my Python script it is necessary to install python 2.7 with LXML installed. You also need ImageNagick and Exiftool installed. So you need some computing skills. There are a few “gotchas” such as LR not writing to XMP files for jpg files so the originals must be raw files (or use Exiftool to fix this).

If anyone wants to do this I am happy to make it available. If there is any interest I will make the relevant files available somehow, and some brief documentation on how to use it.

— comment by Ian Wiese on July 16th, 2017 at 9:10am JST (3 months, 6 days ago) comment permalink

Jeffrey,

I just upgraded my PC and tried to reinstall your Lightroom Collection Publisher plugin, which I’ve been using for years.

However, Norton AV on my new PC now quarantines cygwin.dll and hence the plugin fails.

Any suggestions?

Sigh, that dll file has not changed in years, but they still come around every so often to flag it. Please send them a copy (or point them at the plugin) and ask them to investigate, and, ultimately, stop flagging it. Thanks. —Jeffrey

— comment by Alan on August 3rd, 2017 at 1:50am JST (2 months, 20 days ago) comment permalink

Hy

I dont know where to ask this questions, so feel free to kill the comment. I love your plug-ins and I sed them since a long time (..and I regularly donate as well 😉 ). I am using the data explorer a lot recently, is there a option to export out all the fields, or at least a selection of fields, to text/spreadsheet/… currently I am always exporting one property and then match the database via filename.

thx

Data Explorer works with just one field at a time, sorry. You might consider the Lr/Transporter plugin to export a series of fields to a spreadsheet. —Jeffrey

— comment by Diruas on August 10th, 2017 at 2:47pm JST (2 months, 12 days ago) comment permalink

Hi Jeffrey,
I dont know if my question here is appropriate, so feel free to hide the comment if needed.

Since a while, when I backup my Lightroom Catalog I am getting this message: “An internal error has occurred: Attempt to make a request on a closed server.”
Sometimes when these messages appear, after pressing OK through all of them the backup seems to complete without errors and Lightroom quits. Some other times I had to revert to task manager to kill lightroom without completing the backup process.

Now the point is that it ***seems*** that disabling ALL plugins (not only yours) solves the problem, but I am not able to identify if the error is really related to one or more plug-in(s) or getting lightroom working when plugins are disabled it’s just a coincidence.

Could you be so kind to advise if in your opinion this kind of errors could be in some way related to plug-in(s) or I’m totally wrong and need to investigate in other directions?

Thanks a lot in advance
Paolo – Milano – Italy

I’ve never seen this kind of error, though I know it’s deeply related to Lightroom’s internal communication. As best I can guess, some part of Lightroom is trying to update the catalog after some other part of Lightroom has shut the catalog down. I can’t guess whether it’s related to a plugin, but if it is, I’d think it’s a Lightroom bug. Your best bet, I suppose, is to report it to Adobe. —Jeffrey

— comment by Paolo on August 10th, 2017 at 6:03pm JST (2 months, 12 days ago) comment permalink

Do you have / Are you planning a plug-in to export specifically to Google Photos now that PicasaWeb is closed?

Neither my Photo Upload nor your jf-PicasaWeb will export to a new album on Google Photos, they both merely offer local folders as export locations, even when “Choose folder later” is selected.

Currently I have to export to a local disk and use Google Photos to upload from there.

Thanks
(London, UK)

Google doesn’t offer an API to allow third-party apps to upload to Google Photos. It’s only been six years, so maybe they just haven’t gotten around to it yet. /-: —Jeffrey

— comment by Keith on August 16th, 2017 at 5:56am JST (2 months, 6 days ago) comment permalink

Hi Jeffrey,

I’ve used your plugins for years -they’re fabulous. Thanks for all that work. I have been searching for this answer for weeks . I have a new PC. Moved all the photos and LR Catalogue to the new HD. But none of the Publish Collections came along. I use them extensively and have for over 10 years so the thought of recreating them and trying to connect up what I’ve published where is a nightmare. I can’t believe this information isn’t somewhere in the catalog, or a config file somewhere in the Lightroom folders somewhere. I thought if anyone would know, it would be you.

Thanks for you help.

Jeri
Mill Valley, CA

It’s all in the catalog file (the “*.lrcat” file). If you moved that actual file to the new machine, it will all be there. You’ll have to re-add each plugin via the Plugin Manager to ungray the Publish Services and actually use them, though. —Jeffrey

— comment by Jeri Mearns on September 1st, 2017 at 1:07pm JST (1 month, 21 days ago) comment permalink

Hi Jeffrey, for me, the number one missing item in Lightroom is the ability to display the Canon Focal Points. I am a Canon shooter and the only way to find out where I pointed the focus is to view the image in the Canon DPP program. In DPP the focal points are displayed as red dots. Obviously the focal point position info is stored somewhere in the Canon Raw proprietary image but I have not found any LR lug-in that would allow to view them. Do you know if anyone has come up with a LR solution?
Thanks
Franz

I’ve no personal experience with it, but this plugin seems to be exactly what you’re looking for. —Jeffrey

— comment by Franz Zihlmann on September 16th, 2017 at 12:00pm JST (1 month, 6 days ago) comment permalink

Thank you Jeffrey for pointing me to the “Show Focus Points” LR Plug-In. I installed the plug-in and it works great. Btw, the Author of “show focus points” gives you credit for helping creating this product.

— comment by Franz Zihlmann on September 20th, 2017 at 3:50am JST (1 month, 3 days ago) comment permalink

Hi Jeff, do you have a plugin or workaround that will work with ProSelect by Time Exposure. I’m trying to get purchased image numbers a client selects and have those show up in Lightroom so I can flag or star them for album building, etc. Thanks for all you do.

I don’t think so, no, since I’ve never heard of it, sorry. —Jeffrey

— comment by John Naccarato on September 23rd, 2017 at 2:43pm JST (4 weeks, 1 day ago) comment permalink

Hi Jeffrey,
After a reinstall of Lightroom CC and moving some folders my Metadata Viewer plugin called for registration again. I use this plugin quite often, so I happily made a $5 donation today, Oct 2/17. The confirmation number on the PayPal receipt was rejected. After a number of tries and rejections, I dug out a PayPal receipt from July 10/16. Lightroom was happy to accept it.

Odd. Or not?

Thanks for all of the interesting work that you do.

John Sanders
Vancouver, BC

Thanks for your kind gift(!) Did the new registration number perhaps end with three digits instead of four? PayPal has a bug whereby if the first digit is a zero, they omit it and shift everything over, so it ends up in a “####-####-###” pattern. It’s a really stupid bug that I reported a year ago. Since it seems that they won’t fix it, I’m in the process of updating my plugins to handle the broken code, but I haven’t pushed them all out yet. —Jeffrey

— comment by John Sanders on October 3rd, 2017 at 1:54pm JST (2 weeks, 5 days ago) comment permalink

I just re-donated due to the Lr7 upgrade, and the confirmation number I got from PayPal is not in the pattern you give in your previous reply. It looks like this:

91727117TN0449439

I’ve changed a few digits to other digits in my example. I’m in the US. The same number appears twice in the email from PayPal, identified as both a “Confirmation number” and a “Transaction ID.”

That seems like a valid pattern… they sometimes give a “transaction id” that looks like that, and sometimes digits only in hyphen-separated groups of four. —Jeffrey

— comment by mph on October 19th, 2017 at 8:49am JST (3 days, 8 hours ago) comment permalink

Thanks for your quick reply; when I enter a code in the jf Tumblr plugin in Lr 7, I get a “bad hash” error as shown here:

https://imgur.com/xVPxavb

I have Tumblr plugin version 20171019.66.

Sorry about that, there’s one update since that fixes this bug. —Jeffrey

— comment by mph on October 19th, 2017 at 9:24am JST (3 days, 8 hours ago) comment permalink

Hi Jeffrey
Above you say “Nothing here applies to Adobe’s new desktop app, debuted in Oct 2017 and given the old app’s “Lightroom CC” name”. Do you mean “cloud app” rather than “desktop app”?

No, I mean “desktop app”. Adobe now has two almost-unrelated desktop (MacOS/Windows) apps with the name “Lightroom”. One is the venerable app now in its 7th major release, now called “Lightroom Classic CC”. This desktop app can upload your images to the “Lightroom Cloud” if you like, but the master copy of images are what you have stored locally. The other desktop app is one that keeps the master copy of the image in Lightroom Cloud, and is more integrated with that cloud and the other interfaces to it (mobile apps and Lightroom Web). This new desktop app used to have the code name “Nimbus”, but has now been given the name “Adobe Lightroom CC”, which is what the first desktop app had been called. It’s confusing. —Jeffrey

— comment by Rob Fairhead on October 20th, 2017 at 9:39pm JST (1 day, 19 hours ago) comment permalink
Leave a comment...

Please do not report bugs or other comments related to my plugins here. Please do those on the appropriate per-plugin page (linked from my Lightroom Goodies page).


All comments are invisible to others until Jeffrey approves them.

Please mention what part of the world you're writing from, if you don't mind. It's always interesting to see where people are visiting from.


You can use basic HTML; be sure to close tags properly.

Subscribe without commenting