Send files directly between browsers with an encrypted sharing link. No file uploads to Toolardo, no signup. Keep both tabs open until the transfer finishes.
Choose your files, share one link, and keep this tab open.
Leave empty for link-only access, or use 8–256 characters. Send the password separately from the link. Transfers are encrypted either way.
Password required · send the password separately
Anyone with this link can receive the selected files. Share it privately. One receiver at a time.
This link requires a password. Ask the sender for it; it is not included in the link.
Toolardo P2P File Transfer sends files between browsers using WebRTC and an additional AES-256-GCM encryption layer. An external PeerJS signaling service and Google STUN service establish the connection. No TURN relay is configured, so some networks cannot connect. Files are verified with SHA-256; sender and receiver must stay online.
El intercambio tradicional sube primero el archivo a un servidor y después el destinatario vuelve a descargarlo. Para una transferencia puntual, ese almacenamiento extra puede ser innecesario.
Toolardo P2P File Transfer intenta establecer una transferencia directa entre navegadores cuando la red lo permite, reduciendo la necesidad de guardar el archivo de forma permanente en Toolardo.
La conexión P2P puede verse afectada por NAT, VPN, cortafuegos, restricciones del navegador o la propia red. No cierres la página del remitente antes de completar la transferencia.
Toolardo serves the page and scripts. PeerJS Cloud exchanges connection information, and Google STUN helps discover addresses. File contents and encrypted application messages travel directly between the two browsers; this version does not configure TURN relays.
Desktop browsers with showSaveFilePicker, typically Chrome and Edge, save to disk while receiving. There is no application size cap in that mode, but disk space and browser stability still matter. Other browsers use memory and are limited to 128 MiB per file. At most 100 files can be selected per session.
Some NATs, mobile carriers, VPNs and firewalls prevent direct WebRTC connections. This version deliberately has no TURN relay fallback. Try another network and keep the sender online.
Anyone holding the complete secret link, plus the separate password if you set one. Treat both as secrets. One receiver at a time. Ending the share or closing the sender tab invalidates the link.
No. Peers and connection services can learn IP addresses. The link secret is in the URL fragment, outside HTTP requests and PeerJS metadata. An optional password derives an additional key requirement locally; it is not sent or included in the link. Scripts running on the page can access fields and the fragment.
No. Reconnect and restart the file. A file is marked complete only after SHA-256 verification and successful save finalization. Memory-mode downloads also depend on your browser download manager.
Yes. Enter an optional password of 8–256 characters before creating the link. The receiver must enter it separately. Password-protected links need the updated tool on both sides. Even without an extra password, file transfers are encrypted.
