How browser-to-browser file transfer works
moc coordinates a live transfer between two modern browsers. File data uses an encrypted connection and is not kept as a permanent cloud copy.
Step by step
- The sender selects a file The browser reads the chosen file locally. moc publishes only the encrypted metadata needed to prepare the invitation.
- The receiver joins A private link or code connects the receiving browser to the same one-time room.
- The browsers establish a path moc attempts a direct WebRTC connection. When network address translation or firewalls prevent it, an encrypted live relay can carry the session.
- The receiver accepts File bytes start only after the receiver chooses Download. The room is removed after the transfer completes.
Questions
- Is browser-to-browser always peer to peer?
- moc attempts a direct WebRTC path first. Some networks require a TURN relay, which forwards the encrypted live connection without becoming permanent file storage.
- Why is WebRTC used?
- WebRTC lets modern browsers establish encrypted real-time data channels without requiring a native transfer application.
- What happens if a browser closes?
- The live transfer stops. Reopen the guest page and create a new one-time room if the original session can no longer continue.
Send a file without signing in