Sending files
Select your files, create a transfer, then share the generated QR code or link with the receiving device.
Transfer files directly between devices using your browser. No account, no cloud upload, and no complicated setup.
Select your files, create a transfer, then share the generated QR code or link with the receiving device.
Open the shared transfer, review the files, and accept the transfer to begin the direct connection.
A few simple conditions help make the transfer reliable.
Keep both devices connected to the network throughout the transfer.
Chrome, Edge, Firefox, Safari, or another modern WebRTC-capable browser is recommended.
Do not close or refresh the transfer page while the transfer is running.
Avoid sleep mode or disconnecting Wi-Fi during an active transfer.
For the most reliable local transfer, connect both devices to the same Wi-Fi network. SendIt can use WebRTC to establish a direct browser-to-browser connection between them.
The sender creates the temporary transfer room and chooses which files to share.
Open SendIt on the device containing the files you want to send.
Choose one or multiple files. Check the filenames and sizes before creating the transfer.
SendIt creates a temporary transfer room and prepares the browser-to-browser connection.
Show the QR code to the receiving device or copy and share the transfer link.
Keep this page open while the receiving device joins and accepts the transfer.
Do not close either browser or disconnect the devices until SendIt reports that the transfer has completed.
The receiver reviews the transfer before accepting the direct connection.
Scan the sender's QR code or open the transfer link provided by the sender.
Check the number of files, filenames, and total size before accepting.
Choose Accept when you are ready to establish the direct browser connection.
Keep the receiving browser active until all files have finished transferring.
After completion, check that the received files are present and open correctly.
QR codes are useful when the receiving device is nearby and typing a long transfer URL is inconvenient.
If the receiving device uses the built-in QR scanner, allow camera access when the browser asks for it. Camera access is only needed for scanning the QR code.
The file transfer is happening directly between the browsers, so both devices need to remain available.
Closing or refreshing the tab can interrupt the active WebRTC connection.
Maintain a stable network connection until the transfer finishes.
Keep the devices awake during large or long transfers.
Confirm that SendIt reports completion before closing the transfer page.
Do not assume that the transfer is complete simply because the connection has been established. Wait until all files have finished transferring and the completion message appears.
SendIt is designed around direct browser-to-browser transfer rather than cloud file storage.
The actual file contents are sent through the WebRTC connection between the participating devices. SendIt's signaling system is used to help establish the connection and coordinate the temporary transfer.
Direct transfer does not remove the need for normal security precautions.
Only share your transfer link or QR code with the person who should receive the files.
Check filenames and file sizes before accepting an incoming transfer.
Avoid transferring sensitive information over networks you do not trust.
Modern browsers provide the WebRTC and security features SendIt relies on.
Check these common causes before trying again.
Check that the complete SendIt transfer link was copied correctly and that the transfer has not expired.
Check the browser's camera permission and make sure another application is not already using the camera.
Create a new transfer. SendIt transfer rooms are temporary and are not intended to remain active indefinitely.
Keep both devices awake, keep the transfer tabs open, verify the network connection, and retry with a newly created transfer if necessary.
Create a new transfer and repeat the process. An active transfer should not be treated as recoverable after the session has been interrupted.