Seafile

Last reviewed Aug 26, 2026 · 847 words

Seafile syncs a 200,000-file library faster and on less CPU than Nextcloud does, and the reason is also its biggest trap: it does not store your files as files. Data lands on the server as content-addressed blocks inside library directories, which is why the sync engine, written in C, handles huge trees and partial updates so well, and why you cannot open the data directory in a shell and find your photos. Once you accept that, Seafile is one of the most stable pieces of self-hosted software I run, with about 15,200 GitHub stars and a history back to 2012.

Your files are blocks, and that changes how you operate it

Everything sits under the Seafile data directory as commits, file system objects and blocks, roughly the way Git stores a repository. Consequences follow. You cannot drop files into a folder on the server and have them appear in a library; use a client, the web UI or the API. You cannot restore a single file by copying it from a backup; you restore the database and the data directory together, consistently, then let Seafile serve it. seaf-fsck.sh exists to repair libraries and seaf-fuse.sh will mount libraries as a plain filesystem read-only, which is the escape hatch for pulling data out with rsync or feeding it to a backup tool like restic. If the idea of opaque storage bothers you, Syncthing keeps plain files and my Nextcloud versus Syncthing piece explains when that is the right trade.

The stack is three containers and one hostname you must get right

The official Docker Compose deployment runs Seafile, MariaDB and memcached, with Seafile's own nginx listening on port 80 inside the container. Download the current compose file from the manual rather than copying an old blog post, because the layout changed in recent releases and environment variables moved into a .env file. The value that matters most is the server hostname: it is baked into share links, the sync clients' server address and the mobile app configuration. Set it to the final public name before the first start, put a reverse proxy with TLS in front, and do not change it casually later. Memory is modest: the catalogue floor is 512 MB, and a two-user instance with MariaDB idles comfortably under 1 GB in my experience.

Encrypted libraries are real end-to-end encryption, and unforgiving

A library created with a password is encrypted on the client. The server never sees the password or the plaintext, which is a stronger guarantee than Nextcloud's server-side encryption module. The bill comes with it. Forget the password and the library is gone, with no admin reset. Several server-side conveniences stop working for encrypted libraries, since the server cannot read the contents: full-text search and file previews among them. My rule is one encrypted library for the genuinely sensitive material, everything else in plain libraries, and the password in the household password manager.

Deleted data stays until you run garbage collection

Seafile keeps history per library, 30 days by default, and even after history expires the underlying blocks are not freed until you run seaf-gc.sh. New operators watch disk usage climb after deleting 50 GB and assume a bug. Schedule GC monthly. Read the GC section of the manual for your exact version before you do, because whether it can run while the server is up has changed over the years, and on the versions that require a stop you want that in a maintenance window, not discovered at 2 a.m.

Community versus Pro, and where Nextcloud still wins

The Community edition is AGPL-3.0 and has everything above. The Pro edition is free for up to 3 users and adds full-text search, audit logs, S3 and other object storage backends, and finer sharing controls; above 3 users it is paid. For a family or a solo operator, Pro at zero cost is a reasonable choice, though you are then running proprietary code. What Seafile does not try to be is a groupware suite. Nextcloud has calendars, contacts, Talk, Office integration and 300-odd apps; Seafile has files, sharing, a virtual drive client called SeaDrive, and integration hooks for Collabora and OnlyOffice. If you want a Google Workspace replacement, Nextcloud is the honest answer. If you want Dropbox that works, this is.

What I'd do

Seafile Community behind Caddy on a box with 1 GB free, hostname fixed on day one, MariaDB and the data directory backed up together nightly with a stopped-consistent snapshot, GC on a monthly cron, one encrypted library for documents that matter. Sync clients on every machine, SeaDrive on the laptop with the small disk. For a household that mainly needs files to be everywhere and correct, it is the fastest and least dramatic option in the file sync category, and I would pick it over Nextcloud for that job without much hesitation.