FILE BEACON

Idle

Beam files
device to device.

One four-digit code links two browsers directly. No accounts, no uploads, no cloud copy.

You get a code to read to the other device.

How it works

  1. Start a room

    One device gets a four-digit code. It lives for five minutes.

  2. Enter the code

    The other device types it in. The two browsers link directly.

  3. Drop files

    Either side can send. Bytes travel straight across, both ways at once.

Your files never touch a server.

The server hands out the code and relays a few kilobytes of connection setup. The files themselves move over an encrypted WebRTC channel, browser to browser. You could pull the server's plug mid-transfer and the file would still arrive. Rooms expire after five minutes, codes are single-use, and nothing is written to disk in between.

Common questions

Lots of devices on one Wi‑Fi?
No problem. Any number of devices can have this page open at once. Each code pairs exactly two of them in a private room, and a third device entering a used code is politely turned away. On the same Wi‑Fi, transfers take the local path and run at network speed.
How big can files be?
Hundreds of megabytes are fine and won't freeze the tab. The receiving browser holds a file in memory until it's saved, so the practical ceiling is the receiver's free RAM.
Is it encrypted?
Always. WebRTC channels are end-to-end encrypted with DTLS. It cannot be switched off.
What can block it?
Both tabs must stay open during a transfer. There is no cloud copy, that's the point. Very strict corporate networks can prevent a direct link; if that happens the app says so plainly instead of spinning forever.