Lightroom Classic batch history and action duplication manager

The moment it becomes a problem: a photographer finishes editing a wedding gallery of 800 images and realizes they applied a specific combination of adjustments — skin tone correction, shadow lift, lens correction override — to one hero shot that now needs to be duplicated across 40 similar images. Lightroom's sync feature copies settings, but it has no memory of what was done in what order, no way to label and save that sequence as a named preset bundle, and no way to duplicate the history state itself. The history panel is per-image, non-exportable, and disappears when the catalog is moved or the image is removed.

This gap persists because Lightroom Classic's architecture treats editing history as a local, ephemeral log — it was never designed as a transferable workflow object. Adobe's incentive is to push users toward Lightroom (cloud) where sync is a selling point, so improving Classic's history system would reduce migration pressure. The user who complains — 'I wish it was easier to duplicate actions and saving history states was more intuitive' — is almost always a freelance or studio photographer who chose Classic specifically to avoid the cloud, meaning Adobe has actively reduced incentive to improve their experience.

The gap isn't just saving history — it's that there's no way to turn a successful editing sequence into a reusable, shareable recipe that another photographer on the same team can apply. Presets partially solve this but they capture endpoint values, not process. If step 3 of your workflow depends on what step 2 produced, a preset can't express that.

This is a business because every photographer who shoots recurring work — weddings, portraits, real estate, product — has a consistent visual style they re-implement manually on every catalog. That repetition is pure friction. A studio with three shooters sharing a house style loses consistency every time one editor makes a judgment call that others can't replicate because the process was never captured.

What to build

Build a Lightroom Classic plugin that intercepts and logs develop module history states into a named, exportable sequence format, lets photographers label and save those sequences as reusable 'edit recipes' distinct from presets, and applies them to selected images in the correct order via Lightroom's SDK.

Where to start

Launch as a free plugin for a single high-value use case: saving and sharing a named 'session style' across a two-person shooting team, which is a problem every second-shooter wedding workflow hits. Charge for team library sync and multi-catalog export.

The hard part

Lightroom Classic's plugin SDK exposes develop settings but does not expose history states directly — you'd need to reconstruct edit sequences by diffing settings snapshots at each user action, which introduces timing and reliability problems that are hard to debug without access to the host application's internals.

How it makes money

Free for single-user local use; $15/month per studio for shared recipe libraries synced across multiple Lightroom catalogs.