List of P2P file sharing tools

list_of_p2p_file_sharing.md

Browser Based

1. Web Wormhole https://webwormhole.io/ https://github.com/saljam/webwormhole
2. Localsend https://web.localsend.org/
3. FilePizza https://file.pizza/
4. ShareDrop sharedrop.io https://github.com/szimek/sharedrop (SOLD, not recommended, use one of the forks)
   1. A clone SnapDrop snapdrop.net https://github.com/RobinLinus/snapdrop (SOLD, not recommended, use one of the forks)
      1. A fork PairDrop https://pairdrop.net/ https://github.com/schlagmichdoch/pairdrop
5. ToffeeShare https://toffeeshare.com/
6. Instant.io https://instant.io/
7. FileTC https://file.tc/
8. Send Anywhere https://send-anywhere.com/
9. Just Beaam it https://www.justbeamit.com/
10. Peermesh https://perguth.de/peermesh https://github.com/perguth/peermesh
11. drop.lol https://drop.lol/ https://github.com/mat-sz/filedrop
12. rDrop https://rdrop.link/
13. AirDelivery https://airdelivery.site/
14. Blaze https://blaze.vercel.app/ https://github.com/blenderskool/blaze
15. SendFiles https://sendfiles.dev/ https://github.com/jchorl/sendfiles
16. Katana https://sekky61.github.io/Katana/ https://github.com/Sekky61/Katana
17. FileLove https://file.love/ https://github.com/midzer/filelove
18. Filegogo https://send.22333.fun/ https://github.com/a-wing/filegogo
19. Peertransfer https://github.com/perguth/peertransfer https://perguth.de/peertransfer/
20. Yt2fb.in https://yt2fb.in/file-transfer/
21. P2P File Transfer https://chidokun.github.io/p2p-file-transfer/ https://github.com/chidokun/p2p-file-transfer
22. P2P File Transfer https://webbrowsertools.com/p2p-file-transfer/ https://github.com/leocompson/p2p-file-transfer
23. NeighborHoodShare https://neighbor-share.vercel.app/ https://github.com/dikshantrajput/neighborHoodShare
24. Vegh https://vegh.netlify.app/ https://github.com/veghfile
25. P2P File Sharing https://taonexus.com/p2pfilesharing/

TODO

• Test which of these tools can send very large (10GB+) files without freezing/crashing the browser.

CLI

1. croc https://github.com/schollz/croc
2. p2pcopy https://github.com/psantosl/p2pcopy
3. pcp https://github.com/dennis-tra/pcp
4. wormhole-william https://github.com/psanford/wormhole-william
5. Wush https://github.com/coder/wush
6. sendme https://www.iroh.computer/sendme https://github.com/n0-computer/sendme
7. B·o·B https://bob.osau.re/ https://github.com/dinosaure/bob

(Updated the list based on comments. Only keeping p2p tools)

Hey, I'm going to build a similar P2P application, but I'm confused about which database to choose. Do you have any suggestions for me?

What do you need it for? Perhaps SQLite and/or LMDB. In case of SQLite, you will need to handle sync/replication logic at the P2P layer. In case of LMDB (lightweight key-value storage), you need complex queries. In case of RocksDB (which is common for P2P logs), things might work fine although it is a heavier dependency than SQLite or LMDB.

If you need distributed database (if peers replicate shared state), then you could use Apache Cassandra (heavy and bloated though), or RethinkDB or CouchDB which has more overhead than embedded solutions. There is OrbitDB (on IPFS) which is specifically designed for P2P but it is not as mature as SQLite/LMDB. Try CouchDB if you want an established database with replication, or OrbitDB if you are already considering IPFS.

As for security considerations, store file chunks with strong hashing (SHA-512, BLAKE2 or BLAKE3). Database should only hold metadata and hashes. Sign metadata updates with public/private keys. Consider encrypting sensitive metadata before storing. That said, the less metadata, the better.

TL;DR:

• For per-peer metadata (local index, cache): SQLite (with WAL mode enabled) if you want relational queries, or LMDB if you want raw speed and durability.
• For distributed metadata sharing, use CouchDB (battle-tested, sync-friendly) or OrbitDB if tied to IPFS. That said, distributed metadata is typically shared with DHT, Gossip protocols, or CRDTs. If the metadata is simple, a DHT alone is enough. Ask yourself: do you need searchable metadata (tags, names, comments)? Do you need user identities or reputations? Is it going to be a collaboration-oriented P2P app?

I believe the safest and most efficient hybrid would be SQLite for local peer database + DHT for peer discovery + optional CouchDB / OrbitDB for global metadata replication.

For what it is worth, a database is not strictly required at all. Many successful P2P systems work entirely on DHTs + file chunk hashes + ephemeral in-memory data structures. That said, if you want persistent metadata then a local DB will give you persistence of file index, known peers, partial downloads and efficient lookups (with indexing), along with atomic transactions.

BitTorrent clients use databases (often SQLite or custom key-value stores) to persist torrent metadata and resume downloads, but a minimal DHT client does not.

Start with a DHT and keep metadata minimal, then store additional metadata off-chain in append-only logs. If structured metadata is required, use a CRDT-based store (OrbitDB, Yjs, Automerge) for distributed consistency, or CouchDB-style replication for document metadata.

In any case, for a P2P file-sharing app, use DHT for discovery, use local DB (SQLite/LMDB) only for persistence per peer and consider a distributed database if and only if you want more than "file hash -> peers", e.g. search, tags, or social features.

I hope this answers your question.

Hello! I developed https://p2party.com which creates WebRTC rooms and does file transfers in the browser. You can find the relevant source code at https://github.com/p2party/p2party-js

Isn't WebRTC insecure? And as you have stated, it shows your IP address to people and possibly adversaries.

@Ccocconut
Well the gist has a section for browser-based tools, which as far as I know all use WebRTC behind the scenes, which exposes information about a peer's network topology in RTCSessionDescription offer and answer and RTCICECandidate, which both need to be exchanged between peers for a connection between them to happen. If you know of another tool and way that works in the browser I would be very glad to hear about it.

In my tool specifically, you can choose to use a whitelist or a blacklist, which means that the signaling server will not send your information to peers who are not in the whitelist or who are in the blacklist, even if they are in the same URL, which is generated by your browser's randomness double-SHA512-hashed so kind of difficult to be found by chance if you don't share it with anyone.

Someone should add dropsilk.xyz

Just a note that many new entries are looking very similar for some reason, and also giving off similar vibes with their privacy/terms/about sections. Same goes for the UI, also for the domain names. Some look like they have been made very recently.

I also tried testing some of the browser ones. Web Wormhole and very few others were the only ones which start downloading the file immediately (to the file system, your browser will show a file being downloaded) and I think these shouldn't crash on very large files (multi GBs). Most other tools download the file in browser (memory? cache?), and only when the download is complete, it's saved as a file.

Hello! I developed p2party.com which creates WebRTC rooms and does file transfers in the browser. You can find the relevant source code at github.com/p2party/p2party-js

Hi, this has been hard to use. I don't understand the UI. I opened two tabs in same browser, also in different browsers using same url. I couldn't see a connection between two peers. Kept saying waiting for peers.

I also tried testing some of the browser ones. Web Wormhole and very few others were the only ones which start downloading the file immediately (to the file system, your browser will show a file being downloaded) and I think these shouldn't crash on very large files (multi GBs). Most other tools download the file in browser (memory? cache?), and only when the download is complete, it's saved as a file.

Which ones do streaming of files in your testing beside web wormhole?

Which of the newer ones have all of you found to be easier to use?

Hello! I developed p2party.com which creates WebRTC rooms and does file transfers in the browser. You can find the relevant source code at github.com/p2party/p2party-js

Hi, this has been hard to use. I don't understand the UI. I opened two tabs in same browser, also in different browsers using same url. I couldn't see a connection between two peers. Kept saying waiting for peers.

It needs two browsers to create a connection because I store some user identifiable info in localstorage and if you use two tabs in the same browser it will be like trying to create p2p session with one peer.
If however you were not able to connect with two browsers then it would be very helpful if you can send me a screenshot of your console in the browser dev tools in a PM if you like.

The streaming part cannot happen in p2party's case because of the crypto algorithm that I use which splits the file into chunks. The chunks are also sent in random order so it cannot create a stream.

Visit https://fileveda.com
to securely send and receive files simultaneously.

I also tried testing some of the browser ones. Web Wormhole and very few others were the only ones which start downloading the file immediately (to the file system, your browser will show a file being downloaded) and I think these shouldn't crash on very large files (multi GBs). Most other tools download the file in browser (memory? cache?), and only when the download is complete, it's saved as a file.

Zetashare doesn't crash with large files; it writes directly to the file system and supports multiple simultaneous downloads. Unlike other P2P platforms, it never exposes your file names or sizes to the server — zero metadata.

I also tried testing some of the browser ones. Web Wormhole and very few others were the only ones which start downloading the file immediately (to the file system, your browser will show a file being downloaded) and I think these shouldn't crash on very large files (multi GBs). Most other tools download the file in browser (memory? cache?), and only when the download is complete, it's saved as a file.

Zetashare doesn't crash with large files; it writes directly to the file system and supports multiple simultaneous downloads. Unlike other P2P platforms, it never exposes your file names or sizes to the server — zero metadata.

Dropsilk has an OPFS option in the settings? (see image) Seems like quite a few CAN download directly to the system. I remember FilePizza being one of them too.

Using OPFS probably means that a copy of all file data is stored in the browser storage. If the file is large, the user may not have enough storage space for an extra copy. Therefore, it would be preferable if the data could be directly streamed to the final destination, without storing it in OPFS first.

Hi, thanks for creating this awesome list! I’d like to suggest adding tool:

Zapfile
– Send large files instantly to anyone, without size limits.

It fits well with the other file transfer / dev tools listed here.

croc is not P2P - it performs transfer entirely over a relay. It is possible to self-host the relay, though.