Client-side encryption
In both encrypted modes, your device encrypts the file with AES-256-GCM before upload. Quick Send does not provide browser encryption.
Pixurity Send
Upload one file with a resumable connection, then share a download link that stays valid for 24 hours after the upload finishes. Free for everyone — no signup required to send or download. Maximum 1 GB per file; expiry is fixed at 24 hours.
Checking your Send allowance…
In both encrypted modes, your device encrypts the file with AES-256-GCM before upload. Quick Send does not provide browser encryption.
Standard Encrypted Send carries the key after #k= in the URL fragment. The fragment stays in the browser and is not included in HTTP requests. Anyone with the complete link can open the file until expiry.
The link contains no decryption key. The recipient must also enter the separate code you share through another channel.
Links automatically expire 24 hours after upload completion. Download requests then fail, and stored data is removed by cleanup.
No. Quick Send, Encrypted Send and Encrypted + code are free for everyone, with no signup required. Recipients also need no account. A necessary 24-hour cookie keeps a guest browser’s sending allowance and upload ownership; signed-in users use their account allowance.
Each original file can be up to 1 GB (1,000,000,000 bytes), in any file format. Encryption overhead does not count against this original-file limit. All modes share the same rolling allowance, currently 3 sends and 2 GB of original files per 24 hours. Paid plans do not increase Send limits.
Quick Send uploads the file as supplied over HTTPS and stores it temporarily in private storage; it is not encrypted in your browser. Encrypted Send encrypts it locally with AES-256-GCM and places the key in the full link’s #k= fragment. Encrypted + code encrypts it locally too, but requires a separate code instead of a key in the link.
Your browser encrypts the file with AES-256-GCM before anything is uploaded. In standard Encrypted Send, the decryption key is carried after #k= in the sharing link. URL fragments stay in the browser and are not sent in HTTP requests, while only the encrypted data goes to temporary storage. The recipient's browser uses the complete link to decrypt the downloaded data locally.
With Encrypted Send or Encrypted + code, Pixurity's storage receives ciphertext, not the readable file, and the decryption key or separate code stays in the browsers. This zero-knowledge design does not apply to Quick Send, which uploads and stores the file as supplied over HTTPS.
Standard Encrypted Send puts the decryption key in the complete link for convenient opening, so anyone with that link can access the file until it expires. Encrypted + code keeps the key out of the link and protects it with a separate code; the recipient needs both the link and that code to decrypt the file. Share the code through a different channel for the intended extra protection.
Every Pixurity Send link expires 24 hours after the upload finishes. After expiry, download requests are rejected and the stored data is removed by the cleanup process. The expiry is currently fixed rather than chosen by the sender.