關於 點對點傳輸
瀏覽器之間直接傳輸檔案、資料夾與文字
瀏覽器之間直接傳輸檔案、資料夾與文字 The interface is designed to keep the important input, options, and result close together so you can finish a small development task without leaving your browser.
如何使用這個開發者工具
- Open the tool on both devices. On the first device create a room and share the eight-character code, invite link, or QR code; on the second device enter that code to join.
- Without a room, switch to manual codes: generate an invite code, hand it to the other side, and paste the reply code back to finish the handshake completely offline.
- Add your own STUN or TURN servers when the two devices are not on the same network, and enable relay-only mode if you do not want local addresses in the candidates.
- Once the channel is connected, drag in files or folders, or type a message. Pick a receive folder first when the transfer is larger than browser memory allows.
私隱與資料處理
File and message contents travel only over the direct WebRTC data channel, which is encrypted with DTLS. The room mailbox relays session descriptions and ICE candidates in memory for at most ten minutes and is released as soon as the channel is up; manual codes avoid the mailbox entirely. STUN and TURN credentials stay in this browser and are sent only to the servers you configured.
相關開發者工具
常見問題
Do my files pass through your server?
No. Files, folders, and text move directly between the two browsers over the WebRTC data channel. The server only relays the short session-setup messages, and only in room mode.
Why do I need a TURN server?
STUN is enough when at least one side can be reached through NAT. When both networks block direct paths, a TURN server relays the encrypted media, so bring your own to keep control of that relay.
Is there a file size limit?
Transfers stream in chunks, so size is bounded by the receiving side. Choose a receive folder to write straight to disk; otherwise received data is buffered in browser memory up to 512 MB.