• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Stop struggling with Lightroom! There's no need to spend hours hunting for the answers to your Lightroom Classic questions. All the information you need is in Adobe Lightroom Classic - The Missing FAQ!

    To help you get started, there's a series of easy tutorials to guide you through a simple workflow. As you grow in confidence, the book switches to a conversational FAQ format, so you can quickly find answers to advanced questions. And better still, the eBooks are updated for every release, so it's always up to date.
  • 12 December 2024 It's Lightroom update time again! See What’s New in Lightroom Classic 14.1, Mobile & Desktop (December 2024)? for Feature updates, new cameras and lenses, and bug fixes.

Export Existing files management broken on batch exports?

oakifphoto

New Member
Joined
Apr 16, 2024
Messages
4
Lightroom Version Number
14.1
Operating System
  1. macOS 15 Sequoia
It looks like the "extisting files" management feature is broken on batch exports.

This is one of my export presets:
1738502450876.png


These are existing files with the corresponding names:
1738502484925.png


This is what I see after exporting with a batch preset:
1738502512520.png


As you can see, the name of the preset, along with a "-2", is appended to the filename. The original files are not replaced. This also happens if you select anything else from the "existing files" dropdown.

I just started using batch exports, which was added last year. I'm not sure how such a large bug exists on such a major feature over a year after its release. Unless I'm the only one whom this is happening to.
 
I think that behaviour is as designed. After all, a user might be exporting the images(s) using multiple presets with the output going into the same folder....and they might have different options selected for the "Existing Files" option. The user is warned that some settings will be greyed out and ignored when doing batch export using multiple presets. See this Adobe help document: https://helpx.adobe.com/uk/lightroo...photos-basic-workflow.html#multi-batch-export

I have attached a screenshot of the important note at the end:

How_to_export_photos_from_Photoshop_Lightroom_Classic.jpg
 
I think that behaviour is as designed. After all, a user might be exporting the images(s) using multiple presets with the output going into the same folder....and they might have different options selected for the "Existing Files" option. The user is warned that some settings will be greyed out and ignored when doing batch export using multiple presets. See this Adobe help document: https://helpx.adobe.com/uk/lightroo...photos-basic-workflow.html#multi-batch-export

I have attached a screenshot of the important note at the end:

View attachment 25454
There's nothing in that support article that contradicts how it should behave, which is different from what it does right now.

"If there is any conflict in file naming" should not supercede the "overwrite without prompting" option. It is meant for when two files with the same name are exported to the same folder due to the selection of multiple presets during a single batch export, not across multiple exports. Otherwise the "existing files" option would be grayed out (which is it not, and if it were supposed to be, that itself would be its own bug).

In any case, there definitely is a bug because the same thing happens when you choose "skip" in the existing files options. It does not skip the export. @Califdan
 
What does the preset do because it looks like it is doing some renaming which could be contributing to the problem.
It keeps the original filename, but one preset exports it to a "hires" subfolder and the other one to a "web" subfolder. There should be no naming conflicts. I tested with different suffixes, different numbering, and even completely different folders and file naming for both presets, but this behavior persists.

I think the best option right now is to just select the presets individually and export manually. Takes 10 seconds more than being able to select multiple presets and doing a batch export, but the overwrite or skip functionality actually works. Not sure why there's the difference as I'm essentially doing the same thing in both instances, just in two different ways.
 
Back
Top