Persistent edit history snapshots for destructive photo workflows

The moment that sends someone searching for a fix is simple: they're twenty minutes into a complex retouch, they hit Ctrl+Z expecting to step back two moves, and instead the image snaps between two states like a toggle. To recover, they either dig through the History panel clicking one state at a time, or they've already blown past the history limit and are staring at work they can't recover. That's when they realize the tool they pay for every month has a structural ceiling on reversibility.

The reason this gap persists is that Adobe has almost no incentive to close it cleanly. The History panel exists as the 'real' undo mechanism, and the single-step Ctrl+Z behavior is a legacy quirk they've patched around rather than fixed — partly because changing it would break muscle memory for millions of users, and partly because the History panel sells users on RAM upgrades and cloud storage. The fix requires touching core state management in a product with decades of technical debt. A standalone tool doesn't carry that weight.

What's missing isn't more history states inside the editor — users say 'editing requires thousands of tiny steps, so using the history is much more accessible,' which means the History panel itself is the problem. It's non-linear, it's buried, and it disappears when you close the file. What nobody has built is a layer that sits outside the editor and continuously snapshots edit states to a local timeline — not screenshots, but actual versioned file states — so a user can scrub backward through a session the way you'd scrub a video, without touching the History panel at all.

This is a business and not a feature because the need recurs every single session. A retoucher who loses 45 minutes of work once a week is losing roughly 30+ hours a year. The incumbent has no structural incentive to fix the root problem, which means the gap won't close. Users already pay for cloud storage and RAM to paper over this; they'd pay a dedicated monthly fee if the alternative is redoing work from scratch.

What to build

Build a background desktop agent for macOS and Windows that monitors open Photoshop and Affinity Photo documents, snapshots file states at configurable intervals and after every major destructive action, stores them in a local versioned timeline, and exposes a floating scrubber panel that lets users step or jump backward through any point in the current session without opening the History panel.

Where to start

Start with Affinity Photo users specifically — they're already on a one-time purchase model, they're more technically self-sufficient, and they have no cloud ecosystem catching their work, making the pain of irreversible edits more acute and the willingness to install a third-party tool higher.

The hard part

Reading file state reliably in real time without corrupting open documents requires deep integration with each editor's file format and save behavior — Photoshop's PSD format and Affinity's AFPHOTO format are both complex, and handling large files (100MB+) without tanking system performance is a hard engineering constraint that will force painful early trade-offs between snapshot frequency and disk usage.

How it makes money

Monthly subscription per seat, around $8-12/month, with a 14-day free trial; expansion path to team plans where a studio manager can set snapshot retention policies across machines.