Slow or failed Direct file transfers
Direct means a browser-to-browser WebRTC connection. It does not guarantee that the file stays on your local Wi-Fi network, or that this path will be faster than Cloud.
First, check both devices
- Open the same Telepaste service and join the same room on both devices. A local server and telepaste.com have separate rooms, even when you enter the same code.
- Keep the sender's original page open. Reloading it removes access to files selected before the reload; select the file again if it is not already cached.
- Keep both pages in the foreground and the devices awake. On iPhone and iPad, switching apps or locking the screen can interrupt browser activity.
- Try a small file first. A failed connection and a connected but slow transfer need different responses.
Connected, but slow on the same Wi-Fi
Expand the file to check its connection status. LAN direct means the reported endpoints use local addresses. NAT direct means the selected connection includes a public NAT candidate; it does not by itself prove how far the packets travel. Direct without a more specific label means the browser has not exposed enough information to classify the path.
A VPN, guest Wi-Fi isolation or a firewall may keep the browsers from using a local path. High latency and packet loss can reduce throughput even after the connection succeeds. Waiting longer or repeatedly retrying does not guarantee a different path. Telepaste cannot force a browser to use a particular network interface.
You do not need to disable a work VPN to use another transfer method. During Direct, choose Switch to Cloud and confirm if you want a server-assisted transfer. This restarts the download, uploads the file and may keep a temporary copy for up to 24 hours. The displayed Cloud file-size limit still applies. Nothing uploads automatically just because Direct is slow.
Use LAN when a local server is available
Open the running local server's LAN address on both devices, join the same local room and select the file there. Choose LAN, not Direct. LAN streams through the local HTTP server; the website at telepaste.com cannot create that server for you. Use local HTTP only on a trusted network.
Direct cannot connect
Retry makes one new attempt. Keep Trying makes up to six attempts, each with a ten-second connection window and a short pause between attempts. Stop ends the attempt. If these repeatedly fail, choose Cloud within its size limit or use an available local LAN server; a network that blocks the path will not necessarily improve with more retries.
Safari and large files
Use an up-to-date browser and keep the receiving tab visible. Direct collects the received file in browser memory before saving it, so a large file can exceed a mobile device's available memory. Direct has no Telepaste Cloud upload cap, but it is not unlimited device capacity. LAN or Cloud uses the browser's normal download path instead.
See the transfer method comparison for limits and storage behavior, or data and privacy before choosing Cloud. For connection diagnostics, the WebRTC IP handling standard describes how browser privacy and network routing affect available interfaces.