LAN File Transfer
Transfer files directly between devices on your network.
No uploads to any server. No account needed.
Share this code with the receiver:
Enter Room Code
Enter the code shown on the sender's device
Drop files here or click to select
Files are sent directly to the other device
Waiting for files...
Files sent by the other device will appear here
How LAN transfer works
- Open this page on both devices while they are on the same network. A phone on the office Wi-Fi and a laptop on the same Wi-Fi qualify; a phone on mobile data may not.
- One device chooses Send and gets a short room code. The other chooses Receive and types that code in. The room code is how the two browsers are paired.
- Once connected, files move straight from one browser to the other over WebRTC, in 64 KB pieces, and the receiving browser reassembles them and offers a download. No file is uploaded to dosya.dev or to any other server at any point.
When to use it instead of a share link
Use LAN transfer when both people are in the same room or building: handing a few gigabytes of footage to an editor across the desk, moving a build from a workstation to a test laptop, or getting photos off a phone onto a computer without a cable. It avoids the upload-then-download round trip of a cloud service, since the file travels directly between the two browsers rather than through a storage service, and it does not depend on your upload bandwidth, so it works when the connection is slow or metered.
Use a share link when the other person is somewhere else, when they will pick the file up later, or when you want a password, an expiry date or a record of who downloaded it. A share link needs the file stored in your workspace first; LAN transfer stores nothing.
What stays private
Neither side needs a dosya.dev account, and nothing about the transfer is written to one. The file itself never reaches a server: the only traffic to dosya.dev is the room code and the signalling handshake, which contain no file content. To find a route, each browser asks a public STUN server (Google's) for its own address; that server sees the two addresses, never the file. dosya.dev keeps a standard access-log entry for the room creation (time, IP address and browser), the same as for any request to the service. An unused room record holds only the pairing details, never file content, and is deleted about ten minutes later, the next time someone creates a room.
Both browsers hold the whole file in memory during the transfer, so very large files are limited by the memory each device can spare. For files that size, the desktop app's sync folder is the better tool.
LAN Transfer only works between devices on the same network. To send a file to someone somewhere else, use a share link, and to keep a folder mirrored across your own machines, use the desktop app.