Before you begin
First keep the original file unchanged. Check that both pages are still open, the receiver has enough storage and the devices remain on the same allowed local network. A sleeping phone, Wi-Fi switch, closed tab or browser restart can all remove the active transfer path. Wait for the device connection to recover before trying the file again.
A practical workflow
Re-send a small test item and then the original file. Tell the recipient which copy to keep so that partial or duplicate downloads do not cause confusion. Avoid repeatedly sending a very large file to a disconnected device. If failures repeat, note the browser versions, network type and the point at which progress stops, but do not send private file contents to support.
Live presence & auto-reconnect
See who is online and how each device is connected. Dropped links rebuild themselves when Wi-Fi comes back.
Questions that matter
How large can files be, and how fast is the transfer?
Each file can be up to 1 GB. Files are split into chunks and streamed directly between devices with flow control, so speed is limited mainly by your Wi-Fi or Ethernet. Every recipient shows its own progress. If a connection drops mid-transfer, simply send the file again.
What happens if my network cannot be verified?
Share shows an explicit message and does not connect you to anyone automatically. Common causes are guest networks with client isolation, VPNs, mobile data, or corporate networks that block peer-to-peer traffic. You can try another network or use an optional LAN verification node.
Which browsers and devices are supported?
Current versions of Chrome, Edge, Safari and Firefox on Windows, macOS, Linux, Android, iOS and iPadOS. The browser needs WebRTC, WebCrypto and IndexedDB, and the page must be opened over HTTPS.
Open the page. That is the whole setup.
OKYA Share uses only standard browser technology, so there is nothing to install or configure.
- Join the same network: Connect your devices to the same Wi-Fi or wired LAN, then open share.okya.app in a modern browser.
- Devices verify each other: A lightweight signaling service introduces candidates. Automatic mode verifies a local host-candidate path; devices attested by a configured LAN node use a separate verification path.
- Share freely: Once verified, files, messages and screens flow directly between devices. Close the tab to stop sharing.
Connection and privacy
Messages and files are sent over WebRTC DataChannels, which are always encrypted (DTLS). TURN relays are disabled by design, so content can never be forwarded through a server.
If automatic local-path verification fails, Share shows a clear message instead of guessing. An optional administrator-run LAN node can attest devices separately; those attested connections may use configured STUN, but never a TURN relay. Network restrictions can still prevent a connection.