Choose one file
The browser reads and encrypts the file locally. The filename, type, size, and bytes are protected inside the encrypted container.
ENCRYPTED FILE SHARING
Share an encrypted file without uploading a server copy.
this2.link encrypts the file on your device, creates a private capability link, and sends authenticated encrypted chunks from an online browser. No account or cloud-drive folder is required.
Start an encrypted transferAES-256-GCM · local processing · no account
THIS2LINK / CHANNEL
01BROWSER AENCRYPT LOCALLY
WEBRTC / CIPHERTEXT
02BROWSER BVERIFY + RESTORE
NO SERVER FILE COPY
PROCESS
What happens to your file
Send the private link
The complete link contains the capability needed to join and decrypt. Treat it like a temporary access key and share it only with the intended recipient.
Keep a source online
An open source browser sends encrypted chunks. A completed receiver can temporarily become the next source while its page remains open.
WHY IT IS DIFFERENT
Encryption happens before transfer
The application server does not receive a plaintext upload or keep a downloadable file copy. Each chunk is authenticated, and the receiving browser verifies the complete encrypted container before offering the restored file.
When browsers can connect directly, transfer uses a WebRTC DataChannel. On a restricted network, bounded ciphertext may pass temporarily through the WebSocket relay; the relay does not receive the file key or plaintext metadata.
GOOD FIT
Useful for short-lived handoffs
Use it for a document, image, export, draft, or other single file that needs to move now rather than live in a permanent shared folder. It is especially useful when neither side wants to create an account.
- One file at a time, up to 150 MB
- Browser-based on desktop or mobile
- The same channel can also pass plain text
- No offline archive or permanent hosting
BOUNDARIES
Security and availability boundaries
The full link grants access
Anyone who receives the complete capability link can access the content while a source is available.
Temporary means temporary
Availability is not guaranteed after the final source browser leaves or its local cache is removed.
Networks still matter
WebRTC is preferred, but strict NAT, VPN, firewall, or browser policies may require the encrypted relay or prevent a transfer.
FAQ
Encrypted file sharing FAQ
Does this2.link upload my file to cloud storage?
No. The application has no server-side file store. An online browser provides the encrypted content, with a bounded ciphertext relay available when direct networking is blocked.
Can this2.link read the file?
The file and its metadata are encrypted locally. The decryption capability stays in the URL Fragment, which browsers do not send in normal HTTP requests.
How large can a file be?
The current preview accepts one file up to 150 MB. The same limit is enforced at the encrypted relay boundary.
Does the link expire at a fixed time?
There is no promised fixed lifetime. The practical limit is source availability: once the last browser holding the encrypted content leaves, the link may stop working.
Encrypted file sharing, without server-side file storage.
Start an encrypted transfer