Self-host Snapdrop with Levelrail
Local network file sharing in the browser, inspired by AirDrop.
- AuthorRobinLinus
- LicenceGPL-3.0
- Memory128 MiB
- Services1
How to self-host Snapdrop
-
Pull the images
One image is pulled on your server.
Show images
lscr.io/linuxserver/snapdrop:latest
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 80.
-
Fill in the secrets
3 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Snapdrop requirements
- Memory
- About 128 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 80
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0, copyleft license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 80 on the host, so open them in the VPS firewall only if you want that.
- Review. Image is not pinned to a version tag, so a redeploy can pull different code (lscr.io/linuxserver/snapdrop:latest).
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Snapdrop. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Snapdrop docs page.
Deploy Snapdrop your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Snapdrop from the CLI
levelrail-cli templates deploy snapdrop --name my-snapdrop Deploy Snapdrop with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/snapdrop/deploy Snapdrop configuration
Snapdrop services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| snapdrop | lscr.io/linuxserver/snapdrop:latest | 80 | snapdrop_config -> /config |
Snapdrop environment variables
| Variable | Service | Value |
|---|---|---|
| PGID | snapdrop | Preset by the template |
| PUID | snapdrop | Preset by the template |
| TZ | snapdrop | Preset by the template |
Ports and volumes
- Ports
- 80
- Volumes
- 1 named mount: snapdrop_config -> /config
Snapdrop FAQ
How much memory does Snapdrop need?
The catalog lists about 128 MiB of memory for Snapdrop.
Does Snapdrop run on arm64?
For Snapdrop, arm64 support is not confirmed; amd64 is unknown.
What licence is Snapdrop under?
Snapdrop is licensed under GPL-3.0, which is copyleft, so changes you distribute must be shared under the same terms.
Does Snapdrop need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Snapdrop use?
Snapdrop listens on port 80 inside the stack.
Where does Snapdrop keep its data?
In a named volume: snapdrop_config mounted at /config.
Can I deploy Snapdrop on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Snapdrop, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image lscr.io/linuxserver/snapdrop:latest is what you deploy there.