SafeBeam FAQ

Answers about SafeBeam, from connecting two devices to how your files are protected.

Last Updated: November 17, 2026

1. Basics

Q1: What is SafeBeam?
A1: A free page that sends files straight from one of your devices to another, for example photos and videos from your phone to your laptop, or documents from the laptop to the phone. Both devices open the page, connect directly to each other on your own network, check a password, and then send files in either direction.
Q2: Is it free, and do I need an account or an app?
A2: It is free. There is no account, no registration and nothing to install: it opens in the browser of the phone and of the computer. Like every page on ZeroDataUpload, it is supported by advertising.
Q3: What kinds of file can I send?
A3: Any kind: photos, videos, music, documents, archives. Several at once, in both directions, up to 2,000 MB for one file and 2,000 files from each device in one session. Folders cannot be sent as such; open the folder and choose the files inside.
Q4: Which devices and browsers does it work on?
A4: Current versions of Chrome, Edge, Firefox and Safari, on phones, tablets and computers. The two devices do not have to be of the same make or use the same browser. Scanning a code needs a camera; a computer without one can take the code as text.
Q5: Does it use Bluetooth?
A5: No. A web page is not allowed to send files to another device over Bluetooth, so SafeBeam uses your local network instead: WiFi, or a cable network that the WiFi belongs to.
Q6: Do both devices need the internet?
A6: Both need to open the page, which comes from the internet like any web page. The files themselves do not travel over the internet: they go directly from one device to the other across your own network.

2. Connecting the Two Devices

Q7: How do I connect my phone and my laptop?
A7: On one device type a transfer password and press Show a code on this device. Point the other device's camera app at the code and open the link (or open this page there and choose Scan the other device's code), and type the same password. The second device then shows a reply code: on the first device press Scan the reply code and hold the second device's screen in front of its camera. The devices connect, check the password and open the transfer area.
Q8: Which device should start?
A8: Either. It is usually easiest to start on the computer: a phone's camera reads a code on a large screen without trouble, and the computer's camera then only has to read one code from the phone.
Q9: Why do I have to scan two codes?
A9: Two browsers that want to talk directly first have to tell each other where they are on the network. Most transfer sites pass that through a server of theirs. SafeBeam has no such server, so the directions go from screen to camera: once from the first device to the second, and once back.
Q10: What is in the two codes?
A10: The address of the device on your local network (or a one-time stand-in name that the browser makes up for it), a one-time fingerprint that lets the two browsers recognise each other, and two short one-time values. A code does not hold your password, a key or anything about your files. The first code is written as a link to this page so that a phone's camera app can open it; the part with the values comes after a # sign, which a browser does not send to a website, and the page takes it out of the address at once.
Q11: How long is a code good for?
A11: Ten minutes. After that the page says that the code was not used in time, and you start again for a new one. A code works once: after two devices have connected with it, it is of no use to anyone else.
Q12: My computer has no camera. What now?
A12: Open the line "No camera?" under the scanner. The other device shows its code as text under its own code, with a Copy button. Type or paste that text into the box and press Use this code. The first code is a link of about 180 characters; the reply code is about 120 digits and capital letters or more, shown in groups of five; spaces, line breaks and small letters do not matter when it is typed.
Q13: The camera does not read the code.
A13: Hold the screen so that the whole code is inside the picture, about a hand's length from the camera, and keep it still for a moment. Turn the brightness of the screen that shows the code up, and tilt it a little if a lamp or a window is reflected in it. If the device has more than one camera, the button Use the other camera changes between them.
Q14: The reply code changed while I was looking at it.
A14: Some browsers stop waiting after about a minute if the first device has not read the reply. The page then makes a fresh reply code by itself and says so. Just scan the code that is on the screen now.

3. The Password and Security

Q15: What is the transfer password for?
A15: It is the lock on the session. After the two devices have connected, each has to prove to the other that it knows the password. Until both proofs are right, no file is sent and none is accepted. A device that does not know the password gets nothing from you and cannot send anything to you.
Q16: Is my password sent to the other device or to the site?
A16: No. The password never leaves the device you type it on. Each device mixes it into a one-time value, and the two values together only work out when both devices started from the same password. This way of proving a password without sending it is a published internet standard (RFC 9382).
Q17: Could someone who records the connection find out my password?
A17: No. What travels during the password check gives a listener nothing to test guesses against, so the password cannot be worked out afterwards, however much computing power is used. The only way to test a guess is to take part in a check, and every check tests exactly one guess.
Q18: What happens if the password is wrong?
A18: Both devices say that the passwords do not match and offer a second and a third try. Type the password again where it was wrong and press Try again on both devices. After three wrong tries the connection is closed and the devices have to be paired again with new codes.
Q19: What makes a good transfer password?
A19: At least eight characters, and not one you use anywhere else. Because a guess can only be tested by taking part in a check, and only three times, even a simple password protects a session well; a longer one is still better. Suggest a strong password gives twelve letters and digits in three groups, without the look-alikes 0, O, 1, I and L.
Q20: Is the password saved anywhere?
A20: No. It is held in the page's memory until the check is over and is then dropped. It is not written to the browser's storage, and the page asks the browser not to offer to remember it.
Q21: Are the files encrypted on the way?
A21: Yes, twice. The direct connection between the two browsers is encrypted by the browsers themselves. On top of that, SafeBeam seals every piece of every file with a key that came out of the password check, using the AES standard with 256-bit keys in its authenticated mode. Each piece is numbered and checked on arrival.
Q22: What if somebody on the same WiFi tampers with the connection?
A22: A piece that was changed, repeated, left out or moved fails its check, and the receiving device closes the connection at once. Somebody who puts themselves between the two devices at the start fails the password check, because that check also covers the fingerprints of the two connecting browsers.
Q23: Can the other device reach into my files?
A23: No. A web page can only read the files you choose in the file picker or drop on it, and it can only save a file when you press Save. Neither device can look into the other's storage, and nothing that arrives is opened or run by the page.

4. Sending and Receiving

Q24: How do I send files?
A24: When the transfer area is open, drop files on the large drop zone, or click it and choose them. On a phone, tap it and pick photos, videos or files. On a computer you can also paste a copied file or picture with Ctrl+V. The files appear under Sent from this device with their progress.
Q25: Where do received files go?
A25: They appear under Received on this device and are held by the browser until you press Save. Save hands the file to your browser, which puts it where your downloads go. On a phone, Share (where the browser offers it) lets you pass a file to another app, for example to save a photo to your gallery.
Q26: Do I have to accept each file?
A26: No. A device that has passed the password check may send, and what it sends is listed on the other device straight away. Nothing is written to your storage until you press Save, and you can stop any file with Cancel while it is on its way.
Q27: Can both devices send at the same time?
A27: Yes. Each device sends its own files one after another, and the two directions run side by side.
Q28: How fast is it?
A28: As fast as your network and the two devices allow. In our tests between two browser windows on one computer, large files moved at about 40 MB a second. Over WiFi the speed is usually set by the WiFi itself.
Q29: How large can a file be?
A29: Up to 2,000 MB, just under 2 GB. A larger file is refused before anything of it is sent, because a browser cannot save a single received file that large. On a phone, free memory and storage can set a lower limit; for long videos, send one at a time, save it, and remove it from the list before sending the next.
Q30: What does "Sent. Waiting for the other device to confirm" mean?
A30: Every piece has left this device. The line changes to Delivered when the other device reports that it has the complete file. If the connection ends before that, the line says so, and the file should be sent again.
Q31: What happens to a file name on the way?
A31: It is cleaned before it is shown or used: folder parts are taken off, characters that a file system refuses are replaced by an underscore, and invisible marks that could disguise a file's real ending are removed. Two files with the same name are told apart with (2), (3) and so on.

5. Limits and Troubleshooting

Q32: Why can the two devices not find each other?
A32: Almost always they are not on the same network, or the network keeps its devices apart. Guest WiFi, hotel and office networks often do that on purpose. Put both devices on your home WiFi, or switch on the phone's hotspot and connect the computer to it, then start again. A VPN on either device can also stand in the way: switch it off for the transfer.
Q33: Does it work over mobile data, or between two places?
A33: No. A phone that is only on mobile data cannot reach a computer on WiFi, and two devices in different homes cannot reach each other. SafeBeam sets up no server that would carry the files between networks; that is what keeps the transfer between your own two devices.
Q34: The connection was lost in the middle of a file.
A34: The devices stopped reaching each other: one left the WiFi, went to sleep, or its browser was put in the background for too long. Files that were complete stay in the list. Connect again and send the unfinished file once more. The page asks the screen to stay on during a session, where the browser allows that.
Q35: Why did it disconnect by itself?
A35: A connection that is not used for 15 minutes is closed, so that a forgotten session does not stay open. Received files that you have not saved yet stay in the list after the connection has ended.
Q36: What does "The connection was closed for safety" mean?
A36: Something arrived that did not pass its check, or that the page did not expect at that moment. Rather than guess, the page accepts nothing more and ends the session. Pair the two devices again.
Q37: The page says my browser cannot run SafeBeam.
A37: The browser lacks something the tool needs, such as direct connections between devices, or it is too old. Use a current version of Chrome, Edge, Firefox or Safari. The tool also needs a secure (https) address, which this site always has.

6. Privacy

Q38: Do my files pass through your servers?
A38: No. The two devices connect directly to each other on your own network, and the files travel only between them. Our site delivers the page, as it does for every tool, and the page carries the site's usual advertising and visitor statistics. Your files, their names, your transfer password and the two codes are not sent to us or to anyone else.
Q39: What does the page keep in my browser?
A39: Nothing of its own. SafeBeam writes nothing to the browser's storage: no settings, no history of files, no password. Closing the page ends the session and forgets everything, including received files that were not saved.
Q40: What does the camera see, and where does the picture go?
A40: The camera is on only while a scanner is open on the page. Each picture is looked at for a code inside the page and then thrown away. Nothing is recorded, kept or sent, and the camera is switched off as soon as a code has been read or you leave the scanner.
Q41: What does the other device learn about mine?
A41: Its address on your local network, which it needs to connect, and after the password check a short general name such as "Android phone" or "Windows computer", so that each screen can show which device it is connected to. Nothing else.

Still have a question?

The help page walks through every part of SafeBeam. For anything else, use the contact form.