Get a stalled transfer moving again.

Ask the sender to reopen the active sharing tab and keep the device awake. The file is not sitting on Dropfile's server, so the original browser must remain available for pieces that no other peer has.

• Keep the Dropfile tab visible on phones and tablets.
• Turn off battery-saving restrictions temporarily.
• Confirm the sender has not pressed Stop sharing.

Corporate networks, school networks, some VPNs, and restrictive mobile carriers can block or degrade direct WebRTC connections.

• Try a different Wi-Fi network or mobile hotspot.
• Temporarily disconnect a VPN if policy allows.
• Keep both browsers on their newest stable version.
• Create a fresh link if the original session has become stale.

Mobile Safari and Chrome can limit temporary storage or terminate long-running tabs. Free local space first, keep the page in the foreground, and avoid switching apps. If the problem continues, use a desktop browser that can stream directly to a chosen file.

The first successful unlock owns a one-person session. If that was the wrong browser or the connection failed, the sender should stop the share and create a new link. Use multi-download mode when more than one recipient is expected.

Passwords are case-sensitive. Copy the complete value without extra spaces and ask the sender to regenerate the share if uncertain. If Turnstile does not appear, disable script blocking for Dropfile and reload the page.

Dropfile rejects pieces that do not match the sender's signature. Restart the transfer with a fresh link. If the error repeats across different networks and browsers, record the browser names, operating systems, approximate file size, and time before contacting support.