Automatic transcoding
A platform may create a viewing rendition with different bitrate, resolution, frame rate, color handling, or audio settings.
How to send large video files without compression
Send the original media file through PhotonFile Relay while the recipient is ready to receive it. Relay moves the selected file as a live transfer instead of creating a smaller viewing rendition.
Use a File Pass when the video is an occasional oversized per-file send. The pass uses the same live Relay path and is consumed only after successful completion.
A preview is not a master.
Messaging, social, and review platforms may create lower-bitrate or lower-resolution viewing copies. Keep the camera original, mezzanine master, or approved export as a file and deliver that file through a transfer workflow.
Why large video delivery goes wrong
The biggest risk is often not the upload itself. It is choosing a platform that treats the video as content to stream, preview, or optimize instead of a file whose original encoding must arrive intact.
Wrong deliverable
A review proxy, camera original, graded master, and distribution export serve different jobs. Sending the wrong one wastes time even if the transfer succeeds.
Missing sidecars
Captions, audio stems, LUTs, project files, XML or EDL data, and checksums may be required alongside the main video.
Recipient constraints
The recipient still needs enough disk space, a stable connection, compatible software, and time to download and verify the file.
Compare video delivery methods
Use a file-transfer path when the original encoding matters. A streaming or messaging platform can still be useful for review, but it should not replace delivery of the approved master.
| Method | When it works | Limitation | How PhotonFile fits |
|---|---|---|---|
| PhotonFile Relay | The recipient is ready now for the original video file | Both sides must keep the live handoff active until completion | Moves the selected file through a purpose-built live transfer rather than creating a viewing rendition. Use a File Pass on this same path for an occasional oversized one-off. |
| PhotonFile Vault | The recipient needs to download the original video later | The video uses retained Vault capacity and the share lifecycle must be managed | Upload the original video without compression, wait for completion, then create a scoped Vault share for pickup |
| Messaging or social platform | Quick review, comments, and low-friction playback | The platform may transcode, resize, or optimize the uploaded media | Send a proxy for review, then deliver the approved master through Relay |
| Video review platform | Frame-accurate review and approval workflows | The viewing copy may not be the same as the source master | Keep review and final file delivery as separate steps |
| Email attachment | A short, small proxy | Attachment limits are unsuitable for production masters | Use the message for context and a live Relay link for the file |
| Cloud-drive link | The recipient needs later pickup or ongoing access | The file becomes retained storage and link management is a separate task | Use Vault when later access is actually required. Otherwise, use Relay. |
| FTP or SFTP | Established automated media pipelines | Accounts, clients, and server operations add overhead for human handoff | Use PhotonFile for human-driven delivery while keeping protocol automation where it is needed |
Prepare the video before transfer
-
1. Choose the exact deliverable
Label the camera original, mezzanine master, graded master, review proxy, or distribution export so the recipient knows what the file represents.
-
2. Preserve the original container and codec
Do not re-export merely to fit a messaging limit. Keep the approved MOV, MXF, MP4, WAV, or other production file as delivered by the workflow.
-
3. Collect sidecars separately
Include captions, audio stems, LUTs, project interchange files, thumbnails, and a manifest when the recipient needs them.
-
4. Check size and destination space
Tell the recipient the approximate file size and confirm that the target disk has enough free space for the download and any extraction.
-
5. Record a checksum when required
Use a checksum for masters, broadcast deliverables, archives, or any workflow that needs exact-byte evidence.
-
6. Confirm availability
Relay is live. Agree on the handoff window before creating the link, especially for very large files.
Master, proxy, and project package are different jobs
Review proxy
A smaller file may be appropriate for comments and approval. Name it clearly so nobody mistakes it for the final master.
Approved master
When it is time to deliver the approved master, send the full-quality export, not a smaller re-encode made to fit a platform limit.
Project package
When the video must travel with sidecars or source assets, package the folder and use the folder-delivery workflow instead of treating it as one isolated clip.
Relay workflow
Send the original video in a live session
- 1. Open PhotonFile Relay. Use the web or desktop client that fits the file size and working environment.
- 2. Select the approved video file. Confirm the filename, extension, size, and version before starting.
- 3. Choose transfer options. Enable optional client-side encryption when the supported recipient environment can use it.
- 4. Start the upload and create the live link. Relay prepares the active transfer session rather than a stored pickup page.
- 5. Send the link to the recipient. They can receive the Relay transfer without creating a PhotonFile account.
- 6. Keep the sender and receiver active. Do not close the workflow until the transfer finishes. Use eligible resume or Retry behavior after an interruption.
- 7. Verify the file. Compare size, duration, metadata, or checksum and test playback from the downloaded file.
File Pass
Use a completion-gated pass for an occasional oversized send
-
1. One file, one pass path
A File Pass applies to the individual video file and uses the same live Relay architecture.
-
2. Only consumed after completion
An incomplete transfer does not consume the pass, so it can return to an available state for retry.
-
3. Works alongside subscriptions
Use a File Pass for a file that needs the one-off option without changing the regular subscription workflow.
-
4. Not delayed pickup
The recipient still needs to complete the live transfer. Use Vault when the video must remain available later.
Original file
Deliver the selected master
Relay is a file transfer, not a video hosting or streaming pipeline that creates a viewing rendition.
Completion gated
Failed attempts do not consume a File Pass
The pass is marked consumed only after the required bytes finish moving through the Relay transfer.
Integrity check
Verify more than playback
A file can play and still be the wrong export. Compare the name, size, duration, codec details, and checksum when required.
ZIP rarely shrinks production video
Common video codecs already use substantial compression. Putting a single master inside ZIP may change the packaging but often saves little space and adds an extraction step.
Archive only when it helps keep related sidecars together.
Keep the local master until acceptance
Do not delete the source merely because the transfer says complete. Wait for the recipient to verify playback, audio, captions, color, and checksum from the downloaded copy.
Delivery confirmation is part of the workflow.
Use Vault when the recipient cannot be present.
Relay and File Pass are live delivery. If the recipient needs to download tomorrow, after a review window, or from another time zone without coordinating a live session, put the approved video in Vault and create a scoped share instead.
Common questions
Frequently asked questions
Does PhotonFile compress or transcode my video?
Relay is a file-transfer workflow, not a video publishing or streaming workflow. Send the original file you select, and compare file size or a checksum after download when exact-byte verification matters.
Should I ZIP a large video before sending it?
Usually not for size reduction. Most production video formats are already compressed, so ZIP often saves little. Use an archive only when the video must travel with captions, audio stems, LUTs, project files, or other sidecars.
What is the difference between Relay and a File Pass?
Relay is the live transfer workflow. A File Pass is a completion-gated, per-file purchase used on that same live path for an occasional large send or a file that needs the pass option.
Can the recipient download the video later?
Not from a completed Relay session. Relay is for live handoff while both sides are active. Use Vault when the video must remain available for later pickup.
Does the recipient need a PhotonFile account?
No. The recipient can receive a Relay transfer without creating a PhotonFile account.
Can an interrupted video transfer resume?
Eligible transfers can resume after some interruptions, depending on the plan, client, browser, transfer state, and recipient session. Keep the source file and use Retry when resume is not available.
Keep going
Related guides
Send an entire folder online
Keep video, audio, captions, LUTs, and project sidecars together.
Send encrypted files without a cloud-drive folder
Use optional client-side encryption in a live Relay session.
Share files without requiring an account
Choose a live Relay link or a later-access Vault share.
Product and technical references: Relay guide Ephemeral transfer model File Pass pricing Relay technology Desktop app
Send the master, not a smaller copy.
Choose the approved video, transfer it live through Relay, and use a completion-gated File Pass when the one-off file needs that path.