# How it works

> How Toss moves files straight between two browsers with WebRTC, and what the server does and doesn't see.

Toss connects two browsers directly. The server only helps them find each other; the file itself never passes through it.

First, the two browsers swap a few setup messages through the Toss server. Then the file goes straight from one device to the other, or through an encrypted relay when a direct path isn't possible.

## 1. Your browser creates an identity

On your first visit, your browser makes a private key that never leaves the device, and a friendly name like HappyElephant7556 derived from it. There's no sign-up.

## 2. You share your link

Your personal link stays the same for as long as you use Toss. If it ends up in the wrong hands, make a new one with one click; the old link stops working right away.

## 3. The sender picks a file

Its name, size and type are encrypted for your browser before they leave theirs, so our server only passes on a sealed note. Every Toss tab you have open shows the offer.

## 4. You accept

You see who is sending what, and how big it is. When you accept in any tab, the file streams directly from their browser into your device over an encrypted WebRTC connection, and is checked with SHA-256 when it arrives. A dropped connection picks up where it stopped.

## Good to know

- Files go straight from browser to browser, so you and the sender both need Toss open while it travels. Offers wait up to 24 hours for you to come back.
- The two browsers can see each other's IP address, unless the connection has to be relayed.
- Clearing your browser data creates a new identity (and a new name).
- Very large files work best in Chrome or Edge on a computer, which can save straight to disk.

Source: https://toss.appbits.dev/how-it-works
