A photographer has spent months building a Lightroom Classic catalog with carefully tuned presets and export recipes. But their laptop has 8GB RAM, and every time they run a batch export, the machine slows to the point where they can't do anything else — sometimes it crashes mid-export. The complaint 'it forces me to close other programs' and 'exporting is difficult' aren't abstract; they describe a concrete workflow that breaks down repeatedly on any machine that isn't high-end.

Lightroom Classic is architecturally a monolith. The export engine, the catalog browser, the develop module, and the adjustment history all live in the same process. You cannot run just the export pipeline without loading the entire application. Adobe has no incentive to change this — separating the export engine would be a major refactor with no new features to show for it, and their target buyer is increasingly the Creative Cloud subscriber on a new Mac, not the photographer stuck on a 2017 Intel machine.

The gap is structural: nobody has built a standalone batch export runner that reads a Lightroom Classic catalog file directly (.lrcat is a SQLite database), applies a defined set of develop settings, and exports files — without launching Lightroom Classic at all. This sidesteps the memory problem entirely because you're not loading the full app. Users currently have no option except to export overnight, leave the machine idle, or buy new hardware.

This is a business because export jobs recur constantly for any working photographer — weddings, portraits, real estate shoots all require batch exports of hundreds of files. The time cost of babysitting a sluggish export or restarting after a crash is real and recurring. A tool that lets them queue exports and walk away, on hardware they already own, has immediate and obvious value.

What to build

Build a standalone desktop app for macOS and Windows that reads a Lightroom Classic .lrcat catalog file, lets the user select photos and assign export profiles, and renders and exports those files using a process with a configurable memory ceiling — completely independently of whether Lightroom Classic is open.

Where to start

Target photographers who only need to export already-developed JPEG or TIFF files (not raw renders) as a first use case — this avoids the ACR licensing problem entirely and still covers a large share of the 'export is killing my machine' complaints, since many users develop first, then batch export finished files.

The hard part

Lightroom Classic's develop module uses Adobe's proprietary raw processing engine (ACR), which is not publicly licensed — so a standalone export runner that achieves pixel-identical output to Lightroom Classic is not legally or technically straightforward, and 'close enough' output quality will cost you the trust of working photographers who've calibrated their presets precisely.

How it makes money

Annual subscription at $39/year, with a free tier limited to 50 exports per month so photographers can validate output quality before paying.

See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Photo Editing.

More ideas in Photo Editing