Jeffrey’s “Data Explorer” Lightroom Plugin

One example of the plugin's 175 ways to group your images

This plugin for Adobe Lightroom allows you group photos and videos in your Lightroom catalog by more than 150 data criteria. For example, grouping a large folder tree by “Crop Amount” might result in the screenshot seen above.

By clicking “isolate” on each row, the relevant images are shown. The plugin also creates a row-specific collection, such as:

Data Explorer > Crop Amount > Slight Crop

and populates it with the pertinent photos so that you can refer to them later.

The basic purpose is essentially the same as Lightroom's own Library Grid Filter, but Adobe's built-in functionality, though fast, has extremely limited scope. If it were able to handle more than the scant few fields it currently supports, there would be no need for this plugin, but it doesn't, so here we are.

As it is, this plugin lets you inspect and group photos via a bewildering number of criteria, from the mundane (“group by copyright name”) to the esoteric (“group by geoencoded hemispheres”) to the particular (“group by amount of Clarity applied in Develop”) to the advanced (“group by camera-calibration profile”). The entire list of 175 criteria is shown below.

Table of Contents


This plugin works in Lightroom 5 and Lightroom 4.

Lightroom 4.1 or later is required.

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.

Search. Filter. Group. Explore.

This plugin can be used to search or to browse. A search helps you locate photos that match specific criteria, such as “Where are my panoramas with a really wide aspect ratio?”, while browsing lets you see the range of values represented by some particular criteria in your library, answering questions like “What range of aspect ratios do I have in my library?” (The answer for my catalog at the moment: as tall as 1 : 2.58151 and as wide as 6.4 : 1”).

Browsing can be both fun and useful, especially for catalog cleanup, such as after grouping by “Copyright”, you may see various versions of the same person's name that you'd want to make identical.

Sometimes the results are surprising. While making the screenshot shown at the top of this page, the first thing I noticed was that four photos had an essentially-100% crop! I wondered what they were, and found the answer with one click of the “isolate” button: the four photos were presented and I recognized them as the extrem crops that appeared on this blog post 18 months ago, and an extreme crop of the first photo on this post that I used to use as my online avatar.

Anyway, I started writing this plugin the first time I tried to use the results of an X-Rite ColorChecker Passport in Lightroom, which allows you to make situation-specific camera-calibration profiles for Lightroom's render engine. After trying it with some photos in my library, I quickly lost track of which photos got which profile; it was very frustrating because the only way to know was to inspect each photo's develop settings, one by tedious one, and manually keep a running tally.

Now, I can invoke this plugin on a folder and quickly see:

It didn't take long to solve my immediate need (a crude plugin that merely listed the camera-calibration profiles and their photos), but it's taken three weeks of never-ending “just one more enhancement...” development to whip it into good enough shape to put my name on and release.

Even while writing up this web page after I thought the plugin was ready to release, I realized that Lightroom does not normally subject images hidden within collapsed stacks to catalog operations (such as the grouping operation done by this plugin), so writing this page got put on hold while I addressed that issue in the plugin:

It wasn't straightforward at all, especially to handle it as efficiently as possible, so I burned the better part of a day on just that. Such is the nature of Lightroom plugin development driven by a passion to make things useful.

While talking about searching and browsing, for times when you want only to search, this Data-Explorer plugin may well fill your needs, but you may also want to keep the following plugins in mind as well:

I've not used John's plugin, but it looks to be quite impressive.


The plugin is invoked via “File > Plugin Extras > Explore...”, but it's much faster and convenient to invoke via a Lightroom keyboard shortcut.

On Windows, the keyboard shortcut is “ALT-F S E”.

On a Mac, you can set the shortcut as you like. For my own workflow, I've chosen Option Shift Command F”.

This pops up a dialog that allows you to select the criterion to explore by:

You can pick something from the dropdown box (currently showing “Aspect Ratio...” in the screenshot above), or just start typing search terms, and the dialog immediately transforms into an effective way to find the item you want among the 175 criteria the plugin supports:

Clicking on any criterion returns you to the initial dialog with that item selected, but if the search results in just one criterion, you can press ENTER to immediately launch Data Explorer with that criterion as the basis for grouping.

The “Include items hidden within collapsed stacks?” option is off by default because with large sets of photos it can cause quite a delay because when enabled, the plugin must fetch stack-related data from the catalog, then walk the list inspecting each stack for new photos not already included.

This doesn't take long for small sets of photos... on my laptop it takes about a second to do 1,000 photos, but even this is highly dependent on what else Lightroom is doing in the background. (When I select “All Photographs”, Lightroom turns my CPU into a space heater as it renders thumbnails in the background.)

But that time adds up, and it's a one-minute delay for 60,000 photos. Because the process must finish before the grouping process can be launched, I made the entire option default to unselected.

By the way, here's an interesting general little Lightroom workflow tidbit: Lightroom ignores stacks if you select both Folders and Collections, bringing anything that had been hidden within collapsed stacks into the target set. So, if you select “All Photographs” in the upper left of Library and see X of Y photos” in the filmstrip instead of just Y photos”, and if this can't be explained by you Library Filter, you have photos hidden within collapsed stacks.

If you then option-click (ALT-click) on any folder, you're not really adding anything new to the target set because any folder's photos are already included with “All Photographs”, but because you've now got a collection and a folder selected, Lightroom ignores stacking and voilà, you're at a straight-up Y photos” that really is everything in your catalog.

You can apply the same idea while viewing a specific folder if you create an empty collection (perhaps named “Empty”) that you can add to the selection.

Criteria List

The following table lists the 175 criteria available as of version 20140820.83.

Due to the nature of Lightroom's plugin infrastructure, items marked with a “*” take longer to process.
Items marked with a “***” take even longer, requiring a full inspection of each master image file.

In Lightroom Library
File Currently Available?*File is available, or offline (e.g. on an external disk not currently connect)?

Example responses include:

  • Offline (master file not available)
  • Offline (but Smart Preview does exist)
  • Available (though without a Smart Preview)
  • Available, but file on disk is empty(!!!)
  • Available, but file on disk is smaller than Lightroom expects
  • Available, but file on disk is larger than Lightroom expects
Smart-Preview Status*Does a smart preview exist for the image? (Lightroom 5.0 and later)

Example responses include:

  • Yes
  • Yes (but master image has fewer bytes)
  • No (but could be built)
  • No (can't be built; photo is unavailable)

Also reports the amount of disk space actually taken by Smart Previews, and the space savings afforded by those Smart Previews (that is, for images with Smart Previews, their disk space relative to the disk space required for their master images).

File TypeFile type (DNG, JPEG, Raw, Video, ...)
File Write-Permission StatusWhether the file can be changed (written) and/or deleted
Folder NameName of the folder (without path) the file is in. Useful for isolating images in a parent folder when there are also images in a subfolder.
Path NameFull path of the folder the file is in. Useful for isolating images in a parent folder when there are also images in a subfolder.
File ExtensionFilename extension (JPG, NEF, AVI, MTS, CR2, ...) in a case-insensitive manner.
File Extension
(case sensitive)
Filename extension (jpg, NEF, AVI, mts, CR2, ...) in a case-sensitive manner
Copy NameVirtual-copy name for the photo/video.
Virtual-Copy CountNumber of virtual copies a master image or video has.
Snapshot Count*The number of snapshots for the related master photo.
Stacking StatusStatus with respect to stacking (within its parent folder).

Example responses include:

  • Not stacked
  • Part of a visible stack
  • Top of a collapsed stack
  • Hidden within a collapsed stack
Stack-Membership SizeNumber of photos/videos in its stack (within its parent folder).
Position in StackPlace in stack (within its parent folder).

Example responses include:

  • Not stacked
  • Top
  • Bottom
  • Inside
Number of UpdatesRough count of changes (both metadata updates and develop edits). It's not an absolute counter, though, as Lightroom lumps multiple changes within a short time as a single update.
Most-Recent Update DateDate of the most recent database change (metadata update or develop edit) to the image
RatingStar rating (a number from 1 to 5).
Flag StatusPick, Rejected, or Neither
Color LabelColor label name.
Keyword List (all)List of all keywords associated with an image (warning: can be long!).
Keyword List (exportable only)List of keywords marked “include on export” (warning: can be long!).
Keyword List (non-exportable only)List of keywords not marked “include on export” (warning: can be long!).
Keywords (individually, all)Each keyword associated with an image, as individual items.
Keywords (individually, exportable only)Each keyword marked “include on export”, as individual items.
Keywords (individually, non-exportable only)Each keyword NOT marked “include on export”, as individual items.
Keyword Count (all)Count of all keywords associated with an image.
Keyword Count (exportable only)Count of keywords marked “include on export”.
Keyword Count (non-exportable only)Count of keywords not marked “include on export”.
Plugin custom metadata?Shows the number of plugins that have added custom metadata for the image. The list of plugin ids is included in TSV spreadsheet file.
Camera Make and ModelCamera manufacturer and model name.
Camera Make, Model,
and Serial Number
Camera name with its serial number.
LensThe lens used to take the photo (e.g. “50 mm f/1.4”).
Lens Description***
(built from master-file data)
A description of the lens cobbled together from the raw master-file metadata. This can be useful to identify certain kinds of manual lenses, or perhaps lens + teleconverter combinations.
Focal LengthFocal length of lens as shot (e.g. “85 mm”).
Focal Length 35mm EquivFocal length of the lens as shot, in full-frame 35mm terms (e.g. “135 mm”).
SoftwareSoftware used to process/create the photo prior to import into Lightroom.
Exposure*Exposure summary (e.g. “1/60 sec at f/2.8”).
Total Exposure
(camera Ev)
Total camera exposure (Ev), derived from the shutter speed, aperture, and the ISO speed rating (but without any adjustment for Exposure added or removed in Lightroom). Gives a sense for how much light was available. Lower numbers mean less light.
Total Effective Exposure*
(effective camera Ev)
Total effective camera exposure (effective Ev), derived from the shutter speed, aperture, and the ISO speed rating, then adjusted to reflect any Exposure added or removed in Lightroom. Gives a sense for how much light was available. Lower numbers mean less light.
Shutter Speed*Shutter speed used to take the photo (e.g. “1/60 sec”).
Aperture*Aperture used to take the photo (e.g, “f/2.8”).
In-Camera Exposure Bias*In-camera exposure bias/compensation (e.g. “-2/3 EV”).
FlashWhether the flash fired (“Did fire” or “Did not fire”).
Exposure ProgramExposure program (“Manual”, “Aperture priority”, “Landscape”, ...).
Metering ModeMetering mode (“Center-weighted average”, “Spot”, ...).
ISOISO Sensor-sensitivity speed rating (e.g. “100”).
Subject DistanceSubject distance (e.g. “1.92 m”); often wildly incorrect.
Cropped?Has a crop been applied in Develop? (“Cropped” or “Not cropped”)
Crop Rotation*Amount of crop rotation applied in Develop, rounded to the nearest degree (e.g. “2° CCW”).
Crop Amount*Relative area of the image cropped away from the original, in percent. Larger numbers indicate images left with increasingly smaller areas compared to their original.
Megapixels (post-crop)Image size, after any Develop crop/rotation adjustments, in megapixels.
Megapixels (original)Original image size, prior to any Develop crop/rotation adjustments, in megapixels.
Width x Height (post-crop)Dimensions, after any Develop crop/rotation adjustments, in pixels and megapixels (e.g. “3208 x 4928 (16.0 MP)”)
Width x Height (original)Original dimensions, prior to any Develop crop/rotation adjustments, in pixels and megapixels (e.g. “3208 x 4928 (16.0 MP)”). Note: “Original” does take into account any “Rotate Left (CCW)” or “Rotate Right (CW)” applied to the photo; just not subtle rotation applied in the Develop Module
Long Edge (post-crop)Length of the long edge of the image, after any Develop crop/rotation adjustments, in pixels.
Long Edge (original)Length of the long edge of the original image, prior to any Develop crop/rotation adjustments, in pixels.
Short Edge (post-crop)Length of the short edge of the image, after any Develop crop/rotation adjustments, in pixels.
Short Edge (original)Length of the short edge of the original image, prior to any Develop crop/rotation adjustments, in pixels.
Width (post-crop)Width of the image, after any Develop crop/rotation adjustments, in pixels.
Width (original)Width of the original image, prior to any Develop crop/rotation adjustments, in pixels. Note: “Original” does take into account any “Rotate Left (CCW)” or “Rotate Right (CW)” applied to the photo; just not subtle rotation applied in the Develop Module
Height (post-crop)Height of the image, after any Develop crop/rotation adjustments, in pixels.
Height (original)Height of the original image, prior to any Develop crop/rotation adjustments, in pixels. Note: “Original” does take into account any “Rotate Left (CCW)” or “Rotate Right (CW)” applied to the photo; just not subtle rotation applied in the Develop Module
Aspect Ratio
(short:long, post-crop)
Aspect ratio of the image, after any Develop crop/rotation adjustments, without regard to image orientation (e.g. “2 : 3”)
Aspect Ratio
(short:long, original)
Aspect ratio of the original image, prior to any Develop crop/rotation adjustments, without regard to image orientation (e.g. “2 : 3”). Note: “Original” does take into account any “Rotate Left (CCW)” or “Rotate Right (CW)” applied to the photo; just not subtle rotation applied in the Develop Module
Aspect Ratio
(width:height, post-crop)
Aspect ratio of the image, after any Develop crop/rotation adjustments (e.g. “5 : 4”).
Aspect Ratio
(width:height, original)
Aspect ratio of the original image, prior to any Develop crop/rotation adjustments (e.g. “5 : 4”). Note: “Original” does take into account any “Rotate Left (CCW)” or “Rotate Right (CW)” applied to the photo; just not subtle rotation applied in the Develop Module
Aspect Ratio compared to...Post-crop aspect ratio compared to an aspect ratio you specify: “Same”, “Wider”, “Taller”. This can be useful if you need to do different processing/cropping/exporting based on how an image's aspect ratio best fits a specific display aspect ratio.
With Respect to Image Sensor
The image orientation with respect to a straight-from-the-sensor presentation, e.g. “rotated 90° clockwise” and “flipped vertically”. For many modern cameras with orientation sensors, Lightroom applies an orientation update automatically upon import; these automatic updates are not distinguishable from subsequent user-directed updates.
File size (bytes)File size of the master image or video, in bytes. Also reports total disk usage for selected items. Note that due to a Lightroom bug, the size for offline items is not shown correctly.
Audio sidecar file*The kind, if any, of the audio sidecar file associated with the image
XMP sidecar file*Does the image have an associated XMP sidecar file?
JPEG sidecar file*Does the image have an associated JPEG sidecar file?
Video Size and RateVideo frame dimension and rate (e.g. “1080 x 1920 (30)”)
Video Trim*Whether the video has had its start and/or end trimmed (“Trimmed at start and end”, “Trimmed at end only”, “Untrimmed”, ...).

Example responses include:

  • Not trimmed
  • Trimmed at start and end
  • Trimmed at start only
  • Trimmed at end only
  • Untrimmed
Video Length (Trimmed)Length of the video, after any trimming in Lightroom (e.g. “17 min”).
Video Length (original)Length of the original video, without regard to trimming in Lightroom (e.g. “22 min”).
Video Frame RateFrame rate for the video (“15.000 fps”, “29.989 fps”, ...)
Audio Sample Rate
(of a video)
Sample rate for the audio track of a video (e.g. “48000 Hz”).
Audio Channels
(of a video)
Number of audio tracks (“Mono”, “Stereo”, “5.1”, ...)
Video Pixel Aspect RatioAspect ratio of pixels encoded in a video (e.g. “1”, “1.3333”, ...)
Develop (except crop)
Develop Sections Disabled*List of disabled Develop-module sections (e.g. “Paint-Based Corrections and Lens Correction”).
Red-eye Corrections*Count of red-eye corrections applied in Develop (e.g. “3 Eyes”).
Clone/Heal Corrections*Count of clone/healing-healing corrections (spots and strokes) applied in Develop, e.g. “27 corrections (7 clone spots and 20 heal strokes)”.

Also reports the total number of corrections across all inspected images, and the median number of corrections among images with at least one correction.

White Balance*White-balance setting applied in Develop (“Daylight”, “Custom”, etc.). Also, notes which images have the same white-balance temperature and tint as the most-selected image.
Exposure Adjustment*
(in Lightroom, to the closest ⅓ stop)
Amount of overall exposure compensation applied in Develop, to the closest ⅓ stop.
Contrast*Amount of overall “Contrast” applied in Develop, rounded to the nearest +/- 5.
Highlights*Amount of overall “Highlights” applied in Develop, rounded to the nearest +/- 5.
Shadows*Amount of overall “Shadows” applied in Develop, rounded to the nearest +/- 5.
Whites*Amount of overall “Whites” applied in Develop, rounded to the nearest +/- 5.
Blacks*Amount of overall “Blacks” applied in Develop, rounded to the nearest +/- 5.
Clarity*Amount of overall “Clarity” applied in Develop, rounded to the nearest +/- 5.
Vibrance*Amount of overall “Vibrance” applied in Develop, rounded to the nearest +/- 5.
Saturation*Amount of overall “Saturation” applied in Develop, rounded to the nearest +/- 5.
Color Treatment*Black & White vs. Color vs. Desaturated Color

Example responses include:

  • Black & White
  • Color (but fully desaturated)
  • Color (but extremely desaturated)
  • Color (but highly desaturated)
  • Color (but somewhat desaturated)
  • Color (but slightly desaturated)
  • Color
  • Color (super-saturated)
  • Color (hyper-saturated)
Tone Curve Name*Name of the tone curve applied in Develop (“Linear”, “Custom”, “Strong Contrast”, ...)
Lens Corrections*List of Lens Corrections enabled in Develop (e.g. “Color defringe + Manual”).
Lens-Correction Profile Name*The name of the lens-correction profile applied
Chromatic-Aberration Removal*Indicates whether “Remove Chromatic Aberration” is enabled
Defringe Enabled*Indicates whether “Defringe” is enabled
Unconstrained Crop*Identifies photos with lens corrections that might expose canvas, but without “Constrain Crop” enabled.
Upright Lens Corrections*Status of the “Upright” Lens Correction in Develop (e.g. “Auto”, “Full”, “Off”, etc.)
Vignette*Amount of post-crop Vignette effect applied in Develop (e.g. “Slight white vignette”, “15 black vignette”, ...)'
Grain Amount*Amount of overall “Grain Amount” applied in Develop, rounded to the nearest +/- 5.
Process Version*Name of the Lightroom render engine applied in Develop (e.g. “2012 (standard in Lightroom 4)”).
Basic Tone/Presence Edits?*Reports whether an images has basic Tone changes (exposure, etc), Presence changes (saturation, etc.), both, or neither.
Camera-Calibration Profile*Name of the camera-calibration profile applied in Develop (e.g. “Adobe Standard”).
Comparison with Most-Selected Image
Develop differs*
from most-selected image?
Experimental comparison of develop settings the “most-selected” image to each other selected image.

This is a very-experimental feature, and it may not be completely accurate; it may incorrectly cite a photo as having different develop settings when in fact those settings that differ play no part in the final rendition (for example, if the redeye data for the two photos differ, but redeye correction is also disabled for both photos, they may flag as “different”).

If no more than 50 images are found to be different, you can pop up a dialog that displays the raw differences. (More than about 50 taxes Lightroom's display infrastructure too much.) This entire feature is subject to radical change in future versions of the plugin.

Artist / Copyright
Copyright StateCopyright state.
Artist / CreatorArtist's name.
Rights Usage TermsInstructions on how image can legally be used.
Copyright Info UrlCopyright info URL.
ProviderName of person who should be credited when image is published.
SourceOriginal owner of the copyright.
Creator JobJob title of the person that created the image.
Creator AddressAddress for the person that created the image.
Creator CityCity for the person that created the image.
Creator State/ProvinceState or province for the person the created this image.
Creator Postal CodePostal code for the person that created the image.
Creator CountryCountry for the person that created the image.
Creator PhonePhone number for the person that created the image.
Creator EmailEmail address for the person that created the image.
Creator UrlWeb URL for the person that created the image.
CityName of the city where image was taken.
StateName of the state where image was taken.
CountryName of the country where image was taken.
Country Code2 or 3 letter ISO 3166 Country Code of the country.
LocationDetails about a location where image was taken.
Geoencoded HemisphereGeoencoded hemispheres (e.g. “North/East”). This can also be used to answer simple “Geoencoded?” queries, and to find mis-encoded “0°N 0°E” entries.
Geoencoded Location*
Marked Private?
Is the geoencoded location marked a private? (“Private”, “Not Private”, or “Not Geoencoded”)
Geoencoded AltitudeGeoencoded altitude (e.g. “65 m”).
Other Text Fields
Title lengthReports whether “Title” is blank, starts or ends with spaces or had doubled spaces; otherwise reports the length.
Title line countReports the number of lines in “Title”.
Headline lengthReports whether “Headline” is blank, starts or ends with spaces or had doubled spaces; otherwise reports the length.
Headline line countReports the number of lines in “Headline”.
Caption lengthReports whether “Caption” is blank, starts or ends with spaces or had doubled spaces; otherwise reports the length.
Caption line countReports the number of lines in “Caption”.
SceneIPTC Scene.
EventNames or describes the specific event at which the photo was taken.
IPTC Subject CodeIPTC Subject.
IPTC Category
(deprecated field)
deprecated IPTC Category.
IPTC Other Categories
(deprecated field)
deprecated IPTC Other Categories.
Description WriterName of the person who wrote the description.
Intellectual GenreIntellectual genre.
Job IdentifierA number or identifier needed for workflow control or tracking.
InstructionsInformation about embargoes, or other restrictions not covered by the Rights Usage field.
Name of Org ShownName of the organization or company featured in this image.
Code of Org ShownCode from a controlled vocabulary for identifying the organization or company featured in this image.
Leading/Trailing Spaces
in a Text Field
Lists which text fields contain a leading and/or trailing space
Multiple Embedded Spaces
in a Text Field
Lists which text fields contain more than one embedded space in a row, “Like    This”
Plus VersionThe version number of the PLUS standards in place at the time of the transaction.
Model AgeAge of human model(s) at the time this image was taken in a model released image.
Minor Model AgeAge of the youngest model pictured in the image, at the time that the image was made.
Model Release StatusSummarizes the availability and scope of model releases authorizing usage of the likenesses of persons appearing in the photo.
Model Release IDA PLUS-ID identifying each Model Release.
Additional Model InfoInformation about the ethnicity and other facets of model(s) in a model-released image.
Source TypeThe type of the source of this digital image, selected from a controlled vocabulary.
Property Release StatusInfo on the availability of property releases.
Property Release IDPLUS-ID identifying each Property Release.
Person Shown in ImageIPTC person-shown field.
Has “dateTimeOriginal” fieldA simple yes/no on whether the “dateTimeOriginal” field is present.
Has “dateTimeDigitized” fieldA simple yes/no on whether the “dateTimeDigitized” field is present.
Has “dateTime” fieldA simple yes/no on whether the “dateTime” field is present.
Has “dateCreated” fieldA simple yes/no on whether the “dateDreated” field is present.
Date fields agree?Reports on whether the “dateTimeOriginal”, “dateTimeDigitized”, and “dateTime” fields are the same

Example responses include:

  • All are empty
  • All are the same
  • They differ
By HourGroups images by the hour of the day in which they were taken.
By DateGroups photos by date they were taken on.
By Day of WeekGroups images by the day of the week that they were taken on.
By MonthGroups photos by the month they were taken in.
Date/Time RangeIsolate photos taken within a specific range of dates, times, and/or week days. Useful for finding all photos taken during a particular season, for example.
Master Image File
Bit Depth / Color Mode***
of the master image file
The bit depth (per channel) and color mode (e.g. RGB vs. CMYK) of the master image.
Color Space***
of the master imgage file
Color space (e.g. sRGB, AdobeRGB) of the master image. Note that the color space for a raw file is specific to the camera make and model; raw files appear here as "unknown".
Speical: List Data Fields***Lists raw metadata field labels and values found in the most-selected master image file. This is useful to find appropriate field names for the “User-Specified Master-File Data Field” search item described immediately below.

With this special item, only one photo/video is processed, regardless of how many are selected. This is sort of a “raw” version of my Metadata Viewer plugin; this item is useful to find the exact master-file field label for use in the “User-Specified Master-File Data Field” search item described immediately below, while the Metadata-Viewer plugin is far superior for general “what metadata is in this master file?” browsing.

User-Specified Field***
of the master image file
Explore the specific master-file metadata field entered by the user.

You can enter any metadata field known to ExifTool; you can see the list of raw fields for a specific master file by selecting it and applying this plugin's “Special: List Master-File Data Fields” search item, described immediately above..

Results Dialog

After the plugin does its work, it brings up a dialog to display the results, for example:

I've spent considerable energy on tailoring the presentation and default sort for each of the 175 criteria the plugin supports. In the “Lens” example seen here (which Adobe's Library Grid Filter does support, though not as well), I take care to sort the lenses by focal length, and to pretty up the presentation (e.g. “50 mm” instead of “50.0 mm”).

Some features of the results dialog:

  • Click on an “isolate” button to create a collection named for the criteria and result, populate it with the appropriate photos, and switch to it.

  • Click on the “Isolate All...” button to create all the individual collections and dismiss the dialog.

  • Click on two or more checkboxes to enable an “Isolate Combined Checked Items” button that creates one special collection with all the photos of the checked rows.

  • Click on a column header to toggle the display sort.

  • Click on a photo- or video- count number to display some percentage information. In the example above, clicking on the “8,306” of the “Voigtländer 125mm f/2.5” row reveals that 31.9% of the target photos were taken with that lens (because it's such an oh-so-sweet lens whose results I adore).


This plugin is distributed as “donationware”. I have chosen to make it available for free — everyone can use it forever, without cost of any kind — but unless registered, its functionality is somewhat reduced after six weeks.

Registration is done via PayPal, and if you choose to register, it costs the minimum 1-cent PayPal fee; any amount you'd like to add beyond PayPal's sliding fees as a gift to me is completely optional, and completely appreciated.

Note: a Lightroom major upgrade, such as from Lr4 to Lr5, de-registers the plugin in the upgraded version, so if you want to maintain registration, a new ($0.01 if you like) registration code is needed in the upgraded version. It makes for a hassle every couple of years, I know. Sorry. See this note for details.

For details on plugin registration and on how I came into this hobby of Lightroom plugin development, see my Plugin Registration page.

Version History
( Update Log via RSS )

20140913.85 Added Olympus E-M1 to the camera crop-factor database. (Why Olympus can't include the crop factor in the metadata like most everyone else is beyond me...)
20140902.84 New build system
20140820.83 Added new items for lens-correction profile name, chromatic aberration, and defringe.

Updated the "White Balance" item to note which images have the same white-balance temperature and tint as the most-selected photo.

The "Develop differs from most-selected image?" item had actually referred to the first image selecte, not the "most-selected image". It now refers to the most-selected image, unless there isn't one, in which case it reverts to the first image.

20140801.81 Added new "Keywords, individually" items.
20140731.80 Registration fix for Lr5.6
20140730.79 Added "Video Size and Rate"

The “has ...” items for dates (for dateTimeOriginal, dateTimeDigitized, and dateTime) now actually work.

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.75 Sigh, had a bug in the Creative-Cloud support.

Now supports Lr5.5+ Creative-Cloud Installs.

20140706.73 Added some more keyword-related search items.
20140704.72 For some reason (bug in Lightroom?), Lightroom is not following the plugin's direction on how large to make the result dialog, so in an attempt to work around it, I've added a "debug options" link in the upper-right corner of the item-selection dialog.
20140701.71 Added some debug logging to track down a display-size issue.
20140630.70 Build-system update

Added "By Month" data item.


Added "By Date Taken" data item. The Library Grid Filter is probably better for browsing by date, but this might be useful if you want to automatically create collections based on the date.

Updated some of the other date-related items to try harder to find a date associated with the photo.


Upgraded to the embedded copy of ExifTool to version 9.60.

20140506.66 Added a new search criteria: file writeability (e.g. readonly or not)

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


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


Worked around a Lightroom bug that stopped the new "list master-file data fields" from displaying properly on Windows.


Added the “User-Specified Master-File Data Field” item, giving the plugin the ability to explore arbitrary master-file metadata.

Added the “Special: List Master-File Data Fields” item to allow you to quickly see the raw metadata field labels need for the “User-Specified Master-File Data Field” item.

Upgraded to the embedded copy of ExifTool to version 9.53.

20140311.60 Wow, I'd really screwed up the calculations for the “Total Exposure (camera Ev)” and “Total Effective Exposure (effective camera Ev)” items. In both cases I had the sense of adjustment for ISO speed backwards, and in the latter case I had the sense of adjustment for the Lightroom develop setting backwards, and in some cases could use the wrong number to begin with. Doh!
20140302.59 added the following items to the list of explorable items: amount of Contrast applied in Develop, amount of Highlights applied in Develop, amount of Whites applied in Develop, amount of Blacks applied in Develop, amount of Vibrance applied in Develop, amount of Saturation applied in Develop, and the IPTC “Person Shown in Image” field.
20140212.58 Updated the file-size counting done for “File size (bytes)” and “Smart-Preview Status” to better indicate the file-size status for offline files.

Added “Most-Recent Update Date” and “Number of Updates” items.


(Lr5.2+) Update the “Clone/Heal Corrections“ item to report the total number of corrections for the inspected photos, and to report the median number of corrections among photos with at least one correction.


Added more detail to the disk-usage summary presented for the “File size” and “Smart-Preview Status” items. Fixed a bug in how previews for vidoes are reported.

Cite in the result-dialog title the number of items inspected.


Result dialog for the “File Size” item could end up too big for the screen.

Upgraded to the embedded copy of ExifTool to version 9.46.

20140104.53 Updated a bug with “Cropped Amount”, and renamed its "100%" result with "Almost Completely Cropped Away".
20131230.52 Updated the “File Currently Available” item to report whether a Smart Preview exists.
20131128.51 Updated how megapixels, video duration, and focal length are displayed, to avoid apparent duplicates (such dual "20.0" and "20" results).
20131125.50 Made the “Expousre Adjusment” results look nicer, and made it clear that results are displayed to the nearest ⅓ stop.
20131124.49 Added “Flag Status” item
20131122.48 Fixed error with “Expousre Adjusment” item.

Fixed a bug in the "File Size" stuff added yesterday.


Discovered that at some point Lightroom developed a bug that makes reporting the byte size of offline images impossible. The plugin report now notices when this happens and points out that the data is not to be trusted.

Added an extra report to the "File Size" item to show the disk space used by all the selected items (the masters, smart previews, and normal previews). However, it currently doesn't work correctly for offline images due to the Lightroom bug cited above.


Update for OS X Mavricks.

Updated the Image::ExifTool library to version 9.39.

20131014.44 Found that with certain settings some math errors would pop up.

Update how the aspect-ratio criteron are computed. Should give more reasonable results.

Updated the Image::ExifTool library to version 9.38.


Added new criteria: "Leading/Trailing Spaces in Text Field" and "Multiple Embedded Spaces in Text Field".

You can now tell which results you've isolated... the "isolate" button becomes "view" once the associated collection has been created.


Added "Unconstrained Crop" criteria.

Fixed a bug with the "Lens Corrections" item, which always indicated that "Chromatic Aberration" and "Constrain Crop" were set for an image regardless of whether they were.

More attention to the default display order of some results.


Added new criteria: "By Weekday", "By Hour", and "Date/Time Range".

An update to track a change in Lightroom 5.2 in how develop clone/heal spots and strokes are encoded.

Made it much easier to see relative percentages in the results... just click on any total and all totals are replaced with percentages.

20130925.39 Updated the camera crop factor database.
20130911.38 The "Total Effective Exposure (effective camera Ev)" criteria couldn't be selected.
20130910.37 Added a bunch of cameras to the crop-factor database.

Added a new criteria, “Aspect Ratio: compared to...”.

Renamed “File Extension” and “File Extension (case-insensitive)” to “File Extension (case-sensitive)” and “File Extension” respectfully, and swapped their order in the list, because Lightroom generally runs on case-insensitive file systems, so case insensitive is the norm, and case sensitive the oddball.

Gave the spell-checker a much needed run.

20130908.35 The “File Currently Available?” item relied on a component of Lightroom's internals that seems to be buggy, so I rewrote it to check the disk directly for the presence of the master image file.
20130830.34 Added a few more cameras to the crop-factor database.

Added new exploring criteria “Has plugin custom metadata?”. If you generate the spreadsheet-data file, it'll include the list of IDs for the plugins involved.

Changed the label “Spot-Healing Corrections” to “Clone/Heal Corrections” and updated it to include clone/heal strokes as well as spots, producing results along the lines of "“11 corrections (2 clone spots, 2 heal spots, 3 clone strokes, and 4 heal strokes)”.

Updated the list of develop changes (as generated by th “Develop differs from most-selected image?” criteria) to include more detail about clone/healing strokes and spots. Also, removed “Orientation” from consideration as a develop change, to match that develop-settings copy/paste doesn't include the orientation. You can deal with orientation via the newly-added the “Orientation With Respect to Image Sensor” criteria.


Added the ability to compare develop settings against the most-selected image. It's a work in progress. See documentation for “Develop differs from most-selected image?” above.

20130826.31 Some fixes to the previous changes for Windows.

Added several new search criteria: “File Extension (case insensitive)”, “Lens Description (built from master-file data)”, “Bit Depth and Color Mode”, “Color Space”,

Made searching large numbers of images a bit more efficient, and allow the searches to be canceled midway.

In the criteria-picker dialog, added a direct link to the full criteria list.


Added the ability to save the raw data to a TSV (tab-separated values) file.

20130721.28 Added Canon 650D to the camera sensor-crop database
20130629.27 In some rare cases photos with a Process Version of 2003 would show up as "Unknown".
20130626.26 Added a bunch of data to the crop-factor database
20130620.25 Updated the "Color Treatment" item to partition color photos based on their amount of saturation/desaturation.
20130613.24 Better support for plugin revalidation.
20130611.23 Yet another Lr5 update

Updated the "Lens Corrections" item for Lr5, and added a new "Lens Corrections (Upright only)" item.

Added an item related to whether smart previews exist.

Added a bunch of new crop-factor data, and corrected the crop-factor data for the Canon Powershot G1 X.

(Note: Lr5 painted heal/clone brush strokes are not yet taken into account.)

20130501.20 Update for Lr5

Added "Folder Name" and "Path Name" to the list of search items.


Added the “Has Basic Tone/Presence Edits” search item.

Fixed the “dateCreated” search.

20130412.17 Build system update.
20130330.16 Added some Ricoh cameras to the crop-factor database.
20130328.15 Fix for the registration system.

Added "Total Exposure (Ev) and Total Effective Exposure (effective Ev).

Filled in some areas where the docs were not yet written.

20130219.13 Added some notes to the aspect-ratio results to denote common aspect ratios (e.g. 16:10 is a wide-screen monitor)
20130218.12 Added some extra text fields (title, caption, etc.)

Added the ability to identify images with sidecar files.

In the criteria-selection dialog, warning messages would sometimes get truncated.

20130212.10 Added some date fields
20130209.9 More build-system maintenance
20130206.8 Tweak for my registration system
20130124.6 Added a bunch of Canon cameras to the crop-factor database.

Computation for the megapixel notation for "Width x Height (post-crop)" was wrong.

Many of the pixel-size items crashed when used on videos.


Focal-Length 35mm crashed if a photo didn't have focal-length data.

Added a bit of buffer to the dialog-height calculations to help ensure that the dialog doesn't grow taller than the screen.

20121113.3 Made "Dimensions" available for video.
20121020.2 Added "Lens Corrections"
20121019.1 Initial public release.

Comments so far....

This feature may be useful for something else (ie Catelog Management).

My catelog is 1.2Gb and growing. I am not worried about 1.2 GB disk space, but backup less frequently than I should when exiting Lightroom because of the length it takes.

I have explored my catalog and discovered the following.

Catalog Size 1.2 Gb
Metadata Table 515 mb
History Table 492 mb
Largest 75 images history Approx 253 mb
Largest 200 images meta data Approx 35 mb

It would be extremely useful to find all images which consume individually say more than approx 1mb or 10 mb of catelog space (or some other sensible number / criteria).

This figure could be calculated approximately by querying the Metadata and History on the key of image number (len of string fields within record).

I may have a collection of images which I no longer need or could refine just sitting in my catalog. If this selection was available in this tool, I could isolate these massive metadata hogs (remove, delete, refine, export to an archive catalog,etc) and massively improve the internal storage needs of my catalog.

I welcome any comments.

Unfortunately, Lightroom doesn’t give a plugin insight into much of this. Something running outside of Lightroom could perhaps access the SQL database directly to figure this out, but this seem dicy to do while Lightroom is running. —Jeffrey

— comment by Matt O'Brien on October 23rd, 2012 at 12:35am JST (1 year, 11 months ago) comment permalink

Hello from France,
Great little plug-in – again !
I cannot try it right now, I have only an XP computer available ; I’ll try it tonight on my home computer with LR4.
There is one thing I’d like to have and do not see in your list : would it be possible to find pictures that Lightroom cannot read except for a small preview ? I have sometimes this problem with pictures I get from the internet, always black & white. Lightroom displays a small preview and a warning sign in the top right of the icon of the picture. Here is an example of such a picture (I could only test it was in error on my LR3 on this XP computer, but usually the problem is the same on LR4, I’ll double check tonight) :
I usually get batches of pictures, then have to open all of them to see which one are in error. I then just open these (usually with Irfanview) and save them without doing anything. That solves the problem, but I would like to have just the pictures in error without having to test all of them…
The plug-in is great already, that would just help me to solve one more problem.
Thanks for your great work, I like a lot your plug-ins
I don’t know of a way for a plugin to find out that kind of status, but you might consider trying this: select all the newly-imported photos in the library and click on “Auto Tone” in the quick-develop panel, then set the grid sort to “Edit Time”, and ones at the bottom require your Irfanview attention. —Jeffrey

— comment by Laurent on October 23rd, 2012 at 11:18pm JST (1 year, 11 months ago) comment permalink

Hello Jeffrey,
Great idea ! I tried it on LR 3.6 (again, I’ll try on LR 4.2 tonight), and it works… well, not exactly as expected, but it seems the process of auto-toning pictures stops when encountering an image in error. So, once sorted per modification date, the picture at the beginning of the not-modified pictures is one of the pictures in error… At least that helps !
Thx for taking time to find a solution, and continue your great job with your plug-ins !

— comment by Laurent on October 24th, 2012 at 4:57pm JST (1 year, 11 months ago) comment permalink


A VERY useful plugin I have been dreaming about would allow the storage of “smart” filters and collections within actual image folders. One of my major (insert profanity) peeves with LR is that collections are stored way off down at the bottom, where they re really inconvenient to get to and use. IN fact, theyr;e USELESS where they sit, since I have to break my workflow just to use them (insert more cursing). I want these to be accessible from a normal project/image folder. I would pay real money for this kind of functionality.

You would know better than me, but I presume it would be possible to create a (hidden?) metadata file that a plugin reads, and store that metadata file in the actual project folder…yes? What about also storing Develop presets in a separate file, also in the real filesystem project/file folder? That would allow a folder of a job to be mostly portable from one machine to another without the tedious job of exporting/importing a library for one simple folder exchange.

I dislike and cannot use Capture one for a range of reasons, but their Sessions are one good way to do this. I had to make a very difficult choice between LR and Aperture, in which LR won, but I was not happy with the compromise. I very much prefer the Aperture way of allowing the library hierarchy to me stored and accessed with albums, projects, and folders.

Good ideas all, but as you’ve discovered, far from how Lightroom was designed. I don’t seen any easy way (or even hard way) to do these things. )-: —Jeffrey

— comment by Nathan Padilla Bowen on October 27th, 2012 at 2:42am JST (1 year, 11 months ago) comment permalink


Just tried it. You are the man! I sometimes have 20 versions of a file, at different sizes and formats from different uses. Now I can see them very quickly in a clean, organized collection.

Next, stack multiple filters from one interface?

Donating now…thanks for the useful plugins.

…San Diego, CA

— comment by Nathan Padilla Bowen on October 27th, 2012 at 2:49am JST (1 year, 11 months ago) comment permalink

Trying your example of copyright info… I ended up with 57 entries! Should be around half that. When using the metadata filters to find erroneous location info, I find I use it like a Smart Collection so that when metadata is “fixed”, it drops out of the filter. Is it possible for this plugin to create Smart Collections vs normal when isolating? I fixed several erroneous groups of copyright names but the collections still contain the now fixed entries under a collection name that doesn’t match the data.

No, that’s the problem… the smart-collection rules are not expressive enough, which is why I made the plugin in the first place. If you could do it all with smart collections or the grid filter, we could dispense with this plugin altogether. As it is, you can quickly reapply the same search on the current photos to re-reflect the new reality. —Jeffrey

— comment by JasonP on November 13th, 2012 at 6:53am JST (1 year, 10 months ago) comment permalink

Hello, another great plugin idea as usual. I’ve come across an issue when trying to examine my photographs by “focal length 35mm equiv”. Shortly after the progress dialog displays “Analyzing…” I get an error message stating “Items:258: bad argument #2 to ‘?’ (number expected, got nil). I’m assuming this is due to me having some bad exif data somewhere in my images (the “focal length” metric works just fine, and properly shows “(unknown)”). Is there anything else I can do to help debug this problem?

- Maryland, USA

Sorry about that… I’ve (finally) pushed a fix that takes care of it. —Jeffrey

— comment by Eric on December 11th, 2012 at 8:21am JST (1 year, 9 months ago) comment permalink

Hi. I love all your lightroom tools, and I’ve just come across this one because I’m trying to filter files based on exifdata that LR doesn’t read (but exiftool does).

The problem is that your tool doesn’t include the specific fields I’m looking for, so… If possible, could you think about adding a custom search to this? Just a key/value search (based on the exif tag name) or a list of all values for a key.

In my specific case, I’m trying to tag different cameras of the same model via the serial (LR reads some serials, but not from this camera). Also trying to add keyword tags for picture effects (e.g. “pop color”) from the camera.

Thanks again!

Sorry, but Lightroom doesn’t make that data available to the plugin. It wouldn’t be impossible if I fire off a separate process to check the photos, but it would be extremely slow, having to read every byte of every photo… potentially hundreds of gigabytes… and could take hours for one search. It just doesn’t seem worth it. )-: —Jeffrey

— comment by Mark on January 6th, 2013 at 2:58pm JST (1 year, 8 months ago) comment permalink

Hi Jeffrey

I have a (minor) bug with your Data Explorer: when I am exploring a descriptor with lots of values (Image Width in my case) the “Dismiss” button is shown below the bottom of the screen. The explorer window doesn’t have any resize controls (in fact, the title bar is shown in gray as if it wasn’t the top window), and if you don’t know that the Dismiss button is there, it isn’t clear what to do.

I try to calculate the maximum size of the dialog down to the pixel, but Lightroom doesn’t make it easy, so I’m off somewhere. I’ve just pushed a new version that is less aggressive… if it’s still bad, please email a screenshot and I’ll try to find where my calculations are off. —Jeffrey

— comment by Alan Harper on January 7th, 2013 at 3:34am JST (1 year, 8 months ago) comment permalink


is there a possibility to check also to the points (develop / Basic module) : highlights, shadows, whites and blacks with your plug in data explorer? I am afraid, I could not find it.
If not, will you integrate it in the future?
Thanks & rgds
Pit / Germany

I added the “Has Basic Tone/Presence Edits” search item to a new version I just pushed… does that help? —Jeffrey

— comment by Pit on April 14th, 2013 at 3:20pm JST (1 year, 5 months ago) comment permalink


Its possible to build in a search function similar “same develop settings” ?
I work with the function “synchronize develop settings”
I ignore or forgot by mistake some of these images.
Thus, i could filter them later out.
Is this possible?

Best greetings Wolfgang

As of version 20130828.32 there’s an experimental option to search for develop changes. —Jeffrey

— comment by Wolfgang on May 19th, 2013 at 9:44pm JST (1 year, 4 months ago) comment permalink

I’d also like to search/sort by bit depth and color profile – is this possible?

THANKS Wolfgang

Not easy at all, because the data is not in Lightroom, so it’d end up having to read every master image from disk… a really costly procedure. —Jeffrey

Update Aug 2013: I’ve added this to the plugin. —Jeffrey

— comment by Wolfgang on May 30th, 2013 at 7:54pm JST (1 year, 4 months ago) comment permalink

Jeffery – Hi from the UK. I don’t know if it’s possible or practical to implement, but could your Data Explorer plug-in be made to search through the custom metadata fields added to images by some of your other plugins? As an example, if I’ve added various Creative Commons licence details with your Creative Commons plugin, it would be really helpful to have the Data Explorer isolate the images into the various different licence types.

Thanks for all your efforts on producing these plugins – I think I’m up to six that are part of my workflow now!


That’s a good idea that I’ll look into, but in the case of my Creative Commons plugin, you can directly group images via the Library filter. —Jeffrey

— comment by Roger Byrne on June 28th, 2013 at 6:30pm JST (1 year, 3 months ago) comment permalink


I am certainly happy with your stuff. Well done and thanks.

Would it be possible in a future releaee to search on highlight clipping and shadow clipping. This would be helpful in restricting the search to just those images that require attention (after Photoshop editing).

Many thanks Jeffrey,

Best wishes,


Unfortunately, no, that’s not something that a plugin has access to… it can look at the develop settings, but clipping is at the other end of the render pipeline. —Jeffrey

— comment by Denis Bennett on July 8th, 2013 at 3:33am JST (1 year, 2 months ago) comment permalink

Yesterday, I downloaded and installed your Data Explorer plugin in my Lightroom 5. My first use of it was to find all photos that were processed under Process Version 2003, to see if any of them might benefit from being re-processed using Process Version 2012. Now, as you know, one of the bugs that Adobe reported when it released LR 5 is:

“Photos adjusted using Process Version 2003 incorrectly display a “Post Crop Vignette: Paint Overlay” History step. Selecting a subsequent History State can reset existing settings that follow that state in the History panel. This reset cannot be undone, effectively deleting any settings that have been applied after the selected History State. This only occurs with images adjusted in PV2003.”

Much to my surprise, when I opened my PV 2003 photos from the collection of PV 2003 photos created by your Data Explorer plugin, this Post Crop Vignette: Paint Overlay was gone (even though it had appeared previously), and the entire History panel worked as expected. You can see a screen capture of this here: http://forums.adobe.com/message/5550293#5550293

So, my question is: does your plugin inadvertently fix this problem somehow? Or is this just one of those amusing coincidences where the two events have nothing to do with one another? I’m not expecting a quick answer, or for you to make this a priority, but if anything pops into your mind, let us know.

Great plug-in, by the way!

The plugin doesn’t update the per-photo catalog info at all, at least not intentionally, so I’d be surprised if it had any effect on the bug, but then, bugs are bugs because things aren’t going as planned, so who knows. —Jeffrey

— comment by Paige Miller on July 30th, 2013 at 8:50pm JST (1 year, 2 months ago) comment permalink

Hi Jeffrey,

Data Explorer is a great plug-in. Thanks very much for creating it.

Is it possible to extend it to search on the date an image was added (imported) into Lightroom?


Unfortunately, no, Lightroom doesn’t expose that data to plugins. —Jeffrey

— comment by Dave on August 12th, 2013 at 7:43am JST (1 year, 1 month ago) comment permalink

Hi Jeffrey,

Thanks for a tremendously useful plug-in and a wonderful website to back it up.

I have 2 questions detailed below:

1) I see that after clicking “isolate”, the results of a single search become a collection. I can then exit Data Exploreer, go into the collection and re-open Data Exploreer to perform a second search to further refine the results. This allows me to build up a search using multiple criteria, but it requires constantly cycling in/out of Data Explorer and navigating my way through intermediate collections. Is there any way to do this as a single search using set logic? (i.e. same type of interface as Smart Collections where the “+” box allows multiple criteria).

2) The results of Data Explorer are “classic” collections, not smart collections. Since I haven’t found a solution to my first question, in order to keep the results of a particular search current, I need to go through all of the cycling mentioned above. It would be FANTASTIC if the results of Data Exploreer were output as a smart collection, so that complicated multiple level searches would be kept current and remain easily editable.

Ideally, what I’m looking for, is the ability to construct searches across multiple criteria and have the results become smart collections. In addition, if I want to modify the smart collection, I would like a dialog box from Data Explorer with similar functionality as “Edit Smart Collection”.

Again, thanks for such a powerhouse plug-in!
Connecticut, USA

Neither are currently possible, #1 because I haven’t built it yet, and #2 because Lightroom doesn’t allow for it… there’s currently no way to have the plugin automatically update data when images are added or changed. )-: —Jeffrey

— comment by Adam on August 14th, 2013 at 9:51pm JST (1 year, 1 month ago) comment permalink

Hi Jeffrey,

Thanks – this is a very useful plugin! I currently am using it in 5.2rc, and will be adding this plugin (and one or to other ones) to my set of jf registered plugins once 5.2 final is released.

I was just wondering – is there a quick way through this plugin (or another one) to find photos that have been affected by the 5.0 “Post Crop Vignette: Paint Overlay” bug for photos with Process Version 2003?

I know I can isolate the Process Version 2003 ones, but only a subset of those have been affected (and I might have updated the Process Version on some after the buggy operation was applied). If it can’t be done, I’ll just have to pay attention to the develop history more or spend some time doing a brute force check of all my files.

I recently have done a significant cleanup of my library (deleting duplicates, moving folders) and only after I started doing this I noticed that this bug existed, so going back to my library before the bug was introduced is not much of an option.


I don’t know of any way to programatically isolate those photos… perhaps first filter on PV2003, then on Vignette… will that get you close? —Jeffrey

— comment by Geoff on August 25th, 2013 at 3:04am JST (1 year ago) comment permalink

Hi, I am using this plugin for quite a while and it serves me well. Thanks.
The one request I have right now is related to how the Lightroom handle the Nikon 70-200/2.8 VR II + Nikon 1.7x TC II. Lightroom do not distinguish the lens with or without the 1.7TC (may be it’s the camera’s fault). So the only clue I have is the metadata field “maximum aperture value” which is 2.8 vs 4.8. For those overlapping focal length and aperture value, this field is the only way to tell if it has a 1.7TC on. So could you add this field in Data Explorer?
Many thanks!

Unfortunately, that field is not available from within Lightroom. I solve this problem myself by running a script on my images before importing into Lightroom, to identify camera/lens settings that are wrong and update them to what I want. It’s a real pain that this can’t be done in Lightroom. —Jeffrey

Update Aug 26 2013: I’ve gone ahead and added this to the plugin. It’ll be slow, but give it a try.. look for “Lens Description” —Jeffrey

— comment by Kolen on August 25th, 2013 at 9:21am JST (1 year ago) comment permalink

Hi Jeffrey,

When filtering with the criterion “File Currently Available?”, photos Lightroom says are offline (and really are offline) are showing as available. This happens whether I select or deselect all photos in a folder. Is this a bug or do I need to do something more than selecting the criterion and clicking Begin?

Thanks for your great work!

Hmmm, it seems to be a bug in Lightroom. I’ve just pushed a new version of the plugin that works around it. Thanks for the report. —Jeffrey

— comment by Chris on September 8th, 2013 at 2:09pm JST (1 year ago) comment permalink

is it possible to select all images with clone corrections.
they are imported not really correct n LR5.2, the feather is not set ok…

… and then change the feather value from 75 to 50 :-)

— comment by Stefan on September 19th, 2013 at 8:31pm JST (1 year ago) comment permalink

Does this plug-in (or any other plugins) have the ability to isolate dates and times individually?
Something like:
ie. Show all pictures taken in December (to get all holiday pictures)
ie. Show all pictures taken on December 25th (to get all Christmas day pics)
ie. Show all pictures taken between 8pm and 5am (to get all night photography)
ie. Show all pictures taken between June->August AND 6pm->8pm (to roughly find sunset pictures)

I’ve added a few new criteria to the Data Explorer, including “Date/Time Range” where you can isolate on any combination of date span, time-of-day span, and specific days of the week. I’d done all the math to compute the angle of the sun above/below the horizon for a particular location and time, but then realized that I can’t use it because it’s not known explicitly what timezone the photo’s capture time is, so there’s not enough data for the calculation. )-: —Jeffrey

— comment by Matt on September 25th, 2013 at 1:35am JST (11 months, 25 days ago) comment permalink

I want to be able to filter all images where LR has put a ‘Reset’ into the History steps. I hoped it would be in Data Explorer, but no luck. Can it be done?


Bob Frost

No, history is not exposed to plugins at all. )-: —Jeffrey

— comment by Bob Frost on September 30th, 2013 at 5:29pm JST (11 months, 19 days ago) comment permalink

Hey Jeffrey,

Thanks for all your hard work! I love your plugins.
Would it be possible to split the ‘Most-Recent Update Date’ so it does not combine the developments settings like the basics, tone curve etc bunched together with say flagging or starring and key wording? I do understand that it’s basically all metadata in the end. So this would probably take bit of coding to extrapolate and qualify it? I would want to mostly see when basic edits was performed and on which date. Setting flags, keywords, ratings, labels or colors sometimes is not seen as an edit in my workflow.
I love the way you split it into hourly where the same day applies.

Looking forward to hearing from you all the way from the tip of Africa :-)

Unfortunately, no, Adobe has one date that they bump up for any kind of change. I’ve been asking for separate pixel/non-pixel data for years, but so far to no avail. —Jeffrey

— comment by Paul on March 3rd, 2014 at 10:38pm JST (6 months, 16 days ago) comment permalink

Hi Jeffrey and thanks for your great collection of Lightroom plugins, I love them!

Hovewer I this plugin, I think I found an coding error!

The problem is in the “Total Exposure” and the “Effective EV”. I think you reversed the effect of ISO. For example, if photo is taken with shutter speed 1/30 and aperture f/2.0 and ISO 100, your plugin calculates EV7 which i agree on, but if of the shutter and aperture remains the same, and i rise the ISO to 400, (iso +2 steps in other words), your plugin calculates EV9, but it should be (as i calculate it) EV5.

I believe you’re right. It turns out that I had a number of mistakes in how I calculate “effective Ev”… for some reason, the subject just seems to turn my brain to mush…. but I think I’ve sorted it out (as of version 20140311.60). Thanks for the heads up! —Jeffrey

— comment by Fredrik Holmberg on March 9th, 2014 at 9:34pm JST (6 months, 10 days ago) comment permalink

Thank you Jeffrey!

Now it works great! it’s very cool with this possibilities with metadata and statistics! :)

— comment by Fredrik Holmberg on March 13th, 2014 at 10:49pm JST (6 months, 6 days ago) comment permalink

Greetings from the UK! Not sure if this is the right place to ask, but is there any way of finding all images that have been published to Flickr that have a non-null Comment field, or ‘Favorite count’? That data displays underneath the standard metadata in LR, presumably under control of the Flickr plugin. –Michael

No, unfortunately, Adobe doesn’t expose that data to the plugin nor to the user. You’d think a sort via most-recent comment would be natural. —Jeffrey

— comment by Michael Maggs on March 24th, 2014 at 3:01am JST (5 months, 26 days ago) comment permalink

Jeffrey, is it possible to make the Data Explorer plug-in or any other plug-in find images for which in-camera or in-lens image stabilisation has been used ?

I just pushed version 20140327.61 of Data Explorer, which now includes a “User-Specified Field” criteria. If you can figure out whether your camera writes stabilization info to the master-file metadata, and what its field name is, you can now explore it. —Jeffrey

— comment by Alan on March 24th, 2014 at 1:44pm JST (5 months, 26 days ago) comment permalink

This plugin will be of great help to me to determine my buying choice for my next camera and lenses. Based on my 50k pictures I will see what light (EV) I most frequently shoot in and it will help me determine which lenses I should invest more in order to have better quality pictures in the future. It might be a tideous task but with your plugin it will be much easier and quicker to come up with an analitical way to make my choice.

Thank you once again for the great work that you are doing. Lightroom is a great tool but your plugins makes it so much more awesome.

— comment by jgrzadka on May 9th, 2014 at 11:06pm JST (4 months, 10 days ago) comment permalink

Is there a way to sort by resolution or ppi?

You mean by pixels per inch on the sensor? No, sorry, not that I know of. That information may not be known for many images anyway…. —Jeffrey

— comment by Ahmet Dereci on June 16th, 2014 at 2:27pm JST (3 months, 3 days ago) comment permalink

Shouldn’t I be able to group by date? I’d like to create a collection for each date I shot at Monkey Bay
I can’t see how.

thanks a lot!

I’d not had it because the Library Grid Filter already offers a great way to explore by date, but I’d not thought about the collection point of view, so I just added “By Date Taken”. —Jeffrey

— comment by Charles e Uibel on June 29th, 2014 at 11:34am JST (2 months, 20 days ago) comment permalink

Hi Jeffrey.
Something even more useful date would be to group by calendar month, because that is not easily accessible in Lr. This would allow a quick review of all photos taken in say August of any past years to reveal what we could expect to find in the coming August.

- Alan

I went ahead and added it, but note that you can do Date Range already, perhaps a more specific way to checking out the seasons… —Jeffrey

— comment by Alan on June 29th, 2014 at 3:54pm JST (2 months, 20 days ago) comment permalink

omg thanks. I have 800 days at Monkey Bay.

— comment by Charles e Uibel on June 29th, 2014 at 8:17pm JST (2 months, 20 days ago) comment permalink

Grouping by kewords(count) would be helpful for me.

Good idea… I’ve added it! —Jeffrey

— comment by Charles e Uibel on July 6th, 2014 at 11:25am JST (2 months, 13 days ago) comment permalink

Hi, is it possible for Data Explorer to break out into individual keywords?

For instance, I may have a photo that’s tagged with 3 keywords: Apples, Oranges, and Pears.

When I run Data Explorer using “keyword list” as the criteria, I’m seeing a single entry “Apples, Oranges, Pears”. I would like it to show an entry for each of the keywords.

Is that possible?


Sure, I just added it in version 20140801.81 —Jeffrey

— comment by Joe on July 31st, 2014 at 10:58pm JST (1 month, 19 days ago) comment permalink

Thanks for adding that feature to the keywords criteria! I let the author of Aperture Exporter know. He has other customers looking for a tool such as yours. With this new feature, it will help many of them.

— comment by Joe on August 2nd, 2014 at 6:04am JST (1 month, 17 days ago) comment permalink

Hi. I am not sure if I have asked you before.
Due to some stupid reason, an unknown amount of photos in my catalog has been synced to the same white balance. I know the synced valued (Temp 5450, Tint 25). And I was trying to use Data Explorer to search the photos that has this exact white balance. Currently if I search it, all of the are “custom” and I can’t tell which is of that settings.
Could you add that search field so that I can search the temp and tint?
Thanks so much.

Upgrade the plugin, select one of the photos with the value you want to find, and then try the “White Balance” setting again. —Jeffrey

— comment by Kolen on August 6th, 2014 at 8:48am JST (1 month, 13 days ago) comment permalink

Thanks so much for updating it so quick. I can successfully hunt down the photos with that White Balance with “Custom (same as most-selected image)”. I didn’t realize “same as most-selected image” means identifying those that share the same white balance.
Thanks so much.

That’s what I updated… that hadn’t been there before. I just realized that I’d forgotten to update the online docs for “White Balance”, but I’ve done so now. —Jeffrey

— comment by Kolen on August 6th, 2014 at 6:06pm JST (1 month, 13 days ago) comment permalink

Hi! Would it be possible to split the Lens Corrections in individual parts? I am interested in isolating all photos where CA or Defringe have been applied and also it would be good to be able to isolate based on Lens Profile alone.

Seems reasonable. I’ve just added them to the latest version of the plugin. —Jeffrey

— comment by Øystein on August 7th, 2014 at 6:39pm JST (1 month, 12 days ago) comment permalink

Thank you for breaking out the CA and Defringe from Lens Correction, Jeffrey! Much appreciated :)

— comment by Øystein on August 20th, 2014 at 3:41pm JST (4 weeks, 2 days ago) comment permalink

Hi. Great plug-in!

Here’s my scenario: I return from shooting a wedding with about two thousand photos from three cameras. A major issue with weddings is the changing light sources. I adjust each camera’s white balance setting and shoot a Gray Card every time the lighting conditions change. In theory, this should make it very easy to batch-correct the white balance in Lightroom for each group of photos shot in the same conditions, but in order to do this, I need to be able to group them by the numeric “Temp” and “Tint” settings, not just by “As Shot” or “Custom”. I seem to have the latest version of your plug-in, but when I explore by White Balance, all I get is “All [quantity] photos have “White Balance” of “As Shot (same as most-selected image)”. It’s not showing me the photos with the same Temp and Tint. Does that only work when it has been changed? (I.e., “Custom” as opposed to “As Shot”.) If so, that doesn’t help me.

Alternatively, there’s an EXIF field that LR does not read called “LightSource”. I tried using Data-Explorer to sort on this field, but it always returns “All [quantity] photos have Master File EXIF:LightSource Field of ‘unknown’ ” even though this field is populated in every photo with settings such as “Flash” or “Cool White Fluorescent”. I tried sorting on a different EXIF field, such as “Exposure Time” and it works very nicely. Am I doing something wrong?


I’m going to guess that the LightSource item in your files is not in the Exif group, but in the MakerNotes group. In any case, you can let ExifTool figure it out by simply using “LightSource” instead of “Exif:LightSource”. —Jeffrey

— comment by Jonathan Ford on September 10th, 2014 at 4:29pm JST (1 week, 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.

More or less plain text — see below for allowed markup

You can use the following tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Subscribe without commenting