A wedding photographer gets home after a 10-hour shoot with 1,800 raw files. They need to cull, apply a base grade, and export web-ready JPEGs before sending a preview gallery. Their laptop — a reasonably decent machine by normal standards — takes 3 hours to export that batch through Lightroom. They sit and wait, or leave it running overnight and find it crashed halfway through. The laptop isn't broken; it just wasn't built to process 1,800 36-megapixel raws in sequence.
The constraint is entirely hardware-bound: Lightroom and Photoshop's export and batch processing pipelines are local-only. There's no way to send a catalog and raw files to a faster machine and receive finished files back. The software companies haven't built this because it would require them to either host massive compute infrastructure or build a file sync layer — neither fits their current product architecture or business model. File sync is a commodity; compute-on-demand for raw processing is not.
Existing cloud storage services can hold the files but can't process them. What's missing is a job-queue service that accepts a folder of raw files plus a Lightroom-exported preset, processes the batch on cloud GPU hardware, and returns finished JPEGs or TIFFs — without the photographer needing to keep their laptop open, buy new hardware, or learn anything new. The photographer uploads, sets parameters matching their Lightroom develop settings, queues the job, goes to sleep, downloads finished files in the morning.
This recurs constantly — every shoot, every event, every client delivery. The cost without a fix is either 3-hour waits tied to a machine, missed delivery deadlines, or a $2,000+ hardware upgrade that the business can't immediately justify. For a working photographer doing 4-6 paid shoots a month, even $8-12 per batch job is cheaper than buying a Mac Pro.
What to build
Build a web-based raw batch processor that accepts a folder of raw files (CR3, ARW, NEF, DNG) and a Lightroom-compatible preset file, processes the export job on cloud GPU hardware using open-source raw processing libraries, and delivers the finished files via download link or direct Dropbox/Google Drive push — no desktop app required.
Where to start
Start with Sony ARW files and Lightroom-exported XMP presets only — a narrow enough format target to nail color accuracy before expanding — and recruit 10 beta users from Sony Alpha shooters communities where hardware complaints about batch export are especially common due to high-resolution sensor files.
The hard part
Raw file processing fidelity — color science, lens correction, noise reduction — varies significantly between Lightroom's proprietary engine and open-source alternatives like RawTherapee or darktable, so output from cloud processing may not match what the photographer previewed locally, which is a trust-breaking discrepancy in a color-sensitive workflow.
How it makes money
Pay-per-batch pricing based on file count and output resolution — something like $0.02 per exported file — with a monthly subscription tier for photographers who process more than 500 files a month that converts the per-file cost into a flat fee.
See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Photo Editing.
More ideas in Photo Editing