# StrongFolder vs FilePizza Source: https://help.strongfolder.com/en/compare/strongfolder-vs-filepizza/ Updated: 2026-11-05 > StrongFolder vs FilePizza: both send files directly between browsers over WebRTC, with no upload and the sender's tab kept open. FilePizza is open source (BSD 3-Clause), self-hostable, with optional passwords; several files arrive as one ZIP. StrongFolder sends whole folders with their structure and no ZIP, and adds a Chrome extension and QR codes. FilePizza and StrongFolder solve the same problem the same way: they connect two browsers and send files directly, with no upload to a cloud and no copy left behind. The differences are in what you can send, how you host it and what surrounds the transfer. This StrongFolder vs FilePizza comparison covers them honestly — including when FilePizza is the better fit. **Key facts** - **Same core:** both are browser-to-browser WebRTC transfers; no upload first; the sender's tab must stay open. - **FilePizza** (as of 2026-11-05): open source under BSD 3-Clause, self-hostable with Docker, optional password, several files arrive as one ZIP. - **StrongFolder:** sends whole folders with subfolders and file names kept, no ZIP; Chrome extension; QR code for every link. - **Size:** FilePizza says "as big as your browser can handle"; StrongFolder sets no size limit of its own. - **Choose FilePizza** to self-host or audit the code; **choose StrongFolder** for folders and one-click sharing from Chrome. ## How do StrongFolder and FilePizza compare? FilePizza facts as of 2026-11-05, from its own README on GitHub (source at the end). "Not stated" means the README doesn't say. | | StrongFolder | FilePizza | |---|---|---| | How it works | WebRTC, browser to browser | WebRTC, browser to browser | | Upload before sharing | None | None | | Size limit | None set by the service | "As big as your browser can handle" | | Sender keeps the tab open | Yes | Yes | | Several files | Sent as they are | Downloaded as one ZIP | | Whole folders with structure | Yes, no ZIP | Not stated | | Several downloaders from one link | Yes | Yes | | QR code | Yes | Not stated | | Browser extension | Chrome extension | Not stated | | Relay when direct connection fails | Encrypted TURN relay, no storage | TURN support optional when self-hosting | | Setup | Nothing to deploy — open the web app or the extension | Use file.pizza, or self-host (BSD 3-Clause, Docker) | | Account | Not needed (Google sign-in optional) | Not stated | | Price | Free | Free | ## How are StrongFolder and FilePizza the same? Both are true peer-to-peer tools. When the recipient opens the link, their browser connects to the sender's, and the file bytes travel over a WebRTC data channel encrypted with DTLS. Nothing is uploaded first, so the download starts right away, and the file isn't stored on a server. Both also share the honest trade-off of P2P: the files come from the sender's device. FilePizza's README says the uploader must leave the browser window open until the transfer is complete; for StrongFolder, The sender's browser tab must stay open and online until the recipient finishes downloading — files come from the sender's device, not from a server. See [why the sender stays online](https://help.strongfolder.com/en/guides/why-sender-stays-online/). ## What is the main difference between StrongFolder and FilePizza? **Folders and packaging.** FilePizza's README says multiple files are delivered to downloaders as a ZIP. That's convenient for a handful of files, but for a large project folder the recipient has to extract an archive afterwards and needs disk space for both. StrongFolder sends folders as folders. The recipient chooses a destination, and StrongFolder writes the same subfolders and file names there, file by file — no archive at any point. Saving a whole folder with its structure uses the File System Access API: Chrome, Edge, Opera and other Chromium browsers on a computer. Other browsers can download the files one by one or as a ZIP. Long Windows paths are shortened, and a note lists any renamed files. More in [how to send a folder without zipping](https://help.strongfolder.com/en/guides/send-folder-without-zipping/). [Send files now](https://strongfolder.com) ## Which one can I host myself? FilePizza. Its code is on GitHub under the BSD 3-Clause license, and the README covers running it with Docker, keeping server state in Redis and pointing it at your own TURN server. If your organization wants the transfer tool on its own infrastructure, or wants to audit every line, FilePizza is the natural choice. StrongFolder works out of the box: you open the web app at strongfolder.com or the Chrome extension, and there is nothing to deploy or maintain. Teams whose rules require running the transfer tool on their own servers will find FilePizza the better fit. ## What happens when a direct connection isn't possible? Some networks — strict corporate firewalls, some mobile carriers — block direct peer-to-peer connections. If a direct connection is impossible (strict corporate firewall, some mobile networks), the encrypted stream passes through a StrongFolder relay (TURN) server. The relay forwards the data and does not store it. StrongFolder runs this relay for you. FilePizza's README describes optional TURN support for peers behind NAT when you host it, and a fallback STUN server when that is off. On a self-hosted instance, whether a relay is available depends on how it's configured. ## Which is easier for everyday sharing? StrongFolder adds a few things around the transfer: - a **Chrome extension** that shares files from the browser toolbar in one click — see [the Chrome extension](https://help.strongfolder.com/en/chrome-extension/); - a **QR code** for every link, handy for sending from a computer to a phone; - **several recipients** from one link, each downloading directly from you; - optional **Google sign-in** that keeps a list of your transfers. FilePizza focuses on the transfer itself and adds an **optional password** for uploads and a way to **report** abuse. Its README says it works on most mobile browsers, including Mobile Safari. ## When is FilePizza the better choice? Choose FilePizza when: - **you want open source** you can read, audit or modify; - **you need to self-host** the tool on your own servers or in a closed network; - **you want a password** on an upload as an extra layer; - **you're sending a few files** and a single ZIP download suits the recipient. ## When is StrongFolder the better choice? Choose StrongFolder when: - **you're sending a folder** — a video project, a photo shoot, a codebase — and it should arrive with its structure, without a ZIP; - **you want one-click sharing** from Chrome via the extension; - **you send from a computer to a phone** and a QR code saves typing; - **you don't want to run anything** — the relay for difficult networks is already there. ## How do I send with StrongFolder? 1. Open [strongfolder.com](https://strongfolder.com) or click the StrongFolder Chrome extension. 2. Choose files or a whole folder. Nothing is uploaded — the browser only reads the files so it can share them. 3. Copy the link or show the QR code and send it by chat or e-mail. 4. Keep the tab open while recipients download, and click **Stop Sharing** when they're done. The recipient needs only the link and a modern browser, with no account and no app. To save a folder with its structure, Chrome, Edge or Opera on a computer works best. See [how it works](https://help.strongfolder.com/en/how-it-works/). ## Summary FilePizza and StrongFolder are close relatives: both stream files directly between browsers over encrypted WebRTC, with no upload and no stored copy, and both need the sender's tab to stay open. FilePizza is the open-source, self-hostable option with optional passwords and ZIP delivery for multiple files. StrongFolder is the hosted option built around folders — kept as folders — plus a Chrome extension and QR codes. Compare more tools in [best P2P file transfer tools](https://help.strongfolder.com/en/compare/best-p2p-file-transfer-tools/). ## Sources Checked on 2026-11-05: [FilePizza README and FAQ on GitHub](https://github.com/kern/filepizza) · [file.pizza](https://file.pizza/) ## FAQ ### Are StrongFolder and FilePizza both peer-to-peer? Yes. Both stream files directly from the sender's browser to the recipient's over WebRTC, which encrypts the data channel with DTLS. Neither uploads the file first, and in both the sender must keep the browser tab open until the transfer is complete. ### Is FilePizza open source? Yes. FilePizza's code is published on GitHub under the BSD 3-Clause license, and its README explains how to run it yourself with Docker (as of 2026-11-05). StrongFolder is a free hosted web app and Chrome extension. ### Can FilePizza send a folder? FilePizza's README says multiple files are delivered to downloaders as one ZIP file and doesn't describe folder uploads. StrongFolder sends a folder as a folder: subfolders and file names are kept and nothing is zipped. ### Can several people download from one link? Both support it. FilePizza's FAQ says several people can download at once from the same link. One link can be opened by several recipients; each downloads directly from the sender. ### Is there a file size limit in FilePizza or StrongFolder? FilePizza's README says files can be as big as your browser can handle. No size limit set by StrongFolder. The practical limits are free disk space on the recipient's device, connection speed, and how long both devices stay online.