Guide · Troubleshooting
Find the weak link in a live transfer.
A Dropfile session depends on the sender tab, recipient tab, signaling service, WebRTC path, and destination storage. Test them in that order instead of repeatedly clicking Download.
Confirm the share is still live
Check that the sender has not stopped sharing, the availability window has not expired, and a one-person link was not claimed by another browser. If uncertain, create a new link rather than reusing a stale session.
Keep both browsers active
Wake both devices, bring the Dropfile tabs to the foreground, and connect laptops to power. Mobile operating systems may pause networking when a tab is hidden or the screen locks.
Test a less restrictive network
Try home Wi-Fi or a mobile hotspot when a company, campus, hotel, or public network fails. Disconnect a VPN only if doing so is permitted and safe. Browser privacy extensions can also block Turnstile or signaling requests.
Check destination storage
The recipient needs enough free space for the complete file and any temporary browser copy. Very large files are more reliable on desktop browsers that support direct file streaming. Free space, reload, and select a new destination before retrying.
Try a small control file
Share a harmless file of a few megabytes between the same devices. If it works, the original problem is probably duration, storage, or device resource pressure. If it also fails, focus on network and browser restrictions.
Record useful details
Before contacting support, note the local time and timezone, browser names and versions, operating systems, network types, share mode, approximate file size, and exact visible error. Do not send the password or the private file itself.