SSD Nodes Learn Hosting plans →
How to do am Matt ConnorBy Matt Connor · Updated 2026-10-19

Best self-hosted Dropbox alternatives for your VPS

We compare Nextcloud, Seafile, and Syncthing to show you which one fit your VPS. Learn why sync no be backup and how to choose the right topology for your files.

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 fit household or small team where other people need receive files. Seafile fit person or team wey dey sync very plenty small files, where sync speed matter pass how the data dey look for disk. Syncthing fit one person wey dey sync their own devices, where nobody outside need link. Object storage fit archive: cheap bytes wey you rarely open.

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

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

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

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

Peers wey no get server. Syncthing dey work like this. 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 to give anybody, because no machine dey serve page.

Four consequences follow, and na dem people dey encounter later.

  • 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 dey off for weeks go catch up from server whenever e wake. For peer setup, e go catch up only while another device wey hold that data dey online too. Na why plenty Syncthing users dey run one instance for VPS as always-on peer.
  • Storage dey add up differently. Server of record dey hold one full copy, plus anything wey each device keep locally. Four peers wey share one folder go hold four full copies, because every peer dey keep the whole folder.

Nextcloud na PHP web application. E dey store your files as normal files inside data directory, and e dey track dem for database. You fit share folder with user, group, or public link wey get password and expiry date. Version history dey on by default, and deleted files first dey enter trash bin. Desktop clients dey available for 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 extra moving parts. Normal installation 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, but large upload or long occ maintenance command fit meet out-of-memory killer. Treat 2 GB as the minimum for small number of users, and expect say you go need 4 GB once you enable more apps. The other price na upgrades: app-store apps dey build against specific core release, so check whether the apps wey you depend on support the next major version before you upgrade.

Nextcloud dey slow down when one account hold hundreds of thousands of small files, because each file na one row for file cache table and one real file for disk, while desktop client dey process dem one by one. For household scale, this issue no dey usually come up. Sizing, TLS (transport layer security) and backups dey covered for Docker-based Nextcloud installation with TLS and backups, and na there you go go after you don decide.

One warning about scope. Nextcloud fit also run your calendar, contacts, notes and photo library, and every app wey you enable dey add 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 piling apps onto your file server. To edit those documents for browser, you need office server on top. Collabora's built-in CODE server installs as Nextcloud app and na for personal use or small teams, while Nextcloud's own manual call am a bit slower than standalone server and recommends dedicated one for better performance. So compare OnlyOffice against Collabora before you assume say the 2 GB minimum still cover you.

Seafile: dem design am for very plenty small files

Seafile dey split every file into blocks and store dem for one internal object store wey content hash dey address, na the same idea wey git dey use for im objects. The unit wey sync and sharing dey use na library, no be folder tree. Because the client dey upload blocks and one commit instead of one request for every 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 only once, so second copy of one large file almost no cost anything.

The trade-off be say your files for server no longer be 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 this arrangement okay for you, because na this property people dey regret later.

Seafile dey release community edition and paid professional edition. 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 get encryption for client side, so server dey store ciphertext wey e no fit read. If you lose the passphrase, you no fit read the library, including you sef. To open encrypted library for browser means say you give that passphrase to the web session, so the strongest version of that guarantee na for 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: nothing to log in to

Syncthing na one Go binary. E dey watch folders, find im peers through discovery server or relay, and 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. Na the option wey require the least work to run here, because small things dey run for am.

The thing wey you lose na the whole sharing column. The entry for am na Device pairing only, no links. You no fit give client, accountant, or relative any link. Mobile na the other gap: Community apps only, no official mobile app. Dem discontinue the official Android app after the last release for December 2024, and the project documentation now list community Android apps like Syncthing-Fork instead. For iOS, the project own FAQ talk am direct: "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 worth knowing dey. Syncthing dey keep one index entry for every file wey e sync, so memory and the first scan grow according to file count, not total size. Hashing a large folder the first time go use CPU for some time, then e go settle. For the smallest VPS plan, e dey run comfortably.

When conflict happen, Syncthing keep both sides. If 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 see files like notes.sync-conflict-20260802-141530-K7MB3QT.md. Nothing dey lost. But nothing dey merge too, and you go resolve am by hand.

Object storage with a client: cheap bytes, no be sync folder

Object storage na S3 (simple storage service) compatible bucket. You fit host am yourself with MinIO, or rent am from provider. Before you self-host am, know say MinIO community repository don archive and remain read-only since April 25, 2026. Dem mark am as no longer maintained, and e no dey get pre-compiled community binaries again. So new install means you go build am from source, with no promise of future patches. You reach bucket with tool: rclone from command line, or desktop client wey show the bucket as drive. If you prefer browse the bucket from web page instead of shell, some tools for this comparison of self-hosted file managers fit use S3 bucket as backend and add their own share links on top. Sharing na presigned URL, meaning link wey you generate and wey carry its own expiry time. Versioning na bucket setting: Bucket versioning, off by default. If you enable am later, e still cover the objects wey already dey inside bucket. Dem carry a null version ID. The next overwrite or delete go keep that copy as older version instead of discarding am. But versioning no fit restore anything wey you overwrite or delete before you turn am on. So turn am on when you create the bucket.

Na when you treat bucket like sync folder trouble 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. Object storage dey work well as backend: backup target, or storage layer behind application. Self-hosted S3 compatible object storage with MinIO cover the server side.

The resource cost for here different. MinIO na one binary and e dey idle with small resource usage. The real cost na disk. For VPS, this means block volume wey you rent by gigabyte, plus the bandwidth wey you use to move objects in and out. None of these dey show for free -h. So read wetin VPS really cost per month before you decide archive size.

Sharing, mobile clients and versioning compare

ChartSharing, mobile clients and versioning, by tool
Di data wey dey behind dis chart
[
  {
    "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": "Community apps only, no official mobile app",
    "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 dey split for one line. Three of dem fit give stranger wey only get browser access to file. One of dem only dey talk to devices wey you already own. Seafile versioning entry, Library history and snapshots, need small note: history dey keep per library, so if person delete library, e go carry the history join am go Seafile system trash. Admin fit restore am from there, but once dem clear that trash, the history don disappear too.

Data wey you fit bring out again

To check exit cost now cheap, but to discover am later expensive, 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 ever start again. Syncthing dey do the same for every peer, and na the strongest exit story here: the files just dey sit for every 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 this gap make people lose data

Every tool wey dey here dey copy changes between machines. Delete na change too. 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, then e upload the encrypted versions. The sync work correctly. Your data still don disappear.

Trash bins and version history fit reduce this problem. But dem dey expire too, the same account wey make the mistake fit empty dem, and dem dey on 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 from at least once. Back up the database for the same run with the files. If you restore Nextcloud data directory without its database, you go get instance wey no know say those files exist. An occ files:scan afterwards fit recover the files but lose the shares and version metadata wey dey inside those tables. The older versions themselves na files under data/[user]/files_versions, so their contents go return with the data directory. Scheduled restic backups from a VPS explain the encrypted, deduplicated version of this, 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 comot from Dropbox na to share link with person wey no go ever install anything, and open file for phone. Nextcloud do both with official clients, and 2 GB of RAM na fair price for that. Run the free server wey you install by yourself. Nextcloud Enterprise subscriptions start from 100 users, and dem dey sell features together with support: as of October 17, 2026, the Nextcloud pricing page list Nextcloud Assistant and Nextcloud Flow as included only for the top Ultimate plan, and e also limit Whiteboard and most third-party integrations according to tier. I get two exceptions. If na only you go ever use the folder and e go ever dey only for hardware wey you own, run Syncthing and enjoy say you no get server to patch and no web login to protect. If you sync a working directory wey get hundreds of thousands of files, run Seafile and accept the opaque storage in exchange for the speed. Object storage suppose dey underneath whichever one you choose, as the backup target, no be in front of am as the sync tool.

FAQ

Syncthing fit be backup for my laptop?

No. Syncthing dey copy changes between devices, and deletion na change like any other one, so any file wey you delete by mistake go disappear from every paired device within seconds. Per-folder file versioning fit help, and 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 show for disk underneath am go remain invisible until you run occ files:scan, and files wey you remove underneath am go leave database rows wey point to nothing. Give Syncthing its own directory, or attach that directory to Nextcloud as external storage so Nextcloud go know say e need check am.

Nextcloud and Seafile both fit create public links, with optional password and expiry date. Object storage go give you presigned URL wey go stop working by itself after the time wey you set. Syncthing no get answer for this one. 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 dey change daily, e go grow fast, so set retention policy early. Put the data for separate volume so that growth no go affect root filesystem, where full disk fit stop the whole server instead of only one upload.

Dis article help you?