Updated October 2026 · Recording workflow
Use one consistent pattern for every file, such as date, project, what it is, take number and version. Put the most important part first, avoid spaces and symbols, and keep the same order across the whole project.
A folder of files called final, final2 and new-mix-v3 is a common sign of a project that will be hard to finish. Good names cost a few seconds each time you save, and they save hours when you come back to a project later or hand it to someone else. The rules are simple, and the discipline is what matters.
Decide on a pattern once, and write it down. A useful one is date, project, content, take, version, for example 2026-10-25_episode12_intro_take03_v2. Use the same order in every file, so you can scan a list and read the story of the project at a glance.
Starting with the date in year-month-day form keeps files in order when sorted by name. It also tells you at once which file is newest, without opening it.
Use take numbers for raw recordings, and version numbers for edits, such as v1, v2 and v3. Never overwrite a version. Save a new file, so you can go back if a change is worse. The project versions post covers how to keep the history tidy.
Name the raw files, the project file and the export with the same base name, so you can match them at a glance. An export called episode12_final should come from a project called episode12, not from a file called mix_new.
A naming pattern only works if you use it every time. Set up a template for new projects, and check the names before you archive. A small amount of consistency beats a perfect scheme you rarely follow.
Spot clipping, noise, rumble and level problems. Runs in your browser, nothing is uploaded.
It sorts files in order by name and shows the newest one without opening it.
Better not. Underscores or dashes work better with most tools and scripts.
Rename the active ones in a batch, and keep a note of the old names for anything archived.
Yes. Small projects grow, and good names make the change easy to manage.
