copyparty vs miniserve
| Tagline | Portable all-in-one file server with resumable uploads, WebDAV, FTP, and media indexing | Single-binary CLI tool to serve files and directories over HTTP |
| Category | File Storage & Sync | File Storage & Sync |
| Replaces | Dropbox, Google Drive | Dropbox, Google Drive |
| GitHub stars | 45k | 7.7k |
| Language | Python | Rust |
| License | MIT | MIT |
| Self-host difficulty | 2/5 Easy | 2/5 Easy |
| Deploy options | Docker Manual | Docker Manual |
| Managed hosting | ||
| Last updated | 2 days ago | 17 days ago |
| View repo | View repo |
Where each falls short
The honest trade-offs — what you give up with each, versus the proprietary tools they replace.
copyparty
- No selective sync desktop client; files must be managed via web UI, CLI, or WebDAV
- User management and access control are basic compared to Dropbox Teams or Google Drive Shared Drives
- No online document editing (Docs/Sheets equivalent)
- Mobile apps are absent; mobile access is browser or WebDAV only
miniserve
- No user accounts or per-user permissions; authentication is a single shared password
- No persistent file management, versioning, or trash/restore
- Not designed for multi-user concurrent collaboration
- No sync client; purely a temporary HTTP-based share mechanism
Bottom line
Both are a similar lift to self-host; choose copyparty for the larger community and ecosystem. copyparty has seen more recent development. Open each guide below for deploy steps and the full feature gap.
copyparty
Portable all-in-one file server with resumable uploads, WebDAV, FTP, and media indexing