How does dkair send a file without uploading it to a server?

dkair reads your file locally and opens a direct browser-to-browser connection (a WebRTC DataChannel) with your recipient. The file streams straight across that connection in batches. Only a tiny connection handshake passes through a public signalling broker — the file bytes themselves never touch a server.

Do both people need to keep the page open?

Yes. Because the transfer is a live peer-to-peer connection, the sender's tab must stay open while the file is sent. The moment the recipient opens the link the connection forms and the transfer begins; once it finishes you can both close the tab.

Is there a file size limit?

There is no fixed cap. dkair streams the file in 256 KB chunks with back-pressure, so memory stays bounded and large files transfer smoothly. The practical limit is your connection speed and how long both tabs stay open.

Is the transfer private?

The file goes directly between the two browsers and is not stored anywhere. WebRTC DataChannels are encrypted in transit (DTLS). dkair itself is a static site with no backend and keeps no copy of your file.

dkair — peer-to-peer file sharing in your browser, no upload

dkair sends any file straight from your browser to someone else's, peer-to-peer over WebRTC. Drop a file, get a link, and stream it to whoever opens the link — in batches, in real time. The file never touches a server: no upload, no signup.

First in the dk file family. Companion to fqvid (trim + YouTube batch upload), fqgif (video → GIF), and fqfit (compress for Discord). Please enable JavaScript to use dkair.