Loading page
Free template · updated October 2026
Short answer: name every cut {project}_{cut}_{round}_{date} - for example acme-launch_cutA_r03_2026-10-12. Lowercase, no spaces, zero-padded rounds, ISO dates. Anyone opening the stack reads exactly where they are, and no file is ever called final again.
Filenames are a user interface - for your team, your client, and future-you at 11pm before delivery. This convention fits in one line, sorts correctly, and pairs with stacked versions so history stays readable.
Every version name follows {project}_{cut}_{round}_{date} - no exceptions, no extra words.
Different creative directions get cut letters (cutA, cutB); rounds within a direction get numbers.
Rounds are r01, r02 (sorts correctly); dates are YYYY-MM-DD upload dates.
Upload each round onto the same video stack. Old names never change - history is append-only.
Paste the one-line legend into your review message so clients read versions like you do.
How to read our versions: acme-launch_cutA_r03_2026-10-12 means project “acme-launch”, creative direction A, 3rd round, uploaded Oct 12. Always review the newest round - older ones stay below for reference.
Bare numbers collide across projects, don't say which creative direction they belong to, and sort badly past v9 without padding. The full pattern stays unique and readable across your whole workspace.
In the approval record: who signed off, on which version, when. Filenames describe what a file is; approvals describe a decision. Mixing them is how final_v7_REALLY-final happens.
Frooty stacks versions so history is automatic, and the convention keeps names human-readable on top. Apply the pattern when you upload each round - it takes ten seconds and saves hours of “which cut?” confusion.
Upload rounds into one versioned project and let the stack keep history straight.
Create a project