Transfers
Transfers is Kadrenta's way of handing finished files to a client without going through a separate service. Drop files in, give them somewhere to go, and a link appears that anybody with it can open. Unlike a review round or a card on a canvas, a transfer is not meant to stay. It always has an end date, and the files it carries clear themselves out once that date passes.
Two letters is enough, and it reads every chapter.
How do I send files to a client?
Open Transfers in the top bar. Drop files in; they show as a list, and you can take any of them back off again before sending. Give the delivery a title (your client reads it at the top of their page; leave it blank and it gets a generic name), an optional line to go with it, and choose how long it stays up: 3 days, a week (the default), two weeks or a month. A passphrase is optional. As the form puts it, it is "the only thing between the link and whoever it gets forwarded to." Then Upload.
Why does it ask who it's for before the upload starts?
So that a large upload does not need watching. Type in who it is for, press the button that says it is going to send, and Kadrenta sends the moment the upload finishes, with nobody needing to sit and wait for it. Nothing goes to a client without a person deciding it: you decided, in as many words, before a single byte went up.
Two things always hold. A failed upload sends nothing. The send only fires once every file in the batch has landed. And the screen says, before you walk away, that it is going to send and to whom.
If you don't want that, leave the "Send it to" field empty. Nothing goes out on its own, and the link still lands on the receipt afterwards, ready to copy and hand over yourself.
If you plan to walk away from your desk: an upload lives in the browser tab that started it. You can leave your desk while it finishes. You cannot close your laptop. Kadrenta does not run an upload in the background the way a native app might; if the tab closes, the upload stops.
Which files can go in a transfer?
Anything. Unlike a review round or a canvas card, which only take what a browser can display, a transfer takes EXR sequences, TIFFs, MKV, FBX, OBJ, Alembic caches, installers, fonts, project files from other software, and a .zip of up to what the upload transport can carry. Anything over 64 MiB is chunked automatically, so a broken connection during a large upload only costs the one part that failed. If you upload a .zip, the transfer page shows what is inside it, names and sizes, without anyone needing to download it first to check.
Do I have to upload work twice to send it?
No. If the work is already on a shot, Transfer sits right beside Send to review on the version list. Tick the versions you want and send them without uploading anything again. The delivery points at the file the version already uses, so a large render is not copied and not counted against your storage twice.
What does my client see?
Their own page: the title you gave the delivery, your note, a plain list of files each with its own Download button, and one Download all above them that hands over everything as a single zip (behind the passphrase, if you set one). You can see how many times each file has been fetched, including a visible zero, which is the row worth a nudge.
Why does every transfer expire?
There is no "forever". After the end date the link stops opening and the files clear themselves out, so nothing piles up in your storage. Thirty days is the longest a single transfer can run, and that ceiling holds even after an extension. Pushing the date out is one press of "more time," but it can never add up to more than a month from today. A transfer is a hand-over, not a shared drive.
Your client is told this too. Their page names the date the files are there until, and asks them to save the work somewhere of their own before then.
What if I need more time?
Extend the delivery from the transfer's own page. That is the "more time" button, capped at a month out from today as above. If a transfer has already run out and you want a client to reach it again, extending it there is the way back. The files are not in the trash, because nothing was ever deleted; a date passed.