kern/filepizza

:pizza: Peer-to-peer file transfers in your browser

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 40 minutes ago
Added to GitGenius on September 6th, 2026
Created on February 25th, 2015
Open Issues & Pull Requests: 49 (+0)
GitHub issues: Enabled
Number of forks: 610
Total Stargazers: 10,160 (+0)
Total Subscribers: 73 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 20.0 days
Mean response time: 261.7 days
90th percentile: 856.4 days
Tracked items: 128

How this project is maintained

100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 93% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 27
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 463 days
Stale 30+ days: 26
Stale 90+ days: 25

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • filepizza-v1-legacy (100)
  • enhancement (4)
  • help wanted (4)
  • bug (2)
  • question (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

FilePizza is a peer-to-peer file transfer tool that operates entirely within the browser using WebRTC technology.

The tool solves the inefficiency and privacy concerns of traditional web-based file sharing services by eliminating the need for files to pass through intermediary servers. Instead of uploading to a central server and then having recipients download from it, FilePizza establishes direct browser-to-browser connections using WebRTC. Files are encrypted in transit through DTLS public-key cryptography, and users can optionally add password protection. The uploader's browser must remain open during the transfer, but once a download completes, that downloader can seed to other incomplete recipients, allowing multiple simultaneous downloads from a single upload.

The tool suits scenarios where privacy and speed matter more than persistent availability. It works well for one-time file sharing between individuals or small groups, particularly when the uploader can keep their browser window open. The project is not designed for scenarios requiring permanent file hosting or downloads that must continue after the uploader disconnects. A hosted instance is available for immediate use without self-hosting, though the tool can be self-hosted with optional Redis for out-of-process state storage and TURN server support for users behind restrictive network configurations.

Development activity shows consistent refinement of core functionality. The project maintains a modern technology stack centered on Next.js, React, and TypeScript, with recent work focused on improving the user interface with dark mode support and expanding mobile browser compatibility. The codebase includes configuration options for customizing STUN and TURN server behavior, Redis integration, and PeerJS server endpoints, indicating attention to deployment flexibility. The tool supports practical features like multiple file uploads delivered as zip archives, transfer progress monitoring with cancellation capability, and streaming downloads via Service Workers.