mirror of
https://github.com/simplex-chat/simplex-chat.git
synced 2026-10-24 12:43:53 +00:00
32 lines
1.4 KiB
Markdown
32 lines
1.4 KiB
Markdown
# SimpleX File Transfer
|
|
|
|
Drag & drop a file here
|
|
|
|
or
|
|
|
|
Choose file
|
|
|
|
Max 100 MB - [SimpleX Chat app](https://simplex.chat/downloads) supports files up to 1 GB
|
|
|
|
Send files securely with end-to-end encryption — no accounts, no tracking.
|
|
|
|
## Get SimpleX Chat — the most secure & private messenger
|
|
|
|
The file transfer you just used uses the same data routing protocol as SimpleX Chat. The app has end-to-end encrypted messaging, voice and video calls, groups, and sending files. No account. No phone. No email. No user profile IDs.
|
|
|
|
# XFTP protocol: the most secure file transfer
|
|
|
|
### No account required
|
|
|
|
Each file fragment uses a new random key. Data routers have no "users" or "files" - they transfer encrypted file fragments of fixed sizes.
|
|
|
|
### Triple-encrypted in your browser
|
|
|
|
File encryption key is present only in the URL hash fragment - your browser never sends it to a server. There are 3 encryption layers: TLS transport, per-recipient encryption (unique ephemeral key per transfer), and file end-to-end encryption.
|
|
|
|
### Independent data routers
|
|
|
|
When file is split to fragments, it is sent via network routers operated by independent parties. No operator can see the actual file size or name. Even if a router is compromised, it can only see encrypted fragments of fixed size. File fragments are cached by network routers for approximately 48 hours.
|
|
|
|
[Read the XFTP protocol specification →](https://github.com/simplex-chat/simplexmq/blob/stable/protocol/xftp.md)
|