ClipCan ClipLogger name files from my logged metadata?
Yes, that's the point of the token templates. A template like {f:team}_{action}_{players}_{original} composes an output name from your confirmed fields (only confirmed values; pending suggestions never reach a filename), plus built-ins like {date}, {reel}, {scene}, {shot}, {take}, {rating}, and a {seq} counter with padding, start, and step. Any palette field is addressable as {f:key} or plain {key}.
What's the difference between rename-on-copy and the Rename bench?
Rename-on-copy names the copies during offload and never touches originals. The Rename Files on Disk tab is the in-place bench for files already on disk: point it at a folder or at your current browsed/filtered set, stack rules (find/replace with regex, token template, case transform, sequence), and watch a live before→after preview per file. Nothing happens until you apply.
What happens when I apply a batch rename?
Review the proposed source-to-destination names and collisions before applying. The action changes paths on disk and coordinates the associated metadata according to the operation's result. Existing NLE projects may still refer to the old paths. Keep the before/after mapping and use only the recovery or undo options actually offered for that run.
Do my sidecars and metadata survive a rename?
Use ClipLogger's rename workflow so it can coordinate media and owned metadata. Inspect the outcome, especially if a file is unavailable or a destination is occupied. Do not assume a partial operation moved every companion file. Preserve the mapping and backup until playback and downstream references have been checked.
Why rename on disk at all if ClipLogger has display names?
Because the filename is the one field every application reads. A display-name template can title clips inside ClipLogger without touching disk; the written-file-name template bakes your scheme into the files themselves, so Premiere, Resolve, Finder, and a stranger's machine all see 72_TD_Johnson_A001C012.MOV. Each project's palette carries both templates, and the Rename tab defaults to the active project's scheme.
Can I go the other way and turn filenames back into metadata?
Yes. "Parse Names → Metadata" reads your template against existing filenames and writes the recovered field values back through the normal logging resolver. A confirmation shows exactly what will be written before it happens. It's the recovery path for footage that was named by convention before it was ever logged.