Share files securely with session-based links that expire automatically. End-to-end encryption keeps keys in your browser — RookFile never needs a permanent inbox.
Create a session, share the link, upload files and collaborative text. When the session expires, files are deleted — no WeTransfer-style long-lived cloud copies.
New sessions encrypt files in the browser before upload. The server stores ciphertext only. Keys stay in your browser and are wrapped to joiners via encrypted invites — not a URL fragment. Compare the Key fingerprint out of band.
Send files up to 1 GB per session with chunked upload support suitable for sensitive documents, builds, and media.
Encrypted Temporary File Sharing exists to open a temporary session, upload files that expire with the session, and keep end-to-end encryption keys in the browser. It is not a second copy of the tool homepage. The homepage introduces the whole product. This page stays on one job so a search for that job lands on instructions you can follow without hunting through other tabs. Read the result on this page against the input you actually used. A screenshot without the input is not evidence. If the result surprises you, change one thing and run it again before you change your VPN, browser, or server config.
Work through Encrypted Temporary File Sharing in order. 1. Create a session and set the lifetime. 2. Share the session link with the people who should upload or download. 3. Confirm the key fingerprint out of band if the session is encrypted. 4. Let the session expire instead of leaving a standing download URL. Write down the input and the output together. When you ask someone for help, send both. Repeat the same input once. A stable tool returns the same answer. If it does not, the input changed or the page is talking to a different network path than you think.
RookFile is not a permanent drive. The link is access. Send it only to the people who should have the files. A burned secret is still the right tool for a password. Treat the output as a measurement, then decide. RookVPN does not log the contents of a client-side tool, and a measurement is not a promise that every other app on the device behaves the same way. Compare a second path when the decision matters: a terminal command, another browser, or the matching guide linked below.
Example: you create a session, upload a 400 MB archive, and send the link. The other person downloads it the same day. When the session ends, the server copy goes away. That is the opposite of a file host that keeps the object until you remember to delete it. If they needed a password for the archive, that password goes in RookSecret, not in the file name.
After you finish Encrypted Temporary File Sharing, open the large-file page if size is the question, or RookSecret for a passphrase if the next question is different from the one this page answers. Stay here if you are still on the same job. Extra pages help only when they answer a new question, such as a different algorithm, a different leak channel, or a different file type. The documentation link on this page is the long form of the same workflow, including the checks that do not fit in the tool UI.
Use Encrypted Temporary File Sharing for one job: to open a temporary session, upload files that expire with the session, and keep end-to-end encryption keys in the browser. Bring the before-and-after evidence with you if you change a setting. A VPN icon, a decoded token, a generated password, or a stripped file is not finished until you have checked the output the way this page describes. Then follow the related guide for the long version, and the sibling tool only when the next job is actually different. Keep secrets out of the same message as the link or the file that needs them. If a second run does not match the first, stop and find what changed instead of publishing the first result.
Example: you create a session, upload a 400 MB archive, and send the link. The other person downloads it the same day. When the session ends, the server copy goes away. That is the opposite of a file host that keeps the object until you remember to delete it. If they needed a password for the archive, that password goes in RookSecret, not in the file name. Work the page in this order: Create a session and set the lifetime. Share the session link with the people who should upload or download. Confirm the key fingerprint out of band if the session is encrypted. Let the session expire instead of leaving a standing download URL. Limits that still apply after a clean result: RookFile is not a permanent drive. The link is access. Send it only to the people who should have the files. A burned secret is still the right tool for a password.
Yes. Create temporary encrypted file sharing sessions at rookvpn.com/file without paying for basic use.
No. Active session pages are noindex. Only marketing pages like this homepage are meant to be indexed.
RookFile uses ephemeral sessions and default end-to-end encryption instead of long-lived cloud storage. Files are deleted when the session expires.
No account needed for basic sessions. Sign in for longer session TTL and larger storage limits.
Sessions accept transfers up to about 1 GB. Larger than that needs to be split or moved another way.
New sessions encrypt in the browser. The server stores ciphertext. Compare the key fingerprint out of band.