LocalShare

Peer-to-peer file transfer

Idle

Send files to another device

Pick your files, then exchange two short codes with the receiving device to establish a direct, encrypted connection.

1

Select files

Drop files here or click to browse

Any file type • No size limit

2

Generate your connection code

3

Paste the receiver's answer

4

Transfer

Files will appear here once connected.

About LocalShare

A self-hosted LocalSend-style file sharer you can deploy to Cloudflare Pages.

🔒 How it works

LocalShare uses WebRTC to create a direct, encrypted peer-to-peer connection between your devices. Files never touch a server — they flow straight from one device to the other over your local network (or even across the internet, when network conditions allow).

Because the app is static (just HTML/CSS/JS), there's no signaling server to relay connections. Instead, you exchange two short codes with the other device — once via copy-paste through any chat app, email, or even by reading them aloud.

📱 Typical usage

Open this page on the sending device, pick files, generate a code.
Open this page on the receiving device, paste the code, copy the answer.
Send the answer back to the sender, paste it, connect — files transfer.

🚧 Limitations

The two-code handshake is needed because static hosting can't run a signaling server.
Very large files (multi-GB) may hit browser memory limits on the receiving side.
If both devices are behind strict NATs on different networks, the connection may fail — same Wi-Fi is the most reliable setup.

☁️ Deploying to Cloudflare Pages

This whole app is a single HTML file. To deploy:

Sign in to Cloudflare Dashboard → Workers & Pages → Create → Pages → Upload assets.
Drag the index.html file into the uploader (or upload the whole folder if you added a README).
Set a project name, click Deploy site. Your app is live on <name>.pages.dev.
Or via CLI: npx wrangler pages deploy . from the folder containing the HTML.

The app needs no build step, no environment variables, and no backend.

⚖️ Why not the real LocalSend protocol?

The original LocalSend uses HTTP/mDNS for device discovery. Browsers can't do mDNS, and a page hosted on HTTPS (as Cloudflare Pages forces) can't make HTTP requests to private IPs (mixed content). So a literal LocalSend protocol clone wouldn't work from a static site. WebRTC gives the same end result — direct device-to-device transfer — and works in any modern browser.