Understand desktop sync

Desktop sync keeps a watched local folder and your Mixhaus account Library in step. The desktop app uploads supported local exports, downloads your matching remote files, and keeps changes in a durable queue when the network is unavailable. Capturing a file does not share it with a client. You still choose when a file enters review or delivery.

Before you start

Install and sign in to the Mixhaus desktop app, then choose a folder your DAW already exports to. Read Choose watched folders before adding a location.

How account sync works

A location syncs both ways between its watched folder and files owned by your signed-in Mixhaus account:

• A supported export created in the folder uploads to Mixhaus.
• A file you add or update in Mixhaus downloads to the folder.
• A known path with a changed checksum becomes the next version of that file.
• A move or rename keeps the same file identity and history.
• A new path starts a new track unless Mixhaus asks you to confirm a version match.

Use Sync or Sync now on a location, or Sync All, to request a catch-up. The queue keeps work pending through a temporary connection failure and retries it later.

Studio accounts

Studio uses the same account Library, file ownership, and watched folders as Pro. It raises the storage allowance and adds your studio name, logo, colours, and custom email templates to client-facing work. It does not add seats, members, or a separate workspace.

Each watched folder belongs to the signed-in account. Do not point a second Mixhaus account at the same folder. If the account session expires, sync pauses with Action required until you sign in again.

What changes travel

Sync tracks files by their stored identity, not only by their name. These changes can travel in either direction:

• New files and changed file contents
• Folder moves and file renames
• Deletes, which follow the rule below

When both Mixhaus and the folder change the same file before either side catches up, Mixhaus preserves both results. It downloads the remote result at the original path and keeps your local result as a separate file named like mix (Conflict 1234).wav. Check the conflict copy before deleting or replacing it.

An export in a new path can be a new track or a renamed version of an existing track. Mixhaus uses filename, folder, project, and recency signals to suggest a match. It does not analyze the audio. See Resolve a version match.

Deleting files

Deleting an owned file from Mixhaus or its watched folder deletes the same file identity on both sides. A web delete moves the cloud file to Trash and removes its matching local replica. A local delete records the same intent, even when the computer is offline, so an old copy is not downloaded again during reconciliation.

Trash keeps deleted files for 30 days before permanent deletion. Open Trash and choose Restore to reactivate the original file identity and history. Mixhaus then materializes it in its original sync scope. If an active file already occupies that path, resolve the path conflict before restoring. A new export created at the same path after deletion is a new identity, not the deleted file.

When sync pauses

The app checks that the watched folder is still the same folder before applying changes. If a removable drive is disconnected, the folder is unavailable, or its identity marker is missing, sync pauses and shows Action required. Reconnect the original folder and restore its read and write access. Do not point the existing location at a different folder.

Temporary network errors leave items pending for retry. A permanent item failure appears in Failed items. Choose Retry failed or Retry All after fixing the cause. Pause stops a location deliberately; Resume starts it again.

What happens next

Use Choose watched folders to configure a safe export location, then Resolve a version match when a renamed export needs a history decision.