Direct transfer (experimental)
Send files straight from one open browser to another with WebRTC. You carry the connection codes yourself, there are no relay servers, and it usually only works on the same network.
On the sending device
On the receiving device
Network options
How a session works
- Open this page on both devices. One chooses Send, the other Receive.
- Swap codes. The sender copies its connection code to the receiver through any channel (chat, email, a message to yourself), and the receiver sends its reply code back.
- Compare the verification code. Both screens show the same 12 digits only if nobody altered the codes in between. Read them to each other.
- Approve and transfer. The receiver sees the file list and size before accepting. Files travel as a one-time encrypted package and are verified on arrival.
When it will not connect
Without a relay, two browsers can only connect when one can reach the other directly, which in practice means the same Wi-Fi or office network. That is a deliberate choice: relays and STUN servers are third parties that see your network addresses. If it fails, make a package and send it any other way. Nothing is relayed silently.
What the acknowledgement means
When the receiver’s browser verifies the files, it tells the sender. That message comes from the other browser’s code, so it shows that browser reported success. It does not prove anyone opened the files, kept them, or deleted them afterwards, and closing either tab ends the session.
Questions
Why does the connection fail between different networks?
Browsers behind home routers and company firewalls usually need a STUN or TURN server to find each other. TinyShare does not use one by default, because it would send your network addresses to a third party. Without one, direct transfer generally works only on the same local network.
What is the verification code for?
Both screens show a code computed from the two browsers' connection fingerprints. If someone tampered with the codes you pasted, the codes will differ. Compare them over a channel you trust, such as a phone call, before approving the transfer.
Do the connection codes contain anything sensitive?
They contain your browser's local network addresses and a cryptographic fingerprint, not your files. Even so, only paste them where you would share your local IP address.