Any Filter lets you search, explore, sort, and export many more photo fields (criteria) than are built-in to Lightroom, including IPTC Extension, GPS location, library properties, develop settings, and plugin fields (748 fields in all). Additional operators include exact text match, matching regular expressions, testing empty fields, distinguishing explicit from implicit ancestor keywords, treating text fields as numeric, and including other saved Any Filters and smart collections.
Define search queries similar to smart collections. Example Any Filters include:
- Has Virtual Copies
- Top of stack, without keywords
- Cropped megapixels less than 1.5 MP
- Aspect ratio (width / height) greater than 3
- Captured Christmas day (any year)
- Keywords include ancestor keywords
- Exact match of explicit keywords (not parents)
- Exactly one person in the keywords
- Exact text match of caption
- Captions starting with number greater than 500
- Within 10 kilometers of Stanford University (GPS)
- Locations Shown in Palo Alto, CA (IPTC Extension)
- Subject Distance less than 1 meter
- Metering Mode is multi spot
- Spot Removal applied
- Develop exposure greater than 1
- Raw camera profile not Camera Standard
Explore field values using a column browser similar to the Library Filter bar’s metadata browser. But Any Filter’s column browser can display any field, including those with thousands of unique values:
Sort photos by one or more fields and save the sorted list in a collection or export the list with the selected fields to a text file:
Any Filter also provides additional commands:
- By Date: filters by dates and date ranges without fussing with the Library Filter bar;
- Fix Burst Times: sets the fractional seconds of bursts of photos so they sort properly in Library.
Try it for free for 30 days. Buy a license at a price you name.
Download and Install
Any Filter requires Lightroom 5 or later, Lightroom CC 2015, or Lightroom Classic. (The newer cloud-focused Lightroom doesn’t support plugins.)
- Download anyfilter.1.56.zip.
- If you’re upgrading from a previous version of Any Filter, exit Lightroom and replace the existing anyfilter.lrplugin folder with the new one extracted from the downloaded .zip. Restart Lightroom and you’re done.
- If this is a new installation, extract the folder anyfilter.lrplugin from the downloaded .zip and move it to a location of your choice.
- In Lightroom, do File > Plug-in Manager.
- Click Add, browse and select the anyfilter.lrplugin folder, and click Select Folder (Windows) or Add Plug-in (Mac OS).
- Lightroom will present a scary-looking, cryptic message: “Your catalog must be updated before it can be used with the following plugin”. Click Update Catalog. This warning is harmless and is shown for plugins that store their own data in the catalog (which is many of them)—but don’t worry, Lightroom ensures such plugins can’t corrupt your catalog.
The free trial is for 30 days—after that, you’ll need to buy a license.
Buy a License
- Buy a license at a price you think is fair:
The license includes unlimited upgrades. Make sure you’re satisfied with the free trial before buying.
- Copy the license key from the confirmation page or confirmation email.
- Do Library > Plugin-Extras > Any Filter > Search.
- Click Buy.
- Paste the key into the License key box and click OK.
Using Any Filter > Search
Creating an Any Filter is very similar to creating a smart collection. If you’re not familiar with smart collections, I recommend you read the Adobe Help before trying to use Any Filter. Any Filter includes all the criteria of smart collections and adds many more.
Any Filter commands are available under Library > Plug-in Extras > Any Filter menu as well as File > Plug-in Extras > Any Filter. Their location under File allows them to be used in any module, while the Library menu is retained for users accustomed to earlier versions of Any Filter.
Applying a Saved Any Filter
When you apply a saved Any Filter, all the images in the currently selected folder or collection are filtered to show just the ones matching the Any Filter. Unlike smart collections, the results aren’t automatically updated as you change images—reapply the filter to see new results.
To apply a saved Any Filter:
- Do Library > Plug-in Extras > Any Filter > Search (keyboard shortcut ALT+L U S on Windows).
- Click Any Filters in the upper left.
- Select one of the saved Any Filters on the right.
- To search only visible photos (showing in Grid mode or in the filmstrip), rather than the entire catalog, check Visible photos only.
- Click Apply, or double-click the selected Any Filter.
- The Library Filter bar will be updated to filter all the images in your catalog that match the criteria of the selected Any Filter.
Each time you apply an Any Filter, the resulting photos are saved in a new collection under the collection set Any Filter Results. Any Filter retains the most recent 8 results. If you want to retain one of the collections permanently, rename it or move it to another collection set. You can disable saving of results by unchecking the option Save results as a collection.
If you don’t want the currently selected folder or collection filtered to show the results, then uncheck Show results using a Library filter. View the results via the collection set Any Filter Results.
To enable reasonably fast searching, Any Filter uses Lightroom’s built-in search facilities wherever possible. But Lightroom has numerous obscure bugs in its search. If you suspect you’re encountering such a bug, use the Avoid Lightroom bugs option. This will avoid the bugs, at the expense of much slower searching.
Applying a Collection or Smart Collection
As a convenience, you can filter using an existing collection or smart collection rather than a saved Any Filter. This lets you view the contents of a collection with all the contained stacks collapsed (Lightroom doesn’t show stacking for collections). It also lets you snapshot the contents of a smart collection, which is handy when you don’t want the set of images matched by the smart collection to automatically update as you modify them. And it lets you intersect the results of a smart collection or collection with a folder, functionality that was removed from Lightroom 4.
- Do Library > Plug-in Extras > Any Filter > Search (keyboard shortcut ALT+L S S on Windows).
- Click Collections in the upper left.
- Select one of the collections or smart collections on the right.
- Click Apply, or double-click the selected collection.
- The Library Filter bar will be updated to filter just the images in the collection.
Creating and Editing an Any Filter
Creating and editing an Any Filter is similar to creating a smart collection:
- Do Library > Plug-in Extras > Any Filter > Search (keyboard shortcut ALT+L S S on Windows).
- Click an existing Any Filter or click New.
- Enter a name for the Any Filter.
- The current criteria are displayed, one per line. To edit a criterion, click on it and then use the drop-downs and edit fields to change the criterion:
Click the magnifying glass 🔎 to search for a field rather than use the drop-downs.
- To add a new criterion after the currently selected one, click the “+” button; to delete a criterion, click the “-” button.
Searching Plug-in Metadata
Any Filter can search custom metadata fields defined by plug-ins. To tell Any Filter to search a plug-in’s fields:
- Click Plug-in Metadata.
- Click Add Plug-in.
- Browse to folder containing the plug-in and click OK.
When editing an Any Filter, the plug-in will now be listed in the left-most drop-down menu along with the other categories of criteria (Library, Date/Time, Description, etc.).
Plug-ins that store numbers in their metadata fields store the numbers as texts, but you can use Any Filter’s numeric-text operators (
= number, etc.) to treat those fields as numeric.
If Add Plug-in gives an error, the plug-in is likely incompatible with Any Filter (due to deficiencies in Lightroom’s plugin support). In that case, use the Scan Catalog button to scan all the photos in the catalog and extract the plug-in metadata fields it finds. These fields will appear as criteria in the Plug-in Fields category with names like
com.johnrellis.anyvision.text. Contact the plug-in’s developer for questions about the meanings of the plug-in’s fields. Use the Filter command to see the range of values for a particular plug-in field.
Any Filter Criteria
Any Filter provides all of the searchable photo fields (criteria) and operators of smart collections and many more, including IPTC Extension, GPS location, library properties, develop settings, and plugin fields. The complete list is available here. Additional operators include exact text match, matching regular expressions, testing empty fields, distinguishing explicit from implicit ancestor keywords, treating text fields as numeric, and including other saved Any Filters and smart collections.
Any Filter provides the following operators for comparing text fields. All comparisons ignore case; for example, JOHN and john are treated as identical. If a field is missing from a photo, it is treated as present but empty.
= value (
Matches if the field is identical to value.
contains value (
Matches if at least one space- or comma-separate sequence in value is contained somewhere in the field. For example,
contains lo to matches bright colors and old photos.
contains all value
Matches if every space- and comma-separated sequence in value is contained somewhere in the field. For example,
contains all lo to matches color photos but not old photos.
contains words value
Matches if every space- and comma-separated sequence in value matches a “word” in the field, where a word is a sequence consisting only of letters, digits, and the characters – _ ‘ /. For example,
contains words joe bob matches bob and joe ellis but not joey and bob.
starts with value
Matches if the field starts with the characters in value. For example,
starts with color photo matches color photos 1960 but not old color photos.
ends with value
Matches if the field ends with the characters of value. For example,
ends with lor photos matches faded color photos but not color photos 1960.
is empty (
Matches if the field is empty or missing from the photo.
< value (
Matches if the field comes before value in lexicographic ordering, comparing every character of the field and value. <= matches if the field comes before or is the same as value.
matches pattern (
Matches if pattern matches the field using the pattern matching documented here. For example,
matches day [0-9]+ matches day 5 of the race and yesterday 1979. Note that
matches is case sensitive, unlike all the other operators, which ignore case. The Lua string escapes are recognized in the pattern, including \n (newline) and \ddd (specifying a byte value with a decimal number). Due to Lightroom limitations, the patterns match against the individual bytes of the UTF-8 encoding rather than the Unicode characters. Thus, a pattern such as 相* doesn’t match zero or more occurrences of the character 相—rather, it matches the first two bytes of the UTF-8 encoding of that character, \231 \155, and then zero more occurrences of the third byte, \184.
< number value (
These operators treat the field as a number and compare it numerically with value. Any characters following a leading number in the field are ignored, and the criterion never matches if the field doesn’t begin with a number. For example,
< number 50 matches 49GKX and 3 dogs but not 50GKX or dogs 49.
Fields with Multiple Values
Any Filter provides more flexibility with fields like
Keywords that contain multiple values. As with smart collections, you can define a criterion
Keywords = John that matches a photo if at least one of its keywords is equal to John. But you can also define that criterion more explicitly as:
Keywords some items
Keyword = John
which is true if at least one of the keywords is equal to John. Similarly, the criterion
Keywords != John matches if none of the keywords matches John; this is equivalent to:
Keywords no items
Keyword = John
Using this explicit testing of individual items, you can write more complicated criteria:
Keywords all items
Keyword = John
Keyword = Peter
This matches a photo if all of its keywords are either John or Peter. See the predefined Any Filter
Exactly one person in the keywords for how to write a more complicated filter that matches photos that contain exactly one person (a subkeyword of People) and no others.
Some of the IPTC Extension fields are actually sequences of multiple subfields. For example, the
Locations Shown field can contain one or more locations, each of which has a
World Region. To match photos showing the location Palo Alto, CA:
Locations Shown some items
City = Palo Alto
State/Province = CA
For any field with multiple values, you can test the number of values using the
number of operators. For example, to match photos with no more than 2 explicit keywords assigned:
Explicit Keywords number of <= 2
Include all items
To match photos with exactly 2 explicit keywords that are subkeywords of People:
Explicit Keywords number of = 2
Keyword subkeyword of People
To match photos with at least one Person keyword (a keyword added by face recognition):
Explicit Keywords number of >= 1
Person is true
To match photos with no keywords that will be exported:
Explicit Keywords number of = 0
Include on Export is true
Lightroom’s smart collections and filtering define the
Keywords criterion to mean any keywords that have been explicitly applied to the photo, the corresponding ancestor keywords, and any synonyms of those keywords. For example, if the keyword People > Family > John has been applied to a photo, then the smart collection
Keywords contains People will match that photo.
With Any Filter’s
Explicit Keywords criterion, you can match the explicitly applied keywords only, ignoring synonyms and the implicit ancestor keywords. You can use the
subkeyword of operator to test if an explicit keyword is a subkeyword or identical to another keyword. For example, the criterion
Explicit Keywords subkeyword of People is the same as
Keywords = People. See the predefined
Any Filter Exactly one person in the keywords for an example.
Explicit Keywords contains ancestors has a unique purpose, to identify a photo that has both a keyword and its ancestor explicitly applied, for example, People and People > Family > John. This can be handy when you’re adding more levels of detail to your keyword hierarchy and want to find photos where you’ve accidentally applied both a keyword and its ancestor.
ExifTool Field criterion (in the Description category) lets you search virtually any metadata field stored in master photos, regardless of whether that field is in the Lightroom catalog. Any Filter uses the well-regarded, authoritative, but hard-to-learn ExifTool utility to read fields from the photos.
You can enter any field name recognized by ExifTool—see its documentation for the complete list. Click the magnifying glass 🔎 to to quickly search for a field.
The field name may include an optional ExifTool group prefix (required only when there are multiple fields with the same name). For example,
IFD0:ImageDescription all refer to the same field.
Any Filter treats every ExifTool field as a string. If the field contains numeric values, use the
number comparison operators. For example:
ExifTool Field > number 3 field: Rating
will search the
XMP:Rating field for values numerically greater than 3.
ExifTool Field searches the metadata stored in the master photo files or .xmp sidecars on disk, not in the Lightroom catalog. Fields in sidecars take precedence over fields in the raw files themselves.
If you’re searching a field that Lightroom may have modified, you’ll need to ensure that the field in the catalog has been written back to the photo files. Select all the photos and do Metadata > Save Metadata to File, or set the Lightroom option Automatically write changes into XMP in Catalog Settings > Metadata.
Compared to other Any Filter criteria,
ExifTool Field is very slow, limited by the speed of the ExifTool utility. ExifTool can process about 50–150 photos per second, depending on the types of photos and the speed of your computer. So to search a catalog with 50,000 photos could take roughly 1000 seconds (17 minutes)!
To speed up the
ExifTool Field criterion, Any Filter runs many instances of ExifTool concurrently. By default, if your computer has n virtual processors (threads), Any Filter will run about 1/3 n instances (e.g. 4 instances on 12 virtual processors / 6 cores). You can adjust that number in the Advanced Settings section of File > Plug-in Manager > Any Filter. Use a smaller number if Any Filter searches are making your Lightroom or computer less responsive, a larger number if you want the searches to go faster. But beware that numbers much larger than the default could make your Lightroom or computer difficult to use interactively. On my Macbook Pro with 16 virtual processors and all the photos on a solid-state drive, I’ve found that using 8 ExifTool processes is about twice as fast as 4, while 16 is only about 25% faster than 8.
Lua Code (Advanced)
The Code criterion lets you define custom criteria with Lua scripts (Lightroom and plugins are implemented in the Lua programming language). This requires programming experience and patience.
In the criterian’s code box, enter a boolean Lua expression (not a statement) to be evaluated for each photo. In the fields box, enter the list of photo fields referenced by that expression, separated by commas.
For example, to match photos whose Title is the same as the Caption and non-blank:
Title, Caption code:
Title == Caption and Title ~= ""
This example is included with the built-in filters, named
Title same as Caption, not blank. For a more advanced example, see the built-in filter
Has person keyword but no associated face rectangle, whose script is in
anyfilter.lrplugin/Any Filter Includes/person-keywords-no-face-tags.lua. For two more examples, see
Capture date this month of any year and
Capture date this month and day of any year.
To refer to a field whose name includes spaces and other punctuation, omit the spaces and punctuation, e.g.
DateTimeOriginalCapture. To refer to a metadata field extracted with ExifTool, in the fields box prefix it with an ExifTool group name, e.g.
EXIF:ImageDescription and in the code expression refer to it without the colon, e.g.
The code expression is evaluated in the standard global environment for Lightroom plugins (see Chapter 1 of the Lightroom Classic Programmers Guide). The fields listed in fields are available as global variables in the code expression. In addition,
photo contains the Lightroom
LrPhoto object for the current photo,
catalog contains the current
Debug is the debugging module from the Lightroom Debugging Toolkit.
You can place your code in a script file and load it with the
include function, e.g.
return statement to return a value from the script. Compared to
include is optimized for use in Any Filter.
You can use an absolute or relative file path to the script. For the latter,
include looks in the
Any Filter Includes subfolder in the Lightroom preferences folder and then in the
anyfilter.lrplugin folder. To see the location of the Lightroom preferences folder, in Lightroom do Preferences > Presets > Show All Other Lightroom Presets.
The values bound to the field variables use Any Filter’s internal representations (generally those provided by the Lightroom SDK). Beware that a field missing from the photo is usually represented as
nil rather than
"". The easiest way to discover these representations is by logging them to the file
Debug.lognpp (photo.path, DateTimeOriginalCapture, Faces)
You can also invoke the debugger via
Any Filter Speed
Some Any Filters match photos as fast as smart collections, and most will match at least 1500 photos/second, often many times faster. But if they access develop settings, they could match as slow as 250 photos/second, and if they use
ExifTool Field, as slow as 50 photos/second. Any Filter is limited by the speed at which Lightroom supplies plug-ins with photos’ metadata.
Wherever possible, Any Filter uses smart collections internally to speed up matching. For example, to implement
Keywords = John, Any Filter first executes
Keywords contains John using smart collections (which is very fast) and then further filters the resulting photos to those whose keywords exactly match John.
If your Any Filter is matching too slowly, consider adding smart-collection criteria that will help Any Filter quickly narrow down the set of photos. For example, if you know that the desired photos were captured in the last several months, add a
Date/Time Original (Capture) criterion.
See ExifTool Field for performance tips on that criterion in particular.
Using Any Filter > Filter
The Filter command provides a column browser similar to the Library Filter bar’s metadata browser:
Each column displays the values of the chosen field, and clicking a value will display only those photos with that value. Shift-click, Cmd-click (Mac) or Ctrl-click (Windows) to select additional values in a column.
Click on + to add a column, – to remove it.
Click the drop-down in the upper-left corner to save the current column settings as a preset or invoke a previously defined preset.
The Filter command filters the photos currently visible in the grid and filmstrip. Lightroom doesn’t always notify the plugin when you change the current source (folder or collection) or the Library Filter bar settings—in that case, click Refresh to recompute the columns.
Filter is often slow, due to Lightroom limitations. Lightroom fetches some fields very quickly, others very slowly. In general, if Filter is too slow, use smart collections and the Library Filter bar to narrow down the set of photos you’re examining before invoking Filter.
If there are more than 100 unique values to display in a column, they will be grouped into 100 buckets, sorted numerically or alphabetically. You can change the maximum number of buckets in Settings (⚙). Here’s an example:
1. Filter is examining 1091 photos, with 1042 unique values for file size.
2. Since there are more than 100 unique values, Filter groups them into 100 buckets.
3. The second bucket contains 11 photos, with file sizes greater than 38,988 bytes and less than or equal to 126,063 bytes.
You can change the column height and width in Settings (⚙).
Using Any Filter > Sort
The Sort command sorts the selected photos by one or more fields and optionally exports the photos and fields to a text file:
You can sort a field in ascending or descending order, and you can force a field to be sorted alphabetically or numerically. (In versions of Lightroom prior to Lightroom 7.2, that option has no effect due to a Lightroom bug.)
If you select the option Save sorted list to collection, the sorted list will be saved in the collection Any Filter Sorted. Be sure to do View > Sort > Custom Order to view the collection in the chosen order.
If you select the option Save sorted list and fields to CSV file, the list of photos and the chosen fields will be saved in the designated text file in comma-separated values format. You can open the file in Excel, Google Sheets, or any other application that understands CSV format.
Sort adds a URL column to the file containing
lightroom: URLs. In Excel, use the HYPERLINK function with this column to make clickable links that will take you directly to each photo in Lightroom.
Using Any Filter > By Date
The By Date command lets you quickly filter by dates and date ranges by typing the dates, rather than fussing with the Library Filter bar. When prompted for a date, you can enter the full year/month/day, year/month, or just a year:
For example, to find all photos in 2012, select Date and enter 2012. To find all photos from 1993 to 1999, select Date Range and enter the years 1993 and 1999.
The option Clear current filter clears all previous filter conditions in the Library Filter bar; deselecting that option causes a Date column to be added to the current filter without removing the existing columns.
Using Any Filter > Fix Burst Times
[Fix Burst Times is no longer needed in Lightroom 11. At some point in the last few years, Adobe silently fixed Lightroom’s sorting by capture time. Files that have the same exact time are sorted by file name.]
Many cameras don’t set the capture time’s fractional seconds of bursts when shooting in drive mode, and the bursts often appear out of order in Library. The Fix Burst Times command finds bursts of photos having the same capture time and sets the photos’ fractional seconds to be increasing in the same order as their filenames, e.g. to .0001, .0002, .0003, etc. This properly orders the bursts in Library when sorting by capture time.
Clicking Save Bursts saves each burst of photos as a collection inside the collection set Any Filter Bursts, letting you preview the bursts before setting their fractional seconds.
We wouldn’t need Fix Burst Times if Lightroom simply sorted by filename when photos’ capture times were equal—please add your me-too vote to this bug report.
Windows: You can use the standard menu keystrokes to invoke Any Filter commands. For example, ALT+L opens the Library menu, U opens the Plug-in Extras submenu, and S invokes the Any Filter Search command.
To reassign a different final keystroke to an Any Filter menu item, edit the file Info.lua in the plugin folder. Move the & in front of the desired letter in the menu command’s name, changing the name itself if necessary.
To assign a single keystroke as the shortcut, download and install the free, widely used AutoHotkey.
Mac OS: You can use the standard mechanism for assigning application shortcuts to plugin menu commands. In System Preferences > Keyboard > Keyboard Shortcuts > Application Shortcuts, select Adobe Lightroom. Click “+” to add a new shortcut, in Menu Title type the name of the menu command preceded by three spaces. For example, if you wanted to assign a key to the Any Filter > Search command, type “<space><space><space>Search”. In Keyboard Shortcut type the desired key or key combination.
Please send problems, bugs, suggestions, and feedback to: firstname.lastname@example.org.
I’ll gladly provide free licenses in exchange for reports of new, reproducible bugs.
If Any Filter crashes with an error or produces surprising results, please check the Debug option and re-apply the filter. Then do File > Plug-in Manager, select Any Filter, and in the Troubleshooting panel, click Show Debug Log. That will open File Explorer or Finder with the file debug.log selected—please email me that file.
Issues and limitations:
- Any Filter requires Lightroom 3 or later, Lightroom CC 2015, or Lightroom Classic—it relies on features missing from earlier versions.
- Your saved filters are stored in the file anyfilters.txt in the Lightroom preferences folder. If you’re moving to another computer, be sure to copy that file. Do Preferences > Presets > Show All Other Presets to open File Explorer / Finder on that folder.
- Any Filter can sometimes match photos as slow as 270 photos/second (the develop settings, in particular), even slower for
ExifTool Field. See Any Filter Speed for tips on speeding up filters.
- If you’re confused as to why a photo does or does not match an Any Filter, use the Filter command to examine the values of fields referenced by the Any Filter.
- The (private AF1) and (private AF2) columns in the Library Filter bar Metadata browser are not intended to be used directly by users. Rather, Any Filter uses them to display the results of applying a filter quickly. Ideally, it would be hidden from users, but Lightroom doesn’t make that possible. Without these columns, it would take Any Filter many times longer to display very large search results. To see the results of the most recent eight searches under the collection set Any Filter Results, check the option Save results as a collection.
- When the option Show results using a Library filter is checked, the Last Edit Time of every matching photo is updated to “now” (due to a Lightroom bug).
- The Filter command’s floating window always appears behind the main Lightroom window, on Windows Lightroom when in Window > Screen Mode > Full Screen (and sometimes Full Screen With Menubar). This is caused by a Lightroom bug, and the workaround is to switch to Normal screen mode.
- If you try to use criteria not supported by your version of Lightroom, you’ll get an inelegant plugin error. For example, if you try to use the Lightroom 5 criterion
Has Smart Previewin Lightroom 4 or earlier, you’ll get an error.
- Any Filter can’t access the custom metadata fields of most of Jeffrey Friedl’s plugins and those of other developers who share Friedl’s code libraries. They don’t follow the usual (but undocumented) plugin conventions. Use the Search > Plug-in Metadata > Scan Catalog button instead.
- Due to a Lightroom bug, Any Filter cannot always search correctly the location fields (
ISO Country Code,
State / Province,
Sublocation) when their values have been automatically added by Lightroom’s address mapping (reverse geo-encoding). Such values appear gray in the Metadata panel. You can work around this by committing these gray values: Click on the field label (e.g. Country) and select the value, changing the field from gray to white. Or use the Commit Locations command of the Any Tag plugin.
- The Folder Details criterion can’t access device folders created by syncing with the Lightroom Cloud (e.g.
John's iPhone > Imported Photos), due to a Lightroom bug.
- Any Filter tries to work around a number of bugs in Lightroom’s smart collections and filtering, which are creaky and need significant improvement (one of my motivations for making Any Filter). I fully expect that there are undiscovered Lightroom bugs that Any Filter’s users will trip over. If you suspect such a bug, see above for how to report them.
- On Windows, when you delete a column in Filter, the size of the window won’t shrink automatically—you’ll have to manually resize the window. (This is caused by a Lightroom bug.)
- Initial release
- Fixed Lens Profile Name to be a text field, not a number
number ofoperators for fields with multiple values
- Added By Date command.
Longitudecriteria now accept either form of coordinate, -118.5469 or 118° 32′ 49″ W.
- Saved Any Filters are now stored in the Lightroom preferences folder, making it easier to upgrade to new versions of Any Filter.
Longitudecriteria execute much faster.
- Fixed incompatibility with user names containing non-ASCII characters (caused by bug in Lightroom SDK).
- Allowed .lrplugin directories to be selected by the Plug-in Metadata > Add Plug-in command on Mac.
- Added new fields for LR 4, including Process Version 2012 develop settings.
- Any Filter commands now appear on both the File > Plug-in Extras and Library > Plug-in Extras menus, so they can be used in all modules, not just the Library.
- Added Visible photos only option for searching just the visible photos.
- Added the field Saved Locations for searching photos located within a saved map location.
- Provided a documentation link above for matches patterns.
- The Scene field is renamed to IPTC Scene Code.
- The Location field is renamed to Sublocation and mapped to the correct metadata field (no longer to “scene”).
- Now ignores errors from corrupted catalog entries.
- Fixed a bug with Apply of collections.
- More gracefully handles syntactically ill-formed captures in
- In LR 4, uses the SDK’s new backoff feature for handling updates to the catalog.
- New field Metadata Status (not available in Lightroom 3).
- New field Crop Constrain To Warp.
- Fixed “assertion failed” when you search with Visible photos only and no photos are visible.
- Fixed error when Visible photos Only and Debug are both selected.
- Correctly handles Subject Distance and Video Frame Rate in countries in which the decimal mark is comma rather than dot.
- New field Collection Sets, similar to Collections.
- New field Associated File Types tests whether there are associated files with the same base name but different extensions (for example, xmp).
- New fields
Incremental Tint, representing Temp and Tint for JPEGs in the Develop module.
- Fixed typo in field
- New fields
Tint, representing Temp and Tint for raw files in the Develop module.
Aspect Ratiowhen used in some compound queries.
- This version includes lots of changes to better support Lightroom 5, along with other miscellaneous changes:
- Added 20 new fields provided by Lightroom 5:
Color Noise Reduction Smoothness,
Enable Circular Gradient Based Corrections,
Circular Gradient Based Corrections,
Lens Profile Filename,
Crop Constrain Aspect Ratio,
Has Smart Preview,
Smart Preview Path,
Smart Preview Size,
Is DNG With Fast Load Data,
Cropped Long Edge, Cropped Short Edge,
Bits Per Channel,
Source Color Mode,
Source Color Profile.
- Significantly speeded up these fields using new features in Lightroom 5:
- The fields
Cropped Megapixels are rounded to the nearest tenth, to conform with Lightroom 5 smart collections.
is unknownoperator for dates/times, making it easier to test for images missing the metadata field Date Time Original.
- Made the user interface a little easier to read on Windows, working around a Lightroom 5 bug that Adobe is unlikely to fix anytime soon.
- Made Any Filter robust in the face of invalid dates/times stored in catalogs converted from early versions of Lightroom. In particular, the
day in monthdate operators won’t fail with such catalogs.
- Changed the option
Log matching metadatato
Log photo metadata, which logs metadata of all the photos, not just those matching the searching criteria.
- New option Save results as a collection saves Any Filter results in collections under the collection set Any Filter Results.
- Worked around many bugs in Lightroom smart collections and metadata, most of which were obscure edge cases that most users would never encounter.
- New field
IPTC Date Created.
- Worked around Lightroom SDK bugs with the fields
Tone Curve Point Adjustments,
- Fixed a bug with the field
Spot Removalthat caused click-and-drag clones from being recognized.
Keywordscriterion now searches keyword synonyms too.
- Clear current filter option lets you keep current filter settings in the Library Filter bar.
- New fields
Location Is Private,
Audio Channel Type,
Audio Sample Rate,
Audio Sample Type,
Video Alpha Mode
- Fixed bug in
- Fixed typo in criterion
Luminance Adjustment Aqua.
- Improved wording of Clear current Library filter.
- Worked around Lightroom bugs with
Max Available Heightand
Last Edit Time.
Location > Image Directioncriterion (GPS image direction).
- Worked around Lightroom bug with
- Added mirrored orientations to
Orientationand made it much faster.
- Worked around Lightroom bug that sometimes prevented By Date from properly setting the date filter.
- Worked around Lightroom bug that broke the
day in weekoperators.
- Case is now always significant when using the
matchesoperator to match patterns. Previously sometimes case was ignored, sometimes it wasn’t.
- New criterion
ExifTool Fieldfor searching any metadata field stored in master photos.
- New criterion
Published Collection Sets.
- New criteria
Effective Exposure Valuefor searching by the total exposure, an estimate of the amount of available light.
- New criteria for Develop’s Upright Transform:
- Fixed bug with
Distance From Google URL.
- Sort command for sorting photos and exporting fields to text files.
- Fix Burst Times command for setting fractional seconds of drive-mode bursts.
- New criterion
- Ability to filter for multiple values meeting specific criteria, e.g. the number of explicit keywords that are subkeywords of People.
- Removed the option Log photo metadata; use the Sort command instead.
- New option Avoid Lightroom bugs for avoiding obscure Lightroom search bugs, at the expense of searching much more slowly.
ExifTool Fieldnow allows is empty and isn’t empty.
ExifTool Fieldnow allows unknown tags (ExifTool’s -u option).
- New criterion
Has Edits, whether the image has any adjustments or cropping.
- New criteria
Cropped Pixels, the exact number of pixels in the image.
- New criterion
Profile, the image profile shown in Basic panel of Develop.
Camera Profileretains its legacy definition, the base Digital Negative Camera Profile (DCP) applied to the image, either directly or indirectly via an enhanced profile including that DCP. (For example, the enhanced profile Adobe Color includes the DCP Adobe Standard.)
- Now provides a polite error message when the saved filters file (anyfilters.txt) can’t be read for some reason.
- Workaround for obscure bug in Lightroom 7.3.
- Updated to latest version of ExifTool (10.99).
- Added Process Version 2017 (Version 4).
- Updated to latest version of ExifTool (11.10).
- The Sort option Alphabetic now works in Lightroom 7.2 and later.
- The new Filter command provides a column interface like that of the Library Filter bar’s Metadata browser, useful for quick searches and exploring the values of criteria.
- You can now search for criteria using the magnifying glass 🔎.
- New criteria D
ate/time Original Year,
Day of Month,
Day of Week, and
Hour, which are a little easier to use than
day in month =, etc.
- Fixed bug with
ExifTool Fieldand fields containing multiple values.
- Added process version 2018 (process version 5).
- Renamed the Any Filter: Search column to (private AF1), to emphasize that it is for internal use by the plugin and not useful to users.
- Fixed bug in Edit and New when plugins were added to Plug-in Metadata.
- Updated to ExifTool 11.37.
- Updated the process-version names to match Lightroom’s new naming (e.g. “Version 5”).
- Added the
ExifTool Fieldnow searches .xmp sidecars of raws as well as the raws themselves.
- Updated to ExifTool 11.60.
- Documented the text operators.
- More readable names for collections in Any Filter Results.
- New criteria
Date/Time Original Minute (Capture),
Date/Time Original Second (Capture).
- Filter won’t let you set the column height taller than will fit on the display. (This may not work on Windows due to a Lightroom bug.)
- New criterion
- New criteria
File Date Createdand
File Date Modified.
File Type(Lightroom 9.2 now supports PSBs).
- New criterion
Facesthat searches faces identified by Lightroom’s face recognition or added manually. Search for unconfirmed and confirmed faces, the number of faces, the size of face rectangles, and more.
- New criterion
Largest Face Areafor searching by the largest face rectangle in each photo. Useful for identifying photos in which the face occupies much of the area of the photo. Particularly useful with the Filter command.
- New button Add Built-in Filters adds any built-in filters that aren’t in the current saved filters. You can safely delete any you don’t want.
- Worked around Lightroom bug causing the criterion Available to falsely report a photo as not missing.
- The criterion
ExifTool Fieldnow correctly searches the .xmp sidecars of .heic files.
- Updated to ExifTool 11.93.
Color Gradecriteria for the develop settings of the Color Grading panel introduced in Lightroom 10.
- Fixed glitch with magnifying glass in the Sort command caused by Lightroom 10.
- Worked around Lightroom bug with
- The new option Show results using a Library filter lets you disable the use of the Library Filter bar for showing the search results, using just the collection set Any Filter Results for displaying results. This avoids the Lightroom bug where simply using Any Filter changes the
Last Edit Timefor all matched photos.
- New criterion
Cropped Amountis the ratio of the cropped area to the total area of the photo (
Cropped Pixels / Pixels).
- The new Code criterion lets you define custom criteria with Lua scripts.
Inside Cropis true if the face rectangle is inside the cropped area. See the built-in filter
Cropped-out facesfor an example.
- The standard Lua string escapes are recognized in
matchespatterns. This lets you match newlines (
\n) and other special characters.
- When you filter by a date range with By Date, the hierarchical dates should once again appear correctly in the Metadata browser’s Date column (though there could still be glitches from a Lightroom bug). By Date has always filtered correctly, but Lightroom sometimes displayed the selections in the column incorrectly.
- Updated to ExifTool 12.25.
- Added new criteria that access the details of local adjustments:
Spot Removal Brush Strokes,
Red Eye Corrections,
Gradient Filter Corrections,
Radial Filter Corrections,
Adjustment Brush Strokes. See the built-in example filters
Gradient filters on the top,
Adjustment brush strokes with Dehaze not 0,
- Fixed bug adding
Some of, and
None ofunderneath a criterion with multiple values (e.g.
- Changed the way multiple-value criteria are accessed by Lua code in the
Codecriterion. For an example, see the built-in filter
Has person keyword but no associated face rectangle. This change is incompatible with the previous version 1.41.
ExifTool Fieldcriterion now runs much faster again. A couple performance bugs that had crept in were fixed (affecting only some cameras’ raw files), providing a 2x speedup on those raws. And Any Filter now runs many instances of ExifTool concurrently, yielding a 2-4x speedup on most types of files on newer computers. See ExifTool Field for details on changing the number of concurrent ExifTool instances.
- New Append option for Sort that appends the results to an existing CSV file rather than overwriting it.
- Two new built-in filters,
Capture date this month of any yearand
Capture date this month and day of any year. To access them, in Search, click Add Built-in Filters.
- Fixed a bug in the
Whatsubfield of the
Adjustment Brush Strokesfield.
- Fixed a bug in the
Largest Face Areafield.
- Added long-missing Develop settings
Enable Color Adjustmentsand
Enable Tone Curve.
- New criteria
Mask Componentsfor searching Lightroom 11’s new masking adjustments.
Maskslets you search the top level entries in the new Masking panel, while
Mask Componentslets you search for the individual components like Brush, Linear Gradient, Select Sky, etc. The built-in filters include examples of how to use those criteria.
- The criteria
Gradient Filter Corrections,
Radial Filter, and
Radial Filter Correctionsare still available and will return results in Lightroom 10 and earlier, but in Lightroom 11 they won’t match any photos, since Lightroom 11 converts them to the new mask representation.
- The built-in filter
Sky/Subject Mask needs updatingfinds all photos with Select Sky or Subject masks that need to be updated (because they were copied from other photos).
- Updated to ExifTool 12.36.
ExifTool Fieldcriterion runs much, much faster when searching photos that contain large amounts of masking brush strokes. (Thanks to ExifTool Phil Harvey for his fast response to this issue!)
- Added criteria for Develop settings that had been overlooked:
Lens Manual Distortion Amount,
Upright Center Mode,
Upright Center Norm X,
Upright Center Norm Y,
Upright Focal Length 35mm,
Upright Focal Mode,
Upright Preview. I don’t know what those “Upright” Develop settings do.
ExifTool Fieldnow runs much faster on .xmp sidecars created by earlier versions and not yet updated by Lightroom 11. Thanks very much to Cosimo Cella for helping to diagnose the problem.
- Fixed bug with Filter‘s preset menu. When Filter first opened, the menu wasn’t available until the first filter column had fully refreshed.
- Added the Scan Catalog button to let Any Filter search the metadata fields of plug-ins that don’t follow the usual metadata conventions.
- Fixed Filter error message that appeared in recent versions of Lightroom,
Filter.lua:906: attempt to index field '?' (a nil value).
- The criterion
Availableis faster and more reliable.
- Updated to latest version of ExifTool.
- Updated documentation for Fix Burst Times to indicate it isn’t needed any more.
- Sort button sorts Search filters alphabetically.
- Built-in filters
Raw / jpg pairs (common raw types),
iPhone portrait mode, and
iPhone Live mov / heic pairs. Click Add Built-in Filters to access them.
Exposure Valuehandles photos and videos with incomplete or nonsensical exposure fields.
Codecriterion won’t allow non-existent fields.
- Added additional mask-component types to
Mask Components.Typethat were introduced in Lightroom 12.0:
Person, and person
- Added the word “Healing” to the descriptions of the Spot Removal criteria; didn’t rename
Spot Removalto Healing, maintaining backward compatibility.
- Any Filter can now directly access the catalog database, accessing much more information than provided by the Lightroom plugin SDK. This allows many new criteria long requested by users. If there are criteria you really want, drop me a note (no promises).
Gory details: For years, Lightroom needlessly placed an operating-system lock on the catalog’s .lrcat file while it was running, preventing plugins from accessing the catalog database. At some point prior to Lightroom 8.4.1, Adobe silently stopped doing that. But I just found out recently!
Synced with Lightroom Cloudmatches all photos that are synced with the Lightroom Cloud ecosystem.
Synced Collectionscontains all the synced collections containing the photo.
Collection Detailscontains details about each collection containing the photo, including its name, containing collection sets, type (Regular, Published, Print, etc.), whether it’s synced with the cloud, and its containing Publish Service.
Collection Stackscontains details about stacks in collections containing the photo, including the collection’s name and path, the position of the photo in the stack, the stack size, and whether the stack is collapsed.
Folder Detailscontains details about each folder directly or indirectly containing the photo, including its name, file-system path, color label, and whether it’s the immediate containing folder.
Sidecarsprovides the file extensions of the photo’s sidecars (e.g. “xmp” or “jpg”).
Date/Time Importedis the when the photo was imported into the catalog, as shown in Develop History.
Date/Time First Develop Editand
Date/Time Last Develop Editare the when the photo was first and last changed in Develop, as shown in Develop History.
Date/Time Last Exportedand
Date/Time Last Publishedare when the photo was last exported and published, as shown in Develop History.
History Stepscontains details about each step shown in the Develop History panel, including the step’s type (Setting, Preset, Import, etc.), its date/time, its description (the text of the step), the increase or decrease in the setting’s value, and the final value of the setting.
Presetscontain all the presets appied to the photo, as show in Develop History.
- New built-in filters demonstrating the use of the new criteria (in Search, click Add Built-in Filters to get these):
Synced photos not in a synced collection
Imported this month
Auto Settings applied
Preset "Texture = +10" applied
Top of stack in a collection
Has a JPEG sidecar
Number of Facescriterion, primarily useful with the Filter command.
Facesand related criteria are much faster, accessing the catalog database directly rather than running ExifTool.
- Added omitted Mask Component type All People.
- Increased the number of results shown in Any Filter Results to 16.
Date/Time Last Printedis when the photo was last printed (as shown in Develop History).
- Fixed Windows-only bug affecting criteria that directly access the catalog database, e.g.
Synced with Lightroom Cloud.
- The Debug option is now persistent.
Enhanced Typegives the specific enhancement made by the Enhance command (Denoise, Raw Details, Super Resolution).
Denoise Amountis the value of the slider used for Denoise.
Photo Merge Typegives the type created by the Photo Merge command (HDR, Panorama, HDR Panorama).
Panorama Projectionis the method used to create the panorama (Spherical, Cylindrical, Perspective).
Tone Curve Adjustmentand
Red|Green|Blue Tone Curve Adjustmentadded as elements to
Error Reasonadded as element to
Mask Components. A non-empty
Error Reasoncan indicate that an AI mask needs updating or can’t be found in the image (e.g. a People mask).
Confirmedadded as an element to
Faces, indicating that the sugggested name has been confirmed by the user.
- New file formats
JXLadded to Lightroom 12.3.
Aperturevalues less than 1 are allowed.
Bits Per Channelis now allowed in the Filter command, due to a Lightroom 12 bug fix.
infrecognized as a valid value for
- The built-in filter
Unconfirmed suggested name for facereplaces the misnamed
Any Filternow requires Lightroom 5 or later.
- Updated to ExifTool 12.62.