Resources · 3 guides
Troubleshooting Peer-to-Peer File Transfer
Diagnose slow transfers, failed WebRTC connections and interrupted large files, step by step.
Last updated
About this topic
When a direct transfer is slow or never starts, the cause is almost always one of a few things: the sender's upload bandwidth, a relay in the path, a network that blocks UDP, or a browser that cannot hold or write the incoming file fast enough. Guessing wastes time; the guides below show how to tell which one it is.
For the SRIFT CLI, srift doctor runs the network checks automatically and prints a fix for each blocked hop; srift doctor --deep adds an end-to-end self-test.
Guides
- Why Is P2P File Transfer Slow? How to Find the BottleneckUpload bandwidth, TURN relaying, Wi-Fi, buffering and encryption overhead: how to find what is limiting a peer-to-peer transfer and fix it.
- Why WebRTC Connections Fail, and How to Fix ThemWhy two browsers sometimes cannot connect directly: ICE failures, blocked UDP, symmetric NAT and missing TURN, with a diagnosis checklist.
- Large File Transfers: Interruptions, Resume and IntegrityWhy multi-gigabyte transfers fail, how browsers store incoming files, what resume really requires, and how to verify the file that arrived.