How to send music to a client privately

For an unreleased master, check the sharing settings before sending the link. Passwords and access restrictions can limit who opens it, but they cannot prevent an authorized recipient from copying or forwarding the audio.

Check the sharing controls in your plan

General file-sharing services offer access controls too. WeTransfer supports password-protected transfers, and Dropbox offers passwords, expiry dates, and download restrictions on eligible plans. Check which settings your plan includes and test the recipient's view before sharing.

• Access: Does the link require a password or a specific account?
• Availability: When does the link expire, and can you change that date?
• Revocation: Can you disable or replace the link if you send the wrong version?
• Downloads: Can the recipient save the file, and what activity does the service record?

Disabling a link prevents future access through that link. It does not remove files someone has already saved.

How to send a master privately, step by step

1. Set access protection

Enable a password or restrict access to the intended recipients. Open the link in a signed-out browser to check what someone can see before entering credentials. Avoid putting confidential artist or track details in a publicly visible URL.

2. Share the password separately when needed

If the link and password travel in the same message, forwarding that message shares both. For sensitive releases, send the password through a separate channel and agree who may receive the files.

3. Check expiry and revocation

Choose an availability period that fits the job and tell the client when access will end. If you send the wrong file, disable or replace the link promptly, then contact the recipient if they may already have downloaded it.

4. Check download activity

A download record can help you follow up, but an anonymous event does not identify the recipient or prove that they saved the complete file. Ask the client to confirm receipt when that matters. A SHA-256 checksum lets them compare their downloaded file with the uploaded original.

A note on watermarking and leak tracing

Watermarking can add a recipient-specific identifier to a file. Depending on the system, this may help trace a leaked copy. It does not prevent copying, and any watermarking requirements should be agreed separately from link access settings.

Keep review and download permissions separate

A client may need to listen and leave feedback before the files are ready for download. These stages can use the same link: in Soneam, you release the selected files on the existing review page when they are ready. If a balance is due, downloads stay locked until payment is confirmed. See how to record client approval and how to send a master for review.

Frequently asked questions

How do I send music to a client privately?

Use a password or recipient access restriction, check download permissions, and agree when access should end. Test the link while signed out before sending it. These controls limit access; they cannot prevent a recipient from sharing files they have already saved.

Is WeTransfer safe for sending unreleased music?

WeTransfer supports password-protected transfers. Check the access, expiry, and download controls available on your plan before sending unreleased music. A password or revoked link cannot remove copies someone has already saved.

How do I password-protect an audio file to send to someone?

You can use an encrypted archive or a delivery link protected by a password. For sensitive files, share the password through a separate channel. Either the archive or the credentials can still be forwarded, so agree who may receive the audio.

Should a delivery link for a master expire?

Choose an expiry date that fits the job and tell the recipient when access will end. For ongoing access, check the storage and retention terms as well as the link settings. Keep your own backup in either case.

How do I know the client actually downloaded the master?

Download activity shows that a download was requested, but an anonymous event does not identify the recipient or prove that the complete file was saved. Ask the client to confirm receipt when needed. They can compare a SHA-256 checksum to verify that their copy matches the original.