
Use Lightroom Classic's hard-drive Publish Service queues to track outputs that need exporting again. Adobe distinguishes New Photos To Publish, Modified Photos To Republish, Published Photos, and Deleted Photos To Remove. Inspect all relevant queues before clicking Publish, then check the actual files in the destination. The documented workflow is Export to hard drive using publish services.
Key Takeaways
- A modified catalog image does not prove its earlier export is current.
- Publish can process removals as well as new or changed images.
- Reconcile the destination against a named delivery list.
Define the delivery set first
Imagine a hypothetical client proof folder containing ten portraits. Two have revised crops and one has been withdrawn. Record those filenames and intended outcomes before running a publishing update.
A managed published folder serves a different purpose from Export With Previous. The latter reuses export settings; it does not provide this same queue-based view of the delivery set.
Check the service's destination, naming, file format, and sizing options. If it uses a smart published folder, inspect its rules so a rating change does not unexpectedly change membership. The Smart Collection guide explains that rule-based distinction.
Review the queues before publishing
Select the intended published folder. Find the two revised files under Modified Photos To Republish. Review New Photos To Publish for accidental additions.
Inspect Deleted Photos To Remove with particular care. Adobe states that published items marked for removal are removed from the folder on the next Publish operation. Do not assume the button only adds files.
Publish the intended folder and respond to any replacement prompt deliberately. Keep the workflow confined to a test delivery folder until you understand the resulting naming and replacement behavior.
Reconcile the files independently
Open the destination outside Lightroom. For the hypothetical job, confirm that the two revised crops match the approved views, the withdrawn file is absent from this delivery set, and the other intended files remain.
Count alone is insufficient. Ten outputs could include an obsolete portrait and omit an approved replacement. Compare filenames and distinctive visible details against the delivery list.
If the folder is copied to a client portal afterward, inspect that second destination separately. A correct local published folder does not prove the portal cache or uploaded set has updated.
This guide describes Adobe's managed export workflow with a hypothetical reconciliation example. It does not perform publication or deletion, and it does not treat a published folder as a backup of the originals.
Related tasks
- Why Did Export With Previous Use My Last Test Settings?
- Why Do Photos Disappear from a Lightroom Smart Collection After I Rate Them?
Sources and scope
- Adobe: Export to hard drive using publish services: Hard-drive Publish Services organize New, Modified, Published and Deleted queues; Publish processes waiting items and can replace newer versions and remove marked items.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance, not a claim of hands-on testing or independent review. Report a correction.
Cover: Pignatta / Pixabay, Content License. The city photograph is an illustrative source asset; it does not show this application or a test result.