alist vs callfs
File browsing and sharing compared with distributed file storage
alist provides a web interface and WebDAV access for browsing and sharing files across many storage types. callfs exposes local disks and S3-compatible storage through a REST API, with features for routing file operations across nodes. Their main difference is alist’s user-facing file access versus callfs’s API and distributed-storage focus.

alist: Browse and Share Files Across Multiple Storages
AList is a self-hostable file-listing and WebDAV server that connects local storage and many cloud and network drives through one web interface. It suits people who want to browse, preview, and share files across storage providers.

callfs: Serve a Distributed Filesystem over REST
CallFS is a Go-based file storage server that exposes local disks and S3-compatible storage through a REST API. It routes file operations across nodes and offers optional erasure coding, metadata coordination, and owner-based access control.
| alist | callfs | |
|---|---|---|
| Language | Go | Go |
| License | AGPL-3.0 | MIT |
| Stars | 50.3k | 403 |
| Forks | 7.9k | 13 |
| Last analyzed | Oct 3, 2026 | Oct 23, 2026 |
Key differences
- alist connects many storage types, including cloud drives, S3, FTP/SFTP, SMB, and WebDAV; callfs supports local disks and S3-compatible storage.
- alist offers browser previews, shareable links, protected routes, and WebDAV; callfs centers on REST endpoints, peer routing, and optional erasure coding.
- Both use Go, but alist also has a SolidJS interface, while callfs is presented as a REST-based storage server.
- alist uses the AGPL-3.0 license; callfs uses the MIT license.
- The supplied project data lists alist at 50.3k stars and 7.9k forks, compared with callfs at 403 stars and 13 forks.
- callfs requires a configured metadata store and documents cluster setup; alist setup requirements can vary by storage provider.
Choose alist if you…
- want to browse and preview files from multiple storage providers in one web interface.
- need WebDAV access, browser sharing, or protected file routes.
- want file operations such as upload, rename, move, and copy through a file-listing interface.
Choose callfs if you…
- need a REST API for file operations on local disks or S3-compatible storage.
- want to route file requests across nodes or configure erasure coding.
- need API-key authentication, owner-based permissions, or single-use download links.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.