FileMonkey the parcel counter for your wifi ✦

Send a file to your other device over wifi

Straight from this browser to the one across the room — no cloud, no account, no cable. Pick a side:

1Open it on both

Load FileMonkey in a browser on each device. The one requirement is that both sit on one wifi network.

2One sends, one receives

On the device with the file, tap send. On the other, tap receive. Each now knows its job.

3Show a code, type it

The sender shows a short code; type it into the receiver, and the file flies across. Nothing to scan, nothing to paste.

Different networks? (not on the same wifi)

Tick this before pairing only when the two devices sit on separate networks. It asks a public STUN server (stun.l.google.com) for your outside address so the pair can meet across the internet — which, honestly, means that server learns your IP. Your files still never pass through it.

What happens at this counter

Two browsers open the same page. The sending one shows a short room code; you read it onto the receiving one and tap connect. Behind that, a tiny matchmaker introduces your two devices by the code — your files still travel straight device-to-device and never pass through it. From then on the pair holds a private, encrypted WebRTC data channel through your own router, and files move as 16 KB chunks with flow control, a running speed readout, and a SHA-256 fingerprint checked on both ends. When the tick says verified ✓, the copy is provably identical to the original.

The part worth underlining: the matchmaker carries only the code and a few hundred bytes of connection detail, both of which expire within minutes. It cannot see a filename, a byte of content, or where the parcel lands — those cross your router alone. Leave the different-networks switch off and everything but that one brief introduction stays inside your wifi.

The whole handshake, in three taps

  1. Show. The sending device taps send and puts a short room code on screen.
  2. Type. The receiving device taps receive, punches that code into the box, and taps connect.
  3. Beam. The pair links itself within a second or two — and the channel is open. Keep it open all evening; every further file rides the same channel with no re-pairing.

More desks at this counter

wifi login QRGet the second device onto your wifi first — print a scan-to-join code for your network. Nothing leaves the page. wifi speed gaugePair two devices the same way, then measure the real device-to-device throughput of your wifi — a number no internet speed test can tell you. text beamJust need a link, a password-reset code or an address moved from phone to PC? The text-only desk. checksum deskProve two copies of a file are identical: drop them, compare SHA-256 fingerprints.

FAQ

Is anything uploaded to a server?

No. Files go browser-to-browser across your own router over an encrypted channel. There's no upload and no relay. The only outside contact is the brief introduction: a tiny matchmaker introduces your two devices by the code — your files still travel straight device-to-device and never pass through it. Once linked, nothing you send touches an outside machine.

Is there a file size limit?

Not from us. Chrome and Edge can stream big parcels straight onto the receiver's disk (File System Access API), so multi-gigabyte files are fine. Safari and Firefox must hold the file in memory before saving — realistically about 1–2 GB. The receiver is told this plainly when a big parcel is announced, and can accept or decline it.

iPhone to Android? Phone to Linux?

Yes. Any two devices with a modern browser and the same wifi can beam — that's the whole advantage of doing it as a web page. AirDrop stops at Apple's fence and Nearby Share at Google's; a browser tab has no fence.

Why won't my devices connect?

Overwhelmingly: guest, hotel or office wifi with client isolation — the network deliberately blocks device-to-device traffic. Everything looks fine (full bars, web works) but peers can't reach each other. Use the main network, or make a phone hotspot the shared wifi. The page tells you when it suspects this.

Is it faster than the cloud?

Usually much faster: a cloud round-trip crawls up your uplink and back down; a beam crosses one room at wifi speed, commonly 5–30 MB/s on an ordinary router. Measure your own pair with the wifi speed gauge.

Do files linger anywhere afterwards?

Only where the receiver saved them. No third machine ever held a byte, because no third machine took part. Closing the tab discards the session, its keys and its room code.

How is this different from AirDrop or Snapdrop?

AirDrop: superb, but Apple-to-Apple only. Snapdrop and its cousins transfer peer-to-peer like we do, and, like them, we use a small matchmaker for the one genuinely hard part: letting two strangers on a network find each other. Ours is deliberately tiny — it holds only the code and the short-lived setup text, and your files never cross it. The reach is the point: iPhone to Android, phone to Linux, a browser tab has no fence.

What's the different-networks switch?

Off by default: everything stays on your LAN. On: each browser asks a public STUN server for its outside address so devices on separate networks can try to meet — the trade, stated plainly, is that the STUN server learns your IP. It never carries your files.