Send large files
In the browser, large transfers use the encrypted pipeit relay and need both sides reachable until they finish; the apps also connect directly.
The large browser file route supports up to 8 GiB per file. The interface shows the size that applies. Memory, local browser space, the operating system and available quotas can limit it further; 8 GiB is not a promise for every phone.
- Choose the file and the receiving device.
- For a large transfer set Connect through pipeit.
- Keep both sides reachable until the transfer finishes. A relayed transfer does not store the file as a copy you could fetch later.
For very large or recurring jobs, the pipeit app on a desktop or the Linux agent with permanent receiving is the better fit.
When the large route is used
The web client switches to the large route for more than eight files, or more than 32 MiB of weighted selection across all recipients. More recipients increase the data volume and can require the large route sooner. This is a technical distinction for detailed help, not a general “32 MiB limit”.
Related guides
- Apps and browser
Send files between two of your devices
Pick files, choose the receiving device, check the connection and wait for “Received and verified”.
Direct, server route and routed networks: which way works?
What “direct” really means, when pipeit routes through its servers and what you can check.
- Command line and servers
Status, progress and resuming
Read the state of a transfer and continue the same job instead of starting a new one.
Still stuck?
Check the troubleshooting guide first. If that does not help, tell us what happened.