Skip to main content

Can I protect my transfer with a password?

Add a password in web Send, help recipients open the files, and handle a wrong or forgotten password.

Written by Grigor

Yes. You can add an optional password when you create a transfer in Send on the web. Recipients need that password to open the transfer.

Use a separate transfer password. Do not share your Hivenet account password or Store encryption passphrase with recipients.

Add a password before sending

  1. Open Send and add the files you want to share.

  2. Choose Create link or Send email. Sign in or complete email verification if prompted.

  3. Enter the transfer password in the optional Password field.

  4. Complete the transfer and wait for Send to confirm that it is ready.

Give the password only to the intended recipients. Use a separate channel from the link when possible.

Open a transfer with a password

  1. Open the complete transfer link.

  2. Enter the password provided by the sender and select Open files.

  3. When the file list opens, select the files you need and use the download control shown.

  4. Wait for the download to finish, then open the saved files to check that you have a usable copy.

If the password is wrong or forgotten

Ask the sender to confirm the password. Enter it exactly, including capital letters and any intended spaces. If copying adds a space, check with the sender before changing it.

If the sender cannot provide the password, ask them to create a new transfer from a saved copy. The sender can also create a new transfer to use a different password. A new transfer does not cancel the original link.

What the password does not change

A password does not extend the link's availability or erase files that recipients have already downloaded.

The current Mac sending action does not offer a transfer password. Use web Send when you need this option. See sending from a desktop computer for the appropriate route.

If the password is accepted but the download fails, follow Send upload and download troubleshooting.

Did this answer your question?