Jfsendit – A dead-simple way to send files straight from one browser to another

coinfused1 pts0 comments

just f***ing send it

Send files

or receive

Join

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

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

Waiting for them to join…

Your code

Copy link<br>Copy code

Only one person can join with this code, and only once — share it with just them.

Scan to open on a phone

Cancel

Connected — drop files to send

Drag files or folders here<br>or pick below

Choose files<br>Choose folder

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

Disconnect

Connecting…

Reaching the other device directly. This can take a few seconds.

Cancel

Connected

They want to send you files

Save & receive

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

Decline

Transfer

you

them

overall<br>0%

files left

speed<br>0 MB/s

eta

play 2048 while you wait →

On the same network but slow? →<br>Cancel transfer

Done.

Send something else

Couldn't connect

Try again<br>On the same network? Make it connect →

2048<br>snake

score 0<br>New game

arrow keys or swipe

Game over — 0

Submit

2048 leaderboard

questions

What is jfsendit?<br>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?<br>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?<br>Free, and no account. Click send, share the code, done.

How big can files be? Can I send a folder?<br>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?<br>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?<br>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?<br>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?<br>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?<br>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?<br>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...

files send code transfer agree jfsendit

Related Articles