PhotonFile - Plans
A detailed look at how PhotonFile plans differ, so you can choose the right level for your workflow.
All PhotonFile plans use the same live, in-memory relay architecture. The differences are about scale, durability, and collaboration.
| Feature | Lite | Pro | Studio |
|---|---|---|---|
| Intended use | Daily, frequent transfers | Team workflows & large projects | Production & high-throughput workflows |
| Monthly relay bandwidth | 250 GiB | 1 TB | 3 TB |
| Max file size | 250 GiB | 400 GiB | 400 GiB |
| Concurrent uploads (shared) | 1 | Up to 3 | 10+ |
| Queue priority | Standard | Priority | Never queued |
| Team members | — | Up to 25 | Unlimited |
| Desktop app | Lite mode (coming soon) | Pro+ mode (coming soon) | Pro+ mode (coming soon) |
| Resume support | Session-based | Durable | Durable |
About resume support
Resume behavior depends on both your plan and the environment used for the transfer.
Session-based resumes allow transfers to continue through temporary disconnects while the relay session remains active. This is ideal for quick interruptions like network drops or tab suspensions.
Durable resumes persist transfer progress and use heroic measures to continue transfers across disconnects and client restarts in supported environments. Browser-based transfers resume on a best-effort basis.
Teams without per-seat pricing
PhotonFile teams are designed differently.
A team is a shared workspace where members operate under the team owner's entitlements while working inside that team. The owner's plan determines capabilities like concurrency, priority, and durable resume behavior.
There is no per-seat billing. You can invite teammates, contractors, or collaborators without your cost increasing for every additional person.
- • Team members inherit the owner's plan benefits while working in that team
- • The team owner is the only paid account required for team benefits
- • Members can still use PhotonFile outside the team under their own limits
- • Creating teams is reserved for eligible plans, but joining a team does not require an upgrade
Teams are a collaboration feature, not a meter running in the background.
Desktop app behavior (launching soon)
PhotonFile will provide a single desktop application that adapts to your entitlements. Currently in final testing.
- • Lite plans run in a lightweight mode suitable for individual use
- • Pro and Studio unlock advanced resume durability and batching
- • File Passes can be used within the desktop app for one-off transfers
File Passes
File Passes are per-file purchases designed for occasional large transfers. They provide full priority and reusability for the specific file size purchased, without requiring a subscription.
Using File Passes with subscriptions
File Passes can be used alongside any subscription to send files that exceed your plan's per-file size limit.
- • If a file is larger than your plan allows, you can apply a File Pass for that transfer
- • The transfer uses File Pass pricing for that file only
- • Your subscription remains active and unchanged
- • Transfers that use a File Pass do not count against your subscription's monthly relay bandwidth
- • File Passes retain full priority and reusability guarantees
This lets you stay on the right subscription tier for your regular workflow while still handling occasional oversized transfers without upgrading.
Queue priority and routing
Queue priority determines how transfers are admitted and routed when relay capacity is constrained.
Standard priority transfers may be queued during periods of high demand. This ensures fair access across all users while protecting overall system stability.
Priority transfers are admitted ahead of standard traffic and are less likely to be queued during peak usage.
Never queued transfers are admitted immediately and are not placed behind other traffic. Studio plans are designed to avoid queueing even during periods of high demand, making them suitable for production and time-critical workflows.
Queue priority affects admission and routing order, not file inspection or data handling. All transfers use the same encrypted, in-memory relay architecture.