AList vs transfer.sh
| Tagline | File list program supporting multiple storages, with WebDAV and web UI | Simple command-line file sharing with URL-based access and optional encryption |
| Category | File Storage & Sync | File Storage & Sync |
| Replaces | Google Drive, Dropbox | Dropbox, Google Drive |
| GitHub stars | 50k | 16k |
| Language | Go | Go |
| License | AGPL-3.0 | MIT |
| Self-host difficulty | 2/5 Easy | 2/5 Easy |
| Deploy options | Docker Manual | Docker Manual |
| Managed hosting | ||
| Last updated | 13 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.
AList
- Primarily a read/list and aggregation layer; not a true two-way sync engine like Dropbox
- No native desktop/mobile sync clients (relies on WebDAV)
- Limited collaboration, versioning, and team permission features
- Documentation is partly Chinese-first and can lag for some backends
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 AList for the larger community and ecosystem. transfer.sh has seen more recent development. Open each guide below for deploy steps and the full feature gap.
transfer.sh
Simple command-line file sharing with URL-based access and optional encryption