Nexynto Transfer

Send files securely

Create an expiring transfer link with optional password protection. No recipient account required.

Nexynto Transfer

Add files

0/— files

Choose files and configure a real server-enforced expiry.

Copy the opaque transfer link after every upload completes.

Unlock protected transfers once, then download individual files.

Public and management tokens are cryptographically random and serve different purposes.

Expired and revoked transfers cannot create new downloads.

Coming in T2. No request workflow is represented as available today.

How do I send files with Nexynto Transfer?

Add files, choose an expiry and optional password, then create the transfer and share its secure link.

How long do transfer links last?

Choose 1, 3, 7, or 14 days. Expiry is enforced by the server and downloads stop immediately afterward.

Can I password-protect a transfer?

Yes. Passwords are hashed on the server and recipients receive a short-lived access session after unlocking.

Can I revoke a transfer?

Yes, from the browser that created it. Revocation immediately blocks public access and downloads.

Are transfer links public?

Anyone who receives the opaque link can open an unprotected transfer. Add a password when the link needs another access barrier.

Where are files stored?

T1 uses the configured object-storage adapter. This installation currently uses isolated local object storage with signed upload intents.

What happens when a transfer expires?

Downloads stop and the cleanup service removes expired transfer objects and manifests.

Can recipients download files without an account?

Yes. Accounts are not required for T1 transfers.

Is file transfer history available?

No. Account history and cross-device management are intentionally not claimed in T1. Management stays in the sender browser.

Can I send folders?

Folder hierarchy and resumable multipart uploads are prepared for T2 but are not enabled yet.