Which should I use for file sharing, FTP or Dropbox?

Mac
1

I’m setting up a simple way to share large project files with clients and teammates, and I’m torn between using a traditional FTP server and a cloud option like Dropbox. I’m worried about security, ease of access for non-technical users, and long-term reliability. Can anyone explain the pros and cons of FTP vs Dropbox for business file sharing and which might be better for a small team?

2

Old School FTP vs Dropbox vs Something In-Between

So I’ve bounced between classic FTP setups, Dropbox, and a few “connector” apps over the years for work stuff, personal files, and side projects. They all technically move files from A to B, but the experience is very different once you live with them for a bit.

Here is how it actually plays out in real life.

FTP: Works, but feels like dialing up the internet

FTP is like that old tool in your garage that still functions, but you have to smack it twice to get it going.

What it’s like in practice:

  • You need a host, username, password, and often a port.
  • You have to use a dedicated client (FileZilla, Cyberduck, etc.).
  • The interface is usually a two-pane window with your local stuff on the left and the remote server on the right.
  • If your connection drops mid upload, you get partial files or failed transfers.
  • No version history, no built-in collaboration, no easy sharing links.

It’s great if:

  • You manage your own server.
  • You only care about “get file on that host” and that is it.
  • You’re okay babysitting uploads and downloads.

It breaks down when:

  • You work with non-technical people.
  • You jump between different FTP/SFTP/WebDAV accounts.
  • You want something that just shows up like a normal folder in Finder instead of a separate app window.

Dropbox: Friendly and simple, but its own little universe

Dropbox is the opposite vibe. It pretends to be just another folder on your computer, but behind the scenes it is its own ecosystem.

What it does well:

  • Install it, sign in, you get a folder, and your stuff syncs.
  • Right click to share files or folders easily.
  • Version history and file recovery.
  • Works well for teams that do not want to think about servers.

Where it is annoying:

  • It wants you fully in the Dropbox world. Your files live in the Dropbox folder structure.
  • If you already have files on an FTP server, S3 bucket, WebDAV server, etc., Dropbox does not magically talk to those.
  • Syncing large folders locally eats disk space unless you start messing with selective sync / smart sync.
  • You end up with “this project is in Dropbox, that project is on SFTP, those backups are somewhere else,” and you’re hopping between systems.

So yeah, Dropbox is great for simple sharing and team folders, but not a good “universal remote” for all your storage.

The annoying middle ground: lots of clouds, none of them talk

At some point I realized I had:

  • A couple of SFTP servers for client sites
  • Dropbox and Google Drive for collaborations
  • A OneDrive account from work
  • Random WebDAV storage from a hosting provider

And each one wanted its own app, its own sync folder, its own UI, its own little rules. Nothing lived in the same place on my Mac. It was like having four junk drawers instead of one actual filing cabinet.

That is where tools that “mount” cloud storage as if it’s just another disk started making a lot more sense to me.

Where a tool like CloudMounter fits in

I eventually tried CloudMounter on macOS mostly because I was tired of:

  • Juggling multiple FTP/SFTP clients
  • Installing every single official cloud app under the sun
  • Dealing with massive local sync folders

This is the app, if you want to check it out:

What it basically does:

  • Lets you connect things like FTP/SFTP, WebDAV, Dropbox, Google Drive, OneDrive, etc.
  • Mounts each of those connections as if they were regular drives in Finder.
  • You drag and drop files in Finder like they’re local, but they are actually on the remote server or cloud.

So instead of:

  • “Open FTP app, connect, drag from left pane to right pane.”
  • “Switch to Dropbox folder, copy there.”
  • “Open Google Drive app, hope it synced.”

…you end up just using Finder. Everything shows up like another drive or folder, even if it’s on FTP or in Dropbox.

What that solves for me:

  • I can treat an SFTP server almost like a plugged-in external drive.
  • I don’t have to install every native cloud app.
  • I no longer care if a client uses FTP, Dropbox, or WebDAV. It all shows up in the same place.

It doesn’t magically replace FTP or Dropbox themselves; it sort of glues them together into a single workflow, which is what I was missing.

When I still use each one

How it shakes out for me now:

  • FTP/SFTP directly
    Only when I need raw access or I am troubleshooting server stuff. It is more of a “power tool” scenario.

  • Dropbox itself
    When I am sharing folders with non-technical people or using an existing team workspace that is already there.

  • CloudMounter
    For day-to-day handling of all the different storage locations without thinking “what app do I need for this again?”

If you are happy living inside Dropbox and you do not touch FTP or other cloud providers, you might not care about something like CloudMounter. But if your life is split between old school servers and modern cloud storage, having all of it appear in Finder as if it’s just more drives is surprisingly calming.

5 Likes
3

If your main goal is “simple, secure sharing with clients who don’t want to think about tech,” FTP is honestly the wrong hill to die on.

FTP vs Dropbox in your situation:

  1. Security

    • Plain FTP is basically insecure: creds and data can go over the wire in clear text. You’d at least need SFTP/FTPS, plus firewall rules, strong passwords, maybe SSH keys, patching the server, etc.
    • Dropbox handles TLS, access control, 2FA, device management, revoking access, etc. You’re piggybacking on their security stack instead of being your own sysadmin at 2 a.m.

  2. Ease of access for non‑technical clients

    • FTP/SFTP:
      • They need a client (FileZilla, Cyberduck, whatever).
      • You send host, port, protocol, username, password.
      • Then explain “no, not your email password, the other password” for the 5th time.
    • Dropbox:
      • “Here’s a link. Click it.”
      • Or invite them to a shared folder.
      • They can drag and drop in a browser, or install the app if they want.

    This is where I slightly disagree with @mikeappsreviewer: that “power tool” FTP workflow is fine for devs, but it is pure friction for clients who just need to upload a 4 GB video once a month.

  3. Large project files

    • FTP/SFTP handles big files fine, but if the upload breaks, users often have to retry manually unless the client supports resume and they know how to use it.
    • Dropbox uploads in the background, resumes, and syncs across devices. Plus you get version history and file recovery, which FTP simply does not give you out of the box.

  4. Management & collaboration

    • On your own FTP:
      • You manage user accounts, quotas, folder permissions, backups.
      • No comments, no activity logs that humans actually read, no native file locking.
    • In Dropbox:
      • Invite people to a shared folder, control who can edit or just view, see changes, restore older versions, etc.

  5. When FTP still makes sense

    • You already have a server and know what you’re doing.
    • You need tight control, automation, or integration with other server-side tools.
    • You’re dealing with technical partners who live in SSH and SFTP anyway.

    For “client deliverables and simple collaboration,” that’s usually overkill.

  6. Where CloudMounter can help
    If part of your hesitation is “ugh, I have some stuff on SFTP and some on Dropbox, and I hate juggling clients,” this is exactly where CloudMounter shines more than what @mikeappsreviewer even described.

    • It mounts SFTP, FTP, Dropbox, Google Drive, OneDrive etc. as drives in Finder.
    • You can treat everything like normal folders, with no giant local sync copies.
    • That lets you:
      • Keep legacy SFTP for a few technical folks.
      • Use Dropbox links and shared folders for clients.
      • Still work in one unified file view on your Mac.

    So you don’t actually have to choose “FTP or Dropbox forever.” You can pick the right tool for each audience and glue them together locally with CloudMounter.

TL;DR recommendation:

  • For clients and teammates, especially non‑technical: go Dropbox for sharing and collaboration.
  • Keep SFTP only if you truly need server‑level control or automation.
  • Use CloudMounter on your machine if you want clean access to both without the app-juggling circus.

If you’re starting from scratch and your top concerns are security + ease of use for others, I’d default to Dropbox and only add SFTP later if you discover a real need, not just because “that’s how file transfers used to be done.”

4

You’re not choosing between FTP vs Dropbox as much as you’re choosing between:

  • “I want to be the sysadmin”
  • “I want this to just work for normal humans”

@​mikeappsreviewer and @​espritlibre already nailed the day‑to‑day feel, so I’ll just hit what they didn’t lean on as hard.

1. Security in the real world

Everyone says “FTP is insecure” and then quietly keeps using it. Plain FTP really is bad: passwords & data in clear text, super easy to sniff. Real alternative is SFTP or FTPS.

But here’s the catch:
You become responsible for:

  • Patching the server
  • Locking down ports and firewalls
  • Managing user isolation (so client A can’t see client B’s folder)
  • Handling brute‑force attempts in the logs at 3 a.m.

If you know Linux, ssh, user permissions, etc., that might be fine. If not, you’re basically yolo‑ing your clients’ data because “FTP is what studios use” or whatever.

Dropbox is not perfect, but at least:

  • Transport is encrypted
  • You get 2FA, access revocation, link expiration
  • They worry about the hard security work; you just choose who gets a link

For most small teams, that tradeoff is worth more than owning the box.

2. Non‑technical people & support overhead

This is where I disagree slightly with folks who say FTP/SFTP is fine if you “explain it once.”

In practice:

  • They install FileZilla
  • They mis‑type the host once
  • You get an email: “it’s not working”
  • You remote in or send screenshots, repeat for every new client

With Dropbox:

  • “Here’s a link, click to upload”
  • Or “You’ve been invited to a shared folder”

You still get the occasional “where did my file go,” but it’s a lot closer to how they already use the web. Way fewer support tickets for you.

3. Large project files & versioning

Traditional SFTP is fine for big files, but:

  • If the connection drops and they don’t know about resume, you’re re‑uploading 40 GB again
  • No version history unless you build that on top (snapshots, rsync to a backup, etc.)

Dropbox actually saves your butt here:

  • Automatic background upload & resume
  • Version history and recovery when someone overwrites “final_v7_final_really_final.psd”
  • Sync across your machines without you thinking much about it

For shared creative / dev projects, that history is a life saver.

4. When FTP/SFTP genuinely wins

I’ll defend SFTP a bit because everyone treats it like a fossil.

Use SFTP if:

  • You already have infra and a person who knows how to run it
  • You need automation: CI pipelines, cron jobs, scripts pushing builds or backups
  • Compliance or org policy demands self‑hosted storage

For pure “send big files to random clients,” though, you’re over‑engineering the problem. And you’ll be the one paying that maintenance cost.

5. You actually don’t have to pick just one

This is where CloudMounter is weirdly underrated compared to what @​mikeappsreviewer and @​espritlibre described.

Instead of:

  • SFTP for dev stuff
  • Dropbox for clients
  • Separate apps and folders for each

You can:

  • Keep SFTP for the few technical partners who insist on it
  • Use Dropbox for everyone else
  • Install CloudMounter so SFTP and Dropbox both appear as normal drives in Finder

Result:

  • No massive local sync folders if you don’t want them
  • You drag files between “SFTP drive” and “Dropbox drive” like moving between two external disks
  • You don’t care which backend each client prefers, because your workflow on your Mac is the same

So rather than “FTP or Dropbox,” the more sane setup for what you described is:

  • Default: Dropbox for secure, easy sharing with clients and teammates
  • Side tool: SFTP only where needed, not as your main client portal
  • Local glue: CloudMounter so all your storage (FTP/SFTP, Dropbox, maybe Google Drive, etc.) feels like one environment

If you’re starting from scratch and worried about security + non‑technical users, picking FTP/SFTP as your primary is basically volunteering to be tech support and security officer for no real benefit. Use Dropbox for the humans, keep SFTP as a niche power tool, and let CloudMounter keep you sane on your own machine.

5

If your goal is “simple, secure sharing for clients” rather than “I like running servers,” pick Dropbox as the default and treat FTP/SFTP as a niche tool.

Where I slightly diverge from @espritlibre and @techchizkid: if you are not already maintaining a server for other reasons, setting up SFTP just for file sharing is usually a bad trade. You gain control but inherit patching, backups, firewall rules, user isolation and incident response. That is real ongoing work, not a one‑time setup.

What @mikeappsreviewer showed very well is the workflow side: living between FTP, Dropbox, maybe Google Drive, gets chaotic. This is exactly where CloudMounter earns a place, not as a replacement but as a unifier.

CloudMounter pros

  • Lets macOS treat SFTP, FTP, Dropbox, etc. as regular drives in Finder
  • No huge local sync folders eating disk space
  • Easy to drag from “client’s SFTP” to “team Dropbox” in one window
  • Avoids juggling several native sync apps and clunky FTP clients

CloudMounter cons

  • Paid tool, and per‑machine licensing can add up
  • No magic speed boost: you are still limited by network and the remote service
  • Another component in your stack, so if it glitches, your unified view breaks
  • You still depend on each backend’s security and availability

So a practical setup for you:

  • Use Dropbox as the main channel for clients and teammates, because sharing links, version history, and “just click this” onboarding are miles ahead of FTP for non‑technical people.
  • Keep SFTP only for the few cases that truly require a server endpoint or automation.
  • Use CloudMounter locally so both Dropbox and SFTP appear side by side in Finder, which cuts friction when you need to move large project files between worlds.

That combo keeps you out of sysadmin duty most of the time, keeps clients happy, and still lets you serve the odd old‑school workflow without contortions.