just f***ing send it

Files go straight from your browser to theirs. No upload, no server, no account.

or receive

Got a code or a link? Drop it in and join.

By sending or receiving a file, you agree to the Terms & Disclaimer.

questions

What is jfsendit?

A dead-simple way to send files straight from one browser to another — no upload, no account, no middleman. You get a short code; whoever you give it to gets the files.

How are my files sent?

Directly device-to-device over an encrypted WebRTC connection. The bytes never pass through or get stored on a server — only a tiny code-exchange does, to introduce the two browsers to each other.

Is it free? Do I need an account?

Free, and no account. Click send, share the code, done.

How big can files be? Can I send a folder?

No hard limit — multi-gigabyte works fine. Drop a whole folder and it streams across as one .zip. Data streams straight to disk, so nothing has to fit in memory.

What if the connection drops mid-transfer?

It reconnects and resumes from the exact byte it left off — as long as you keep the tab open. Keep both devices awake for the whole transfer.

Are my files encrypted?

Yes. WebRTC encrypts everything end-to-end (DTLS) by default. We can't see, scan, store, or recover what you send — there's nothing on our side to look at.

Can I send to more than one person?

No. Each transfer is strictly one-to-one: one sender, one receiver. Whoever connects first with a valid code becomes the receiver, and the code is then used up.

Why won't it connect, or why is it slow?

There's no relay server, on purpose — so it needs a direct path between the two devices. If it can't find one, get both onto the same Wi-Fi, or turn on a phone hotspot and connect both to it. The in-app "connection help" walks you through it.

Which browsers work?

Chrome, Edge, Firefox, and Safari — including iPhone and Android. For multi-gigabyte transfers, a desktop Chromium browser saves straight to disk most reliably.

Do the codes expire?

Yes. They're short-lived and one-time — once a transfer finishes or it times out, the code is dead.

no accounts · no tracking · files never touch a server

Terms & Disclaimer

Read this. Using jfsendit means you agree to it.

By using jfsendit to send or receive files, you agree to these terms. If you don't agree, don't use it. You must be of legal age and able to enter a binding agreement.

How it works. Files transfer directly between two devices, one sender and one receiver, end-to-end encrypted. Nothing passes through or is stored on our servers, only a brief signaling handshake that carries no file data. We cannot and do not see, scan, moderate, store, recover, or control what you send or receive. Each transfer is strictly one-to-one: a code is short-lived and pairs exactly one sender with one receiver. Whoever connects first with a valid code becomes that receiver and the code is then used up, so only share it with the person you mean to.

Your files, your responsibility. You are solely responsible for what you send, what you receive, and who you share a code or link with. You represent and warrant that you own, or have all rights and permission to send and distribute, every file, and that doing so is lawful. Because we can't scan anything, treat received files as unverified and scan them yourself before opening.

No illegal or harmful use. Nothing illegal, infringing, or harmful, including malware or files meant to damage others or their devices.

As is. The service is provided "as is" and "as available," with no warranties of any kind, including delivery, availability, or fitness for any purpose. Transfers can fail.

No liability. To the fullest extent permitted by law, jfsendit and its creator have no responsibility or liability for any files sent or received, or for any damages arising from use of, or inability to use, the service.

You cover us. You agree to indemnify and hold jfsendit and its creator harmless from any claims, losses, or expenses arising from your files or your use of the service.

Changes. We may update these terms at any time; continued use means you accept the changes.

On the same network but slow?

If both devices are on the same Wi-Fi/LAN but it's slow, the data is going out over the internet instead of staying local. The transfer screen shows path: via internet when that happens — the goal is path: LAN direct. Try these, restarting the transfer after each, and watch the path line:

1. Turn off any VPN on both devices. A VPN forces traffic through its tunnel and blocks the direct local path — this is the most common cause.

2. macOS: allow Local Network access. System Settings → Privacy & Security → Local Network → switch on your browser (e.g. Chrome), then fully quit and reopen it. Browsers need this to find devices on your LAN.

3. Same network, not “guest.” Put both devices on the same Wi-Fi name, and on your router turn off “client isolation” / “AP isolation.” Guest networks almost always block device-to-device traffic.

4. Best: use wired Ethernet. Plug both devices into the same router or switch — that always gives a direct LAN path at full speed.

5. Check the firewall. macOS: System Settings → Network → Firewall — allow your browser (or turn it off briefly to test). Windows: allow the browser through Windows Defender Firewall.

We never relay your files through a server, so if no direct path can be made the transfer stays slow or fails rather than routing your files through us — that's by design.