SafeBeam Help Documentation

A complete guide to SafeBeam, from pairing two devices to how your files are protected.

Last Updated: November 17, 2026

Table of Contents

  1. Getting Started
  2. What You Need
  3. The Transfer Password
  4. Pairing: The First Code
  5. Pairing: The Reply Code
  6. Without a Camera
  7. The Password Check
  8. Sending Files
  9. Receiving and Saving Files
  10. Ending a Session
  11. How the Protection Works
  12. Limits
  13. Keyboard and Accessibility
  14. Privacy and Your Data
  15. How It Was Checked
  16. Troubleshooting and Support

1. Getting Started

SafeBeam sends files straight from one of your devices to another over your own network: photos and videos from the phone to the laptop, documents from the laptop to the phone, in either direction and as often as you like within one session. Both devices open the page. Nothing is installed, and no account is needed.

A session has three parts. First the two devices are paired: each shows a code once, and the other reads it with its camera. Then both prove that they know the same transfer password. Only after that does the transfer area open, where files are dropped in and saved.

The shortest way: on the computer, type a password and press Show a code on this device. Point the phone's camera app at the code, open the link and type the same password. The phone shows a reply code; on the computer press Scan the reply code and hold the phone's screen in front of the camera.

2. What You Need

Networks that keep devices apart

Guest WiFi, hotel and office networks are often set up so that devices on them cannot see each other, and a VPN can have the same effect. If the two devices do not find each other, use your home WiFi or the phone's hotspot, and switch a VPN off for the transfer.

3. The Transfer Password

The transfer password is the lock on the session. You choose it on the first device and type the same one on the second. It has to be at least 8 characters long (at most 128). Capital and small letters count as different; spaces at the start and at the end are ignored.

Suggest a strong password writes one for you: twelve letters and digits in three groups of four, without the look-alikes 0, O, 1, I and L, so that it can be read off one screen and typed on the other. It is shown in clear while you copy it; the Show and Hide button changes that at any time.

The password is not saved, on either device. It stays in the page's memory until the password check is over and is then dropped. It is never sent: section 11 explains how it can be checked without travelling.

4. Pairing: The First Code

Press Show a code on this device. A square code appears, together with three numbered steps and, beside it, the place where the reply will be scanned. The code is good for ten minutes.

On the second device there are two ways to read it:

The code holds the first device's address on your local network (or a one-time stand-in name the browser makes up for it), a one-time fingerprint that lets the two browsers recognise each other, and two short one-time values. It is written as a link to this page; the values come after a # sign, which a browser does not send to a website, and the page takes them out of the address as soon as it has read them.

5. Pairing: The Reply Code

As soon as the second device has the first code and the password, it shows a reply code with the same kind of values for itself. On the first device press Scan the reply code and hold the second device's screen in front of the camera, about a hand's length away, with the whole code inside the picture.

When the reply has been read, the two devices connect, usually within a second. If they cannot reach each other within 25 seconds, the page says that the two devices could not find each other; section 16 lists the usual reasons.

If the reply code changes

Some browsers stop waiting after about a minute when the first device has not read the reply yet. The page then makes a fresh reply code by itself and says "The reply code was renewed". Scan the code that is on the screen at that moment.

6. Without a Camera

Under every code is the line "No camera? Use the code as text", and under every scanner "No camera? Type or paste the code". The first shows the code as text with a Copy button; the second takes that text in place of a scan.

The first code is a link of about 180 characters. The reply code is about 120 characters or more, made of digits and capital letters without I, L, O and U, and is shown in groups of five. Spaces, line breaks and small letters do not matter when it is typed, and a typed O, I or L is read as the digit it looks like. A text that is not a code of this tool, or that was not typed completely, is refused with a message, and a first code offered where a reply is expected (or the other way round) is recognised as such.

7. The Password Check

Once the devices are connected, the page says "Checking the password". Each device proves to the other that it knows the password, and each checks the other's proof. This takes a moment. If both proofs are right, the transfer area opens on both devices and the password fields are emptied.

If they are not, both devices show "The passwords do not match", with a password field and the number of tries left. Type the password again on the device where it was wrong and press Try again; then press Try again on the other device too. The check runs again when both have done so. After the third wrong try the connection is closed, and the devices have to be paired again with new codes.

Until the check has succeeded, the connection carries nothing but the check itself. A device that has not passed it cannot send a file, and anything else it sends closes the connection.

8. Sending Files

The transfer area has a bar that says which device you are connected to, a drop zone, and two lists. To send, drop files on the drop zone, or click it and choose them; on a phone, tap it and pick photos, videos or files. On a computer, a copied file or picture can also be pasted with Ctrl+V.

Each file appears under Sent from this device with its size and a line that changes as it goes: Waiting, Sending with a percentage, the speed and the time left, then "Sent. Waiting for the other device to confirm", and finally Delivered when the other device reports that it has the whole file. Files are sent one after another. Cancel stops a file that is waiting or on its way.

One file can be up to 2,000 MB; a larger one is left out with a message before anything of it is sent. Folders cannot be sent as such: open the folder and choose the files inside.

9. Receiving and Saving Files

Files from the other device appear under Received on this device as soon as they are announced, and fill up as they arrive. Cancel stops one. A complete file shows "Received. Press Save to keep it" and three buttons:

With more than one received file, Save all saves them one after another; the browser may ask once whether the page may save several files. Photos in the common formats show a small picture in the list. Nothing received is ever opened or run by the page.

A received file lives in the browser's memory until you save it. If you close or reload the page first, it is gone; the page asks before you leave while unsaved files are in the list.

10. Ending a Session

Disconnect ends the session on both devices. The other device is told and shows "The other device disconnected". A connection that nobody uses for 15 minutes is closed by itself. Closing the page ends the session too.

After a session has ended, the lists stay on the page so that received files can still be saved. Connect again returns to the start; if received files have not been saved, the page asks first, because starting again removes them.

11. How the Protection Works

No server in the middle. The page names no helper server of any kind for the connection. The only addresses the browsers offer each other are the devices' own, and they travel in the two codes, from screen to camera.

The password is proved, not sent. The password check follows a published internet standard for exactly this purpose (RFC 9382, on the standard curve P-256). Each device stretches the password with 200,000 rounds of a standard function, mixes the result into a fresh one-time value and sends that value. Only two devices that started from the same password arrive at the same secret, and each then proves to the other that it did. What travels gives a listener nothing to test guesses against. A device that takes part with a wrong password learns only that this one guess was wrong, and it gets three tries.

The check covers the connection itself. The proof includes the fingerprints of the two browsers' connection certificates. Somebody who managed to put a device of their own between the two would present different fingerprints, and the check would fail.

Every piece is sealed. A successful check leaves both devices with a secret key that exists only for that session. From it the page makes one key for each direction and seals every message and every piece of a file with the AES standard (256-bit keys, authenticated mode). Pieces are about 60 KB long and numbered. A piece that was changed, repeated, left out or moved fails its check, and the receiving device then closes the connection instead of going on.

What arrives is treated with care. File names are cleaned before they are shown, files that a browser could run as a page are saved as plain data, and the page saves a file only when you press Save.

12. Limits

13. Keyboard and Accessibility

Every control can be reached with Tab. Enter in the password field shows this device's code. The drop zone opens the file picker with Enter or the space bar. The codes can be used as text without a camera (section 6). Changes of state, such as "Checking the password", the result of the check and the end of a session, are written in lines that screen readers announce, and every progress bar carries the file's name and its percentage.

The code is always drawn black on white, in the light and in the dark theme, because that is what cameras read best.

14. Privacy and Your Data

Your files, their names, your transfer password and the two codes are not sent to this site or to any other server. The files travel directly between your two devices. SafeBeam writes nothing to the browser's storage. The camera is on only while a scanner is open, and its pictures are looked at inside the page and thrown away.

Like every page on ZeroDataUpload, this page loads the site's advertising and visitor statistics; they are described in the Privacy Policy. They have no part in a transfer.

15. How It Was Checked

Before publishing, the part that does the password check, the sealing and the codes was tested apart from the page: 69,533 cases in 16 groups. The password check reproduced the four test cases published with the standard, value for value. The arithmetic behind it was compared with two other, separately written versions on several hundred values, and the two fixed points the standard prescribes were made again from their published seeds. Sealed pieces were compared with a second implementation and then changed, cut, repeated and reordered in every way: each was refused. Damaged codes, hostile file names and malformed messages were refused or cleaned as well.

The page itself was then used in test browsers: 133 checks, none failed. They cover pairing by link, by camera and by typed code; the password check with the right password, with a wrong one followed by the right one, and with three wrong ones; a page without the password trying to send; files in both directions at once, among them a file without contents, a name in Hindi, and names, file types and a device name made to break the page, which were cleaned; saving, Save all and Remove; cancelling from either side; a file over the limit; sessions ended from either side, lost, and left unused for 15 minutes; and the layout at four screen widths in the light and the dark theme. A file of exactly 2,000 MB was sent, saved and found identical to the original. The pairing was repeated between Chromium and Firefox in every combination (19 checks, none failed) and in the protected form in which the scripts are published (11 checks, none failed). The page was scanned for accessibility in every one of its states (72 runs, no violations) and measured for phone screens (no text under 16 px and no tap target under 44 px).

The tests ran between browser windows on one computer, with a simulated camera. Real phones, real WiFi networks and Safari were not part of them, and networks differ; if something does not work on yours, please tell us through the contact form.

16. Troubleshooting and Support

For questions the FAQ does not answer, use the contact form.