Recover verified progress after an interruption

WolfP2P distinguishes bytes placed into the network from bytes safely written to the destination. Large files are checkpointed to disk, and the receiver acknowledges durable offsets.

Bytes sent into a network connection are not necessarily saved at the destination. WolfP2P bases resumable progress on receiver-confirmed durable checkpoints, not solely on the amount placed into the data channel.

Durable checkpoint recovery requires a Compatible Browser, such as Chrome, Edge, or Brave and destination-folder access. A Partially Compatible Browser, such as current Safari or Firefox may send individually selected files when live capability checks permit it. Receiving requires writable destination-folder access; the current receiver has no browser-download fallback.

A brief network interruption can be handled by reconnecting the two peers inside the surviving tunnel. Transfer recovery goes further: after a supported reload or restored tab, WolfP2P can continue a large file from the last durable destination offset rather than starting that file from byte zero.

Both mechanisms depend on the relevant tab session surviving. They do not make the transfer available from an unrelated device or create a hosted copy.

Reloading the same tab or restoring a browser-discarded tab can preserve the tab-scoped session. Genuinely closing the tab ends its tunnel. See What Happens If a Tab Closes? for the recovery choices.

If a computer sleeps, file movement pauses. After wake, WolfP2P attempts to reconnect when the tabs and session survive. Follow What Happens If a Computer Sleeps? for the safe sequence.

A new tunnel can offer the same set again. When the receiver selects the same destination, relative path and byte size identify possible matches; they do not authorize reuse by themselves. WolfP2P uses SHA-256 content or prefix evidence to verify the reusable result before it skips a completed file or resumes a durable prefix.

If verification cannot establish a legal reuse point, WolfP2P retransfers the affected file or portion instead of treating path and size as proof of identity.

One tunnel carries one offered set. After the set completes, sending another set requires a new tunnel. If a file fails, follow the action shown by WolfP2P and use the linked Transfer and Resume Help for the specific state.