Version control for songs: keeping every take without losing track

Why the filename keeps growing

Nobody plans mix_final_v3_ACTUAL_final_USE_THIS.wav. It accretes, one honest decision at a time: you finish a mix, you name it final, and then you change the vocal. The new one cannot also be called final, and you are not willing to overwrite the old one, because you are not certain yet. So the name grows a suffix.

The suffix is doing real work — it is holding two facts, which version is newest and which version is the good one, in a place that can only hold one. Those facts come apart constantly. The newest mix is frequently not the one you want to send.

What version control actually means

Programmers hit this decades ago and settled on a shape that is worth borrowing. Every change is kept forever, one version is marked as the current one, and the two are separate ideas — you can move the pointer without destroying anything, and you can go back without hunting through filenames.

The part that does not transfer is merging. Two people editing different lines of a text file can have their edits combined automatically; two vocal takes cannot be merged by any tool, and anyone who tells you otherwise is selling something. What transfers is the history and the pointer.

What is worth keeping

Not every bounce. You will make forty while nudging a hi-hat, and thirty-nine of them are indistinguishable. The useful test is whether the version left the room.

Anything you played to another person

That is the version they have opinions about. When someone says “I liked the old one”, this is the only way to know what they mean.

Anything before a decision you might reverse

Before you re-cut the vocal, before you drop the second verse, before you commit to the new arrangement. Bounce first, then change it.

Anything you sent anywhere

Submissions, a collaborator, a label. You want to know exactly what they heard, months later, when they finally reply.

The one that is current

Marked, not inferred from the date. The newest render is not reliably the one you would want played.

A scheme that survives

If you are doing this with folders, dates beat numbers: 2026-03-14 sorts correctly forever, while v12 tells you nothing about when or why. Put the date first, then the song, then one word about what changed — 2026-03-14 disappear new vocal. The word is what makes the list readable a year later.

The thing folders cannot do is mark which one is current, which is why the marker usually ends up as a second copy of a file, and why the second copy eventually goes stale. That is the specific job software can do and a folder cannot.