FilePizza vs LocalSend
Editor take
Choose FilePizza to send from a browser with nothing installed, even between networks. Choose LocalSend for native apps and transfers that stay on the LAN.
Where they differ
Only what is true of one of them and not the other. Each app's weak spots are the other app's strengths.
FilePizza
Where FilePizza is stronger
- Across networksWebRTC with a TURN fallback, once coturn is switched on, connects browsers on different networks; LocalSend is built for the same LAN.1
- One zip, optional passwordSeveral files arrive as one zip and the upload can take a password; LocalSend sends the selected files as they are and uses a PIN, not a password.2
FilePizza vs LocalSend: specs side by side
Every spec for both apps in one table, so you can check install options, hardware and client apps before you pick one.
| Spec | ||
|---|---|---|
| Price | Free | Free |
| Licence | BSD-3-Clause | Apache-2.0 |
| Web UI | Yes | Yes |
| iOS | – | Yes |
| Android | – | Yes |
| Windows | – | Yes |
| macOS | – | Yes |
| Linux | – | Yes |
| Docker | Yes | – |
| Linux package | – | Yes |
| Windows | – | Yes |
| macOS | – | Yes |
| Tech stack | Node.js | Flutter |
| Docker Containers | 3 (app + Redis, coturn) | None – runs locally |
| Database | Redis | none |
| Architecture | Worth checking: x86 only | Advantage: x86 + ARM |
Common questions
Does either upload my files to a server?
No. FilePizza uses its server only to introduce the browsers, and the file travels over WebRTC; LocalSend sends directly between devices on the local network.
Do I need an app for FilePizza?
No. Both people open file.pizza in a browser. LocalSend has native apps for iOS, Android, macOS, Windows and Linux, plus a web client.
Which works when the devices are on different networks?
FilePizza, through WebRTC once its TURN server is switched on, when a direct connection fails. LocalSend is built for devices on the same local network.
Sources: FilePizza docs and LocalSend docs.