WolfP2P
Transfer reportsMy Settings

What happens if a computer sleeps during a transfer?

For:All usersNo technical knowledge required.

The transfer stops moving while either computer sleeps because the browser-to-browser connection is no longer active. Wake the computer and return to the same WolfP2P tab; when the session survives, WolfP2P attempts to reconnect and resume from durable progress.

The device may sleep during a transfer

No file bytes can move while either peer is asleep. On compatible browsers, WolfP2P requests a screen wake lock while actively sending or receiving, but no browser can prevent every form of operating-system suspension.

When the computers return and the tab session survives, WolfP2P reconnects and continues from durable destination progress rather than retransmitting completed files.

What to do after waking the computer

  1. Wake and unlock both computers

    The sleeping device must restore its browser and network connection before file movement can continue.

  2. Return to the original tabs

    Do not begin by closing them. A surviving tab may still hold the session needed to reclaim the tunnel.

  3. Allow automatic reconnection

    Wait for WolfP2P to determine whether the direct connection and transfer can continue.

  4. Follow the recovery action

    When prompted, restore access to the same source or destination associated with the interrupted transfer.

  5. Create a new tunnel only when required

    If the previous tunnel no longer exists, offer the same set through a new tunnel. WolfP2P can identify candidates by path and size, then reuse completed files only after SHA-256 verification.

When recovery can continue from a checkpoint

Recovery boundaries after sleep

  • Durable byte-level recovery requires Safe mode, a Compatible Browser, and destination-folder access.
  • Quick mode may restart the interrupted current file from its last genuinely durable point, often byte zero.
  • Receiving requires writable destination-folder access; the current receiver has no browser-download fallback.
  • A wake lock cannot prevent lid closure, restart, forced suspension, battery loss, or every system policy.
  • Recovery depends on the relevant tab session and local file access surviving.

Read Transfer Recovery and Reliability for the complete recovery model and Browser Compatibility for the difference between compatible and partially compatible browsers.

Reduce the chance of sleep interruption

Keep both devices connected to power, leave the transfer tabs open, and temporarily adjust operating-system sleep settings for a long transfer if appropriate. A screen wake lock is helpful but cannot override every system policy, lid closure, battery event, restart, or forced suspension.