Music file naming and version control: retire final_final.wav

A filename should survive leaving your folder

You open an old project and find final.wav, final2.wav and final_USE_THIS.wav. Somewhere in there is the mix the artist approved. The file names have strong opinions, but unfortunately they disagree.

A simple pattern gives you something more dependable: Mira_Harbor_Mix_v04.wav. Artist, song, type and revision are enough for many projects. Add an alternate when needed, such as Mira_Harbor_Mix_v04_Instrumental.wav.

This is a suggested convention, not an industry rule. The important thing is that the whole team understands it. Keep punctuation uncomplicated, use leading zeros if they help sorting and agree on a stable song identifier while the public title is still changing.

Approval deserves its own sentence

A version number tells you which revision you are hearing. It does not tell you whether the artist approved it, or for what purpose. A mix that is fine for rehearsal might still need work before release.

Keep a short record with the exact filename, approver and intended use. “Mira_Harbor_Mix_v05.wav approved by Mira for stereo mastering on 2026-10-07” leaves considerably less room for interpretation than a celebratory thumbs-up buried in a group chat.

If the decision changes, update the record and tell the team. Renaming every copy already in circulation can make the history harder to follow. It is usually kinder to preserve the filename and explain what changed about its status.

Give changed audio a distinguishable name

Even a small vocal edit deserves a new revision if someone is reviewing the audio. Otherwise, two people can hear different files with the same name and spend their time trying to explain a difference neither can locate.

A corrected folder label is another matter. If the audio is identical, you may only need to explain the naming correction. The rule should support clear communication, not turn every administrative adjustment into a production event.

Alternates need the same care. The instrumental from mix 04 does not automatically become the instrumental for mix 05. A shortened intro, changed guitar or new fade may require new exports. Keep each alternate connected to the revision it actually came from.

• Mix_v05: the current stereo mix.
• Mix_v05_Instrumental: the corresponding instrumental.
• Mix_v05_VocalUp: an explicitly requested alternate.
• Master_v02: a separate mastering revision sequence.

Write the change down while it is obvious

Right after exporting, you know exactly what changed. Three weeks and six songs later, that knowledge becomes less impressive. A line such as “v05: softer snare in verse two, original outro restored” is a small gift to the person returning to the project.

Include the source session or alternative when it will help you recreate the bounce. Apple’s Logic Pro documentation describes project alternatives for managing different project versions. That can preserve a useful branch of the work, but it does not replace an independent backup or a readable export name.

The person receiving the WAV cannot see your session history. Give them the part they need, without sending a diary of every fader movement.

Keep the current choice easy to find

A few folders can do a lot: Review, Approved and Archive. The current listening copy belongs somewhere obvious. Older copies can remain available without standing shoulder to shoulder with the file the team is supposed to use today.

There is no need to delete history just to make the folder look tidy. An earlier version may still be referenced by comments, a delivery email or someone else’s session. Preserve it while those connections are useful.

For each review round, choose one named reference. If everybody receives a different file called latest.wav, the first job becomes figuring out what everybody heard. That is an avoidable meeting, and probably not the one anyone wanted.

When the folder is already a mess

Start with a copy before reorganizing an old project. Listen to likely candidates and use dates and durations as clues. A newer modification date alone cannot prove that something is the approved mix; a copied or renamed file can muddy that trail.

Make a small inventory: existing name, what you have identified and intended use. Ask the decision-maker to confirm the current version rather than guessing which bounce sounds most finished.

Then begin the clearer system from there. Keep a mapping of old names to new ones if you rename files, so earlier feedback still makes sense. You do not need to solve the entire archaeology of the project before making the next export easy to recognize.