Files and storage

Why was my upload added as a new version?

A file named like a song already in the project arrives as its next version. You can take it back out from the version menu.

Updated 2026-09-26 · published 2026-09-20

When an uploaded filename matches an existing track after its version suffix is removed, the file is added as the next version of that track. For example, "Gold Hour v1.wav" and "Gold Hour v2.wav" become two versions of one track. The newer version becomes current for client playback.

Recognized suffixes include "v2", "rev 3", "take 4", "final", "master" and "mix". The remaining name must match exactly. A number on its own is not a version suffix, so "Study 2.wav" and "Study 3.wav" remain separate tracks.

Unresolved comments carry over as they do when you add a version manually.

On Free, a track can retain three versions. A fourth upload is added as a separate track rather than rejected.

If a file was added to the wrong track, choose Make this its own track from the version menu. Its comments and approval move with it. It becomes v1 of its new track, unless an approval record, a release or a pinned review link names its number; then it keeps that number so the record still matches.

The other way round: if a file came in as its own track but is the next mix of another, drag it by its ⋮⋮ handle onto the right half of that track’s card, where “Add as versions” appears (moving up and down on the left reorders instead), or choose Add to another track as its next versions from its ⋯ menu. Its versions are numbered after the ones there and keep their comments, and the version your client hears on that track stays the same. A track with an approval record, released files or a pinned review link stays as it is.

The version menu, with Make this its own track above Delete
The menu on a version: the way back out.

Not covered here? Write to support@soneam.com.