copyparty vs transfer.sh
| Tagline | Portable all-in-one file server with resumable uploads, WebDAV, FTP, and media indexing | Simple command-line file sharing with URL-based access and optional encryption |
| Category | File Storage & Sync | File Storage & Sync |
| Replaces | Dropbox, Google Drive | Dropbox, Google Drive |
| GitHub stars | 45k | 16k |
| Language | Python | Go |
| 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 | 5 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
transfer.sh
- No web UI for browsing or managing stored files; purely CLI/API-driven
- No user accounts, access control, or per-user storage quotas
- Files are temporary by design; not suitable for persistent storage or file organization
- No sync client, versioning, or folder hierarchy support
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
transfer.sh
Simple command-line file sharing with URL-based access and optional encryption