Tresorit Send: what to do with lost links and download limits

A Tresorit Send package gives you two links with different jobs. Recipients need the Send URL to get the files. You need the Admin URL to manage that package, including revoking its link. Save both when you create a send, and label them by purpose. If you lose the Send URL, the Admin URL cannot recover it: Tresorit says the download URL contains a decryption key that it does not store.

There is a second limit to plan around. Tresorit Send allows 10 downloads of each file, not 10 downloads of the package and not 10 different people. Plan for completed downloads of the file, including a second transfer when someone needs another device. Opening a previously saved local file does not require a new transfer.

Save the links when you create a send

Tresorit Send requires an email address. After adding the files and choosing any available password or email notification options, select Create Secure Link. Copy and save the recipient Send URL before leaving the creation page. Tresorit emails the separate Admin URL; open that emailed Admin link to verify the sender address for that upload, then keep it with your record of the send.

A simple private record might say:

• Release A, recipient URL: the link sent to recipients
• Release A, Admin URL: the link used to review or revoke Release A

The labels matter when you have several sends for the same project. Give recipients only the Send URL. Keep the Admin URL where you can find it if a file needs replacing or access needs to end.

A send can contain up to 100 files at once, with a 5 GB total limit and a 5 GB limit for one file. Its link is available for seven days. You cannot edit or update its files after creation, so correcting a file means creating another send. If delivery will run across a closed weekend, account for the seven-day window when you choose when to share the link; these rules do not establish an exact expiration time of day.

Count downloads by file

Suppose logo.svg, manual.pdf, and readme.txt are in one send. Their download allowances are separate. Eight completed downloads of logo.svg leave two for that file, regardless of how often readme.txt has been downloaded.

Here is a synthetic planning example, not a record from a Tresorit account. Say logo.svg has already had eight completed downloads. Two people plan to download it again, and one more person still needs a first copy. That would be 8 + 2 + 1 = 11 downloads, one beyond the file’s limit. If only one repeat is needed, 8 + 1 + 1 = 10 fits. Meanwhile, eight downloads of readme.txt count toward readme.txt, not logo.svg.

The same rule matters for a group send. Twelve people each downloading the same file once would require 12 downloads of that file, even though Tresorit permits up to 100 files in a send. Putting those files into one ZIP would make the ZIP one uploaded file; it would not raise that file’s 10-download allowance. Grouping may make distribution simpler, but it does not solve a download-count shortfall.

Budget for expected repeat downloads as well as recipients. A recipient who needs a second copy has a practical reason to use another download; the 10-download figure alone does not tell you how many distinct people will be served. The example assumes completed downloads as stated. It does not establish how an interrupted transfer is counted.

Calculate the remaining download budget

Open the per-file download budget calculator. It uses whole-number counts for one file and does not connect to Tresorit or read an actual download counter. The starting example is eight completed downloads, two additional completed downloads, and one download you want to reserve. Its result is eleven, exceeding the documented allowance by one.

Change the additional-download count to one. The total becomes ten, with the final reserved download included. Clear the reserve count and you are planning nine. This lets you distinguish a delivery that barely fits from one that leaves room for another completed transfer. Each file needs its own calculation; do not add all files’ download counts into a shared ten-download pot.

The inputs describe assumed completed downloads. They deliberately do not try to predict the product’s treatment of previews, interrupted attempts, or Download all. Check the actual product message and activity for those questions. A link-open email is not a substitute for a completed-download count.

Replace a file with a new release

Suppose you sent Release A with logo.svg, manual.pdf, and readme.txt, then found an error in manual.pdf. The files in Release A cannot be changed in place. Create Release B with the corrected manual and whichever other files recipients need in the replacement package. Save both Release B URLs and open its emailed Admin link to verify that new upload.

Then find Release A’s Admin URL and revoke Release A. Tresorit describes revocation as permanent. Send recipients the Release B Send URL, identifying it as the replacement so they do not keep using the old message. Release B is a new send with its own files and download allowances; it does not add downloads to Release A or silently redirect its recipients.

The order of the labels helps prevent a common mistake: revoking the newly created package while the erroneous one remains available. Write down which Admin URL belongs to A and which belongs to B before acting. Revocation stops access through the old link, but it cannot take back copies someone already downloaded.

Diagnose a missing link

If you have the Admin URL but lost the recipient Send URL, first check wherever you saved or sent the recipient link. The Admin URL is a control link, not a substitute download link. Tresorit says the download URL’s decryption key is not stored and that losing your copy requires a new link. Create a new send for the recipients, save its two URLs, and use the old package’s Admin URL if you also need to revoke the old link.

If you have the Send URL but cannot find the Admin URL, search the email address used for the Admin confirmation. Each Admin link requires email verification when opened. Do not send the recipient URL to someone as a way to control the package; its job is to provide file access. If the email address was entered incorrectly or the Admin email cannot be found, the documented steps here do not establish a recovery method, so avoid promising that the old package can be revoked through the recipient link.

If a recipient says the link no longer works, check the specific package before guessing at a cause. Was that recipient given A after B replaced it? Was A revoked? Has the seven-day availability period passed? If the issue is that one file reached its 10 downloads, another file in the same send may have a different remaining count. These are distinct situations and call for distinct fixes: share the correct current URL, or create a new send when a fresh package is needed.

Use the right control for the scope

The Admin link can show opens and lets you enable email notifications later. An open event is useful for tracing activity, but it does not prove who read a file or that a download finished. Tresorit says activity remains available for 14 days after revocation.

To end access to one package, select Revoke link now on that package’s Admin link. Tresorit also documents suspending an email address, which revokes all active sends associated with that address and blocks creation of new ones. That is a broader action than cleaning up one outdated release.

The seven-day link window describes when recipients can use a Send link. It is separate from server data retention. A recipient URL becoming unavailable does not establish when every stored file or administrative record has been erased. If retention affects your use of the service, check the vendor’s current retention information separately.

Source note: Based on Tresorit’s Send overview, Admin link guide, and FAQ, with source information checked October 7, 2026. The download counts and Release A/B scenario are synthetic; no real account test is represented.