Utility

Shot naming generator

Build consistent shot and file names with VFX, episodic, commercial or Netflix-style delivery conventions. Generate one or a whole sequence and copy them with one click.

Convention

Tokens: {project} {ep} {seq} {shot} {task} {v} {desc} {date}. The rest of the text stays literal.



Batch

My saved presets PRO

Your cloud-synced naming presets. Load, delete or save new ones with the button above.

Loading…

Apply to files — generate rename script

🔒 100% local

Drop files or a folder. See the rename preview, then download a .sh (macOS / Linux) or .bat (Windows) script. Run it from your folder to rename. Nothing uploaded.

Drop files or a folder

Renaming follows the pattern + batch start number above.

Tip: on macOS, after downloading the .sh move it into the folder with your files, open Terminal there and run chmod +x pmt-rename-*.sh && ./pmt-rename-*.sh. Always review the script before running.

Naming best practices

A good shot name is readable by humans and machines: no spaces, consistent separators, zero-padded numbers and a clear version field. Number shots in tens so you can insert intermediate shots without renaming the sequence.

Uppercase or lowercase?

What matters is being consistent across the whole project. Many pipelines use lowercase for tasks (comp, roto) and uppercase for sequences/projects. Avoid mixing rules between shots.

What goes in “task”?

The pipeline step: plate, layout, anim, fx, light, lookdev, comp, precomp, roto, paint, matte, track… Keep a fixed, documented vocabulary for the team.