Jeffrey’s “Collection Publisher” Lightroom Plugin

This Lightroom “Publish” plugin allows you to export copies of your Lightroom photos to local disk in a folder hierarchy that mimics the collection hierarchy you build within Lightroom.

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

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

This is a sister plugin to my Folder Publisher plugin, which is similar to this plugin except that Folder Publisher creates a layout on disk that mirrors the images' folder hierarchy instead of their collection hierarchy.

Unlike a normal export, this Publish service allows you to create an ongoing relationship between the photo in Lightroom and the copy on disk. The tree on disk is refreshed for any changes (new images, removed images, and image changes) each time you “Publish”. I've found it very convenient to publish selected collections of portfolio images for my iPad.

Here's an overview of what it looks like in the Publishing Manager.. the areas marked in red are from this plugin (with the blue and green items being from other plugins that I happen to be using in this example):

The plugin is normally used in the following pattern:

  1. Initial setup of the publish service.
  2. Initial setup of the collection hierarchy within the publish service.
  3. Populate the collections with images.
  4. “Publish” them, causing copies of the images to be reflected into a hierarchy on disk matching the collection hierarchy in Lightroom.
  5. Going forward, any time changes are made (images updated, added, or removed), “Publish” causes those changes to be reflected on disk.

Publish-Service Setup

When setting up a new publish service, you first assign a name, though you can leave it blank if you'll only have one...

You indicate where published copies are to be placed by specifying the root of the publish tree. When first setting up a new publisher, you'll likely want to pick an empty folder as the root.

The next sections are all part of the standard Lightroom export. In them you decide the size and quality of the published copies...

The next two sections shown in the example aren't included unless you specifically add them:

They're from my crop for iPad and Metadata Wrangler plugins; I use them in my exports to allow me extra control of what metadata is included in each exported copy, and in the case of my iPad portfolio, special iPad-specific crops so that some images better fill the screen.

The next section controls what changes in Lightroom should cause published images to be slated for republish.

Then we have a plugin-specific seciton on file renaming that gives much more flexability than Lightroom's standard “File Naming” section, should you need it:

This allows you to have the files for the exported copies named derived from image matadata using template tokens that are processed on the fly for each image.

The next section provides a way to do an FTP sync of the published copies, should you need it. Photo-viewing iPad apps tend to allow updates via FTP sync, so this section is convenient for that.

It's here as a convenient tool rather than an actual part of the configuration; the FTP sync is never automatic... it happens only when you launch it manually from the Publishing Manager.

The plugin also provides a way to import and export settings, making it easier to set up comparable publish services on multiple catalogs (such as when part of your library is on your desktop, and part on your laptop, as is my case).

When first setting up a service, you'll have the ability to import settings...

... but once it's been set up the first time, after that the section allows for export:

Collection Setup

Once you've got the publish service created, its context menu (alt-clicking or right-clicking on it in the left hand side of Library) brings up a menu allowing you to create collections or sets...

Collections can contain images, while collection sets can contain collections and other collection sets. It's different from the normal file/folder hierarchy on disk because images can only go into collections, and not into collection sets. This makes it inconvenient and unnatural to mapping between how you must organize images within the plugin and how the plugin writes them out to folders and files on disk, so I've built two ways to do it; hopefully at least one will make sense...

When you create a collection in the plugin, you have three choices for the Collection Type, which determines how the plugin treats photos in the collection when outputting copies during Publish:

If the “Collection Type” is “Its own sub-folder”, the collection name (“Travel” in the example above) becomes a sub folder in the publish destination, and images in the collection are placed in the sub-folder. This is likely the most common collection type for most folks.

When the collection type is “Part of its parent”, the name of the collection is not used by the publish system. Instead, exported copies are placed into the folder of the collection's parent collection set.

(The third option, A mirror of..., is discussed below.)

Let's look at an example, two ways to put images into a “Japan” sub-folder within “Travel”:

  1. Invoke “Create Sub-Folder or Mirrored Collection Set” named “Travel”, then within it create a collection named “Japan”, being sure to select “its own sub-folder”.

  2. Invoke “Create Sub-Folder or Mirrored Collection Set” named “Travel”, then within it create another sub-folder named “Japan”, then within that create a collection, with any name, being sure to select “Part of its parent”.

Mirroring Pre-Existing Collections

A new, experimental feature as of August 2015 allows the plugin to mirror (automatically keep in sync with) collections you already have elsewhere in your catalog.

This mirroring feature is a bit fragile because what it aims to do does not fit easily into how Lightroom's plugin infrastructure has been designed. In trying to implement this feature, the plugin is pushing the envelope with what Lightroom can do, and as a result some loose ends can potentially make for surprises if you (the user) don't keep the important caveats discussed below in mind

When creating a collection or collection set with this plugin, you have the option to mirror a collection or an entire hierarchy of collections. When one collection is mirrored from another, the plugin semi-automatically keeps the set of photos in one updated to reflect any changes in the other.

For example, consider these normal collection in a Lightroom catalog:

If we've spent time curating the Travel set of three collections and would like to see that set mirrored in the Collection Publisher so that we can have a local hierarchy of copies on disk, we right click on the Collection Publisher and choose Create Sub-Folder or Mirrored Collection Set to bring up the set-creation dialog:

We've selected Mirror collection tree rooted at... and then pulled up Travel from the list of sets. (The list includes all collection sets in your Lightroom catalog except those within a Collection Publisher service).

After having selected the Travel set, the name of the new published set to be created is pre-filled in as MIRROR: Travel and can't be changed.

Upon pressing the [Create] button, we see the new MIRROR: Travel set in our publish service, filled with the three new collections and pre-populated with respective photos from the three source collections:

The MIRROR prefixed to the name is there to remind you that the plugin is supposed to have control over it and its contents, and that you shouldn't manually make any changes to the collections or add/remove photos within (they should be added/removed in the source collection this publish collection mirrors). More on this in a moment in Caveats below.

In the example above, the publish collections have been created but they haven't actually been published yet — all the photos in them are in New Photos to Publish — but you can publish them individually (click on their name then on the [Publish] button), or en mass via File > Plugin Extras > Refresh and Publish Mirrored Collections.

The Caveats of Mirroring

As noted above, this well beyond what Lightroom's plugin infrastructure was designed to handle, so it's not as smooth as one would like...

  • We'd like for the mirroring to be completely automatic, but unfortunately Lightroom's plugin infrastructure doesn't allow for it. Rather, mirrored collections are synced only when they are published, and/or when via File > Plugin Extras > Refresh and Publish Mirrored Collections is invoked.

    Publishing a single collection via [Publish] syncs and publishes just that collection, while invoking the Refresh and Publish Mirrored Collections syncs (and optionally publishes) all Collection Publisher collections. Depending on the changes made during the sync (discussed below), syncing via the [Publish] button may leave some photos in the Deleted Photos to be Removed section of the collection, so it may need to be published once more to finally push out all changes.

  • Syncing means that the target collection in this plugin is made to have the same photos as the source collection it mirrors, so any extra photos here but not there are deleted (even if you had manually, specifically added them here), and any photos there but not here are added (even if you had manually, specifically removed them here). It would be nice if this were a full two-way sync, but the plugin has no idea why a photo might be in one place and not the other (did you remove it there or add it here?), so it's a simple make this look like that.

  • Given that it's a simple one-way sync, it'd be nice if Lightroom disallowed local changes (that is, disallowed adding/removing photos to the publish collection), but such restrictions are not possible with the current plugin infrastructure, so if you forget a collection is mirrored and start adding/removing images, that work will be silently lost at the next sync. That's why the collection name has MIRROR prepended, to remind you.

  • The same can be said for mirrored sets. If you add/remove collections within a mirrored set, that work will be undone at the next sync when the collections are re-mirrored back from the source set.

  • Once a mirrored collection is set up, it can't be edited or modified because there's nothing to edit or modify. (It's renamed by renaming the collection it mirrors and then syncing.) However, it can be deleted via the context menu for its name in the publish-services list.

  • Similar to the previous point, mirrored collections can't be moved within the published-collection sets of the publish service, nor can other collections be moved or created within a mirrored collection set. If you want to add or subtract collections, do so in the original source being mirrored and then sync.

  • There's a bug in Lightroom that has the potential to cause some havoc with collection creation. Due to this bug, the collection-creation part of the plugin sometimes gets confused about where within your publish service a collection is about to be created, and so sometimes mistakenly gives a can't create a collection within a mirrored collection error, or sometimes might not give it when it should.

    The bug can happen when you have a collection or set selected for display in Loupe/Gird at the time you bring up the collection-creation dialog...

    Lightroom conveniently pre-fills the Set in the collection-creation dialog with whatever set is associated with the selection at the time it's invoked...

    The bug is that if you change the Set in the dialog, information about that change may or may not be passed to the plugin.

    The workaround is to make sure that either no collection-publisher collection is selected when you invoke the collection-creation dialog, or that only a root-level collection is selected.


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 Lr5 to Lr6, 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 )


Added some debug logging.


Added the following tokens to the template tokens that my plugins understand/a>: Artworks, ArtworkTitle, ArtworkCopyright, ArtworkSource, ArtworkCreator, ArtworkDateCreated, ArtworkInventoryNum


Couldn't set the exported-copy file date older than about 50 years ago; fixed.


The rules about what characters are disallowed in a folder name were too aggressive, so relax them.

Fixed a bug with the keyword tables in the LUA token.

Added Weekday, Wday, weekday, wday, and ISO8601Date to the list of template tokens that my plugins understand.

Switch the log-sending mechanism to https.


Added the following tokens to the templates that my plugins understand: FileModYYYY, FileModYY, FileModMM, FileModDD, FileModHH, FileModMIN, FileModSS, FileYYYY, FileYY, FileMM, FileDD, FileHH, FileMIN, FileSS, {FilenameNumber}.

Better support for network shares on Windows.


Fixed a "TreePublisher_Mirror:91" error.

Fix to get around a Mac display issue with Lr6 on OSX.

Added Russian-langauge support for the People-Support {People} tag.


Fixed the "Spec:2164" error.


Added ChildOf and DescendantOf filters to the {Keywords} and {KeywordsAll} template tokens that my plugins understand.

Fixed how custom {People} formatting works with people keywords that have no birthday associated with them.

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


If there's an error exporting one particular image, try to continue with others and merely have Lightroom report a summary of errors at the end.

Added support for sequence numbers on publish. See the "sequence numbers" link in the "Enhanced File Renaming" section of the dialog.

Added {SpeedKPH} and {SpeedMPH} to the list of template tokens supported by my plugins.

The {People} token wasn't working properly for some keywords without a registered birthday.


Allowed the Enhanced File Renaming to actually create sub-folders under where an image would normally be placed.

20150822.68 Added extra debug logging to track down file-copy issues.

Added the ability to automatically mirror normal Lightroom collections in this plugin; See this link for details.


Fixed the "SpecPeople:259: attemt to index al nil value" error.


If the root folder of the publish tree had a very long name, the view/change buttons would be pushed off the edge of the screen.


In the "Enhanced File Renaming" section, add the ability to override the extension on the exported filename.


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


Fix to the date_diff() function supported by the LUA template token.

Updated the camera-name code to try to guess the actual camera model of Hasselblad H5D files, since in their infinite wisdom Hasselblad decided to encode three distinct models with the same internal code, making it impossible to know for sure what camera produced a given image file.

20141219.61 Added a bit more debug-logging for when a file copy can't be done.
20141019.60 Windows Only: Add a one-time check for the POODLE security vulnerability, and alert the user if it exists.
20140923.59 Added the LrMD5, LrLocalization, LrSystemInfo, and LrMath packages to the {LUA} template token.
20140902.58 If the plugin failed to create such-and-such a folder because a file of the same name already exists, report the details to the user.
20140828.57 Extra debug logging to track down a folder-creating problem on some systems

Made the {GPSAltitude}, {Altitude}, and {GPSCoordinates} tokens subject to the geo-privacy settings like the other geo-related tokens.

20140731.55 Registration fix for Lr5.6
20140720.54 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.51 Sigh, had a bug in the Creative-Cloud support.

Now supports Lr5.5+ Creative-Cloud Installs.

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

Added date_diff() and raw_time_diff() functions to the special {LUA} token understood by the plugin.

20140612.46 Under some error conditions plugin would crash instead of presenting the proper error message.
20140514.45 Got rid of a "Done" confirmation dialog that's not really necessary.

Added new tokens to the template language the plugin understands: LrVersion, LrVersionMajor, LrVersionMinor, LrVersionRevision, LrVersionBuild, Location, CatalogName, CatalogPath, OperatingSystem, OS

Added new token filters: NS and LO

20140423.43 Fix a location-related template-token bug introduced in a recent build.

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


Enhancements to the FTP stuff: take care not to work with "." and ".." that some servers return.

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

The {Empty} template token wasn't working properly.


Internally track whether exports are via the master image or via a smart preview. In the future this may allow for a "republish those for which a master is now available" feature.

Worked around a mysterious "attempt to get length of a nil value" bug.

20131213.39 Added {PublishCollectionName}, {PublishCollectionDepth}, and {PublishServiceTitle} tokens to the preset templates. See template-token web page for important restrictions.
20131102.38 Update for OS X Mavricks
20131010.37 Yikes, it seems that version 20130905.36 broke the "Metadata that Triggers Republish" section, clearing all items you might have had set (well, all but Caption). Sorry about that. Please visit the "Metadata that Triggers Republish" section to reconfigure to your liking.
20130926.36 Oops, fix a bug introduced in the previous update

Added a bunch of tokens to the preset templates supported: ExportFormat, ExportColorSpace, ExportBitDepth, ExportQuality, ExportSharpeningLevel, ExportSharpeningMedia, IpernityUrl, GoogleDriveUrl, and TumblrUrl.

The token-examples dialog had been broken. Also deprecated Folder and Path tokens in preference to FolderName and FolderPath tokens.


Work around a Lightroom bug concerning the determination of whether a photo is offline.


Respond more gracefully when enhanced file renaming can't come up with something valid.

Fixed the KW/KWE tables in template tokens; they had been broken when using load for the script.

Added an "Ask" option to the "Export with Smart Previews?" section, so one can be alerted to the situation at each export.

Made the file time control stuff (added in the previous update) optional, because it imparts a (small) performance penalty. The default is set to "off", so you'll need to re-enable it if you actually care about the file date/time stuff.


When "Format" is "ORIGINAL" (meaning to spit out the original image pixels with new metadata, instead of the developed version with new metadata), the plugin didn't handle XMP sidecars properly at all. Now it does.

You now have control over the file time of exported copies (set to the image capture time, or the time of export).

20130620.31 Allow published copies to remain on disk even if a photo is deleted from Lightroom.
20130613.30 Better support for plugin revalidation.
20130612.29 A failure for the plugin to copy a file on disk resulted in a plugin crash instead of the appropriate error message display.

Added the ability in Lr5 to export images even if the master image file is not available, so long as there's a smart preview available.

20130611.27 Yet another Lr5 update
20130610.26 Final update for Lr5
20130513.25 More changes for the root-selection problem... really seems to be a bug in Lightroom, but it's hard to tell because I can't replicate the bug myself.
20130501.24 Update for Lr5
20130412.23 Build system update.

More with with the code that handles changing the root of the publish tree.


Added support for some new template tokens: FlagStatus (requires Lr4.1 or later), and for Lr3 and later, a bunch of IPTC extended metadata: AdditionalModelInfo, CodeOfOrgShown, DigImageGUID, Event, ImageSupplierImageId, MinorModelAge, ModelAge, ModelReleaseID, ModelReleaseStatus, NameOfOrgShown, PersonShown, PlusVersion, PropertyReleaseID, PropertyReleaseStatus, and SourceType.

20130209.20 More build-system maintenance
20130206.19 Tweak for my registration system

The plugin wasn't robust against case-only changes in filenames or folders. This is a real pain because such names (e.g. "test" vs. "Test") appear different to the plugin, but they refer to the same underlying file on most filesystems for most users (because most Windows and OSX file systems have case-insensitive file naming). There's no easy way for the plugin to make such renames, so the plugin now reports that it won't work for existing files, and offers a chance to abort along with info on how to actually get it done: rename to something different (e.g. from "test" to "test2", then from "test2" to "Test").

While doing a rename, Lightroom pops up a "this may take a while; proceed?" dialog, and if the user canceled it, the plugin neglected to cancel the entire update, leaving things in an inconsistent state.

20121210.16 Added some extra debug logging.
20121024.15 Allow Video to be FTP'd as well.

Workaround for an "attempt to call field 'getProgressScope'" bug introduced in Lr4.2.

Disallow DPX video export because it breaks things.

Enhance the {EMPTY} template token so that it interrupts the squelching of superfluous joining characters.

20121004.13 Oops, hte file-extension thing got worse, not better... reverting that change.

Work around a "situation" (likely Lr bug) where exported video loses its file extension.

More debug logging for the elusive "no root folder" problem.


Updates to the environment in the {LUA} token (in the template tokens in my plugins) to include photoTime() and currentTime(), and other changes to match the updated docs at that link.


Added the ability to create dynamic destinations on disk via naming patterns using plugin templates. This is a pretty big change, so you may want to test carefully before using it wholesale.

Reduced the amount of debug logging done, unless the "debug logging" option is checked in the plugin manager.


Oops, I was moving the original XMP file (when the Publish format was "Original" instead of copying it. Fixed.

Update to handle the Mac App Store version of Lightroom.


Added the ability to move/reset the root folder. As a byproduct, this should allow the "choose a root folder" situation to be repaired.

In some crazy file-renaming situations, the plugin could get confused about the file extension.

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

Added to the template tokens supported by the plugin: {FullMasterFile}, {FullMasterFolder}, {FullExportedFile}, and {FullExportedFolder}


When a new collection is created, require that the type be explicitly selected. This may help avoid screwups when one doesn't notice that there are different types to being with.

Update to handle 4.1RC

20120315.6 Add some extra debug logging to try to track down some network-folder errors.

Update to the debug logging to better track down timing issues that might arise.


Wasn't handling some kind of file-rename templates properly.

Now handles things much more gracefully when some files are offline when the publish is started.

Better support for video in Lr4.

20120217.3 Didn't handle XMP sidecars correctly when publishing original raw files.
20120217.2 Discovered why "metadata that triggers a republish" wasn't reliable, and fixed it.
20120213.1 Initial release, evolving from my earlier tree-publisher plugin, which dated back to the summer of 2010.

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


I’ve been using on of Rob Coles plugins until LR CC, where it stopped working unfortunately.
The way his plugin worked, was to create Standard Lightroom Collections (including Collection Sets) and configuring his plublishing service, and just dropping photos into service (unsorted).
By hitting publishing, it mirrored everything from the standard LR collections.
I was wondering if your plugin can be configured like this? I’ve tried, but only came to the concolusion, that I have to recreate all my Collections, right?
I realize that both version have disadvantages 🙂
* his was limited that you should place your photo only once in a collection
* yours forces me to recreate my collections, and possible “lose” the collection tree, should you plugin ever stop to work, for whatever reason 🙂

anyway, I still like this plugin and am still considering recreating everything from scratch.

Lightroom makes this really difficult to do the way someone would naturally want. Mine has nothing to do with whatever collections you might have in your Lightroom catalog; I can certainly see the desire to mirror your normal collections, but this would be kludgy to implement at best. )-: —Jeffrey

— comment by Ivan on August 4th, 2015 at 5:24am JST (1 year, 9 months ago) comment permalink

Hi Jeffrey,

I’m coming from Germany – between Hannover and Bielefeld…
I’m working with LR (current version: CC) for a few months and I have created many collection sets with sub-collection sets. Now I was looking for a tool to export my collection sets to my disk.
So I found your 2 tools: “Folder Publisher” and “Collection Publisher”
I tried the Folder Publisher – and it works fine, all folders and subfolders were published.
But with the Collection Publisher I’ve my problems.
I follow your instructions on your homepage and I create a new collection with “Part of its parent” – but the collection only published the fotos and not the structure of my collection set.
Then I tried “It’s own sub-folder” – the folder with the name of the collection was created but in this folder are only the fotos…

Hope you can help me
Thanks a lot in advance

Collection Publisher doesn’t work that way, sorry… it lets you set up your own collections for publish to disk, and doesn’t have anything to do with non-collections in your library. You’re not alone in wanting to do what you suggest, but Lightroom’s plugin infrastructure doesn’t make it easy. —Jeffrey

UPDATE: I’ve given a try to fitting this into the plugin, despite Lightroom’s plugin infrastructure making it really uninviting. See here. —Jeffrey

— comment by Wolfgang on August 6th, 2015 at 3:24pm JST (1 year, 9 months ago) comment permalink

I use a number of your plugins. Have LR CC 2015.0.1. I don’t understand about the folder name. Currently i have 2 files as plug ins:


Neither of these is in a folder and they, and others, are stored within a folder I have named LIGHTROOM PLUGINS.

What change should I make, or how can I get the update and begin using it??


I suggest deleting both and downloading the latest zip from my server, unzipping it (if your browser doesn’t do it automatically), then moving the resulting “collection-publisher-jfriedl.lrplugin” to your LIGHTROOM PLUGINS folder. Then point Lightroom at it via the [Add] button in Lightroom’s Plugin Manager. —Jeffrey

— comment by VINCE on August 9th, 2015 at 12:18pm JST (1 year, 9 months ago) comment permalink

For those looking to mirror their pre-existing collections, I’ve just added the ability to do so… see here. —Jeffrey

— comment by Jeffrey Friedl on August 18th, 2015 at 9:25pm JST (1 year, 8 months ago) comment permalink

The “mirror” feature is great !!!! …. I know we’re always ask more… but …. would it be possible to specify an “exclusion pattern to prevent mirroring ?

I usually create a collection set for eg holidays. then I create a collection names “ALL-xxx” containing all picture took during this holliday.
Then I create collection 01-fvisit thuis, then 02, visit that
I would be very comfortable for me to mirror the whole collection set “holidays” and ignoring all collections having names starting with “ALL”

Does it make sense ?

It makes sense, but I probably won’t add new features for a while, to see how it settles down. For the time being you could perhaps put the “ALL-” collections off the side somewhere, or just individually mirror the 01-fvisit, 02… collections one by one. —Jeffrey

— comment by Etienne Charlier on August 18th, 2015 at 11:47pm JST (1 year, 8 months ago) comment permalink

Hi Jeffrey,

Awesome to suggested features implemented! Totally understand the limitations.
Thanks, again

— comment by Ivan on August 19th, 2015 at 4:42am JST (1 year, 8 months ago) comment permalink

Hi Jeffrey,

last weekend i’ve tested your new mirror-feature and faced a problem. I’ve published my new mirrored collection set with several sub collection sets and collections. It works fine.
I developed some pictures in my source collection and added some new pictures – publishing works. But if I delete a picture – the collection publisher don’t recognized this change. The picture will still be published and will not be deleted.

Thanks a lot

After it gets published in error, run the “Refresh and Publish Mirrored Collections” in “File > Plugin Extras” to see whether it gets deleted. In either case, then send the plugin long with a note reminding me of the problem, being sure to explicitly note the image that should have been deleted. —Jeffrey

— comment by Wolfgang on August 31st, 2015 at 5:51pm JST (1 year, 8 months ago) comment permalink

Hi Jeffrey,

i’ve tried to “Refresh and Publish Mirrored Collections” in “File > Plugin Extras” – everything works fine!!!
Thanks a lot

— comment by Wolfgang on September 9th, 2015 at 3:18pm JST (1 year, 8 months ago) comment permalink

The mirror collection feature is great.

Usability would be much better if instead of having to go to “File > Plugin Extras” to run “Refresh and Publish Mirrored Collections”, users can right click on the “MIRROR: collection name” entry under the Collection Publisher and have a Refresh entry in the pop-up context menu.

Thanks for the great works.

No kidding, but despite having asked for access to the context menu for years, it’s still not available to plugins. )-: —Jeffrey

— comment by Minh on October 2nd, 2015 at 5:16am JST (1 year, 7 months ago) comment permalink


Do you have any suggestions on how to handle file sequencing? I’m scanning old photos in fairly random order with no particular file naming conventions. I then put them in collections and use drag and drop to put them into some sort of chronological or other logical sequence. Before starting to use your publisher, I would export and use LR file renaming to add a sequence number to the exported images so that they can be displayed on a website sorted by filename.

Using Mirrored Collections, the publisher collection looses the sequence worked out for the original collection.

I’ve had some success with re-ordering the images in the publisher collection, but it only seems possible for images which have been published. Dividing the display into images waiting to be (re)published and published makes sorting difficult.

I don’t have a warm feeling that any manual sorting I do will be preserved when selected images are modified and queued for republishing. Am I right to be worried – or do you think that any manual sort order will be retained during republish cycles.

I also see problems when adding new images and changing the sort order after images have been published. I suspect that I should manually delete all images in the target folder before doing a republish to make sure that any LR sequence numbers in the filename match the manual sequences in the complete collection of images to be published.

I’ve also had problem with virtual copies where LR doesn’t seem to put them in the same sequence as the manual sequence I use in a collection.

Does LR give the plugin/template access to a sort sequence number for an image within a manually sorted collection which I could use in the renaming section, rather rely on LR export sequencing.

Appreciate any thought you may have.
David. Harwell, UK

You’re certainly tickling a lot of spots where Lightroom doesn’t shine well, combined with the concept of sequence numbers, which are much more full of pitfall than one might at first imagine. For example, if you publish a bunch of images and then delete one, do you expect all the (perhaps hundreds of thousands of) other images to be renamed to fit? What if you then add a photo somewhere in the middle? It’s a huge can of worms. That being said, I’ve just pushed a new version of the plugin that has some support for sequence numbers…. see the “sequence numbers” link in the “Enhanced File Renaming” section of the dialog, and give it a try. Do be sure to keep fingers crossed and lucky socks on. —Jeffrey

— comment by David on October 11th, 2015 at 3:23am JST (1 year, 6 months ago) comment permalink

Hi Jeff, love the tools. Is it possible to do an auto publish every day or so? Using the lightroom mobile and if pictures are picked then would like to automatically publish to folder for apple TV or other services

You mean leave Lightroom running on an unattended computer, and have Publish run every so often (to reflect changes incorporated via Mobile)? I don’t know of a plugin that does this, but it’s certainly possible. —Jeffrey

— comment by Ian on October 15th, 2015 at 10:46am JST (1 year, 6 months ago) comment permalink

My collection publish works as excpected except it doesn’t publish video files that I shot on my iPhone. I get this error report:

An unknown error occurred. This photo was not rendered. (5)
/Users/thomas/Pictures/Lightroom managed/Tom’s iPhone/IMG_1569.MOV
/Users/thomas/Pictures/Lightroom managed/Tom’s iPhone/IMG_1572.MOV

The plug-in worked in the past but doesn’t anymore. I do have the include video files checkbox selected, I’ve tried both original files and H.264 format, the files requested are on my local drive.

Any ideas what’s not working?

Could you try the same export using Lightroom’s built-in “Hard Drive” export/publish? I suspect it’s a Lightroom issue unrelated to the plugin, and this would shed some light on that. —Jeffrey

— comment by Thomas White on October 30th, 2015 at 2:14pm JST (1 year, 6 months ago) comment permalink

I tried exporting the same set of videos from LR6 to Hard Drive twice–original format and H.264–it worked fine both times.

I tried deleting the videos fro the troubled publish collection and creating a new publish collection. Again the publish failed.

— comment by Thomas White on October 31st, 2015 at 2:05am JST (1 year, 6 months ago) comment permalink

I tried completely deleting the publish service and creating a new service that seemed to fix the problem. Working fine now.

— comment by Thomas White on October 31st, 2015 at 5:42am JST (1 year, 6 months ago) comment permalink

New question:

Is it possible to reorder the processing steps and inserted plug-ins used by Collection Publisher. It seems like “Crop for iPad” should be before Sharpen in the workflow.

Extras added via other plugins (like Crop for iPad) can be reordered among themselves, but they all fall together in the overall stack. Lightroom renders the copy of the image (with Sharpen, etc.) and then passes it to the extras, then to the main host plugin. You needen’t worry about Crop for iPad reducing quality… the crop is done with a special JPEG-processing tool that makes it completely lossless. —Jeffrey

— comment by Thomas White on November 1st, 2015 at 10:37am JST (1 year, 6 months ago) comment permalink

Hi Jeffrey,
I’ve been very happy with your Collection Publisher and the way I’ve been syncing my LR collections with my iPad thanks to your blog post

Now I have to relocate the root of my collection tree to a new folder on my hard drive. Can I feel pretty confident relocating the tree that won’t make a mess of all that I’ve already published to my iPad? Do you have any warnings or suggestions about a best way to do it to minimize potential problems?

Thank you,
Julliette from Belmont, Massachusetts

I don’t see much potential for a mess from the Lightroom side… at worse, you just have to republish to refill the local folders intended for your iPad, but I’d expect the plugin to handle the relocation fine. How it reflects on your iPad is dependent upon how you get them there and what app you use, but in general I’d think that no matter what method you use, the moved photos will appear on the iPad as different photos (and the old ones either deleted or left lying around), so any kind of work you’d done there (adding comments, etc., or whatever the app allows) would be lost. In my case I use the iPad only for display, so this wouldn’t bother me because I have no “value-added” data added on the iPad. —Jeffrey

— comment by Julliette on November 15th, 2015 at 8:39am JST (1 year, 5 months ago) comment permalink

Julliette here again, adding to the previous comment. The reason I want to move the collection tree is that I followed your suggestion and put it in my Dropbox folder, but now my Dropbox space allotment has reached its limit. Since I’m not syncing the tree with other devices, I don’t see any value to it being in Dropbox so I may as well move it.

BTW I read above that you added the function to mirror collections to jfCollections! That’s great, thanks!

— comment by Julliette on November 15th, 2015 at 9:36am JST (1 year, 5 months ago) comment permalink

I have a feature request for MIRROR support in your Collection Publisher plugin. I would like to create a “Smart Mirror Collection Set”. What I mean from “Smart” is that in addition to doing the normal Mirror operations I would like to filter the images that get mirrored (in my case I want to mirror only the photos in each collection that have a particular star rating). I wonder if it would be possible to leverage Lightroom’s existing smart collection filtering dialogs? The icing on the cake would be a way to integrate the collection publish plugging with smugmug. I might be able to use the ftp sync option but haven’t fully explored it yet.


— comment by Aaron on December 24th, 2015 at 11:37am JST (1 year, 4 months ago) comment permalink

Hi Jeffrey! Thanks so much for your work to extend Lightroom’s capabilities seemingly in every possible way.

I was hoping you could shed a little more light for new users of jf Collection Publisher like me on how it differs from the build in “Hard Drive” publish service. The web page says:

“Unlike a normal export, this publish service allows you to create an ongoing relationship between the photo in Lightroom and the copy on disk. The tree on disk is refreshed for any changes (new images, removed images, and image changes) each time you “Publish”.”

…but it seems to me that statement equally describes the built-in “Hard Drive” publish service. It too establishes an ongoing relationship between the photo in Lightroom and the exported copy on disk, and offers to re-export or delete updated and deleted photos, respectively, in Lightroom.

I see in a previous comment response that you confirm that your plugin follows the same concept as the built-in service, but that it offers the ability to “go beyond manually setting up the folder structure”. I’m unclear on exactly how. Having read the documentation in detail I see that synced collections offer the option to output photos to their parent collection or collection set’s output folder, thereby reducing the amount of folder structure generated, but I don’t get how this automates setting up the folder structure.

Perhaps you could explain a scenario or two that Collection Publisher is able to support but that the built-in Hard Drive publish service is not?

Thanks in advance, and sorry if I’m missing something obvious.

First of all, the bit about “ongoing relationship” applies to any Publish service, but Lightroom also supports a one-time “Export” (in Lr1 and Lr2, only Export was supported). So in this sense, “Hard Drive” and “Collection Publisher” are equal. Collection Publisher has many more features than “Hard Drive”, but if “Hard Drive” suits your needs, there’s no need to bother with anything else. Among Collection Publisher’s enhancements, it allows you to change the root folder, you can control the file date on exported copies, you can be warned if exporting via Smart Previews would degrade quality too much, you can explicitly set what metadata changes cause a republish (though Lightroom is notoriously buggy in this area, so this is of marginal benefit), you have much more flexibility in how exported copies are named (used to great effect here), and there’s a built in FTP transfer module that might come in handy for some workflows. —Jeffrey

— comment by Kevin Yank on January 16th, 2016 at 4:29pm JST (1 year, 3 months ago) comment permalink


How about WordPress library management as a Publish relationship? Does your collection tool allow “relationship” with the WP Media Library?

I have a few of your plug-ins; thank you for all the work on both the code and your effective customer service. I am working on a new template for my WordPress(.org) website so have to repopulate what will be a “big” Media Library just to re-collect them into galleries. All those images go “loose” in there, forget easy searching… whatever management/maintenance might be needed after the loose images are identified to WordPress as belonging on a page. I found one gentleman’s plug-in that manages the Library from within Lightroom, but I thought I should ask you about WordPress Publish support first. Once I collect in Lightroom a set of images that is a demonstration of a professional photography skill I can offer, I want to maneg that going forward within the easy interface of Lightroom.

I realize that image changes of any kind will still require that I go in and update the page on the web server through the WP dashboard. But I want tags to make it through to the Library. The keywords?

Thanks for thinking about this — Jonathan

I don’t have any blogging-specific plugins, sorry. I use an Export Preset to dump images for my own blog, the writing of which is still a fairly manual process. —Jeffrey

— comment by Jonathan Rawle on January 22nd, 2016 at 6:33am JST (1 year, 3 months ago) comment permalink

It would be nice, if I could export the xmp file too. I export my photos with Collection Publisher to .jpg for my Homepage. Now I want the xmp file too, so that I can read the metadata with a 3rd party tool.
Thank you

The data that would be in an XMP file is already included within the exported JPG. A separate sidecar file is required only when the original can’t hold the data, or you don’t want to modify an original. A tool that could read an XMP file should, one would hope, be able to find the same data within the JPG, because it’s there unless you go out of your way to strip it during or after export. —Jeffrey

— comment by Marco on February 26th, 2016 at 3:48am JST (1 year, 2 months ago) comment permalink


i have the same wish as Aaron
i would like to export only images with a rating or a minimal rating of x

Thanks you!

For this your best bet is to us a Smart Collection, using one of the rules to name the source collection you want to mirror. For me to add it to my mirroring stuff would require me re-inventing the wheel, so to speak, about smart-collection dialogs, rules, and actions. That’s a bit much. —Jeffrey

— comment by Daniel on April 13th, 2016 at 5:36pm JST (1 year ago) comment permalink

Hi Jeffrey, does the collection or folder Publisher also support publishing to an NAS or to local disk only (as does LR). My setup: Win10, LR6/CC. Best, Guido

Well, by definition of “NAS”, yes, it’ll publish to it once you do the “A” part and mount it so that it appears as a local disk. —Jeffrey

— comment by Guido on August 22nd, 2016 at 7:07am JST (8 months, 3 days ago) comment permalink

Hello Jeffrey,
I can succeed to export a collection using the button “Export”.
But in can’t find the button “Import” when i try to create a new service of publication vie Collection publisher – I can only see “export” event the service is not yet registered.

Could you please check if the fonction has not deasapear in the new version of your plugin ?


One doesn’t “Import” into a publish collection… just drag photos from the Library Grid into the collection. —Jeffrey

— comment by Richard on September 18th, 2016 at 4:58pm JST (7 months, 7 days ago) comment permalink

Hello Jeffrey,

Thanks for awesome Lightroom plugins! However, I have some problems with Collection Publisher plugin. I installed Lightroom to a new computer and opened the old catalog in which I had some old collections made with the plugin. Even though I have only “Title” and “Rating” triggering to republish, Lightroom is marking every old published photos to republish. This is very annoying because now I can’t publish any new photos because I have to wait that Lightroom has processed republishing. Is there anything that I could do to stop Lightroom marking the old pictures to republished?

Best regards

Adobe designed Lightroom to handle this situation, but the implementation is full of bugs that seem to bite at random times. The best I can suggest is to select photos you don’t want to republish (that are in the queue to republish), and from the right-click menu invoke “Mark as Up-to-Date”. —Jeffrey

— comment by Lasse on October 5th, 2016 at 6:37pm JST (6 months, 20 days ago) comment permalink

Hi Jeffrey, as a long term user of your fabulous collection publisher plugin I have just a simple
question: I was doing some picture renaming in my catalog and was hoping collection publisher
gets notice of this activity and automatically selects all photos for re-publish. Unfortunately
this did not happen and I needed to manually select the photos with the changed names for
publishing again. I had selected all options which lead to a re-publish in the collection
publisher settings under the section “Metadata that Triggers Republish”.
Would this be possible to introduce such a behaviour in the plugin ?
I personally think this would make much sense.
Thanks a lot for your awesome plugins and best regards,Heiko

Sadly, Lightroom doesn’t include filename or folder location among metadata that causes a republish. —Jeffrey

— comment by Heiko on October 11th, 2016 at 6:19am JST (6 months, 14 days ago) comment permalink

Is it possible to only publish images that are ‘picked’. I realize that I can create a smart collection that matches ‘picked’ but I would rather just publish all picked images without having this extra step, and also double the amount of collections I have.

If you select some photos in a Publish Collection and hold down the alt/option key, the [Publish] button becomes [Publish Selected]. Preparing the selection via the Library Grid Filter to show only Picks, then selecting them all, you can do it this way. —Jeffrey

— comment by Min on December 4th, 2016 at 8:21am JST (4 months, 21 days ago) comment permalink


Your plugins are impressive!! I’m wondering if one of them offers a feature I need…

I have thousands of photos across a set of Lightroom collections. In order to track changes and ensure that none are missing/accidentally deleted from the collections, I would like to export a list (ideally CSV or text file) from lightroom that shows which photos (folder/name) are in each collection. Alternatively if the collection names could be copied into the metadata, I could extract the info with exiftool.

Any suggestions/advice would be much appreciated!


Unfortunately, nothing comes to mind. The first idea (dumping data to a text file) would be possible with a custom plugin; I don’t think Lr/Transporter can work with collection data, but you might ask the author. The latter idea (writing collection names) would be more difficult because Lightroom doesn’t let you list all collections a photos is in… you have to walk every smart collection and accumulate data for all the photos. —Jeffrey

— comment by Craig on December 25th, 2016 at 8:43am JST (4 months ago) comment permalink

Hello, I love your work and now I own collection publisher! It saves me so much time and I completely do not understand why Adobe hasn’t done this or folder publisher.


I’m writing about nested collection sets. You cannot mirror these, as it makes a path with an > with isn’t an allowed character.

Trip (collection set)
|Day 1     (collection)
|Day 2     (collection)
|Approval needed     (collection set – Nested)
||Day 1a     (collection)
||Day 2a     (collection)

If I want to export Day 1a and 2a because they need approvals, I’ll export collection set Approval needed. However mirroring this collection set will automatically, an unable to edit, create a name of MIRROR: Trip > Approval needed.

I can work around this by temporarily moving the collection set to the stop but if this were changed I’d very much appreciate it.


The plugin was a bit too conservative, I guess. I’ve pushed out a new version that should work for you. —Jeffrey

— comment by Stuart on February 14th, 2017 at 5:50am JST (2 months, 11 days ago) comment permalink

Thank you! I updated and tested it. Thank you again for the quick response and all your hard work.

— comment by Stuart on February 23rd, 2017 at 11:57pm JST (2 months, 2 days ago) comment permalink
Leave a comment...

All comments are invisible to others until Jeffrey approves them.

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

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

Subscribe without commenting