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 528; see all), most recent last...

Hi. I have many presets. When I work on one image, I’d love to see a grid of what all these presets would look like, instead of going through them one by one. Is there any way that you know of to do this? Thanks for your time.

No, sorry. It’s a common request, but Lightroom doesn’t allow for it. —Jeffrey

— comment by Ian Douglas on December 26th, 2017 at 7:20am JST (11 months, 25 days ago) comment permalink

Can you create a plugin that applies the new Auto feature (process version 4) to all selected images?

I can’t, because there are internal problems if the plugin tries to apply the new auto. But you can apply Auto from grid, to all the selected images. —Jeffrey

— comment by Mark on January 12th, 2018 at 2:41am JST (11 months, 8 days ago) comment permalink

Hi Jeffrey,
some time ago I asked your opinion regarding an error message shown when shutting down LR with the backup enabled: “Attempt to make a request on a closed server.”

You supposed it could be related to a bug of LR and this seems confirmed. Here the information posted by John Ellis on several threads :

“This is caused by plugins running tasks in background tripping over a Lightroom bug.  I’ve changed one of my plugins (Any Source) to work around the bug, but another still needs the workaround (Any Tag). The error message is harmless and can be ignored.

You can see if this is causing your instance of the error message quick enough: Go to File > Plug-in Manager and disable all plugins. Exit LR, asking it to do a backup.  If the error doesn’t appear, then one of the plugins is triggering the bug. You can re-enable each plugin in turn to find out which one. 

Send the plug-in developer a link to this post: https://forums.adobe.com/thread/2440474“

I hope this could help others experiencing the same problem. The message is harmless but really annoying since you need to click OK multiple times (once for each plug-in) in order to complete the backup.

I added this comment here also because I suppose your “Photo safe” plug-in could be affected by the same lightroom bug.

Once again thanks for your time

Paolo – Milano – Italy

It could be the same underlying Lightroom bug, but not exactly the one that John refers to, since none of my plugins use LrShutdownApp. —Jeffrey

— comment by Paolo on January 23rd, 2018 at 7:32am JST (10 months, 28 days ago) comment permalink

Dear Jeffrey,
I am writing from Switzerland.
I am looking for a possibility to search with Data-Explorer in the IPTC-Headliner-field in Lightroom. I can find Headline Lenght and Headline Lenght Count but not Headline. Can you help?
Thank you
Wolfgang

Data Explorer is not really for searching for values within text, it’s for grouping by value (e.g. “find all the ones without a headline”). For searching, try my Extended Search plugin; I’ve just added Headline for you. —Jeffrey

— comment by Wolfgang Frei on February 14th, 2018 at 6:56pm JST (10 months, 5 days ago) comment permalink

Hi, I’m having problems with exporting from Lightroom Classic to Zenfolio, I keep getting the error message “LIghtroom couldn’t render a copy from a master image “Users/Di/Pictures/In the Round/Rotterdam.psd” because it can’t access the file. Perhaps it’s been deleted or is on a disk that’s currently offline”

The image is not offiline, or deleted – it’s in Lightroom, and will export happily to the desktop or any other application. I’ve updated your plugin, but am not seeing any errors in the plugin manager.

I’m also seeing a message to include profiles to include which I’ve never seen before.

Any good ideas?
Thank you

Sounds mysterious…. could you send a plugin log after getting the error? —Jeffrey

— comment by Diane Seddon on March 7th, 2018 at 11:53pm JST (9 months, 12 days ago) comment permalink

Hi Jeffrey, are you thinking to create also presets for lightroom, or you are focusing more on great utilities?

Presets are artistic, so out of my range (except, I guess, for these funky presets). —Jeffrey

— comment by Dumitru on March 26th, 2018 at 8:16am JST (8 months, 25 days ago) comment permalink

I’m looking to update my Jeffrey’s Folder Watch – but Adobe says the plugin doesn’t work in LR7 – I can’t see your replacement – which is the one I should download please

The one linked from the plugin’s home page, which is listed above on this page. —Jeffrey

— comment by Lucy Mandyczewsky on May 5th, 2018 at 11:44am JST (7 months, 15 days ago) comment permalink

I love the Jeffrey’s Folder watch which I currently use, but I’ve just upgraded to LR7 and it doesn’t like it. Have you got an updated version? I can’t see it in your lists…
Lucy from Australia
PS I forgot to tick email and so I’m resorting to checking each day — or writing another comment.

Lightroom’s plugin manager will tell you the home page of a plugin, but anyway, it’s here. —Jeffrey

— comment by Lucy Mandyczewsky on May 7th, 2018 at 12:03pm JST (7 months, 13 days ago) comment permalink

Looks like Google announced a new “library” API for google photos today at their conference, any thoughts on if that would make a Photos plug-in possible?
https://developers.googleblog.com/2018/05/introducing-google-photos-partner.html

Looks promising! I’ll dive into it…. —Jeffrey

— comment by Charlie on May 9th, 2018 at 5:02am JST (7 months, 11 days ago) comment permalink

Hi Jeff,
I’m looking for a plugin that can imprint (during export) some metadata such as shooting time or other. As for the watermark, having freedom to indicate the position, the type of character, the color etc. etc
This exists for the presentation of lightroom but does not exist for the export of the library.
thank you
Marco

The Lr/Mogrify plugin should do exactly what you need. —Jeffrey

— comment by marco on May 16th, 2018 at 6:41am JST (7 months, 4 days ago) comment permalink

Hi there Jeffrey.
Thank you for offering so many usefull tools for Lightroom!
I do timelapse shots alot, and i was wondering if you have a deflicker in your tools or know a way to deflicker timelapse weather in lightroom or premiere.
Thank you & have a good day.

I have no experience in this stuff, but if you want to even out the visual look across frames, would the new “Auto Tone” perhaps do it? —Jeffrey

— comment by Bea on June 11th, 2018 at 2:44am JST (6 months, 9 days ago) comment permalink

Jeffrey
I have been using the jfzenfolio it seems to be slower, I am able to output jpegs and upload them faster to zenfolio, which I really do not want to do. Is there a setting that I am missing or set wrong.

Please let me know

Thanks
Jerry

Yikes, I see now that they announced something a month ago that just took effect, disabling plugin access. I’ll dig in and try to get a new version out soon. —Jeffrey

— comment by Jerry Rizzo on June 12th, 2018 at 4:34am JST (6 months, 8 days ago) comment permalink

This isn’t a bug in your Flickr plug in but I’m having trouble. I bought a new external hard drive and created a new LR catalog for that drive. I then moved all my images over to the new drive and I’m using the new catalog. Everything is fine, but I’ve lost connection to my Flickr images previously uploaded to jf Flickr using the other catalog? Can you help me regain that connection?

It might be easiest if you use your old catalog, but re-point the base folder in the catalog to the new location on your new disk. Then you can just carry on as before. With the new catalog, you can try to associate photos in Lightroom with ones at Flickr (see “File > Plugin Extras > Flickr Extras > Associate), but due to the fragile nature of that, it’ll almost certainly be a frustrating, unsatisfying process with an incomplete result. —Jeffrey

— comment by Roland Penttila on June 14th, 2018 at 2:38am JST (6 months, 6 days ago) comment permalink

Hi – I am hoping you can help me find a LR plugin that will allow an export of IPTC metadata to a CSV file and then after making adjustments (for ex: spell check) import back to LR to update the metadata on the file – I am working in LR CC on a Mac – thanks!

You might look in to Lr/Transporter. —Jeffrey

— comment by Antonina Smith on June 23rd, 2018 at 6:25am JST (5 months, 27 days ago) comment permalink

I’ve been using your plugins for years with Zenfolio and love them. I’m try to upload to Zenfolio and one or two photos upload and then I get a Zenfolio note saying SERVICE UNAVAILABLE. I’ve reloaded your plugin and it still down’t work. Zenfolio said contact you. Help!

Sadly, it’s a problem with Zenfolio’s servers, but they’ve been aggressively antagonistic about it, even going so far as to make a video with worthless suggestions instead of bothering to contact me. It’s surreal and disappointing (and exceedingly frustrating). —Jeffrey

— comment by Stephen Herlihy on June 27th, 2018 at 2:46am JST (5 months, 23 days ago) comment permalink

Hi Jeffrey,

When there is a discrepancy in metadata between disk and catalog, LR notes that difference and allows you to copy the disk metadata to the catalog or vice-versa. But, it does not indicate what that difference is nor does it allow you to pick and choose what metadata to copy.

Do any of your wonderful plugin’s show the metadata difference between what’s on disk vs what’s in the catalog when LR indicates there is a difference? Even better, allow you to pick and choose which metadata fields to transfer (disk to catalog or catalog to disk).

Thanks — Dan

I’m afraid that I don’t have a good solution for you. My Metadata Viewer shows what’s in the file and what’s in Lightroom, but doesn’t highlight the differences. (They’re two almost-unrelated views of the data, and so discerning when data has been changed would require work on a per-camera per-field basis, and even after all that, what’s available to a plugin is not the full set of data, so it would be a half solution anyway.) —Jeffrey

— comment by Dan on September 4th, 2018 at 1:47am JST (3 months, 16 days ago) comment permalink

Hi Jeffrey! I would encourage you to move to another way to pay for your Lightroom Plugins. PayPal is nothing but a frustration. I have been trying to register a plugin for the past half-hour and PayPal just keeps getting stuck mid-transaction and it never goes through. I’ll try later, but this is why I avoid PayPal unless there’s no other option.

Also, at a minimum $1.00 donation (I’m in Canada, maybe that’s why it’s not the $0.01 minimum that you refer to) I suspect they are making more money off my registrations than you are. Major Lightroom updates are more frequent now, and as a result I expect that most people are donating smaller amounts, which means that PayPal is taking a bigger share of the revenue. If you don’t want to move away from PayPal, how about allowing five activations per PayPal transaction so that I could give you a single bigger donation and you’d get most of it?

— comment by Richard Drdul on October 17th, 2018 at 3:34am JST (2 months, 3 days ago) comment permalink

Hi Jeffrey! As a follow-up to my earlier suggestion about moving away from PayPal, you should know that PayPal doesn’t tell people what the minimum donation is unless they try to donate less than the minimum. I only discovered this because I mistyped the amount and one of the three numbers didn’t register, so PayPal thought I was trying to donate less than $1.00. You have added a note on the registration page about the $1.00 minimum, but anyone who donates $1.00 or more won’t know what minimum applies to their donation, and won’t realize how much they’re giving PayPal instead of you. Once I realized what was going on I switched over to sending you money instead of donating, and will do the same in the future. Maybe you should just request that everyone send you money so that you can avoid giving PayPal any more money than necessary.

PayPal takes their same cut regardless of how it’s sent (they take the first 35 cents or so, then a percent of anything beyond that). Whether the original transaction is $.01 or $1, I more or less get nothing, and that’s fine. I don’t pay or gift for all the software I use, either. I do realize that PayPal can be ultra frustrating at times, and that the system I’ve built is pretty kludgy, but it’s what I have, at least for now. Sorry. As I note on the registration page, those who want to register a bunch of plugins can send me a transaction code that’s been used for one plugin, along with their needs, and I can manually permission it for the others. The vast majority of folks who register any plugin just register the one, though. —Jeffrey

— comment by Richard Drdul on October 17th, 2018 at 5:45am JST (2 months, 3 days ago) comment permalink

Hi Jeffrey. Now that I’m not as frustrated, I’ll try, again, to explain the problem I’m having while trying to install your Zenfolio plugin. Thank you for your patience. I deleted all previous files related to the plugin.
1. I downloaded 209181017.315.zip from your site. the “.zip” was not orange.
2. It dowloaded zenfoliojfriedl.lrplugin 1.1mb. It was NOT a zip file!
3. I moved the file to my plugin folder.
4, I opened Lightroom and opened plugin manager
5.I added Zenfolio-jfriedl.lrplugin using plugin manager
6. It says I have the latest version and that it is registered.
7. I go to plugin extras and it only shows “Zenfolio extras”.
8. I’m really confused because the plugin manager says installed and running!!
I tried another plugin (focus points) and it works fine.
I hope this explanation is better than the rambling one I gave you the other day. The comment you didn’t understand was an attempt at humor while I was frustrated. Sorry.
Stan

The surprise in step 2 is because your browser apparently unzipped it for you automatically. Everything else except #8 is as expected. The main work of the plugin is via the Export dialog, or, more commenly, as a Publish Service. See the docs for more info about publish services. —Jeffrey

— comment by Stan Cowen on October 20th, 2018 at 12:28pm JST (2 months ago) comment permalink

Hi Jeffrey, I trust you are well.

I have two queries for you as follows:

1-Collection Publisher Functionality

I have been using Collection Publisher for as long as I can remember, it’s GREAT! However, there is one facility that it lacks that would be epic for me. Presently, on export, one can only choose a single ‘watermark’. I use watermarks to create job specific borders with logos etc. That means having portrait and landscape versions. As Publisher only allows a single watermark, I have to run two copies of CP with identical export parameters in portrait and landscape versions. this is obviously time consuming and process heavy.

Therefore, would it be possible to incorporate a function within the export panel to use landscape and portrait watermarks on a single export? This is something that Printripper can do but I don’t want to include more software into the chain.

2-Automatic printing

Is it possible to include a print command into the export chain on any publisher plug-in?

Thanks again for your excellent work.
Kind regards,
Glenn

Lightroom doesn’t allow for either of these, sorry. You might be able to get Lr/Mogrify to help with the watermarks, but I’m not sure….—Jeffrey

— comment by Glenn Curley on October 20th, 2018 at 5:37pm JST (1 month, 30 days ago) comment permalink

I just installed the latest updates for my Adobe Creative Cloud Photography subscription, including Lightroom Classic CC. After completing the update and launching Lightroom Classic CC, I received several messages warning me to update plugins that are not compatible with Lr8. For example jf Creative Commons, the messages say “The version of the “Creative Commons” plugin you have does not work in Lr8. Please upgrade your copy of the “Creative Commons” plugin to the latest version from Jeffrey’s site.”

The same message is generated for:
jf Facebook (which I understand will no longer work but there doesn’t seem to be a way to delete from LR)
jf Flickr
jf Tumblr
jf Twitter

Are you planning to update these plugins so they will work with Lr8?

Thanks

They were updated on my site the moment Lr8 came out, but you have to actually do the update on your own computer. —Jeffrey

— comment by Gregg Plummer on October 24th, 2018 at 4:40am JST (1 month, 27 days ago) comment permalink

So I just updated Light Room Classic and it says that I’ll need a Lr8 version of the Zenfolio Exporter. Any chance there is something in the works?

Thanks!

Brian

Recent versions of the plugin support Lr8… please upgrade. —Jeffrey

— comment by Brian Baer on October 25th, 2018 at 10:35am JST (1 month, 26 days ago) comment permalink

Quick question. For the past couple weeks my uploads from Lightroom to Zenfolio (with your plugin) are running ridiculously slow. SO slow it times out. So slow i have been unable to upload a wedding in the past 3 days. My workflow has completely halted. Are you aware of any issues that are happening? Just trying to troubleshoot and wasn’t sure if it was with Zenfolio or Lightroom. Thought maybe you would have some insight.

I’ve gotten sporadic reports like this for years, but have never been able to figure out the problem, whether it’s at Zenfolio, the user’s computer, or Lightroom. My code is the same for all my upload plugins, but only Zenfolio suffers this kind of problem (and only sporadically; I’ve never been able to reproduce it). You might try contacting them while it’s happening and ask them to check out the server that you’re connected to, or something. I’m really at a loss on how to debug this. )-: —Jeffrey

— comment by Gretchen Wakeman on November 10th, 2018 at 5:35am JST (1 month, 10 days ago) comment permalink

Updated all my plugins when LR8 came out. Newest version of the Geocoding plugin now displays a message about “shutdown tasks” each time I close LR. Not a big deal at all but never did that before.

What is it doing? Thanks,

Mark

It’s related to a super-convoluted workaround I came up with for a longstanding bug in Lightroom. This bug causes plugins to crash in certain cases if the Geoencoding Support plugin is not running. Lightroom doesn’t offer a way for one plugin to know when another is running, so I came up with a ridiculous way of trying to signal the other plugins that Geoencoding Support is there, and part of that hooks into when Lightroom shuts down. It’s not something that users need to be bothered with, so I wish Lightroom would put that stupid message up. I’ve been talking to Adobe about the bug and various workarounds, so hopefully I can remove this silliness in the future. —Jeffrey

— comment by Mark Chernis on November 18th, 2018 at 1:58am JST (1 month, 2 days ago) comment permalink

Hello Jeffrey,

Do you know if there is a plugin that scans all image files in a catalog to make sure they are not corrupt (after they’ve been imported, of course)?
I found a small external utility “Bad Peggy” that does very well for standard formats of photo files (jpg, …), but NOTHING for RAW files.
The only solution seems to be to use Lightroom’s DNG conversion function, which lists images that can not be converted (but you need to have room to store converted images … or delete them as you go. .. Not cool !

I suppose you could just ask Lightroom to rebuild previews for every photo (perhaps after deleting cached previews); it will tell you if it couldn’t build any. —Jeffrey

— comment by Yves Durivault on November 23rd, 2018 at 7:08pm JST (3 weeks, 5 days ago) comment permalink

In Santa Barbara, editing photos shot in Paris in October.

Do you know of a way to batch change white balance tint to a specific numeric value? For example, tint = 12.

Sure, select all the photos you want to do it to, enter Develop, turn on “Auto Sync” (by clicking on the “Sync” button in the lower-left of the right-hand-side metadata panel), then click on the number next to the tint slider and enter the value you want. The Auto Sync will send it to all the selected photos. (Just make sure to turn off Auto Sync when you’re done!) —Jeffrey

— comment by Mark Alan Thomas on November 29th, 2018 at 7:56am JST (3 weeks ago) comment permalink

Running LR6.12 and as of today, 01/12/18, the Map module is no longer supported. I had thought your geoencoding plug-in would take over but it hasn’t. I’m sure there is a simple way of getting this to happen but I can see it. Can you help me?

Thanks

The geoencoding plugin doesn’t replace the Map module (nothing can do that). The plugin, which predates the existence of the Map module, provides various geoencoding-related features, and I use those features instead of those that the Map module provides, but YMMV. —Jeffrey

— comment by Steve Chasey on December 1st, 2018 at 9:56pm JST (2 weeks, 4 days ago) comment permalink

Dear Jeff,

I love your plugins. Capture One just announced that they are opening up their doors to third-party plugins in the newest version (Capture One 12). It would be my dream come true if you could make the metadata wrangler and the custom metadata fields plugins for Capture One. Pretty please, thank you very much.

Gratefully,
Zach

Sorry, but I won’t be doing stuff for other systems. Even if I had the energy for such things, it’d feel like I was having an affair. 😀 —Jeffrey

— comment by zach kobrinsky on December 5th, 2018 at 4:34am JST (2 weeks, 1 day ago) comment permalink

Brilliant! I’ve been using Lightroom since v1.0 and never figured this out. You’re awesome.

— comment by Mark Alan Thomas on December 7th, 2018 at 5:48pm JST (1 week, 5 days ago) comment permalink

Hey Jeff,
Are you considering doing something about the problem with Maps not working anymore?
Adobe gives a damn in their customers and will not fix it.
The cause to the problem is Google. What about using Bing Maps?

Unfortunately, it’s not something a plugin can do anything about. Adobe would have to build a new version of Lightroom to update things to handle Google’s changes, or to work with Bing, but they’re already two major versions past that old version. I totally feel your pain about moving to a subscription service, but that’s all that Adobe offers, and so that’s where they’re putting their efforts. /-: —Jeffrey

— comment by Ole Michael Mikkelsen on December 9th, 2018 at 9:41pm JST (1 week, 3 days 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