Dropbox vs Client Portal: What's Better?

When you send a client a link to a shared Dropbox folder, what they see is Dropbox's logo. When they open a client portal, they see yours. Shared folders work for low-stakes, one-off transfers. For professional services firms sending confidential documents -- tax returns, contracts, deliverables -- to multiple clients every week, shared folders create problems that a dedicated portal is built to prevent.

When a Shared Folder Is the Right Tool

If you occasionally send a finished document to a single client who already uses Dropbox, a shared folder is fine. No setup, no extra tool. The client logs in, downloads, and it's done. The situation changes the moment you're handling multiple clients, sensitive documents, or any need to track who accessed what.

The problem is not Dropbox itself. It's repurposing an internal collaboration tool as an external client-delivery channel. Dropbox was built for teams working together. A client portal -- you can read more about what a client portal is -- is built for firms delivering files to clients.

Five Signs Shared Folders Have Stopped Working

Most firms hit one of these five points within their first year of using shared folders for client delivery. The pattern is the same: it works for one client, then things get messier as more clients and more sensitive documents pile up. Each item below is a concrete failure mode, not a hypothetical.

1. Your client doesn't have a Dropbox account. They either create one -- adding friction to every first delivery -- or you send a public link, which has no identity attached. Anyone with the URL can open it.
2. You need to know who downloaded a file. Dropbox shows activity in your own account, but not a per-client record of exactly when a specific person downloaded a specific file. There is no log you can export per client.
3. You're managing files for multiple clients. One wrong share -- a folder permission set too broadly, a link sent to the wrong address -- and one client sees another's documents. This is the most common source of accidental data exposure in small professional services firms.
4. A team member left the firm. Shared folders are linked to individual Dropbox accounts. Unless you reassign every shared folder before they go, that person's account still has access to your client files.
5. You want clients to see your firm's name. A shared folder link opens to a page branded as Dropbox. A client portal opens to a page with your firm's logo and colors.

Cross-client exposure is the most common issue; the former-team-member problem is the most underestimated. Both have the same root cause: shared folders give you one level of access control instead of per-client permissions. If you run into the same friction with email, Email Attachments vs. Client Portal covers that comparison. For more tool comparisons, browse the Alternatives category.

The Data Security Difference

For accounting and tax preparation firms, the FTC Safeguards Rule (16 CFR Part 314) requires a written information security program that covers the tools you use to share financial records with clients. That includes service-provider oversight: the software you use to transfer client files needs appropriate safeguards, and an access log showing who downloaded what and when is one of them.

A client portal produces that log automatically. Every upload, download, and preview is timestamped and tied to a named client account. Shared folders do not give you this -- not per client, and not in a format you can export for a compliance review. For law firms, the ABA Model Rule 1.6 on confidentiality requires reasonable measures to prevent unauthorized disclosure of client information. Electronic file sharing is covered. A client portal with per-client permissions and an access log meets that standard in a way that a public shared folder link does not.

Your Clients Don't Need an Account Anywhere

A Dropbox shared folder requires your client to log in to Dropbox. If they don't have an account, they either create one or you send a public link -- which means anyone with the URL can access the file. A client portal gives each client their own login on your platform, and a private link option for one-off delivery.

You set up each client account yourself. The client gets a login email, sets a password, and sees only the files you've shared with them -- nothing else, not even the names of your other clients. On ProjectSend Cloud, clients never pay. The Pro plan includes 25 active client accounts; Business is unlimited.

A Different Pricing Model

Dropbox Business charges per internal user: every person on your team who needs a Dropbox account. A client portal charges per active client account instead. Your clients don't count as users and they never pay for access. For a firm with three staff members and twenty active clients, these models scale very differently.

The difference matters most as your client base grows. Adding a new client to Dropbox means asking them to create an account on a platform you don't control. Adding a client to a portal means sending them a login to a space with your name on it -- no new license on your end, no account creation on theirs. The metric you pay for is active client accounts: accounts that are actually in use. The full breakdown of how this compares to per-seat pricing is in Per-Seat vs. Per-Client Pricing.

The Exit Is Always Open

ProjectSend Cloud runs on ProjectSend, the same GPLv2 open source software used by 4,000+ self-hosted instances worldwide. If you ever want to leave the hosted version, you export your data and run your own install. There's no proprietary format, no migration tool to buy, and no negotiation required. The code is open, and so is your exit.

The source code is at github.com/projectsend/projectsend. The self-hosted version and community documentation are at projectsend.org. The same team maintains both. For a practical step-by-step guide, see how to switch to a client portal.