Large-file proxy workflow manager for photographers and retouchers

The moment a retoucher opens a 10 GB composite file on a mid-range workstation and watches their machine grind to a halt — then waits 4 minutes to save — is the moment they start googling for a better way to work. That moment happens daily in studios and freelance setups worldwide, and nobody has built a clean answer to it.

The gap persists because Adobe is structurally incentivised to sell you more RAM and a faster machine, not to make their software run well on the hardware most people already own. The performance ceiling is a business model feature, not a bug — upselling Creative Cloud storage and pushing users toward higher-spec hardware both benefit Adobe. Fixing large-file performance at the application layer would reduce that leverage.

What users actually need is a proxy-based editing layer that generates lightweight stand-ins for heavy source files, routes edits through the proxy during the creative phase, and then batch-applies those edits back to the full-resolution originals when rendering. This isn't a new concept in video production, but it simply doesn't exist as a clean, standalone product for still-image workflows in the 1–20 GB file range. Users reporting 'file handling freezes when opening huge size files' and 'the program gets laggy with files between 100–500 GB' are doing manual workarounds — flattening layers prematurely, working in reduced resolution, or splitting composites across multiple files — all of which cost them time and introduce errors.

This is a business because the pain recurs with every project. A commercial retoucher working on product photography or architectural images hits this every single week. Studios with multiple workstations need a consistent workflow, not a per-machine hack. The cost of the current situation is concrete: wasted hours, missed deadlines, and hardware upgrade cycles driven by software inefficiency rather than genuine need.

What to build

Build a desktop application that automatically generates proxy versions of PSD and TIFF files above a configurable size threshold, syncs edit metadata (adjustments, masks, crop) from the proxy session, and re-applies those edits to full-resolution originals via a batch render queue — integrating with Photoshop via scripting API without requiring the user to change their file structure.

Where to start

Start with architectural and real estate photographers shooting high-megapixel medium-format cameras — they have the most consistent file sizes, the most predictable layer structures, and the clearest pain because their turnaround deadlines are tight and their hardware is rarely top-spec.

The hard part

Photoshop's scripting API is deep enough for some automation but was never designed to support a full proxy-sync workflow, so early builds will hit edge cases with layer comps, smart objects, and adjustment layer stacking that require painful workarounds or capability restrictions.

How it makes money

Annual subscription per seat, priced below the cost of a RAM upgrade — around $80–120/year — with a team tier for studios managing shared file libraries on NAS.