AList

Self-hosted file management, honestly reviewed. No marketing fluff, just what you actually get when you run it on your own server.

TL;DR

• What it is: A self-hosted file list program and WebDAV server that connects to 35+ cloud storage providers — Google Drive, OneDrive, Dropbox, S3, and many others — and serves them through a single web UI [4].
• Who it’s for: Self-hosters who juggle multiple cloud accounts and want one place to browse, share, and access everything via WebDAV. Also useful for anyone trying to expose cloud storage as a network drive [3][4].
• Cost savings: If you’re currently paying for Dropbox Plus ($11.99/mo) or Google One ($9.99/mo for 2TB) to get enough space, AList lets you aggregate free tiers across multiple providers — 15GB from Google Drive, 5GB from OneDrive, 2GB from Dropbox — into one interface for the cost of a $5 VPS.
• Key strength: 35+ supported storage backends, WebDAV layer over all of them, extremely lightweight single-binary deployment, file preview for almost every format, and 49,175 GitHub stars that make it one of the most-starred self-hosted projects in existence [4].
• Key weakness: AGPL-3.0 license (not MIT — commercial embedding requires attention), not a storage backend itself (you still need actual storage elsewhere), and a noticeable skew toward Chinese cloud services in the supported providers list that may not be relevant for US/EU users.

---

What is AList

AList is not a file storage system. This is the most important thing to understand before you deploy it.

What AList does is act as a gateway: you tell it where your files live (Google Drive, OneDrive, an S3 bucket, a local directory, an FTP server, a Raspberry Pi’s SMB share), and it presents all of them through one clean web UI with consistent file operations and a WebDAV endpoint on top [4]. It’s the difference between a file manager and a NAS — AList is the former.

The project is written in Go (Gin framework) with a SolidJS frontend, which is why it’s so lightweight. The default install is a single binary backed by SQLite. No Postgres required, no Redis required, no elaborate compose stack. You can run it on a Raspberry Pi or a $4/mo VPS without breaking a sweat [README].

With 49,175 GitHub stars, AList sits in the top tier of self-hosted projects by community size — well above most tools that get called “popular” [4]. That star count matters because it signals something real: the tool has been tested by a very large number of people in very different configurations.

The AGPL-3.0 license means the source is open and you can self-host freely. But if you plan to embed AList in a commercial product or SaaS, AGPL requires you to open-source your entire application stack. This is more restrictive than MIT, and it’s the kind of thing that matters to founders building products on top of infrastructure tools [README].

---

Why people choose it

The use case that drives most AList adoption isn’t “I want a Dropbox replacement.” It’s more specific: people who already use multiple cloud services and are tired of switching between them.

LinuxLinks placed AList in its roundup of the best web-based Linux file managers, specifically calling it a “file list program that supports multiple storages” — the key differentiator versus tools like Tiny File Manager or Filebrowser, which manage local files only [3][4].

The WebDAV layer is what elevates AList from a browser to an infrastructure tool. WebDAV is a protocol that operating systems understand natively — macOS Finder, Windows Explorer, and Linux file managers can all mount a WebDAV share as a network drive. AList exposes all your connected storages over WebDAV, which means you can mount Google Drive, an S3 bucket, and a local folder simultaneously as a single network drive [README][4]. That’s not something Google Drive’s official desktop client does.

The offline download feature is notable. You can hand AList a torrent link or direct URL, and it downloads the content directly to your configured storage backend — not to your local machine, not through your home internet connection. This is useful if your VPS has a faster pipe than your home ISP [README].

The Crypt feature is underrated: AList can encrypt and decrypt files before passing them to any supported storage backend [website]. Your files land on Google Drive or S3 in encrypted form; AList holds the key locally. The provider sees ciphertext.

---

Features

Based on the README and official documentation:

Storage backends (35+ supported) [README][4]:

• Local storage, FTP, SFTP, SMB
• Major Western services: Google Drive, OneDrive/SharePoint (global, CN, DE, US), Dropbox, S3-compatible, ProtonDrive, Mega.nz, Seafile, Azure Blob Storage, YandexDisk
• Chinese cloud services: Aliyundrive, BaiduNetdisk, 123pan, PikPak, Quark, Thunder, Lanzou, 115, UC, Baidu photo, Google photo
• Others: MediaFire, Terabox, UPYUN, Teambition, Cloudreve, dogecloud

File operations:

• Web upload (can be enabled for visitors), delete, mkdir, rename, move, copy [README]
• Copy files directly between two storage backends (server-side) [README]
• File and folder package download [README]
• Offline download (torrent and direct URL) [README]
• Multi-thread download acceleration for single-thread streams [README]
• Permanent file link generation [README]

Previews:

• PDF, markdown, code, plain text [README][4]
• Image gallery mode [README]
• Video and audio with lyrics and subtitle support [README][4]
• Office documents: docx, pptx, xlsx [README][4]
• README.md rendering inside folders [README]

Access and sharing:

• WebDAV endpoint for all connected storages [README][4]
• Protected routes with password authentication [README][4]
• Single sign-on (SSO) [website]
• Cloudflare Workers proxy (useful if your VPS IP is blocked or slow from certain regions) [README]
• Crypt storage driver for client-side encryption [website]

Deployment:

• Single binary (Linux, macOS, Windows, ARM) [README]
• Docker and Docker Compose [README][4]
• SQLite default, external DB optional [README]
• Dark mode, I18n [README]

What it doesn’t have: built-in user sharing with permissions (like Nextcloud’s share links with expiry), photo album management, collaborative editing, or a native mobile app. It’s a file list + WebDAV server, and it stays in that lane.

---

Pricing: SaaS vs self-hosted math

AList itself is free software under AGPL-3.0. There’s no SaaS version of AList and no paid tier [README].

The cost calculation is about what you were paying for the underlying storage before AList, and whether you can replace that with free tiers or cheaper alternatives.

Typical cloud storage pricing before AList:

• Google Drive: 15GB free, 100GB $2.99/mo, 2TB $9.99/mo
• Dropbox: 2GB free, Plus $11.99/mo (2TB), Professional $19.99/mo
• OneDrive: 5GB free, 100GB $1.99/mo, Microsoft 365 Personal $6.99/mo

AList approach:

• Connect Google Drive (15GB free) + OneDrive (5GB free) + Dropbox (2GB free) + a local directory on your VPS = 22GB across free tiers, managed from one UI
• Add an S3-compatible backend (Backblaze B2 charges $6/TB/mo, far below AWS S3) for bulk storage
• Self-hosted AList runs on a $5/mo VPS without complaint

Concrete example: A founder paying $9.99/mo for Google One 2TB because their files are scattered and hard to manage could replace that with AList on a $5 VPS connecting their existing free-tier accounts plus a $3/mo Backblaze B2 bucket. Total: $8/mo versus $9.99/mo — marginal savings, but with full control, WebDAV access, and no vendor lock-in. The bigger win is when you’re paying for multiple storage subscriptions across services and you consolidate.

Note: AList doesn’t eliminate your need for storage — it just makes existing storage more useful. If you have zero cloud storage accounts, you still need somewhere for your files to live.

---

Deployment reality check

This is where AList earns its stars. The deployment story is one of the simplest in self-hosted software.

Minimal install:

1. Download the single Go binary for your platform
2. Run ./alist server — it starts on port 5244 with SQLite in the local directory
3. Open the web UI, set admin password, add storage providers
4. Done

Docker path:

docker run -d --restart=unless-stopped \
  -v /your/path:/opt/alist/data \
  -p 5244:5244 \
  xhofe/alist:latest

That’s it. No Postgres, no Redis, no compose file with 8 services [README].

What you actually need for a production setup:

• A Linux VPS (512MB RAM is sufficient for light use; 1GB is comfortable)
• A reverse proxy (Caddy or nginx) for HTTPS — strictly optional but recommended
• OAuth credentials for cloud providers like Google Drive (standard OAuth2 app setup)
• Cloudflare tunnel or VPN if you don’t want to expose a port publicly

What can go sideways:

OAuth authentication for each cloud provider is configured separately, and some providers — Google Drive in particular — require going through their developer console to create OAuth credentials. This is a 15-minute process, not a crisis, but it’s not zero friction.

The Chinese cloud services (Aliyundrive, Quark, BaiduNetdisk, etc.) authenticate via QR code or SMS to a Chinese phone number. If those aren’t services you use, ignore them — but be aware the README’s feature list includes a lot of them, which can give a misleading picture of how relevant the tool is to a Western audience [README][4].

Offline download requires the AList server to have outbound internet access to the download source. If you’re behind a strict firewall, this won’t work.

There’s no built-in HTTPS — you need a reverse proxy or Cloudflare tunnel. Not unusual for self-hosted Go services, but worth knowing.

Realistic time for a technical user: 20–30 minutes to a working instance including at least two cloud providers connected. For a non-technical founder following a guide: 1–2 hours including domain setup and OAuth configuration for Google Drive. Far simpler than Nextcloud.

---

Pros and cons

Pros

• 35+ storage backends. No other self-hosted tool matches this breadth. If a cloud storage service exists, there’s a reasonable chance AList already supports it [README][4].
• WebDAV over everything. Mount any connected storage as a network drive in macOS Finder, Windows Explorer, or any WebDAV client. This is a genuinely useful capability that most individual cloud apps don’t offer [README].
• Extremely lightweight. Single Go binary, SQLite default, 512MB RAM comfortable. Runs on hardware that would choke Nextcloud [README].
• File preview for almost anything. Video, audio, office documents, PDF, code, images — all in-browser without downloading [README][4].
• Offline download. Server pulls torrents and direct URLs directly to your configured storage [README].
• Client-side encryption (Crypt). Files encrypted before leaving your server, decrypted only by AList. The storage provider sees ciphertext [website].
• 49,175 GitHub stars. Large community, active development, many storage drivers maintained by contributors [4].
• Server-to-server file copy. Copy files between two cloud backends without downloading to your machine [README].

Cons

• AGPL-3.0, not MIT. Commercial embedding requires open-sourcing your application. Fine for personal use and internal tools; significant constraint for product builders [README].
• Not a storage backend. AList doesn’t store your files — you still need actual storage. It’s a portal, not a NAS [README][4].
• Heavy Chinese cloud focus. Roughly half the supported providers are Chinese services most Western users don’t have accounts with. The breadth is real but the relevance to US/EU founders is narrower than the list suggests [README].
• OAuth setup friction per provider. Each cloud provider requires separate OAuth credentials. One-time effort, but it’s not zero [README].
• No native user permissions model. You can password-protect paths, but there’s no per-user quota, per-user storage allocation, or granular sharing. Not a replacement for Nextcloud if you need multi-user file management [website].
• No built-in HTTPS. Requires a reverse proxy or Cloudflare tunnel to serve over HTTPS in production [README].
• No mobile app. Web UI is mobile-responsive, and WebDAV works with mobile apps like nPlayer or Infuse — but there’s no dedicated iOS/Android app [README].
• Limited third-party reviews in English. The self-hosted community covers AList extensively in Chinese-language forums; English-language in-depth reviews are sparse [3][4].

---

Who should use this / who shouldn’t

Use AList if:

• You have files scattered across multiple cloud providers (Google Drive, OneDrive, Dropbox, S3) and want one interface and one WebDAV endpoint to access all of them.
• You want to mount cloud storage as a network drive on macOS or Windows without paying for desktop sync clients.
• You’re paying for cloud storage subscriptions and want to consolidate to fewer paid tiers by aggregating free tiers from multiple providers.
• You want server-side offline downloads from torrents or direct URLs into your cloud storage.
• You need client-side encryption before uploading to a cloud provider you don’t fully trust.

Skip it (use Nextcloud instead) if:

• You need multi-user file management with per-user quotas, sharing links with expiry, and calendars/contacts/notes integrated.
• You want to be the storage backend — not just the gateway to other backends.
• Your team needs collaborative document editing (Nextcloud + OnlyOffice or Collabora).

Skip it (use Filebrowser instead) if:

• You only manage local files on one server and don’t need cloud storage integration — Filebrowser is simpler for that case.

Skip it (use rclone instead) if:

• You’re a command-line user who wants to sync or mount cloud storage programmatically rather than through a web UI. AList and rclone solve overlapping problems; rclone is more powerful for automated workflows.

---

Alternatives worth considering

• Nextcloud — the obvious alternative for multi-user file sharing with apps, calendars, and contacts. Far heavier to deploy and maintain, but it’s an actual storage platform, not just a gateway.
• Filebrowser — simpler, local-files-only web file manager. No cloud storage integration, but less setup friction for straightforward use cases [3].
• rclone — command-line tool that supports the same cloud providers. No web UI; better for automation, sync, and mounting via FUSE.
• Seafile — self-hosted file sync and share with a client app. More comparable to Dropbox (sync model) than AList (gateway model).
• Immich — if your primary use case is photos, Immich is purpose-built for it. AList’s gallery mode is competent but not a photo management system.

---

Bottom line

AList is the most capable cloud-storage aggregation layer in the self-hosted space, and the 49,175 GitHub stars reflect that real people have found it useful in large numbers. The core value proposition is clear: if you have files in multiple places and want one web UI and one WebDAV endpoint to rule them all, nothing else comes close on breadth of provider support. The deployment story is genuinely the simplest in its category — a single binary, SQLite, and 30 minutes is all it takes.

The honest limitations are equally clear: it’s a gateway, not storage, so you still need somewhere for your files to actually live; the AGPL license matters if you’re building a product on top of it; and the feature list’s breadth is partially an artifact of Chinese cloud market support that most Western users won’t touch. If you need multi-user file management, Nextcloud is the answer. If you need to aggregate existing cloud accounts into a single interface and access them via WebDAV, AList is the answer.

---

Sources

1. LinuxLinks — “15 Best Free and Open Source Web-Based Linux File Managers” (roundup including AList). https://www.linuxlinks.com/best-free-open-source-web-based-linux-file-managers/
2. LinuxLinks — “AList - file list program that supports multiple storages” (dedicated entry). https://www.linuxlinks.com/alist-file-list-program-multiple-storages/

Primary sources:

• GitHub repository and README: https://github.com/AlistGo/alist (49,175 stars, AGPL-3.0)
• Official website and documentation: https://alistgo.com
• Docker Hub: https://hub.docker.com/r/xhofe/alist