Handoff

Handoff turns a file or folder on your server into a shareable download link with an expiry date.

  • Cloud
  • Network Services
  • Tools & Utilities
Handoff turns a file or folder on your server into a shareable download link with an expiry date. Mount a folder the way you would for any container and browse it in the admin interface. Click a file to share it and it is served straight off the share, so nothing is copied and no extra disk is used. Or share a whole folder and Handoff zips it once with no compression, which is the fast option for photos and video since they do not compress anyway. You can also drag a file into the browser to upload it. Every link can carry an expiry, an optional password, and an optional download limit. When a link expires it is deleted, along with anything Handoff created for it — an upload or a generated archive. Your mounted folder is read-only to Handoff — it is only ever read from, never written to or deleted from. Note on disk space: generated archives are written to the Appdata path, so zipping a

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

40/100 Fair

Maintained
68last commit 97 days ago
Popular
61 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
304 GB minimum RAM

Availability: platform listings confirmed today, links checked 21 days ago

GitHub stars
1
Open issues
0
Last commit
2026-08-16
License
MIT
Activity
stale

Checked 7 days ago - source: GitHub (jackmeyer/handoff)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 2 CPU core(s), 4 GB disk.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Prepare .env and projects folder first Before running Docker, copy .env.example to .env (a settings file) and create the projects folder. The config file is required, and if Docker creates the folder as root, the app user can't write files and the container breaks. source
  • Log Claude in once, then restart Run docker compose exec agent claude login, then restart the agent. This one-time sign-in lets the app use Claude; without it, the assistant parts won't work. source
  • Where the app opens After docker compose up --build, use localhost:5180 for the web UI, localhost:3009 for the API, and localhost:3100 for MCP. These are the local addresses you'll use to open or connect to the app. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where should I mount the shared folder and generated archives?

Mount the source folder as /library read-only, and use the /data appdata volume for anything Handoff creates. The /data volume needs room for the largest folder you plan to zip.

What port does the Handoff web UI use?

The web UI uses port 8080. In Docker, expose the container with 8080:8080.

What must I configure to expose Handoff through a reverse proxy without 403 or broken login?

Handoff speaks plain HTTP and expects a proxy in front. Set PUBLIC_URL or ALLOWED_HOSTS to the hostname you use, and set TRUST_PROXY=1 only when a proxy forwards X-Forwarded-* headers.

Does the admin password also protect shared download links?

The admin password gates the admin UI only, not share links. Share links can still carry their own optional password, expiry, and download limit.

Can interrupted file transfers be resumed?

Downloads can resume because Range requests are supported, so a large download resumes instead of restarting. Uploads are not resumable, so put anything huge on the share instead.

Answers sourced from github.com

Community

Collected 49 days ago - public community threads