Unnecessary retention
A one-time send can remain in storage, backups, sync folders, and stale shares long after the recipient has the file.
How to send encrypted files without a cloud-drive folder
Use PhotonFile Relay for a live encrypted handoff. Select the file, enable optional client-side encryption in a supported flow, share the full link with the recipient, and keep the session active until delivery completes.
Photon Transfer offers Live + Cloud delivery without creating a cloud-drive collection. Send together with Live Relay, or use temporary Cloud backing for pickup later. Use Vault for ongoing storage and managed sharing.
Live Relay: Both you and your recipients must remain online until the transfer completes. Keep your browser tab or desktop app running until all downloads finish.
Cloud Transfer: Recipients can begin downloading while you upload. Keep your browser tab or desktop app running until your upload finishes. After that, you can close it or go offline, and recipients can still download your files using the shared link. Cloud Transfer allows one confirmed delivery. Once the complete transfer is confirmed saved, new downloads stop and automatic deletion begins. Use Vault for repeated downloads.
Cloud transfers default to seven days from upload completion. Choose one to seven days with Free or File Pass funding, or up to the server maximum with Relay subscription funding. Use Photon Vault to keep, share, and sync files over time.
Encryption does not require permanent storage.
Client-side encryption protects files before Live or Cloud delivery. The file does not need to become a permanent cloud-drive object merely to move from sender to recipient.
Why a cloud-drive folder is not always the right path
Stored links are useful when later access is required. They add unnecessary retention and permission work when the real job is a one-time handoff while both sides are ready.
Overbroad permissions
A shared folder can expose filenames, adjacent content, or future additions beyond the one file being delivered.
Password-archive friction
Encrypted ZIP files create password distribution, compatibility, and revocation problems without solving delivery timing.
Mixed security models
Transport encryption, client-side encryption, recipient verification, and retention answer different questions and should not be collapsed into one checkbox.
Compare encrypted delivery methods
The best method depends on whether the file should disappear from the transfer path after delivery or remain available. Relay is the live, short-lived model. Vault is the persistent encrypted model.
| Method | When it works | Limitation | How PhotonFile fits |
|---|---|---|---|
| PhotonFile Relay | Both sides are ready for a live one-time handoff | The session must remain active, the full link must be protected, and client-side encryption needs a compatible PhotonFile client | Moves files through encrypted connections, with optional encryption on your device in supported flows. Live Relay does not store a copy for later download. |
| Encrypted ZIP by email | A small file and a recipient who can handle the archive | Password sharing, attachment limits, and no link revocation | Use Relay to avoid splitting the password and payload across an email workflow |
| Cloud-drive encrypted link | The recipient needs later downloads or ongoing access | The file becomes retained content and permissions must be managed | Use Vault when persistence is intentional. Do not force a live send into storage. |
| SFTP | Automation, scheduled jobs, or protocol requirements | Server accounts, client configuration, and key management remain operational work | Use Relay for human-driven one-time delivery and keep SFTP for integrations |
| Peer-to-peer tool | Both endpoints can connect directly and the network permits it | Peer IP exposure, NAT, firewall, or client compatibility may complicate delivery | PhotonFile uses a controlled relay path without requiring peers to expose network addresses to each other |
Prepare the encrypted handoff
-
1. Verify the recipient first
Confirm the person and contact channel before sharing the transfer link.
-
2. Choose Live or Cloud delivery
Schedule Live Relay when both sides can stay online, or choose Cloud transfer for pickup after upload.
-
3. Select only the intended file
Remove unrelated material and use a clear versioned filename.
-
4. Choose the encryption mode
Use optional client-side encryption in a supported flow when the recipient environment can open the full link.
-
5. Protect the full link
The link can contain the decryption material. Treat it as a secret and avoid broad or permanent posting.
-
6. Keep an integrity reference
Record the size or checksum when the recipient must prove the exact file arrived.
Relay workflow
Send the encrypted file in a live session
- 1. Open PhotonFile Relay. Use the web or desktop client supported by the sender and recipient environment.
- 2. Select the file or files. Confirm the version, size, sensitivity, and recipient before starting.
- 3. Enable client-side encryption when desired. In supported PhotonFile Desktop and browser flows, file chunks are encrypted before upload and the decryption material is carried in the link fragment.
- 4. Begin the transfer. Choose Live Relay for an active session, or Cloud transfer with funding and policy acceptance before upload.
- 5. Share the full link with the recipient. They can receive the Relay transfer without creating a PhotonFile account. The full link must remain confidential.
- 6. Keep the workflow active. For Live Relay, both sides must remain online with their browser tabs or desktop apps running until all downloads finish. For Cloud Transfer, keep the sender running until the upload finishes. After that, recipients can download using the shared link even when the sender is offline. Use eligible resume or Retry behavior after interruptions.
- 7. Verify and close. Confirm the file size or checksum, then end the session and handle the local source according to policy.
What the encryption layers do
TLS protects the connection
Relay traffic uses encrypted transport between the client and service. This protects data in transit on the network path.
Client-side encryption protects the payload
In supported PhotonFile Desktop and browser flows, file chunks are encrypted before upload so the relay handles ciphertext rather than plaintext file data.
The link carries access
Client-side encrypted links keep key material in the URL fragment. It is not sent in normal HTTP requests, but anyone with the full link may be able to decrypt.
Live state
Relay is short-lived by design
Encrypted chunks move during the active session instead of becoming a stored delivery bucket by default.
Client control
Optional encryption happens before upload
Supported client-side flows keep decryption material with the shared link rather than a server-side key.
Recipient access
No account is required to receive
The external recipient completes the live download task without becoming a PhotonFile workspace member.
The full link is sensitive
Client-side encryption does not make link handling irrelevant. The decryption material is part of the complete link, so a forwarded or exposed link can transfer access to someone else.
Verify the recipient and use a trusted channel.
Encryption does not prove compliance
Client-side encryption and encrypted transport are technical controls. Identity verification, data minimization, retention, local copies, incident response, and legal obligations still belong to the workflow.
Do not market a single encryption setting as automatic compliance.
Use Vault when the file must remain available.
Live Relay requires the sender to stay online during delivery. Cloud transfer temporarily stores encrypted files and supports downloads after the sender disconnects once upload completes. When versions must remain accessible or a managed share is required, store the file intentionally in Photon Vault and create a scoped share.
Where File Pass fits
One File Pass covers one occasional large transfer containing one or multiple files. Choose Live Relay when both you and your recipients can remain online until the transfer completes. Keep your browser tab or desktop app running until all downloads finish. Choose Cloud Transfer so recipients can begin downloading while you upload or download later. Keep your browser tab or desktop app running until your upload finishes. After that, you can close it or go offline, and recipients can still download using the shared link. A Live Relay pass is consumed at completed delivery. A pass used for Cloud transfer is consumed at complete encrypted upload, even if nobody downloads.
Common questions
Frequently asked questions
How do I send an encrypted file without uploading it to a cloud-drive folder?
Use Photon Transfer. Choose Live Relay or Cloud transfer, keep client-side encryption enabled, and share the full link. For Live Relay, both sides must remain online with their browser tabs or desktop apps running until all downloads finish. For Cloud Transfer, keep the sender running until the upload finishes. After that, recipients can download even when the sender is offline. Cloud Transfer allows one confirmed delivery. Once the complete transfer is confirmed saved, new downloads stop and automatic deletion begins. Use Vault for repeated downloads.
Does Live Relay store the file for later download?
No. Live Relay requires both you and your recipients to remain online with your browser tabs or desktop apps running until all downloads finish. Choose Cloud Transfer so recipients can begin downloading while you upload. Keep your browser tab or desktop app running until your upload finishes. After that, you can close it or go offline, and recipients can still download using the shared link. Use Vault to keep files and manage their share links. Cloud Transfer allows one confirmed delivery. Once the complete transfer is confirmed saved, new downloads stop and automatic deletion begins. Use Vault for repeated downloads.
What protects a Relay transfer?
Relay uses encrypted transport. In supported PhotonFile Desktop and browser flows, optional client-side encryption encrypts file chunks before upload so the relay handles ciphertext and the decryption key remains in the link fragment.
Does the decryption key go to the server?
With client-side encryption, key material is kept in the URL fragment, which is not sent as part of normal HTTP requests. The full link is still sensitive and must be protected.
Does the recipient need a PhotonFile account?
No. The recipient can receive a Relay transfer without creating a PhotonFile account.
Can I use a File Pass for an encrypted Relay transfer?
One File Pass covers one transfer containing one or multiple files. Live Relay consumes the pass after completed delivery. Cloud transfer consumes it after the entire encrypted upload completes, even if nobody downloads. File Pass funding for Cloud transfer includes a link with a selected download period of one to seven days from upload completion, defaulting to seven days without charging account storage or Relay allowances. Cloud Transfer allows one confirmed delivery. Once the complete transfer is confirmed saved, new downloads stop and automatic deletion begins. Use Vault for repeated downloads.
Keep going
Related guides
Send large video without compression
Deliver the original media file through Live or Cloud transfer.
Share files without requiring an account
Keep the recipient task separate from workspace membership.
Send sensitive documents securely
Add recipient verification, scope, retention, and post-download controls.
Product and technical references: Relay guide Ephemeral transfer model Relay technology PhotonFile FAQ File Pass pricing
Move the file. Do not create a storage folder.
Open Relay and choose Live or Cloud delivery. Keep client-side encryption enabled and the sender open until live delivery or the Cloud upload completes.