Jeffrey’s “Metadata-Viewer Preset Editor” Lightroom Plugin

This plugin allows you to create and edit tagset presets for Lightroom's metadata viewer. That is, it allows you to pick and choose which metadata items Lightroom should show for each photo, and in what order they should be shown.

To be clear: this plugin does not allow you to edit photo metadata itself.
It merely allows you to configure the list of items that Lightroom displays.

This plugin works in Lightroom 6/CC (and older versions as far back as Lightroom 3, though some features depend on the version of Lightroom).

The same download works for both Windows and Mac. See the box to the upper right for the download link (in orange) and installation instructions.

This plugin is an in-Lightroom version of the web-based preset editor that I published a couple of years ago. That application continues to work, but this plugin should prove to be more convenient. Also, this plugin incorporates the ability to include the custom metadata from other Lightroom plugins in your presets, a feature that I have not gotten around to update the online tool with.

This plugin is currently in beta release, without much documentation.

Mini Instructions

After installing it, you'll see a “Configure Metadata-View Presets” button in the Plugin Manager itself. Clicking on it will bring up the preset-edit dialog. Please see the “help” link in its upper-right corner.


I distribute this plugin as “donationware”. I provide it for free and it is mostly functional for the first six weeks. Until registered, it can not create “static custom presets”, nor import/export presets.

After the six-week trial period expires, custom presets remain usable, but with an ugly “unregistered” heading inserted at the top.

If registered, the “unregistered” heading goes away, of course, and also, the plugin gets the ability to create “static custom presets” that remain even if the plugin is removed, and it also gains the ability to import and export presets (so that you can move them from one computer to another, for example, or share with friends).

Registration is simple and costs the minimum 1 cent PayPal fee; any additional donation you'd like to make in encouragement or thanks is up to you. For details, see my blog post titled Lightroom Plugin Development: Now With Added Encouragement.

Version History
( Update Log via RSS )


Added support for the "Temperature" field I just added to my geoencoding-support plugin.

Switch the log-sending mechanism to https.


Added support for Alloy Photo's Print Size Calculator plugin.

Highlight more that you can import fields from unrelated plugins.

Try to avoid yet another place where Lightroom gets hung because it can't handle certain kinds of dialogs at the same time.


Added the "At Facebook" item, which somehow got missed earlier.


Added two new items I found in Lightroom 6, "Camera + Lens" and "Camera + Lens Setting".

Added data for's Alamy Picture Manager.


Update the code that puts together the example value for the "Camera" metadata item, to mimic the grotesquely-verbose way that Lightroom actually does it itself.


In the POODLE-vunerability dialog, display a raw URL of a page on my site that discusses the issue, so that folks can be independently sure that the dialog is indeed from me and not malware.

20150125.78 Wasn't working on Lr2 again.

Added data for my Google Drive plugin, for my ipernity plugin, and for my Tumblr plugin.

Registration was broken on Lr2.

20141127.76 Added support for my Geoencoding-Support's "Timezone" metadata field.
20141019.75 Windows Only: Add a one-time check for the POODLE security vulnerability, and alert the user if it exists.
20140902.74 New build system
20140731.73 Registration fix for Lr5.6
20140729.72 Previous updates broke support on Lightroom 2
20140720.71 More Creative-Cloud support.

Fixed an issue with Creative-Cloud revalidation.


Lr5.5 and later Creative-Cloud installs can now revalidate themselves if needed.

20140710.68 Sigh, had a bug in the Creative-Cloud support.

Now supports Lr5.5+ Creative-Cloud Installs.

20140704.66 Sigh, introduced an error for some folks with the rebuild the other day.
20140630.65 Build-system update

Fixed a bug in the "smoother revalidation" stuff recently added.


Added a second form of the color-label item. Adobe seems to support two forms, one which is readonly but you can set a custom label, and one that you can edit but you can't set a custom label (and for whatever reason the standard label is included in the value column, so it looks oddly indented).

Make the revalidation process smoother, especially for folks using Lr5.4 and later.

Fixed some Windows dialog-layout bugs.

20131210.62 It seems the save-to-static-preset function had stopped working.
20131023.61 Fixed a bug that stopped the "Label" (color-label label) text from being changed.

Added new "Direction" field (direction of view) that seems to have appeared circa Lr5.

The "Supplier Image ID" entry was broken... would never actually be included in the preset.

20130908.59 Update default text for "Person Shown" to "Person Shown in Image" to match Lightroom
20130613.58 Better support for plugin revalidation.
20130611.57 Yet another Lr5 update
20130524.56 Apparently, a recent change broke things on Lr2, which some folks apparently still use.
20130501.55 Update for Lr5
20130412.54 Build system update.
20130328.53 Fix for the registration system.
20130209.52 More build-system maintenance
20130206.51 Tweak for my registration system

Note: you must restart Lightroom after installing this update.

Added support for my Creative Commons plugin.

Added support for Video and DNG metadata in Lr4.

Added a bunch of other new metadata fields I noticed in Lr4.

Updated the plugin's idea of Lightroom's builtin presets to match Lr4.

20120617.48 Add the ability to include custom metadata from any local plugin.
20120608.47 Fix an "attempt to perform arithmetic on field" error.

Update to handle the Mac App Store version of Lightroom.

Tweak for Lr4.1RC2.

Enhanced the send-log dialog to hopefully make reports more meaningful to me, yielding, I hope, the ability to respond more sensibly to more reports.

20120330.45 Update to handle 4.1RC
20120309.44 Had broken registrations in Lr2; Update to the debug logging to better track down timing issues that might arise.

More updates for Lr4.


More updates for Lr4.


More on the march toward Lr4, including upheaval in the code to handle Lightroom APIs being discontinued in Lr4.

Added data for a bunch of plugins.

Added some extra bulletproofing when reading preset files.


There's a bug in Lightroom that causes the whole plugin to fail for some users. This failure happens when the "build a preset" dialog tries to pull up example image data saved by other plugins (e.g. an export plugin's "Uploaded to..." flag).

This is just for the display of example image metadata while building a preset, and it'd be nice to show actual data, but not at the expense of crashing, so I've disabled it. The resulting preset, when used with Lightroom, of course does show all the data as appropriate to the preset you've built.... this bug is only related to how example metadata is shown in the builder dialog.

Also, removed registration-related restrictions from the Lr4 beta, since you can't register in a beta.

20120114.39 More tweaks for Lr4b

Update for Lr4 beta: explain in the plugin manager that the plugin can't be registered in the beta.


When doing a plugin upgrade, offer the ability to flush all the old copies of the plugin.

Had issues with the registration button sometimes not showing.

Added a system-clock check and reports to the user if the system clock is more than a minute out of date. An incorrect system clock can cause problems with various kinds of communication and authentication with some of my plugins, so I've just gone ahead and added this to every plugin.

20110910.36 Work around a bug that caused the plugin to crash in the Lr3.5 beta.
20110207.35 Was dorked in Lr2... now fixed.

More debugging to try to crack this tough dialog-won't-open bug. The best I can figure at this point is that it's a bug in Lightroom.

One workaround that just came to mind: before invoking the plugin manager, make sure that no photos are selected (e.g. that when in Loupe, "no photo selected" is shown, via control-D or command-D). That should, in theory, bypass the area of the dialog-creation code that's running into the bug. I can't reproduce the bug myself, so I can't test this workaround myself.

20110107.33 More debugging to try to crack this tough dialog-won't-open bug.
20101219.32 Added support for new IPTC in Lr3. Updated display for recent versions of my megapixel-sort plugin. Added yet more debugging to try to track down a missing-dialog problem some have been seeing.
20101209.30 Fixed an "ISO ISO" typo. Added a bunch of debug logging to try to track down a missing-dialog problem some have been seeing.
20100829.29 Made the revalidation process much simpler, doing away with the silly need for a revalidation file.
20100820.28 Discovered a bug in my plugin build system that caused horribly difficult-to-track-down errors in one plugin, so am pushing out rebuilt versions of all plugins just in case.

Added support for my focal-length sort plugin.

20100625.26 Yikes, shaking out some more build issues.
20100624.25 Discovered a nasty build bug; pushing a new version in case it affects this plugin.

This version can be registered in Lightroom 3. It can run in Lightroom 2 or Lightroom 3; it does not work in the Lr3 betas.

It uses my new registration system when run on Lightroom 3, which avoids some of the silly issues of the old one. Please take care to note the details on the registration page: use of this version (or later) of the plugin in Lightroom 3 requires a new registration code, even if you had registered some older version of the plugin.

20100525.23 Turns out that "Metadata Date" is not available to the Lr3 beta, so the plugin wasn't working there. Made it always empty in the Lr3 beta preset-building screen.
20100520.22 Fixed the data used for the "Metadata Date" sample data in the preset-building dialog... I'd been showing the last-edit date by mistake.
20100516.21 Update for the Lr3 beta.

Completely changed how the one-click upgrade applies the newly-downloaded zip file, in the hopes that it'll work for more people. Rather than unzipping over the old copy, it now unzips to a temporary folder, then moves the old folder out of the way and the new folder into place. Prior versions' folders are now maintained (with the version number in the folder) in case you want to revert a version; you may want to clear them out from time to time. Of course, it won't take affect until you try to upgrade after having upgraded to or beyond this version.

20091205.19 Minor internal debugging tweaks.
20091027.18 Minor UI tidyup for OSX.
20091027.17 More LR3b fixes... actually seems to work now.
20091022.16 Added a first draft of some rudimentary support for Lightroom 3 Beta. See this important note about plugin support in Lightroom 3 Beta and Lightroom 3, including future plans for features and my registration system.

Enhanced the one-click upgrade stuff quite a bit, now detecting ahead of time when it will fail because the plugin is installed where Lightroom can't write (if Lightroom can't write to it, it can't update itself). I also added a progress bar, and now download in smaller chunks to avoid 'out of memory' errors on the larger plugins. Do remember that this new functionality becomes available after you upgrade to or past this version, when you then upgrade with it.

20090626.14 Added another new Video-Asset Management plugin field.
20090624.13 Added fields in support of my new Video-Asset Management plugin.
20090617.12 Added the new upload date/time fields for my other upload plugins (Zenfolio/SmugMug/Facebook/PicasaWeb).
20090603.11 Added support for the new "Flickr Upload Date" and "Upload Time" fields that I just added to my Flickr plugin.
20090601.10 Seems some Mac users were still losing presets each time... thought I tamed that bug, but indeed found another bug and fixed it. Hope this is the last one.
20090521.9 Fixed a "loadstring" error some users got.

This update affects Mac users only

It seems that many (all?) Mac users had problems with Lightroom forgetting presets each time it restarted. I've discovered a bug in Lightroom that I think I've been able to work around in this version, but the change is not backward compatible, so Mac users who were actually able to make Custom User Presets will lose them upon upgrade. Sorry. This happens only when upgrading from before this version to this version or after, and subsequent upgrades should be lossfree. (Static User Presets, and all presets on Windows, are unaffected and should carry through unharmed.)

20090510.7 Added a link in the Plugin Manager to the plugin's update-log RSS feed.
20090428.6 Added custom metadata from my Megapixel Sort plugin.
20090426.5 Added a bunch of debugging stuff to try to track down why presets are not saved for a few users.
20090425.4 Oops, the one-button upgrade stuff didn't work due to a typo on my part, sorry. Upgrading to this version will still need to be manual, but upgrading from this version to whatever's next will hopefully work.
20090423.3 Fixed "ID_PREFIX" bug that popped up when converting a custom prefix to static.

Wow, this plugin continues to be one of the most complex I've ever worked on. Tons of new stuff this time, including...

  • Now donationware.
  • Lots of UI cleanup.
  • Added "label" and "separator" links at the bottom, so that you can easily add labels and separator lines without scrolling to those entries at the bottom of the right-side master list.
  • Added a "show photo data from" toggle in the bottom-right corner, allowing you to toggle between photo data from the image selected when you invoked the dialog, or fully-filled-out fake sample data. (If no images are selected when you invoke the dialog, you get only the fake sample data.)
  • If you click on the active line in the left-side preset preview, the associated item in the right-side master list is scrolled into view and highlighted.
  • Some have been confused by how a new preset's title is entered, so I've added a bunch of visual hints (big flashing "EDIT HERE!!!" signs 🙂 ) until I can figure a more intuitive interface.
  • The "Blank Slate" built-in preset didn't really work. Does now, and has been renamed to "Empty (No Items)"
  • Added the ability to edit/save/create static user presets, and to import/export presets. I've left these as candy for when the plugin is registered.
  • Added a help page describing the different types of presets the plugin works with (Lightroom default, Plugin default, User custom, and Static user custom).
  • Added the "map" metadata item from my geoencoding plugin
  • Lots more I can't remember.

One of the big todos is to add the ability to set attributes to items, such as the the number of lines of a caption.


Initial public beta release.

The UI for this plugin has been by far the most difficult to do, and that's mostly what this plugin is about: a snazzy interface for editing a simple preset file. Lightroom's plugin infrastructure is still in its infancy and understandably Adobe has not yet filled out every feature required to make a rich, interactive presentation. Taking it almost as a personal challenge, I've expended enormous effort to try to work around some of the limitations. This is the best I can do for now.

At this first-beta-release stage, I'd appreciate comments via email, so I've turned off comment-submission for this post.

Because this is an early beta that I don't want to hang around very long, the plugin expires after a month. It'll certainly be updated well before then.

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

Hi there!
Currently testing the metadata plugin.
All working well, I have made a preset based from Large caption.

I was wondering if you could tell me where my newly created preset lives on disk so I can quickly (assuming it is possible) go in and alter the preference designating the size of the box which I am after reducing slightly.


If you’ve saved it as a static preset, it’s in the folder named in the comment just prior to this one (which wasn’t yet visible when you posted your comment, in case you’re wondering how you missed it 🙂 ). —Jeffrey

— comment by Richard Costin on July 31st, 2013 at 11:57pm JST (3 years, 9 months ago) comment permalink

Hi, I try to find the spot to copy a saved irtemplate preset for use on another PC. C:\Users\BK\AppData\Roaming\Adobe\Lightroom\Metadata Presets seem not be it.

So where to go to – Bernd

It’s there only if you’ve saved it as a static preset. Otherwise, it’s only within the running plugin. —Jeffrey

— comment by Bernd on August 10th, 2013 at 3:51pm JST (3 years, 8 months ago) comment permalink

Hi Jeffrey,

Just a heads-up about two small bugs in Preset Builder 20130613.58: The IPTC Extensions field “Person Shown” shows up in my preset as “Person Shown in image” and “Location” in the IPTC Image Description turns out as “Sublocation”.

Really small issues indeed but I thought you may want to know, if you don’t already do.

Keep up the great work!

Daniel, a German in Singapore

This is “as designed” according to Adobe. Unless you manually change a label in the preset builder, the preset merely references a field by an internal code and leaves it up to Lightroom to call it whatever it calls it (which may change from version to version, and certainly from language to language). In any case, you can always override the label with your preferred text. —Jeffrey

— comment by Daniel on September 2nd, 2013 at 2:48pm JST (3 years, 8 months ago) comment permalink

Hi Jeffrey,

I’m just evaluating your great Metadata-Viewer Preset Editor, version 20131010.60 (and will definitely pay for it). I works just fine – but there’s one field I can’t seem to rename. It’s the “Label” field (for the color labels), called “Beschriftung” in my German Lightroom UI (version 5.2). While I can change the labels of the other fields, this field just resists all changes. It’s saved in the plugin, but doesn’t show up in Lightroom after reloading the plugin. Is this a bug in the plugin? Or in Lightroom? Or is it just simply impossible to change this because of a reason I don’t know?

Thanks in advance for your help!

Greetings from Kiel, Germany,

Thanks for the report… I’ve just pushed a fix. —Jeffrey

— comment by Jan-Christoph Ihrens on October 22nd, 2013 at 7:09am JST (3 years, 6 months ago) comment permalink

Hi Jeffrey,

thank you very much for fixing this so quickly, now it works perfectly. After updating, the renamed field was removed, but I could add it again and then rename it successfully.

BTW: In the meantime I registered the plugin. Thanks for your great work! 🙂


— comment by Jan-Christoph Ihrens on October 23rd, 2013 at 12:42pm JST (3 years, 6 months ago) comment permalink

Hello, I’m French and I do not speak English, so excuse me if the computer translation is not correct.
In the list of metadata fields available in your plug-in, there is one called “title” in the IPTC Status section. I choose this field and include it in my preset in the plugin, it also appears in LR but the field “title” is empty, I had filled with the original “title” field LR .
The reverse is exactly the same.
I have not seen other metadata “title” in the plugin.
Thank you for the help.

The “Title” entry in “IPTC Status” is the same as Lightroom’s default “Title” entry, so I don’t understand why you are not seeing the title. Perhaps you switched images? If you save your preset to a file, perhaps mail it to me and I’ll take a look… —Jeffrey

— comment by Jérôme on November 13th, 2013 at 7:05am JST (3 years, 5 months ago) comment permalink

I’m quite confused by the date/time fields that this plugin shows as available. Here’s a link to screenshot that shows the available date/time fields:

I see multiple fields with the field name “Capture Time.” The first shows just a time, and the other one farther down shows a date and a time.

There are also two fields called “Date Time.” These show identical values.

So, my first question is: why are there multiple fields in the LR database that have identical field names but seem to have different data in them?

What brought this up is that I have two images that should sort (by Capture Time) together, but do not. Here are links to screenshots showing what your plugin shows for these two images…

Image 1:
Image 2:

Image 2 (the tiff file) has several fields missing, and it sorts in LR between two files with dates on either side of the “Date Time digitized” date.

So, question 2: What field exactly does LR use when sorting images by “Capture Time”?

And finally, question 3: What can I do to provide the tiff image with the data values necessary to get these two images to sort together?

(FWIW, when I use LR’s “Edit Capture Time” menu item, both images show up as having exactly the same Capture Time!)

Thanks for your plugins and for your help.

If you mouseover each item and pause, the tooltip will explain the difference. The two “Date Time” entries, for example, show the same value, but the second one simply disappears if it’s the same as the Capture Time. As to why there are two different fields labeled “Capture Time”, that is a good question whose answer I don’t know. The plugin merely mimics what Lightroom itself does, and Lightroom has the two separate fields labeled the same. As for the sorting, Lightroom has bugs in this area, especially with videos. I’ve reported many. I *think* it uses “Date Time Original” for sorting, which your TIFF doesn’t have. For best results, make sure that all the various date/time fields agree, and then cross your fingers and hope Lightroom does something reasonable. /-: —Jeffrey

— comment by Robert Camner on February 23rd, 2014 at 11:18am JST (3 years, 2 months ago) comment permalink

Thanks for the quick and helpful response! I’ll do my best to figure out how to get a value into the Date Time Original field when no value currently exists.

You might try ExifTool to inject it (perhaps copying it from another date field), then “Metadata > Read Metadata from File”, but be sure to “Metadata > Save Metadata to File” before so that when you do the read, the only thing different is the date. If you don’t write it first, you’ll wipe out anything you’d changed in Lightroom. I sure wish Adobe made this easier. —Jeffrey

— comment by Robert Camner on February 24th, 2014 at 11:16am JST (3 years, 2 months ago) comment permalink

A couple of questions..

1. Where does this plugin store the custom presets I create? If I export one of the custom-created presets, it creates a .lrtemplate file with a name obviously connected with the name of my custom preset, but I can’t find any other file on my filesystem with that name.

2. If I understand correctly, a static preset can be used OUTSIDE the plugin (the help says “Static presets and be copied to other computers”). If I generate such a status preset, where does it go within ~/Library/Application Support/Adobe/Lightroom on another computer?

Thank you.

Custom presets are stored either within the Lightroom preferences, or exported as the lrtemplate file you noted. Lightroom’s built-in metadata-viewer presets are indeed built in, so the only metadata-viewer preset files you’d find are ones you create. They go in “~/Library/Application Support/Adobe/Lightroom/Metadata Field Lists” —Jeffrey

— comment by Robert Camner on April 4th, 2014 at 1:38am JST (3 years ago) comment permalink

Hmmm…I don’t have a Metadata Field Lists folder in ~/Library/Application Support/Adobe/Lightroom; it jumps from “Locations” to “Metadata Presets.” But I do have several metadata presets I created with your plugin. From the absence of that folder, I presume you store the presets created by the Metadata Preview Viewer preset in the LR prefs, yes?

So, I want to edit the preset so that a field has multiple lines (such as happens by default with “Caption”), and I did the following:
1. Build the preset the way I want with your plugin
2. Export the preset
3. Using TextWrangler edit the .lrtemplate file to add the code to make the item show 2 lines
4. Changed the title of the preset within TextWrangler and saved the file
5. Imported the new .lrtemplate file

That worked fine, but the old custom preset is now marked “disabled.” It has a different id field.

Why did the original preset get “disabled” and what magic step am I missing?

Thanks again.

Lightroom has three ways for presets to exist… its internal default presets, “*.lrtemplate” files in the “Metadata Field Lists” folder (if it exists; it doesn’t originally), and via a special plugin mechanism. My plugin does save your non-static preset data in the Lr preferences file, but needs to provide them to Lightroom via the special plugin mechanism, which it does upon startup.

Anyway, that’s the background. To do what you want, you’ll want to “Convert to Static Preset” to save the file in your Metadata Field Lists folder (which the plugin will create as needed), then edit that file in place. I’m not sure what you meant by “imported the .lrtemplate file”, but you don’t need to import anything… once the template is saved, just edit its fields as you like. —Jeffrey

— comment by Robert Camner on April 9th, 2014 at 12:18pm JST (3 years ago) comment permalink

Great plugin! Is there any way you could add bit depth?

No, unfortunately that’s not one of the fields that Adobe exposes to plugins (nor to users). However, FWIW, you can inspect the bit depth on an individual-file basis with my metadata-viewer plugin, and group photos by their bit depth with my Data Explorer plugin. —Jeffrey

— comment by Matthew Turley on April 10th, 2014 at 2:23am JST (3 years ago) comment permalink

Really sorry for the dumb question: how to I get it to show? I reloaded it after configuring which fields I need it to show, the Manager says it’s enabled but I can’t find it anywhere in the menus? I’m using a Mac with Mavericks. Thanks!!

There’s a dropdown list in the metadata panel itself, as illustrated in the image just under this page’s title (with the cursor pointing to “Jeffrey’s View”). —Jeffrey

— comment by Danny on May 6th, 2014 at 5:04pm JST (3 years ago) comment permalink

One more questions: would it be possible to get it to show some of the “green” items from your Viewer Plugin like the AF Micro Adjust Value?

No, Lightroom allows for only certain items in the metadata panel. The metadata-viewer plugin goes outside Lightroom to access the metadata, then displays it in a custom dialog. —Jeffrey

— comment by Danny on May 6th, 2014 at 11:41pm JST (3 years ago) comment permalink

Hi Jeffrey,

Thx for this plugin. It comes very handy to display only what I need on the limited space of my laptop.

I’d like to add the altitude from the Geoencoding plug-in. You explained how to do it in another message – here or on the Geoencoding page: edit the LR Template.

Do I have to save a static preset to do that ? Because I don’t the file that I’m supposed to edit.

Thx — Philippe

There’s been no separate “geoencoding plugin altitude” since Lr4 when Adobe gave plugins the ability to update geodata, so just use this metadata-viewer-preset plugin to create a preset that includes the normal altitude. No need to edit any files. —Jeffrey

— comment by Anonymous on August 10th, 2014 at 8:18am JST (2 years, 9 months ago) comment permalink

Writing from Edinburgh, Scotland.

Just updated my plug-ins. Despite clicking the clean up old versions tick box, both “metadata presets” and “google drive” created a second folder on my PC plug-in directory.

No real issue, but worth mentioning.

— comment by Colin McDonald on October 21st, 2014 at 7:20am JST (2 years, 6 months ago) comment permalink

Writing from just outside of Athens, GA. This comment is a question about the Metadata Presets plugin, but first I have to say that your Metadata Viewer plugin works great! It even shows the “Custom Rendered” EXIF field that Apple and apps developed for iOS use to indicate an HDR image. A value greater than 1 indicates an HDR image. The value displayed in Metadata Viewer (and some other EXIF viewers) is “Unknown (value)”.

I’d like to use the Metadata Presets plugin to open up that EXIF field to Lightroom’s metadata display, but I can’t find Custom Rendered in the master list. Is there a way to get that field added to a custom preset? If not, would you please consider adding it to the master list? Many more of my iPhone 6 photos will be HDR in the future, so this field would help searching for them in the Lightroom Library.


(PayPal donation on its way!)

Unfortunately, Lightroom doesn’t include that field among those that can be accessed by the plugin or via the metadata display… the “master list” is determined by Adobe. Incidentally, I gave it a try (iOS7 on an iPhone 4s) and all photos, HDR or not, had “Custom Rendered” values of 3 and 4, so I’m not sure what the values mean… —Jeffrey

— comment by Jeff Bellune on October 24th, 2014 at 12:04am JST (2 years, 6 months ago) comment permalink

Thanks for the info on what fields Lightroom exposes. My workaround is to find the Custom Rendered values I want using your Data Explorer plugin, and then adding “HDR” to the image’s Caption field. I don’t generally use Captions in Lr, so that lets me visually tag the HDR photos. Who knows, the workaround may end up being better than my original idea. 🙂

With iOS 8 on an iPhone 6, using the ProCamera 8 app with the vividHDR plug-in, HDR photos have a Custom Rendered value of 3, while all non-HDR images leave that field blank (or exclude it completely). After some ‘net research, I found the consensus is that normal images from the iOS Camera app have the Custom Rendered field set to 4, while HDR images have the field set to 3. I couldn’t find any authoritative documents on this, but the developers of ProCamera say that they set the field to 3 for HDR images the same way that Apple does. They didn’t comment on why they leave that field blank or missing for normal images.

Thanks for all your hard work on these plug-ins!


— comment by Jeff Bellune on October 28th, 2014 at 9:51pm JST (2 years, 6 months ago) comment permalink

Is there a way of showing:
> Resolution
> Bit Depth
> Color Mode
> Color Profile

Not in the metadata panel, but FYI you can access it via My Metadata-Viewer plugin, and my Data-Explorer plugin. —Jeffrey

— comment by Jack on January 19th, 2015 at 3:42am JST (2 years, 3 months ago) comment permalink

Hi Jeffrey,
Is it possible to display information from your “people support” plugin ?

Unfortunately, no, because Lightroom doesn’t allow for dynamic computation of values to display. I suppose I could create a plugin-specific metadata field that you could have the plugin fill in for a set of photos, and that could then be displayed. You’d have to manually apply this process to a set of photos before it would work, and would have to remember to rerun it after any change to the people data that might effect the photos. It’d feel kludgy. )-: —Jeffrey

— comment by m4fi3ux on February 4th, 2015 at 6:30am JST (2 years, 3 months ago) comment permalink

“Metadata-Viewer Preset Editor”

I was hoping that this might help me edit my list of Location presets – it’s much too long for convenience.

Can I use it for this or do I need to try something else?


No, sorry, this plugin has nothing to do with location presets, but you might be able to do what you want with Finder/Explorer. Right click on a preset name and “View in Finder/Explorer”, then you’ll see them all there. Shut down Lightroom, then delete the ones you don’t want (if that is indeed what you want to do)… —Jeffrey

— comment by Roger Walton on July 9th, 2015 at 12:05am JST (1 year, 10 months ago) comment permalink

I love this metadata presets plugin. I have stumbled upon an anomaly though. I am using “At Tumblr”, “At Flickr” and “At PicasaWeb” and would like to use “At Facebook” as I see it in the “all possible items” list (the active, righthand column when your dialog is not active but rather when one is actually working on images) but in the dialog to build/configure my preset, the “At Facebook” field is not provided, only the “Uploaded to Facebook” (and the date/time fields) is listed for use 🙁 🙁

In the “all possible items” list I see this field (At Facebook) is in the jf Facebook “stanza” whereas the other “At …” fields are in the “Jeffery’s Export-to-…” stanzas.

LR CC, and plugins are all up-to-date.

I’m not sure how this got omitted in the first place, but I’ve just pushed out a new version of the plugin that includes it. Thanks for the report. —Jeffrey

— comment by Larry Williamson on December 15th, 2015 at 5:39am JST (1 year, 4 months ago) comment permalink

I could not find shutter count in the list to modify for my metadata presets plugin. Is this not available in this metadata list, it is available in the Metadata Viewer which I have and registerd and works real good, just a lot of data.

Lightroom doesn’t make it available, sorry. —Jeffrey

— comment by Floyd Cantrell on January 8th, 2016 at 8:56am JST (1 year, 4 months ago) comment permalink

A very nice plug-in. I want to ask you where (in which subfolder of the system) to put the exported .lrtemplate file of this Metadata-Viewer Preset Editor-plugin. I work on a Mac. Thanks.

Hans Schäppi from Switzerland

The plugin should put it there for you, but in any case it’s “~/Library/Application Support/Adobe/Lightroom/Metadata Field Lists/” —Jeffrey

— comment by Hansruedi Schäppi on June 12th, 2016 at 5:23pm JST (10 months, 13 days ago) comment permalink

Is it possible to include XMP data as options to view even if read-only?

In particular I am looking for a way to view Panorama / Photosphere data which is saved from software such as PT GUI or Android photosphere.

I know I can sort-of get this info in Lightroom either via Data-Explorer or Metadata Viewer plugins but it gets a little cumbersome to view this info for multiple files.

In particular the XMP fields I’m looking for are:


Unfortunately, no, the plugin is limited to arranging from among the specific fields that Lightroom provides access to, or fields defined from other plugins. (If you can get a plugin that imports those GPano fields into plugin custom fields, this plugin can display them.) —Jeffrey

— comment by Matt on August 28th, 2016 at 6:09am JST (7 months, 28 days ago) comment permalink

With latest LR upgrade all your plugins disappeared.
Was able to reload them and they work after revalidating but the several custom presets made with Metadata Presets havc disappeared.

I tried to puzzle through the instructions at “Robert Camner on April 9th, 2014” but couldn’t find the ones I created anywhere on C: drive.

Any hints on where to find them and where to move them or should I just redo them?

Using Win10 64 bit



It sounds like you lost Lightroom’s preferences file. If you can’t restore it from backup, then yeah, sorry, you’ll have to recreate your presets. —Jeffrey

— comment by Lew Lorton on September 13th, 2016 at 9:10am JST (7 months, 12 days ago) comment permalink

Hi Jeffrey,
thanks for adding support for Alloy Photo’s Print Size Calculator plugin!
Regards Thomas

— comment by Thomas Kemnitz on November 28th, 2016 at 11:24pm JST (4 months, 27 days ago) comment permalink

I really like this plugin, great job. Is it possible (maybe with next release) to include Metadata from Piwigo Export Plugin?

Plugin is available at

I assume when you contact the author you will get a full list of Metadata definitions.

Best Regards

Have you tried the relatively-new import feature? There’s an “import fields from plugin” button at the bottom-center of the dialog. —Jeffrey

— comment by Wernfried on January 16th, 2017 at 1:00am JST (3 months, 10 days ago) comment permalink

great plugin –
I figured out how to show the caption field with 2 ore more lines, but how can I show the keyword field with ie 2 lines?
thx Bernd

Alas, Lightroom doesn’t allow it. —Jeffrey

— comment by Bernd on February 19th, 2017 at 12:22am JST (2 months, 7 days ago) comment permalink

Hi Jeffrey,

I have been using registred versions of your plug-ins since Lightroom since version 3. Somehow I have only now discovered the Metadata-Viewer Preset Editor. This may be my favourite of them all. I have been struggling with swapping between various Lightroom meta-data options. Now I can get just what I need and ONLY what I need.

Thank you.

— comment by Khürt Williams on March 24th, 2017 at 4:12am JST (1 month, 1 day ago) comment permalink

Trying to bring all my images from Aperture – ~ 50,000 images using your metadata preset.

Was just about to start after working with it, but I am unable to bring in the GPS data. I have manually set the photos in Aperture to locations, and in Aperture it is listed int he metadata as two fields, the Latitude & Longitude.

I don’t see those fields separately – only as one field ‘GPS’ in LR , but it doesn’t read the information from Aperture separate fields (longitude & latitude). Do you know of a way make this work? Thank you for your time.

Sorry, I don’t know anything about Aperture. Are you using the plugin that Adobe provides, for migrating data? I’d hope that takes lat/lon into account(!) —Jeffrey

— comment by David Barron on March 26th, 2017 at 6:40am JST (4 weeks, 2 days ago) comment permalink
Leave a comment...

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