A photographer shooting 500 RAW files per session eventually hits the wall where their internal drive is full — and Lightroom Classic's catalog, previews cache, and smart preview files alone can consume tens of gigabytes before a single source file is stored locally. The complaint 'heavy installation, takes a lot of space' from Lightroom Classic users isn't really about the install binary — it's about the catalog infrastructure that balloons over time as previews accumulate for every image ever imported.

Lightroom's architecture was designed around a local machine as the primary storage environment, which made sense in 2007. Today, photographers increasingly work across multiple drives, NAS devices, and external SSDs. The catalog and preview management tools inside Lightroom require the user to manually relocate, purge, or rebuild previews — operations buried in menus, with no visibility into what's actually consuming space or why. Users discover the problem only when their boot drive sends a low-space warning, not before.

What's missing is a standalone catalog health tool: it scans all Lightroom catalogs on the machine, maps the space consumed by each preview type (standard, 1:1, smart previews), shows what can be purged without affecting editing capability, and gives a one-click path to moving the previews cache to an external drive. It would also flag orphaned preview files from catalogs that no longer exist — a common accumulation point that Lightroom itself never surfaces.

This is a business because every shooting session makes the problem worse. It doesn't resolve once — previews regenerate, catalogs grow, drives fill. A photographer who solves it manually in January will face the same audit in July. IT managers supporting photography teams at news organizations or real estate agencies face this across 10–30 machines simultaneously, with no centralized view of which catalogs are bloated.

What to build

Build a macOS and Windows desktop utility that scans all Lightroom Classic catalog locations, inventories preview cache files by type and size, identifies orphaned or redundant preview data, and lets the user purge or relocate preview storage with a single confirmation — without opening Lightroom.

Where to start

Launch targeting wedding photographers specifically, since they have high per-session file volume, tight laptop storage, and active communities (forums, Facebook groups) where a working tool shared by one member spreads quickly to hundreds.

The hard part

Lightroom's catalog and preview file formats are SQLite-based but undocumented officially, so parsing catalog metadata accurately — especially across different Lightroom versions — requires reverse-engineering that may break on minor Lightroom updates.

How it makes money

One-time purchase for individual photographers with an optional annual update subscription; separate per-seat annual license for IT teams managing five or more machines.

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

More ideas in Photo Editing