Feature

New cut? Stack it,
don't overwrite.

Version chaos is the oldest bug in editorial: final_v2_FINAL_new.mp4. In Aperture, a new version keeps its place in a stack — nothing is ever overwritten, comments remember which cut they were about, and the compare view shows exactly what changed.

The easy explanation

A family photo album, not a shredder.

Each upload is a new page in the album, not a replacement. v1 stays. v2 sits on top of it. When the client asks "what changed since Tuesday?", you open both and watch them side-by-side, synced — because "trust me, it's better" is not an answer.

Version stacks
Every upload keeps its place in the line. History is a feature, not clutter.
Side-by-side compare
Two versions, one screen, synced playback. Eyes decide, not memory.
Context-aware comments
A note made on v1 knows it was made on v1 — even after v4 exists.
Approval on record
The sign-off names the version. Compliance stops being archaeology.

The quiet superpowers.

Upload from the asset detail view — a new version is one drag
Version history strip — scrub the lineage like a playlist
Threads survive version changes; resolved decisions stay searchable
Approvals land in the audit trail — exportable as JSON/NDJSON
Duplicate detection stops the same cut entering twice by accident

"We stopped naming files final. We started stacking versions."

— versions & compare

In loving memory of v2

v1 was not bad. It was a rough draft of v4.

Stack versions instead of overwriting them. Compare side-by-side, synced — because "trust me, it is better" is not an answer.

Stack the versions