Browse Docs

Upload a revision as a new version

Add a new bounce to the same track so its review history stays together.

Last reviewed 4 September 2026

Before you start

You need an existing track in Mixhaus and permission to edit it. Owners and editors can upload versions and change which version is active. Viewers can see version history but cannot upload or switch versions.

Supported audio files are MP3, WAV, AAC, M4A, OGG, and FLAC. Wait until the export is complete before choosing the file.

1. Start from the existing track

  1. Open Projects, select the project, and stay on Overview.
  2. Find the track you want to revise and open its action menu.
  3. Select Upload New Version. When your plan includes spatial audio, the menu may say Upload audio version.

You can also open the track workspace and select New version. If a menu appears, choose Audio file. The same upload action is available from a track's action menu in Library.

Do not use Add Songs, Add Files to Project, or drag a file onto the project page for a revision. Those controls add a new track, which starts a separate version history.

Start from the existing track's action menu so the new bounce stays in its version history.

2. Choose the audio file

Choose the new MP3, WAV, AAC, M4A, OGG, or FLAC bounce.

Mixhaus checks the file and starts a private upload while the details dialog is open. It does not create the saved version until you confirm the details. The dialog can show Preparing upload..., Uploading while you add details..., Upload ready. Confirm to add it., or Finishing upload....

If Mixhaus finds tempo or key information in the filename or the audio metadata, it may fill those fields for you.

3. Add details

  1. Check Name. Mixhaus starts with the filename without its extension.
  2. Add Tempo (BPM) and Key if you know them. These may already be filled from the filename.
  3. Add Tags when they will help you find the track later.
  4. Leave a field blank if you do not need to change it. Blank tempo, key, and tag fields keep the track's current values when the upload is saved.

The version name, tempo, and key you enter describe this upload. Tags help classify the track.

Check the new version's metadata while Mixhaus prepares the private upload.

4. Confirm the version

When the dialog says Upload ready. Confirm to add it., select Upload. Wait for the success message before navigating away.

Mixhaus confirms Version uploaded and adds the revision to the track's Revision timeline. From a project, you may also see that the new version is ready to use.

Expected result

For a changed audio file, Mixhaus:

  • adds the next version number to the existing track
  • marks the new version Active
  • starts the new version at Draft
  • keeps earlier versions, feedback, and decisions in place
  • keeps the upload private until you deliberately share or send it

A review that was already sent continues to use the exact version selected for that review. Uploading a revision does not swap that review to the new audio.

What happens next

If your plan includes client review, open Review & Delivery in the project, select the track, check the active version, and send that version for review. Client review, approvals, and final delivery are available on Pro and Studio. Free still includes version timelines and comparison within its storage limit.

For private work, use Version History or open the track workspace and go to Revision timeline. You can compare versions, play an older version, or select Make active version to switch the current version.

This example shows the track workspace with the active version, feedback, and its revision timeline.

After the upload, the track workspace keeps the new active version and the earlier review record together.

Common problems

I created another track instead of a version

You probably used Add Songs, Add Files to Project, or the project drop zone. Remove the extra project item if you do not need it, then upload the bounce from the original track's action menu or track workspace. Removing an item from a project does not remove the original track from Library.

Upload New Version is missing

Only project owners and editors can upload. Ask the project owner for edit access if you have Viewer access.

The upload never becomes ready

Keep the details dialog open while the private upload finishes. Check that the file uses a supported extension and that your account has storage available. If you closed or cancelled the dialog, select the file again to start a new upload.

I expected another timeline row, but none appeared

Mixhaus checks the file's checksum. Uploading the exact same audio again may reuse the existing version instead of creating a duplicate row. Check that you selected the changed bounce before trying again.

The client still hears the old version

That is expected until you send or share the new version. A review link stays attached to the exact version that you sent. Open Review & Delivery and send the new active version when it is ready.

I need to make an older version active

Open Version History or the track workspace's Revision timeline. Select the older version and choose Make Active or Make active version, depending on where you opened the history.

Was this useful?