What is this?
FilePizza is a free web app for peer-to-peer file transfers in your browser: pick a file, share a link, and the recipient downloads it straight from you — there's also a hosted instance at file.pizza.
FilePizza is a free web app for peer-to-peer file transfers in your browser: pick a file, share a link, and the recipient downloads it straight from you — there's also a hosted instance at file.pizza.How is it different from WeTransfer-style file sharing sites?There's no initial upload step: WebRTC streams the file directly from your browser to the downloader's, so data never sits on an intermediary server, which makes transfers fast, private, and secure.
There's no initial upload step: WebRTC streams the file directly from your browser to the downloader's, so data never sits on an intermediary server, which makes transfers fast, private, and secure.How do I send someone a file?Open file.pizza (or your own instance), choose one or more files, and share the short or long URL it generates. Whoever opens the link downloads the files directly; multiple files arrive bundled as a zip.
Open file.pizza (or your own instance), choose one or more files, and share the short or long URL it generates. Whoever opens the link downloads the files directly; multiple files arrive bundled as a zip.Can I just use it in the browser, including on my phone?Yes — nothing to install and no account: both sides need only a modern browser. The v2 UI works on most mobile browsers, including Mobile Safari.
Yes — nothing to install and no account: both sides need only a modern browser. The v2 UI works on most mobile browsers, including Mobile Safari.What's the catch — can I close the tab once I've shared the link?No: your browser window must stay open until the transfer completes, and closing it kills the URLs. Downloaders who already finished can keep seeding to incomplete ones, but no new downloads can start.
No: your browser window must stay open until the transfer completes, and closing it kills the URLs. Downloaders who already finished can keep seeding to incomplete ones, but no new downloads can start.Can I run my own FilePizza server?Yes — it's a Next.js/TypeScript app you can run with npm or Docker Compose (the compose setup includes Redis and a coturn TURN server). Redis is optional; without it, server state falls back to in-memory storage.
Yes — it's a Next.js/TypeScript app you can run with npm or Docker Compose (the compose setup includes Redis and a coturn TURN server). Redis is optional; without it, server state falls back to in-memory storage.Are my files encrypted in transit?Yes — all WebRTC traffic is automatically encrypted with public-key cryptography via DTLS, and you can add an optional password to an upload for extra protection.
Yes — all WebRTC traffic is automatically encrypted with public-key cryptography via DTLS, and you can add an optional password to an upload for extra protection.Can several people download my file at the same time?Yes — just send the same short or long URL to everyone who needs the file; there's no one-downloader limit.
Yes — just send the same short or long URL to everyone who needs the file; there's no one-downloader limit.Is there a limit on file size?FilePizza sets none: files can be as big as your browser can handle, and uploading several files at once works too — downloaders receive them as a single zip.
FilePizza sets none: files can be as big as your browser can handle, and uploading several files at once works too — downloaders receive them as a single zip.Why might two peers fail to connect — what is TURN for?WebRTC can't always punch through strict NATs. Self-hosters can set COTURN_ENABLED=true to relay traffic through a TURN server; by default FilePizza uses Google's public STUN server.
WebRTC can't always punch through strict NATs. Self-hosters can set COTURN_ENABLED=true to relay traffic through a TURN server; by default FilePizza uses Google's public STUN server.What is FilePizza built on?The v2 stack is Next.js, React, TypeScript, and Tailwind, with PeerJS handling WebRTC, optional Redis for server state, and downloads streamed through a Service Worker.
The v2 stack is Next.js, React, TypeScript, and Tailwind, with PeerJS handling WebRTC, optional Redis for server state, and downloads streamed through a Service Worker.What are similar projects?documenso, Resume-Matcher, typebot.io, waoowaoo, snapdrop, solana-meme-tool, OpenStock, gitdiagram
documenso, Resume-Matcher, typebot.io, waoowaoo, snapdrop, solana-meme-tool, OpenStock, gitdiagramWhich topics is it in?file-sharing, webrtc, p2p, tailwindcss, app, redis, nextjs, docker-compose, web-app, react, server, nodejs
file-sharing, webrtc, p2p, tailwindcss, app, redis, nextjs, docker-compose, web-app, react, server, nodejs