Share files and text between your devices

Text and clipboard updates have a 64 KiB encoded message limit. Send larger content as a file. Clipboard access also depends on permissions, page focus and browser support.

Online rooms use an internet discovery and signaling service. Files prefer a direct encrypted WebRTC channel. TURN and MQTT content relay require explicit permission in each tab; Direct only disables them. After permission, broker file fallback accepts up to 25 MiB. A DIRECT badge describes the selected route; it does not prove both devices are on the same Wi-Fi.

WebRTC data channels use transport encryption. Online signaling uses an internet broker. Text and clipboard prefer the direct channel. If you explicitly allow content relay, public-room broker payloads are not encrypted against the broker unless you set a room password. Share links use their own secret. Share room codes and links only with intended receivers.

After explicit relay permission, broker fallback accepts up to 25 MiB per file. Share links and folder packing accept up to 256 MiB. Receiving room files over 256 MiB requires a supported disk-saving API; browser and device limits still apply. No 50 GB transfer or fixed speed is guaranteed. Received downloads in the open room share a 512 MiB temporary cache; save files and clear the receiving stream when it is full.

Discovery uses an internet service and cannot prove that devices share a Wi-Fi network. If a device does not appear, open the same room code or share the room QR. The offline connection workflow exchanges two QR codes after both devices open the same room.

Clipboard sync must be enabled on both devices. Browser permissions, focus and system background restrictions apply. A received update may wait until the page is active. Manual copy is available when automatic access is unavailable.

The receiving app has verified the complete file, or text has been accepted by the receiving app. This does not mean a person has read it or that a browser download has been saved to disk. After reconnecting, the sender must Retry; reconnection alone does not restart a failed transfer. Room transfers can resume verified in-memory blocks for up to 10 minutes while both pages stay open, for browser-received files up to 256 MiB. To recover after refresh, enable temporary file recovery in receiver Preferences before transfer, then reselect the original source file on the sender. This stores incomplete file data locally, unencrypted at rest, for up to 10 minutes (expired data is removed when the app next runs). With temporary recovery enabled, disk-received files up to 256 MiB can resume after choosing a destination again. Share receivers can resume the same link; the sender must keep the source page open and choose Try Again.

Open and cache the site before going offline. Nearby devices on a reachable local network can exchange offline connection QR codes. Guest Wi-Fi isolation, VPN routing and browser restrictions can prevent a direct connection even on the same Wi-Fi.

The web app requires no account. Available features depend on the browser: clipboard, camera, disk saving, system sharing and background operation have different permission and support requirements. Keep both pages open during transfer.