Sending files

Sign in, press New transfer, and drop files on the dropzone. Up to 50 files per transfer by default, each up to 2 GB — both configurable.

How an upload actually works

The composer does three things in order, and it is worth knowing because it is what makes large transfers survivable:

1. A draft is created. An empty transfer row, with no files yet and nothing e-mailed.
2. Each file is uploaded in its own request, streamed straight to disk rather than buffered in memory. A 20 GB transfer costs the same working set as a 20 MB one, you get real per-file progress, and a single failed file can be retried without starting the whole thing again.
3. The transfer is sent. Only now is anything e-mailed, and only now does the retention clock start — an upload that took an hour doesn't eat an hour of the recipient's download window.

A draft that is never sent is swept after NUXT_DRAFT_MAX_AGE_HOURS (24 by default), so an abandoned upload doesn't quietly fill the disk.

Recipients, or none at all

Type one or more addresses and each gets an e-mail with a download button. You get a receipt with the same link, so you have your own copy.

Leave the list empty and nothing is e-mailed: you get the link on screen and pass it on yourself, by message or chat or your own mail client. This is the right choice when you don't have the address, or when the recipient is a group.

A transfer can address at most 25 recipients. Each one is an outbound e-mail, and that cap is what stops the instance being used as a mail relay.

The message

The subject and message you type appear on the download page and in the e-mail. Replies to that e-mail go to you, not to the system mailbox — which is what a recipient will try first.

What the recipient sees

A page with your name, your message, the file list and a Download all as ZIP button. The zip is streamed and stored rather than compressed, so it starts immediately even on a multi-gigabyte transfer instead of making the recipient wait while the server packs an archive.

Filenames are reattached on the way out. On disk every file has a random name, which removes path traversal, reserved Windows names and case-insensitive overwrites as a class of problem rather than sanitising them one at a time.