Every small team hits the same wall: a video, a design file, or a dataset that is too big for email and too awkward for chat. Commercial file sharing tools solve it, but they charge per user and per month, which is hard to justify when you share large files a few times a week. Self-hosting turns that recurring cost into a one-time setup.

A self-hosted file sharing app runs on your own server and gives you a simple upload page, a share link, and controls over expiry and passwords. It is private by default, it carries your own domain, and it has no per-user pricing because you are the only user that matters.

The essentials are simple: uploads that handle large files reliably, links that expire automatically, optional passwords, and a clean download page that does not confuse recipients. Chunked uploads matter for big files, because a single interrupted upload should resume rather than restart from zero on a slow connection.

Beyond that, look for a small footprint and simple maintenance. A sharing app should be a quiet utility, not a second job. Prefer tools with a single container, a straightforward update path, and no database server to babysit. If the setup takes a weekend, it is the wrong tool for the job.

Install the app behind HTTPS on your own domain, and set sensible defaults: links that expire after a week, a maximum file size that fits your server's disk, and automatic deletion of expired files so storage does not grow forever. These defaults protect you from the two classic failures: links that live forever and a disk that quietly fills up.

Create a simple sharing habit for the team: upload, set a password for anything sensitive, and send the link and password through different channels. That last step matters more than any feature, because a link and its password in the same message are effectively an unlocked door. Good habits beat good software, but good software makes good habits easy.

Self-hosting is not always right. If your recipients are non-technical clients who distrust unfamiliar links, a well-known commercial service may be worth the fee for its familiar name alone. Similarly, if you need compliance certifications or legal guarantees about data handling, a commercial provider's paperwork may matter more than the cost saving.

For most small teams sharing files internally or with regular collaborators, though, self-hosting wins. The files stay on your server, the links carry your domain, and the only recurring cost is the server you probably already pay for. Start with one project, see how the team takes to it, and expand from there.

External sharing needs stricter defaults than internal sharing. Set shorter expiry times, require passwords for anything sensitive, and avoid letting clients upload to the same space your team uses for internal files. A separate upload area for client material keeps your internal organisation clean and prevents accidental exposure of files a client was never meant to see.

Tell clients in plain language how long the link lasts and what to do if it expires. Most client confusion around file sharing comes from expired links and unclear instructions, not from the tool itself. A short message with the link, the password sent separately, and the expiry date prevents almost every support question before it is asked.