Every transfer verified, chunk by chunk

Move files, keep control

Drop files, prepare them in your browser and send them straight to another device. Peer to peer, no account, nothing kept on our servers

  • No sign-up
  • Nothing stored
  • Any modern browser
clex.in/workspace Runs in this tab
  1. 01Drop images, PDFs, documents, anything
  2. 02Prepare with tools that run in the tab
  3. 03Share by code, link or QR
Someone sending to you? Receive here
Nothing in between

Your files go from your device to theirs, and nothing in between keeps a copy that's the point

How it moves

One tab, three moves

No hopping between a converter, a compressor and a file host. The file you drop is the file you prepare is the file you send

  1. 01

    Drop

    Drag files in, paste from the clipboard or pick them from your device. They stay in this tab's memory and nothing is uploaded anywhere.

    • Images
    • PDF
    • DOCX
    • Anything else
  2. 02

    Prepare

    Compress a photo, convert its format, merge or split PDFs, turn a Word file into a PDF and bundle it all into a ZIP. Every tool runs in the browser.

    • Compress
    • Convert
    • Merge
    • ZIP
  3. 03

    Share

    You get a six character code, a link and a QR. The other browser opens it, connects to yours and the file streams across, encrypted in transit and verified on arrival.

    • Code
    • Link
    • QR
Clex Direct+

Every chunk accounted for

Direct transfers are cut into 64 KB chunks and acknowledged one by one. Lost chunks are resent, damaged ones are re-requested by hash, and a transfer can pause and pick up where it stopped. When the last chunk lands, both sides get a receipt

  • Chunk manifestsize and SHA-256 for every chunk
  • ACK and retryonly missing chunks are resent
  • Pause and resumeno restart from byte zero
  • Health scorea live reading from 0 to 100
  • Verified receiptcontent free, with a root hash
  • Compatibleolder peers fall back on their own
PDF report-final.pdf3.1 MB · 48 chunks of 64 KB Streaming
Acked
0/48
In flight
0
Retries
0
Health
—
Senderyour browser Receivertheir browser
Verified receipt48/48 chunks · 2 retries · health 97 · root
Delivery

Two routes, both direct

Whichever you pick, the file goes from one browser straight to the other. There is no relay in the middle holding a copy

only says hello straight across

Direct

Default

Across the internet. A STUN server helps the two browsers learn each other's address, and that is all it does. After that, the data channel runs between them alone.

Transport
WebRTC data channel
In transit
DTLS encrypted
Best for
Anyone, anywhere
never leaves the house

Local

Same Wi-Fi

Inside your network. Only local addresses are offered, and if the connection would leave the network, Clex stops rather than route it out.

Transport
WebRTC, host only
Speed
Your LAN's
Best for
Big files, own devices

Can't connect either way? Clex tells you instead of quietly uploading. Keep both tabs open until the transfer is done.

Vault, inside the workspace

The private side built in

Flip the workspace to Vault for encrypted notes and secret links. Notes are encrypted before they touch your device's storage, sync only between devices you pair, and never appear on the public chain

  • Encrypted notes and folders, searchable and offline
  • Peer to peer sync between paired devices
  • Secret links with expiry, view once and copy guards
  • QR hand-offs and short reveal codes
Transfer chain

Receipts, not copies

Every finished transfer prints a receipt you can keep, save as an image or send on: route, size, chunks, retries and a root hash, nothing about the file itself. The same record joins a public, hash linked chain, so anyone can check that a delivery happened

Transfers
—
Completed
—
Browsers
—
Open the explorer
Developers

Send from the terminal

Mint a key without signing up, then upload with one HTTP call from any language and get a share link back. It runs on clex.in today.

Get an API key