What Share2Us is
Share2Us moves a file from wherever you are to whoever needs it, without asking you to think about storage buckets, expiring credentials, or which chat app mangles attachments.
There are three ways a file travels, and they are genuinely different mechanisms rather than three buttons on the same one.
A link
Section titled “A link”The file is uploaded and you get back a short, opaque link. Opaque matters: the link says nothing about you, the file, or how many others exist. Anyone holding it can open it, so a link is as private as you keep it, and you can narrow that with a password, an expiry, a view limit, a single use, or a list of email addresses allowed to open it.
This is the default and it is what s2u report.pdf does.
End to end, to a device
Section titled “End to end, to a device”The file is encrypted on your machine before it is uploaded, and the key is sealed to the device you are sending to. The server stores and relays the ciphertext and never holds the key, so no endpoint on our side can return the plaintext, and neither can we.
Use it to move something between your own machines, or to send to a contact.
Directly, over your own network
Section titled “Directly, over your own network”Nothing is uploaded at all. One machine listens, the other connects, and the bytes go straight across your LAN, your tailnet, or a WireGuard link. It works with no account and no internet connection, and it is the right choice for a large file between two machines in the same building.
What runs where
Section titled “What runs where”| Piece | What it is |
|---|---|
s2u |
The command-line client. One binary, no runtime. |
| Desktop app | A window plus a right-click entry in your file manager. |
| The service | Stores shares, serves links, relays encrypted transfers. |
The command line and the desktop app share the same library underneath, so they behave the same way. Anything you can do in one, you can do in the other, except where the interface makes no sense: there is no right-click menu in a terminal.