Connect devices
Both devices must stay connected. Restricted networks may not connect without a relay.
Choose files to send
Transfers
Nothing is received until you accept. Cancellation stops pending chunks; delivered files stay on the recipient device.
Received files on this device
No automatic expiry. Download or delete your copies. Clearing browser data removes them.
How to use P2P File Transfer
Choose files, pair your devices and accept on the recipient. Both devices must remain connected with their tabs open.
- Choose local files or drop them into the sender workspace.
- Create a private room and open Invite. Scan the QR code or enter the invitation code on the other device.
- Select the recipient and send your offer. On the other device, inspect the filenames and sizes, then accept or decline.
- Keep both tabs open while progress advances. Download the verified received copies or delete them explicitly.
Questions
Are files uploaded to Pevlika?
No. Pevlika only establishes the initial connection. File metadata and chunks travel directly to the selected recipient over WebRTC; they do not enter public room snapshots.
Can large files be transferred?
When supported, received bytes stream into browser-private disk storage with bounded chunks and backpressure. Available storage and browser limits apply. Browsers without writable private-file storage use a 16 MiB per-file, 32 MiB active-memory fallback and reject larger receives visibly.
Must both devices stay online?
Yes. This is a live direct transfer, not an offline delivery service. Mobile operating systems may suspend background tabs. Restrictive networks may not connect because no TURN relay is provided.
Can an interrupted transfer resume?
An interrupted connection can resume its acknowledged prefix when both original tabs still hold the source and receive stream. Reloading or closing a tab cannot restore a sender file selection or an uncommitted writable stream. Already verified received files remain saved.
How long are received files kept?
Verified browser-local copies have no automatic expiry. Delete them explicitly or clear browser data. Storage pressure rejects new receives and preserves existing copies. The local catalog holds up to 256 completed or interrupted entries.
How is integrity checked?
Both devices compute incremental SHA-256. The recipient commits a file only after its exact length and digest match. This checks the agreed bytes; it does not establish that a file is safe to open.