Updated October 2026 · Recording workflow
Save a new version at each major change, label it with a number and a short note, and never overwrite the previous version. Keep the last few versions and the final export, and archive the rest. Clear versioning lets you go back when a change turns out to be wrong.
Audio projects change a lot, and it is easy to lose a good version when a later change goes wrong. Versioning means saving the project at key points, so you can return to any earlier state. It is one of the simplest habits in audio work and one of the most useful.
Save a new version when you make a significant change: a new edit of the structure, a big level change or a new mix. Do not save a new version for every small tweak, or the history becomes noise. A version should mean something you might want back.
Use a number and a short note, such as v3_levelled or v4_music_under. The note tells you what changed without opening the file. Keep the labels consistent across the project, and follow the same pattern as your file naming.
Save a new file rather than replacing the old one. An overwritten version is gone, and you may need it later. If the file is too large to keep many copies, archive the older ones to external storage, rather than deleting them.
Keep the last few versions in an active folder, the final export and the raw recordings. Archive the rest, and write a short note at the top of the project about what each version did. A clean history helps you finish faster.
Before you publish, check that the export came from the version you intended. Use the version label in the export name, so there is no confusion later.
Versioning uses storage space, and very long projects need a plan. Keep the number of active versions small, and archive the rest. The aim is to be able to go back, not to keep every file forever.
Spot clipping, noise, rumble and level problems. Runs in your browser, nothing is uploaded.
At major changes, not every small tweak. A version should be something you might want back.
Keep the recent ones and the final export. Archive older versions to save space.
Rarely. Save a new file, so you can go back if a change is worse.
Put the version label in the export name, and note it in the project.
