# How to Self-Host File Uploads for Dropshare on a Virtual Machine If you want a **self-hosted file sharing workflow** on your Mac, you do not have to settle for generic cloud tools. With **Dropshare** and **dropshare-selfhosted**, you can run your own upload backend on a **virtual machine** and keep control over your files, URLs, and infrastructure. It is a practical option for self-hosters, developers, agencies, and anyone who wants faster file sharing without giving up ownership of the backend. ### Why self-host file uploads for Dropshare? Many Mac users want fast file sharing, but they do not necessarily want to depend on a generic hosted service for every upload. If you already run your own infrastructure, self-hosting your Dropshare uploads can be a better fit. - **Keep control of your files:** Uploads go to a backend you manage instead of a third-party storage silo. - **Build a self-hosted file sharing workflow:** You can combine Dropshare’s fast Mac workflow with infrastructure you already trust. - **Use your own VM or server:** If you already have a VPS, home server, or virtual machine, it can become your upload destination. - **Create a better alternative to generic file sharing tools:** Instead of adapting to someone else’s product, you shape the setup around your own workflow. * * * ### What is dropshare-selfhosted? [dropshare-selfhosted](https://github.com/dropshareapp/dropshare-selfhosted) is a self-hosted backend for Dropshare. It lets you run your own upload target on a server or virtual machine, so files uploaded from Dropshare land on infrastructure you control. That makes it useful if you are looking for: - a **self-hosted file sharing solution for Mac** - a **bring-your-own-storage workflow** - a **private file upload backend** - or a **virtual machine based file sharing setup** * * * ### Why use a virtual machine for self-hosted uploads? A virtual machine is one of the simplest ways to run a self-hosted Dropshare backend. It gives you flexibility without requiring a large or complicated setup. - **Easy isolation:** The upload service stays separate from other apps and services. - **Works almost anywhere:** You can use a VPS, a local VM, a cloud instance, or a home lab environment. - **Easier maintenance:** Backups, updates, and migrations are simpler when the service lives in its own environment. - **Good fit for technical users:** Developers, self-hosters, and IT teams often already think in terms of VMs and services. * * * ### How the workflow works - **Take a screenshot or select a file:** Use Dropshare as you normally would on your Mac. - **Upload to your self-hosted backend:** The file is sent to dropshare-selfhosted running on your virtual machine. - **Get a shareable link immediately:** Once the upload is finished, the URL is ready to paste into email, chat, docs, or tickets. - **Keep the fast workflow:** You still get the speed of Dropshare, but with a backend you control yourself. * * * ### Who should use this setup? - **Self-hosters:** If you prefer to run your own services, this is the most natural way to use Dropshare. - **Developers and technical teams:** A self-hosted upload backend can fit neatly into an existing server stack. - **Agencies and consultants:** Useful if you want more control over client file delivery, branding, and storage. - **Privacy-conscious users:** If you care where uploads go and how links are served, self-hosting gives you more transparency. - **Mac users with high-volume sharing workflows:** If you send screenshots, recordings, builds, or assets every day, workflow quality matters. * * * ### Use cases for this kind of setup A self-hosted Dropshare backend can work well in several common workflows: - **Self-hosted screenshot sharing on Mac:** Capture, upload, copy link, done. - **Private file sharing for agencies or teams:** Share assets and deliverables without routing everything through a generic SaaS tool. - **Developer file sharing workflows:** Upload builds, logs, screenshots, or recordings to infrastructure you already manage. - **Bring-your-own-storage file sharing:** Use Dropshare as the frontend workflow and your VM as the backend. - **Alternative to generic file sharing tools:** Useful if you want more control over links, storage, and infrastructure. * * * ### What to think about before you self-host - **Server updates and maintenance:** If you run the backend yourself, you are responsible for keeping it updated and healthy. - **Public access and routing:** Download links need to be reachable in the right way from outside your network. - **Storage and retention:** Think about where files live, how long they should remain, and how backups should work. - **Security:** Use TLS, sensible firewall rules, and a deployment you understand well enough to maintain safely. * * * ### Why this is compelling for Mac users The real value here is not just self-hosting for its own sake. It is the combination of **control** and **workflow speed**. Generic file sharing tools often ask you to accept their storage model, their UI, and their workflow. Dropshare takes a different approach. It gives you a fast Mac-native sharing workflow and lets you pair it with infrastructure that matches your needs. That is what makes a self-hosted Dropshare setup appealing: it can feel more flexible, more trustworthy, and more aligned with how technical users already work. * * * ### A practical self-hosted file sharing setup for Mac If you want a **self-hosted alternative to generic file sharing tools**, running **dropshare-selfhosted** on a **virtual machine** is a practical place to start. You keep the convenience of Dropshare, while taking ownership of the backend.