Limits vary
A successful send to one organization does not prove the same attachment will pass through another.
How to send a file too large for email
Upload the original file to Photon Vault, create a share link for that file, and put the link in your email. The recipient can open it later, so the link behaves like an oversized attachment without forcing the file through the mailbox limit. Paid Photon Vault has no per-file upload size restriction, so you can upload files of any size.
Photon Transfer offers Live + Cloud links for temporary delivery. Choose Photon Vault when the files need ongoing access 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.
The email carries the link. Vault carries the file.
This keeps the familiar email workflow: write the message, explain the attachment, and include one place to retrieve it. The difference is that the file stays in Vault until the recipient is ready rather than traveling inside the email itself.
Why email rejects large files
Attachment limits are not controlled by one mailbox alone. The sender, recipient, mail gateway, security scanner, and forwarding path can each apply a different cap. Email encoding can also increase the transmitted size, so a file that appears to fit locally may still be rejected in transit.
Copies multiply
Attachments can remain in sent mail, inboxes, archives, backups, and forwarded threads long after delivery.
Retries are unclear
A bounce may arrive late, and the sender may not know whether the recipient received a complete copy.
Compare realistic ways to send it
Replace the attachment with one link. Choose Photon Transfer for Live + Cloud delivery, including temporary pickup after upload. Choose Photon Vault for ongoing access to selected files or folders.
| Method | When it works | Limitation | How PhotonFile improves the workflow |
|---|---|---|---|
| PhotonFile Vault share | The recipient should retrieve the file later | The retained file uses Vault capacity and the share link must be managed | Replaces the oversized attachment with one scoped link to the selected file or folder |
| PhotonFile Relay | Both people are ready for a live handoff | It is not intended for later downloads | Provides a purpose-built live delivery option when email-style access is not needed |
| Email attachment | Small, routine documents | Unpredictable limits and persistent mailbox copies | Put the file or directory in Vault and send one scoped link instead of placing the file in the mailbox |
| Split archive | The recipient explicitly requires multipart files | Every part must arrive and be reassembled correctly | Upload the file or directory to Vault and share one simple link |
| Messaging platform | Quick, low-risk collaboration | Retention, file handling, or download rules may not fit the job | Keep the message for context while Vault holds the complete file and its managed share link |
| Cloud-drive folder | Ongoing collaboration and version access | Folder permissions can expose more than one finished deliverable | A Vault share targets the selected file or folder, so the delivery scope can stay narrower than the workspace |
| Live file transfer | Both people are ready at the same time | It does not behave like an attachment that can be opened later | Photon Transfer offers live handoff or temporary Cloud pickup. Vault provides ongoing access through a scoped share link |
Prepare the delivery before you share it
-
1. Send the right version.
Give it a clear name so the recipient does not mistake it for an earlier draft.
-
2. Upload the finished file or directory.
When several files belong together, upload and share the finished Vault directory. There is no need to create a ZIP just to preserve the delivery layout.
-
3. Share the smallest useful scope.
Share one file for one deliverable, or a carefully reviewed directory when the recipient needs the complete set, and revoke the share when access should end.
Vault workflow
Send the oversized attachment as a Vault share
- 1. Open or create a vault. Use a vault that matches the client, project, team, or sensitivity of the file.
- 2. Unlock the vault. Upload and sharing controls need the active vault to be unlocked.
- 3. Wait for the full upload. Do not create the share link until every expected file appears in the Vault delivery.
- 4. Confirm the full delivery. Check that every expected file appears before creating the share link.
- 5. Select the exact file or folder. Share only what the recipient needs.
- 6. Create and copy the share link. Use the Vault share action for the selected item.
- 7. Put the link in the email. Explain what the file is, its approximate size, and any deadline or handling instructions.
- 8. Manage the share afterward. Revoke the link when access should end, and keep or delete the retained file according to your workflow.
Available later
The recipient does not need to be online now
Vault retains the file so the recipient can retrieve it after the email arrives, while the share remains active.
Scoped access
Share the deliverable, not the workspace
A Vault share link targets a selected file or folder instead of giving the recipient broad access to the vault.
Managed lifecycle
Keep control after sending
Review the share later and revoke it when the recipient no longer needs access.
Wait for the full delivery
Do not create a share link until the full delivery appears in the Vault. A directory link created while files are still uploading would be scoped only to the files that have finished, leaving the delivery incomplete. Keep the browser tab open until a browser upload completes, or use PhotonFile Desktop when its background Vault transfer queue better fits a long desktop upload.
Keep the local original until the recipient confirms a successful download.
Treat the share link as access
Verify the selected file or folder, send the link through a channel you normally use with that recipient, and do not reuse it for unrelated recipients or projects.
Use share management to revoke the link when the delivery is complete or the recipient should no longer have access.
When Relay is the better tool
Use Relay when both people are ready now and the goal is a live handoff rather than later downloads. Relay should not be the primary recommendation for an email-style attachment replacement because the sender and receiver workflow needs to stay active until the transfer completes.
Common questions
Frequently asked questions
What is the best way to send a file that is too large for email?
Wait until the full delivery has uploaded before creating a share link. A directory link created earlier would show only files that have finished uploading, so it could be incomplete.
Can the recipient download the file later?
Yes. With Cloud transfer, recipients can download after your upload finishes, even when you're offline. They can also start downloading during upload. For files you want to keep and share over time, use Vault. A Vault share works while the file stays in Vault and its link remains active. Manage or revoke the Vault share when delivery is complete. 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.
Should I split a large ZIP into smaller parts?
Only when the recipient specifically requires a multipart archive. Otherwise, one Vault upload and one share link are simpler and reduce the risk of a missing part.
Should I share a file or a folder?
Share the smallest useful scope. Select one file when the recipient needs one deliverable, or share a carefully reviewed folder when several related files must stay together.
Can I stop the share link from working later?
Yes. Photon Vault share management lets you revoke a share link when access should end. Do not reuse the same link for unrelated recipients or projects.
What file-size and storage limits apply?
Retained files count toward Vault storage usage. Paid Vault storage has no fixed capacity limit. Storage beyond the included amount is billed at $0.04/GiB-month. Vault Free has 10 GiB included, no paid overage, and files that expire seven days after upload. Client, account, and abuse controls still apply.
Keep going
Related guides
Send large CAD files securely
Package drawings, models, links, fonts, and project assets before sharing the finished bundle.
Send sensitive documents securely
Add deliberate scope, link handling, retention, and recipient verification to the send.
Replace human-driven FTP transfers
Map external delivery, intake, and persistent storage to simpler workflows.
Product and technical references: Vault overview Upload and organize files Vault sharing guide Vault pricing Photon Transfer: Live + Cloud
Send the link now. Let them download the file later.
Upload the finished file to Vault, create a scoped share link, and place that link in your email as the replacement for the oversized attachment.