Transfer session audio safely between studios

Agree the package and recipient

List the required masters, stems or session material, versions, timing references and supporting notes. Confirm the authorised recipient and intended purpose before sharing. Do not include unrelated project files, credentials, private identity documents or assets the recipient is not entitled to receive.

Use controlled transfer

Choose an appropriate trusted transfer route with the relevant access restrictions. Check the actual sharing settings and any expiry, not just the folder name. Sending a link does not confirm receipt, and a secret link can still be forwarded. Keep any password through an appropriate separate process where used.

Verify the received files

Provide a manifest of filenames, sizes and checksums where useful. Have the receiving studio check the package, required alignment and playback. A checksum supports byte comparison, not audio quality or legal permission. Investigate mismatches before work begins rather than guessing which export is current.

Close the handover record

Retain the sender, recipient, date, agreed use, approved version and receipt confirmation. Review access after the collaboration and follow applicable retention obligations rather than promising automatic deletion. This workflow does not connect a studio, upload client audio or activate a DistroBolt file-transfer integration.

Sources and review

Reviewed 4 November 2026. Platform requirements and plan terms can change. Examples are planning aids, not a promise of account access, release acceptance or earnings.

• NIST file-fingerprint basis
• DistroBolt permission records

Continue your release planning

• Gapless albums: prepare transitions and separate tracks
• Use file checksums to identify the approved master
• Name audio versions so your team selects the correct master

Ask the DistroBolt team about your release. Send a concise question and release reference; never send account passwords or verification codes.