Files an editor can actually read

The problem it solves

Handing over a folder of camera-numbered clips moves the sorting problem to whoever opens it. That is an hour of someone else's life, repeated every project.

What it needs first

• Ingested footage, and a spine if you want bin-per-beat grouping rather than a flat rename.

How it works

1. 1 It works on the owned copyThe app renames the copy in its own workspace. Your originals keep their names and their place.
2. 2 Names come from the storyFiles are named for the beat and shot they serve, so the folder is organised by the video rather than by the camera.
3. 3 Failures are reported per fileAnything that could not be renamed comes back with a reason and a retry for just those files, rather than a count and a shrug.

What you get back

A proposed rename per clip

Computed, shown, and not executed. Dry run is the default: you see the full before-and-after list before anything touches the disk.

Bin-per-beat folders

The workspace is grouped by beat, so the folder structure itself carries the story order into your editor.

A per-item failure report

If a file cannot be moved, it comes back named with a plain-language reason, plus a retry that re-attempts only the failures.

What it will not do

• Your originals are never touched. Renaming operates only on the copies the app owns.
• It never assembles or trims a timeline. Markers and suggestions only.
• It will not silently overwrite. Name collisions are disambiguated rather than resolved by clobbering.

What it buys you

• Originals are never touched, which is the anxiety that stops most people organising at all.
• The naming reflects the story, so the folder is already a map of the edit.
• Partial failure is visible and recoverable.

Questions