Connexion…
No file selected

Folder support depends on your browser. If it is unavailable, choose files instead.

Keep this page open during direct transfer. No upload needed.
Received files appear where your browser saves downloads.

Send files with one private link

No cloud, no account. Choose files, then share a Magic Link, one-time code, or QR with the person receiving them.

One gesturePick files and create the private link.
Local firstYour browser prepares the share before you send it.
Clear progressSee what is ready, moving, or complete.

Mode ROOM

Create a private room for a group

One temporary room, one invite link, many files. Invite people, exchange files, and keep the page open during direct transfers.

Start a temporary room

Create a room, choose your avatar, then share the invite. Files and chat unlock once the room exists.

Activity

Send without explaining the tech

Drop a file, Filenymous encrypts it here, then offers the best available path. For large files, direct P2P takes over instead of blocking the send.

1DropPlace the file in the drop zone.
2Create the codeA short code is enough for the recipient.
3Stay connectedDirect transfer continues while both pages stay open.

File to send

Recipient (optional)

You can leave this empty: Filenymous creates a code or link you share yourself.

Send to a contact (end-to-end)

Pick a contact: the file key is encrypted for them only - the link alone cannot decrypt.

My identity - receive end-to-end

No key yet

Share your identity code: your contacts add it in their Contacts tab and every file they send you is encrypted for you alone.

Message (optional)

0 / 500

Options

  • Local AES-256-GCM encryption in your browser
  • Direct WebRTC for browsers, Iroh v1 for future verified transport
  • Holochain/HWC remains available in advanced mode
  • No account required, pseudonym by default

Receive a file

Paste a Filenymous link or enter the one-time code given by the sender. Filenymous chooses the right mode automatically.

After validation: keep this page open. For large files, transfer continues directly with the sender. The downloaded file will appear in your browser Downloads folder, unless your browser asks you to choose a location.

My files and public links

Everything stays local by default. The public open directory lists only links you explicitly publish, never private keys or a raw server folder.

Public open directory Visible on the web, fed only by explicitly published links.
Open
Local inbox History stored in this browser, without automatic sync.

Important: "public open" means a voluntary catalog. Automatic OVH directory indexing is not enabled, preventing accidental publication of files or metadata.

Local history

No transfer yet.

Advanced networks

The public can use Filenymous without a conductor. This area explains and activates stronger engines: Iroh for verifiable large files, Holochain for identity and coordination.

Iroh v1 Modern QUIC transport

Priority for the web roadmap: dial-by-key, encrypted relays, NAT traversal, and more robust transfer without a native installer.

iroh-blobs BLAKE3-addressed files

Enables verified streaming, partial resumes, and a better experience for large files.

Browser WebRTC remains direct

Iroh in browser WASM currently goes through relays; WebRTC DataChannel remains the direct no-download path.

Sender identifier

Loading...
Loading...

Recipients will see the first 16 characters of this identifier with your transfer.

Portable web version

Filenymous remains a P2P web app: no native installer, no mandatory local Holochain conductor. These archives open the same app in a modern browser.

Download the web version
WindowsmacOSLinux
?Web: local AES-256-GCM encryption
?Web: one-time code and direct WebRTC P2P
?Web: keys and history stored locally
~Advanced: Holochain/HWC and Iroh remain optional network modules

Your sovereign identity

Generate a local X25519 keypair to receive end-to-end encrypted transfers. Your private key never leaves this browser. Share your identity code so contacts can encrypt files directly for you.

My identity code (X25519 public key)

Loading...
No key yet

Send this code to your contacts (email, chat...). They add it in their Contacts tab to send you end-to-end encrypted files.

My keys (backup)

The exported file contains your private key. Keep it safe and never share it.

Holochain DHT publication

With a Holochain conductor or Holo Web Conductor, you can also publish your key on the DHT so senders find you by email or phone hash. See the Advanced tab.

My contacts

Add the people you send files to. With their identity code, the file key is encrypted end-to-end for them (ECIES) - the link alone is no longer enough to decrypt.

Add a contact

Contacts

Advanced wallet

Web version: encrypted local wallet, Bitcoin Signet and Ethereum Sepolia by default, mainnet locked.

Receive BTC / ETH

  • BTC and ETH addresses are derived locally from a BIP39 seed.
  • The seed stays encrypted in IndexedDB with a local password.
  • No private key is published on Holochain, GitHub, or OVH.

Send with guardrails

Mainnet sends remain blocked until the user explicitly unlocks them in the React version.

Privacy by design

Filenymous is not only GDPR-aware. Its architecture is designed so an operator cannot read your files by structure, not by promise.

Transfer solution comparison

WeTransfer

?Files stored on centralized AWS servers
?Analysis for ad targeting on the free plan
?Account required above 2 GB
?US servers subject to Cloud Act exposure
~HTTPS transit encryption only

SwissTransfer

~Swiss servers with stronger legal protection
?Files stored in cleartext by Infomaniak
?No advertising
?Infomaniak can technically read files
?Free up to 50 GB

Filenymous

?No file on a third-party server
?Browser-side AES-256 end-to-end encryption
?No account, no ads, no tracking
?P2P network with reduced centralized exposure
?Cryptographic expiry and revocation

Holochain security pillars

Key

Cryptographic identity

Each participant is a locally generated Ed25519 key pair. No central authority issues identity, and your private key never leaves your device.

Chunks

Encrypted fragmentation

Files are split into 512 KB chunks, encrypted with AES-256-GCM, then distributed across different DHT nodes. No node holds a complete file.

DHT

Coordinator-free DHT

The Holochain DHT stores data redundantly without a master server. There is no single attack, seizure, or censorship point.

TTL

Enforced expiry

Expiry publishes a DeleteAction on the DHT. Participating nodes are required by DNA validation rules to remove the data.

Hash

Minimal contacts

Your email or phone number is never published on the network. Only its SHA-256 hash is stored with your public key.

Log

Immutable source chain

Each agent keeps a signed local chain. Forging an action is detectable by the network without blockchain consensus.

Legal and GDPR notes

Data controller

Filenymous is a decentralized open-source protocol. Without a central file database, there is no classic data controller for transferred files. Each user is responsible for the data they publish to the DHT.

Collected data

The notification bridge may temporarily receive the destination address and transfer link for email/SMS delivery. This data is not persisted beyond sending. There are no tracking cookies, analytics, or advertising.

Right to erasure

The sender can revoke a transfer from the History tab. Revocation publishes a cryptographic delete action on the DHT, and participating nodes remove chunks under the app rules.

Data hosting

Encrypted chunks are distributed across active Holochain Filenymous network nodes. No chunk is located on an editor-managed file server, and node geography is unknown by design.

Open-source code ? github.com/Geoking2104/Filenymous