V14_FINAL_FINAL is no longer a filename
Vandall saves every upload as a version automatically. Compare side-by-side, restore an old one, attach notes per revision. No more emergency Slack threads at 11pm.
Every upload is a version
Drop a new bounce, Vandall keeps the old one. No file naming gymnastics, no overwrites, no silent loss.
Compare side-by-side
Play two versions at once, see the waveform diff, A/B without leaving the project.
Restore in one click
Decide V8 was actually the keeper. Restore it as the current version. The old current becomes V13.
Notes per revision
Tag each version with what changed. "EQ pass on vocals", "client wants more low end". Searchable later.
Lossless preserved
Versions stored at original quality. The V1 you uploaded six months ago is still 24-bit WAV.
Audit trail
Who uploaded what, when. If a version went missing, you can see exactly when it happened.
V14_FINAL_FINAL is replaced by a real version stack
Open a project and you see every bounce ever uploaded, oldest at the bottom, newest at the top. No filename math. The current version is the one on top, and the rest sit underneath, ready to play.
- Every upload becomes a numbered version automatically.
- The stack lives inside the project, not in a Dropbox folder.
- Each version keeps its original 24-bit WAV quality.
A/B two mixes without bouncing them into the same session
Pick any two versions and play them side-by-side. The waveforms align so you can spot the change. The notes for each version sit next to the player, so you remember why V9 sounded thinner than V11.
- Switch between any two versions mid-listen.
- See the waveform diff next to your notes.
- Threaded comments stay tied to the specific version.
Restore v3 from your phone before the gig
You are on the way to a venue and the engineer asks for the older mix. Open the mobile app, tap the project, choose the version, restore it. The current version moves down the stack, the old one moves up. Same stack on every device.
- Restore from desktop or mobile — same stack, same versions.
- The old current becomes the next version down, never deleted.
- Whoever has the share link gets the new current automatically.
See who uploaded what, and when
Every version carries an audit trail: who uploaded it, from which device, at what time. If a collaborator swears they sent the new vocal take, you can check. We never silently delete versions, so the trail stays intact.
- Per-upload timestamp, uploader, and device.
- No silent deletion — versions stay until you remove them.
- Permalink per version for sharing a specific revision.
What you get with Vandall version control
| Versioning | 4 capabilities |
|---|---|
| Every upload becomes a numbered version automatically. | |
| Original quality preserved — 24-bit WAV stays 24-bit WAV. | |
| Notes per version, searchable across the project. | |
| Mobile and desktop see the same version stack. | |
| Comparison & restore | 4 capabilities |
| Play any two versions side-by-side. | |
| Restore an older version as the current one in a single tap. | |
| Permalink per version for sharing one specific revision. | |
| Threaded comments stay tied to the version they were left on. | |
| Audit & access | 4 capabilities |
| Audit trail per upload: who, when, from which device. | |
| No silent deletion — versions stay until someone removes them. | |
| Unlimited version history on every plan, limited only by storage. | |
| Accidental project deletion can be recovered through support. | |
Frequently asked questions
All plans keep unlimited version history. The only limit is the storage available on your Vandall account. We do not delete versions silently.
Keep reading
Threaded and timestamped comments
How feedback stays tied to the exact moment in the exact version.
Why music file sharing is a mess
The naming, the duplicates, the lost masters — and how versioning fixes it.
Collaboration use case
How versions, comments, and access fit together when more than one person is on a track.
File sharing use case
Send a track without losing the prior take or the lossless quality.
For engineers
Mix revisions, recall notes, and a clean stack across every session.
Mastering and release prep
Why a clean version history is the difference between a smooth master and a panicked one.
No more lost masters.
Every revision, every change, every decision tracked. Restore any version in one click.