Find and save received files
OKYASHAREDocumentation

File transfer

Find and save received files

Know the difference between a conversation preview, browser history and a durable copy on your device.

Updated 3 min read

Check the recipient and conversation before sharing. A local network is not proof that every connected device is trusted.

Before you begin

Each conversation has its own file list. Find the correct room or private conversation before looking for an attachment. An image, video or PDF may have an inline preview, but being able to see that preview is not the same as saving a file into your normal documents folder. Use the available save or download action and check the destination chosen by the browser.

A practical workflow

Browser storage is local to a profile and may be cleared by privacy settings, site-data removal or storage pressure. Keep important work in a folder you control and verify it with the receiving application. A file listed in an older conversation may still depend on an available peer holding its content. Share does not turn history into a permanent, remotely accessible download service.

Inline previews

Images, videos and PDFs open right in the conversation, so everyone sees the same thing without downloading first.

Questions that matter

Where is my chat history stored?

Only in the local IndexedDB database of each browser, separated by network. Nothing is uploaded. You can clear the history at any time, and clearing site data in the browser removes it completely.

Can a newly joined device see earlier messages?

When a direct connection is established, peers share up to 100 recent public records. A device that posted locally while alone can share those records when another device connects. A peer holding the history must still be available; this is not cloud backup. File and voice contents are fetched separately when available, and private conversations are excluded.

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.

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.

Sources and further reading