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.

Editor

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

LocalSend

Where LocalSend is stronger

  • Native appsClients for iOS, Android, macOS, Windows and Linux, plus a web client; FilePizza has no mobile or desktop app.3
  • Stays on the LANDevices talk directly with no relay or outside server; FilePizza uses a signalling server and may need TURN.4

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
PriceFreeFree
LicenceBSD-3-ClauseApache-2.0
Web UIYesYes
iOS–Yes
Android–Yes
Windows–Yes
macOS–Yes
Linux–Yes
DockerYes–
Linux package–Yes
Windows–Yes
macOS–Yes
Tech stackNode.jsFlutter
Docker Containers3 (app + Redis, coturn)None – runs locally
DatabaseRedisnone
ArchitectureWorth checking: x86 onlyAdvantage: x86 + ARM

Common questions

Sources: FilePizza docs and LocalSend docs.

Updated