AList

What is AList?

AList presents files from more than thirty storage services — local disk, object storage, and public cloud drives — behind one web interface you can browse, search and share from. It is commonly used to pull several scattered drives into a single self-hosted index, and it can expose the result over WebDAV so other apps treat it like a normal network drive. It runs as a single lightweight binary.

Best for

Pulling several cloud drives and storage backends into one browsable index

Why choose AList

AList exists to solve one unglamorous but genuinely useful problem: you have files scattered across a dozen cloud providers, and you want one interface to see and reach all of them. It connects to dozens of storage backends — cloud drives, object storage, WebDAV, local disks — and presents everything as a single browsable file tree with search, preview and share links. Because it can expose the whole thing over WebDAV, other applications can mount it as if it were a plain network drive.

Replaces

• Google Drive
• Dropbox
• Nextcloud

Key features

• Unified listing across 30+ storage drivers
• WebDAV output so other apps can mount it
• Search, preview and share links
• Single binary with a small footprint

What to watch out for

Two things to weigh honestly. First, AList is an aggregator, not a backup: if an upstream provider throttles or revokes access, files vanish from the view and you have no local copy to fall back on. Second, the project's governance has been unsettled, with community forks and licence discussions that have made some long-term users cautious — check the current state of the project before making it load-bearing. Speed is also bounded by the slowest backend, and previewing large files through a consumer cloud drive can be painfully slow.

How to deploy

• Docker
• Static binary
• Linux packages

Getting started

The single binary or the Docker image both work; the binary is genuinely small enough to run on a router or NAS. Point it at a data directory on real local storage for its metadata, because the database lives there. Add your storage backends one at a time and verify browsing before adding the next, since a misconfigured provider can make the whole interface feel broken. Put it behind a reverse proxy with authentication before exposing it to the internet — an open AList instance is a directory listing of everything you have ever stored.

Typical setup

Typical deployments run AList on a NAS or a home server that already has decent storage, and point it at a mix of cloud drives and a local disk so the local files become the reliable layer. Because it can output WebDAV, people often attach it to a media player, a document app or a file manager that otherwise could not reach those providers. A reverse proxy with authentication in front is standard, since an open AList is effectively a browsable index of everything you own.

Who should look elsewhere

Avoid it as your only copy of anything important. An aggregator that reads from cloud providers is a convenience layer, not a backup, and providers that throttle or revoke an integration will make files disappear from the interface while the 'backup' continues to look complete. It is also a poor fit if you want a finished consumer product rather than a file-listing utility you configure yourself.

Project health

• GitHub stars: 50,248
• Last code push: 2026-09-29
• Open issues: 564
• Status: actively developed

Figures pulled from the GitHub API and refreshed periodically.