Best self-hosted Dropbox alternatives compared

Which self-hosted Dropbox alternative you suppose run?

Four self-hosted Dropbox alternatives dey worth your time: Nextcloud, Seafile, Syncthing, and object storage with a client on top. Dem no be the same thing. Nextcloud good for house or small team where other people need receive files. Seafile good for person or team wey dey sync very large number of small files, where sync speed matter pass how the data dey stored for disk. Syncthing good for one person wey dey sync their own devices, where nobody outside need link. Object storage good for archive: cheap bytes wey you rarely open.

Choose based on how the sync dey work before you compare features. Feature lists dey look the same. The topology, meaning which machine dey hold the copy wey every other machine agree with, na wetin decide whether you go still dey happy after six months.

Sync topology: server of record, or peers wey no get server

Two designs dey available, and most of wetin follow depend on the one wey you choose.

Server of record. Nextcloud, Seafile and object storage all dey work this way. One machine, usually VPS (virtual private server), dey hold the authoritative copy. Every device dey connect to that machine. Your laptop fit stay off for one month, come back, and catch up by itself. Phone wey get 6 GB free fit hold subset, while server dey hold everything. Browser fit reach the files, and na this make share links possible.

Peers wey no get server. Syncthing dey work this way. Devices dey find each other and exchange file lists directly through encrypted connection. No copy be authoritative: file dey exist for the devices wey hold am, and nowhere else. Two devices must dey online at the same time before change fit pass between dem. No URL dey wey you fit give anybody, because no machine dey serve page.

Four consequences dey follow, and na dem people dey discover late.

• To send file to person wey no go install software, you need server of record. Link na URL, and URL need process wey dey listen on port.
• To reach your files from machine wey you no control, like work laptop, you need server of record.
• Device wey stay off for weeks go catch up from server anytime e wake. For peer setup, e go catch up only while another device wey hold that data dey online too. Na why many Syncthing users dey run one instance for VPS as peer wey dey always online.
• Storage dey add up differently. Server of record dey hold one full copy, plus anything each device keep locally. Four peers wey share one folder go hold four full copies, because every peer dey keep the whole folder.

Nextcloud: users, groups and public links

Nextcloud na PHP web application. E dey store your files as ordinary files inside data directory and track dem for database. You fit share folder with user, group, or public link wey carry password and expiry date. Version history dey on by default, and deleted files first go trash bin. Desktop clients dey cover Linux, macOS and Windows, while the iOS and Android apps na official ones. If na because other people need receive your files make you comot from Dropbox, this na the honest answer.

The price na the many moving parts. Normal install dey run web server, PHP-FPM (the PHP process manager), database like MariaDB or PostgreSQL, and Redis for file locking. Background job dey run every five minutes from cron or systemd timer. For 1 GB VPS e go start, then large upload or long occ maintenance command go meet out-of-memory killer. Treat 2 GB as the minimum for small number of users, and expect say you go need 4 GB after you enable more apps. The other price na upgrades: app-store apps dey built against specific core release, so check say the apps wey you depend on support the next major version before you upgrade am.

Nextcloud dey slow down when one account get hundreds of thousands of small files, because each file na row for file cache table and real file for disk, while desktop client dey process dem one after another. For household scale, this issue no dey show. Sizing, TLS (transport layer security) and backups for Docker-based Nextcloud install cover sizing, TLS (transport layer security) and backups. Na there you go once you don decide.

One warning about scope. Nextcloud fit also run your calendar, contacts, notes and photo library, and every app wey you enable adds background work plus another thing wey fit block upgrade. If photos na the real problem, dedicated tool go handle dem better: see Immich as self-hosted Google Photos replacement. If documents and wikis na the real problem, check self-hosted Notion alternatives instead of stacking apps on your file server. Editing those documents for browser na another server matter, not Nextcloud app, so compare OnlyOffice with Collabora before you assume say 2 GB floor still cover you.

Seafile: dem build am for very plenty small files

Seafile dey split every file into blocks and store dem for internal object store wey content hash dey address, na the same idea wey git dey use for im objects. The unit for sync and sharing na library, no be folder tree. Because the client dey upload blocks and one commit instead of one request for each file, syncing directory wey get 100,000 small files go finish much faster than protocol wey dey handle one file at a time. Identical blocks dey store once, so second copy of large file almost no cost anything.

The trade-off na say your files for the server no longer dey as files. If you open the storage directory, you go see object files wey get hexadecimal names. To bring data out, you need Seafile client, or Seafile own export and fsck tools. Backup still dey work, because those objects na ordinary files, but you no fit restore one spreadsheet with cp. Decide now whether you fit accept this, because na this property people dey regret later.

Seafile get community edition and paid professional edition, and the difference between dem fit change between releases, so read the current terms for their site before you plan team around one specific feature. Official desktop and mobile clients dey available. Encrypted libraries dey encrypt for client side, so the server dey store ciphertext wey e no fit read. If you lose the passphrase, the library no go readable, including by you. To open encrypted library for browser means say you dey give that passphrase to the web session, so the stronger version of that guarantee dey apply to desktop and mobile clients.

Resource cost dey close to Nextcloud. You dey run database, memory cache and two application processes, so 2 GB still be sensible minimum.

Syncthing: no need to log in

Syncthing na one Go binary. E dey watch folders, find peers through discovery server or relay, then sync directly between devices. No accounts dey, and no login page dey for the people wey you dey sync with. You pair two devices with ID and accept the folder for each side. For everything wey dey here, na this one easiest to run, because almost nothing dey to run.

The thing wey you lose na the whole sharing part. Its entry na Device pairing only, no links. You no fit give client, accountant, or relative any link. Mobile na the other gap: Android app, no official iOS. The project own FAQ talk am clearly: "There are no plans by the current Syncthing team to officially support iOS in the foreseeable future", because iOS dey restrict background processing enough to make reliable syncing hard. iOS users remain with third-party apps.

Resource use small, but one thing dey important. Syncthing dey keep index entry for every file wey e sync, so memory and the first scan grow based on file count, not total size. Hashing a large folder for the first time go use CPU for some time, then e go settle. For the smallest VPS plan, e dey run comfortably.

Syncthing handle conflicts by keeping both sides. When two devices change the same file while dem no fit see each other, Syncthing rename one copy and keep am beside the other, so you go find files like notes.sync-conflict-20260802-141530-K7MB3QT.md. Nothing dey lost. But nothing dey merged too, and you need resolve am by hand.

Object storage with a client: cheap bytes, not a sync folder

Object storage na S3 (simple storage service) compatible bucket, either you host am yourself with MinIO or you rent am from provider. You go reach am with tool: rclone from command line, or desktop client wey dey show the bucket like drive. Sharing na presigned URL, link wey you generate and e carry im own expiry time. Versioning na bucket setting: Bucket versioning, off by default, so turn am on when you create the bucket, because e no apply to objects wey you upload before that time.

Na when you treat bucket like sync folder wahala dey start. Nothing dey watch your Documents directory by default. rclone bisync dey do two-way sync, and rclone own documentation talk clearly about the care wey e need. Wetin object storage dey do well na to stay underneath: backup target, or storage layer behind application. Self-hosted S3 compatible object storage with MinIO cover the server side.

The resource cost for here dey unusual. MinIO na one binary and e dey idle with small resource use. The cost wey you actually pay na disk, and for VPS that means block volume wey you rent by gigabyte, plus bandwidth wey you spend to move objects in and out. None of these dey show for free -h, so read wetin VPS actually cost per month before you size archive.

Sharing, mobile clients and versioning compare

[
  {
    "tool": "Nextcloud",
    "sharing": "Public links, users and groups",
    "mobile": "Official iOS and Android apps",
    "versioning": "On by default, plus trash"
  },
  {
    "tool": "Seafile",
    "sharing": "Public links with password and expiry",
    "mobile": "Official iOS and Android apps",
    "versioning": "Library history and snapshots"
  },
  {
    "tool": "Syncthing",
    "sharing": "Device pairing only, no links",
    "mobile": "Android app, no official iOS",
    "versioning": "Optional per folder, off by default"
  },
  {
    "tool": "Object storage",
    "sharing": "Presigned URLs you generate",
    "mobile": "Third party clients only",
    "versioning": "Bucket versioning, off by default"
  }
]

All 4 options split for one line. Three of dem fit give file to stranger wey only get browser. One of dem only dey talk to devices wey you already own. Seafile versioning entry, Library history and snapshots, need one note: e dey keep history for each library, so if you delete library, e go delete the history join.

Data dey get out again

Exit cost dey cheap to check now but expensive to discover later, so check am before you commit.

Nextcloud dey store real files inside real directories, so one tar of the data directory go give you your documents even if the application no start again. Syncthing dey do the same for every peer, and na the strongest exit story here: the files simply dey on each device. Seafile object store need Seafile or its export tools to join the blocks back into files. Object storage need rclone or equivalent, and na just one command away.

Sync no be backup, and na for this gap people dey lose data

Every tool for here dey copy changes between machines. Delete na change. If you remove folder for your laptop, client go tell server, server go apply am, and every other device go remove am too. Ransomware dey use the same path: e encrypt files locally, client see say files change, and e upload the encrypted versions. The sync work correctly. Your data still don disappear.

Trash bins and version history fit reduce the damage. But dem too dey expire, the same account wey make the mistake fit empty dem, and dem dey for the same disk with the live copy. If volume fail, e go carry the files and their history together.

Backup na separate copy for separate hardware, wey you take according to schedule, and wey you don restore at least once. Back up the database for the same run with the files. If you restore Nextcloud data directory without the database, you go get instance wey no know say those files dey exist, and an occ files:scan afterwards go recover the files but lose the shares and version history wey dey inside those tables. Scheduled restic backups from VPS cover the encrypted, deduplicated version of this process, including how to test restore instead of assuming say e go work.

Wetin I go pick

Nextcloud, for most people wey dey read this. Wetin people miss after dem leave Dropbox na to give person link when the person no go ever install anything, and to open file for phone. Nextcloud dey do both with official clients and no paid tier, and 2 GB RAM na fair price for that. I get two exceptions. If na only you go ever use the folder and na only hardware wey you own go ever hold am, run Syncthing and enjoy say you no get server to patch and no web login to protect. If you dey sync working directory wey get hundreds of thousands of files, run Seafile and accept the opaque storage because of the speed. Object storage belong underneath whichever one you choose, as the backup target, no be in front of am as the sync tool.

FAQ

Syncthing na backup for my laptop?

No. Syncthing dey copy changes between devices, and deletion na change like any other one. So, if you delete file by mistake, e go disappear from every paired device within seconds. Per-folder file versioning fit help, but e dey off until you enable am for each folder. Keep real backup for separate hardware, make you take am on schedule, and restore from am once so you go know say the restore dey work.

I fit run Nextcloud and Syncthing for the same VPS?

Yes, dem dey listen on different ports and dem no dey conflict. No point Syncthing folder to Nextcloud data directory. Nextcloud dey track every file for database, so files wey appear for disk underneath am go remain invisible until you run occ files:scan. Files wey you remove underneath am go leave database rows wey point to nothing. Give Syncthing e own directory, or attach that directory to Nextcloud as external storage so Nextcloud go know say e suppose check am.

Which one let me share link with person wey no get account?

Nextcloud and Seafile both fit create public links, with optional password and expiry date. Object storage fit give you presigned URL wey go stop working by itself after the time wey you set. Syncthing no get solution for this. E sharing model na device pairing, so the other person must install Syncthing, give you device ID, and accept the folder.

How much disk the server need?

For server of record, plan for the full size of the shared data, plus space for version history and trash, plus working room for uploads wey still dey progress. Version history na the part wey people dey underestimate: if you keep every version of 2 GB file wey changes every day, the size go grow fast. So set retention policy early. Putting the data for separate volume keeps that growth away from root filesystem. When disk full, e go stop the whole server instead of only one upload.