ProjectSend

Self-hosted client file delivery for agencies and freelancers: each customer signs in to a private page that lists only the files shared with them.

2.1k stars, 363 forks PHP On GitHub since March 2014

Visit website View on GitHub How to run it

ProjectSend at a glance

Open sourceYes, GPL-2.0No paid parts in the repository
Health73 of 100Actively developed
Self-hostingDockerOne-click in YunoHost, Unraid and 1 more
Interface14 languagesIncluding German, French and Spanish
Issue repliesWithin ~3 daysMedian first reply; 92% of recent issues answered

What is ProjectSend?

ProjectSend is a web application for handing files to clients from your own server. You upload a file, pick the clients or client groups allowed to see it, and they log in with their email address to download it, singly, as a zip or by folder. Uploads resume after a dropped connection, and shares can carry an expiry date or a download limit. Admins get folders, categories, per-client storage quotas, custom fields and a full download history. Sign-in works with LDAP, social accounts or email and password, files can sit on local disk, S3-compatible storage or Google Cloud Storage, and a REST API with scoped tokens is included.

Good fit if

  • You deliver documents, designs or reports to customers and want each one to see only their own files.
  • You need a record of who downloaded which file and when.
  • Your team needs separate roles so that uploaders cannot change administrator settings.

Look elsewhere if

  • You only need quick anonymous links without client accounts: PsiTransfer or Gokapi.
  • You mostly upload screenshots and files from ShareX: Zipline.

Before you adopt it

ProjectSend is GPL software, licensed GPL-2.0 or any later version, and commercial licenses are offered to organizations that cannot accept copyleft terms. There are no paid parts in the repository, though the same team sells a hosted edition called ProjectSend Cloud. ProjectSend contributors sign a CLA. Development is busy, yet one developer wrote about 90% of the recent commits. The recommended install is Docker Compose with MySQL and Redis; a release zip covers servers without Docker. The interface comes in 14 languages. The current code is a rebuild, so installs of the older ProjectSend Legacy move over through a migration tool rather than an upgrade.

Drafted with AI from the project's README and repository data, then checked against that data on 7 November 2026. Report a correction

How to run ProjectSend yourself

One-click install

Not listed in Umbrel, TrueNAS, CasaOS, Runtipi and Coolify. Checked against each panel’s app catalog on 12 November 2026.

Ways to install

Docker files
Dockerfile or compose file in the repository
Docker image
projectsend/projectsend: 25.8k pulls · x86-64, ARM64 · 88 MB download
Compose file
compose.yaml: 11 services (mysql, redis)
Setup effort
4 of 5, judged from the compose file
Kubernetes
No Helm chart in the repository
Desktop and mobile
No app builds in GitHub releases
Interface languages
14 languages, including German, French, Spanish, Portuguese, Dutch, Polish, Russian, Turkish, Japanese and Chinese
Show all 14

Catalan, Chinese, Czech, Dutch, French, German, Japanese, Polish, Portuguese, Russian, Spanish, Swahili, Turkish, Vietnamese

Install instructions: projectsend.org or the README on GitHub. Docker images and packages are checked weekly.

ProjectSend health: is it still maintained?

73 of 100, actively developed

Release rhythmEvery ~7 days13 releases in 12 months; latest v2.8.1
Issue repliesWithin ~3 daysMedian first reply; 92% of recent issues answered
Bus factorHigh riskOne person wrote all recent commits
  • Activity
    702 commits in the last 90 days, the latest on 11 November 2026.
    30 / 30
  • Contributors
    1 person wrote the latest 100 commits; the most active wrote 100% of them.
    2 / 20
  • Releases
    13 releases in the last 12 months; the latest, v2.8.1, on 9 November 2026.
    19 / 20
  • Replies to issues
    Maintainers answered 92% of recent issues, with a median first reply after 3 days.
    17 / 20
  • Security practices
    OpenSSF Scorecard 4.5 of 10.
    5 / 10

Read from GitHub on 12 November 2026. How the score works

ProjectSend security

Security advisories are the vulnerabilities the maintainers disclosed on GitHub, with the versions that fix them; many advisories can mean careful disclosure as much as weak code. OpenSSF Scorecard checks how a project is developed and released: reviews, protected branches, pinned dependencies, signed releases. It does not audit the code itself.

Security advisories16 published7 high; all list a fixed version
OpenSSF Scorecard4.5 of 10How the project is built and released
Security policyYesExplains how to report a vulnerability
Signed releasesNoDownloads cannot be checked against a signature

Latest advisories

All 16 advisories on GitHub

What each Scorecard check found

  • Binary files10 / 10No compiled binaries checked into the repository
  • Dangerous workflows10 / 10No risky patterns in GitHub Actions
  • License file10 / 10A license file is present
  • Maintained10 / 10Steady commits and issue activity in the last 90 days
  • Security policy10 / 10Explains how to report a vulnerability
  • Branch protection3 / 10Rules on the main branch are partly enforced
  • Pinned dependencies2 / 10Some dependencies use fixed versions
  • Best-practices badge0 / 10No OpenSSF Best Practices badge
  • Code review0 / 10Changes are merged without review
  • Fuzzing0 / 10No fuzz testing found
  • Signed releases0 / 10Releases are not signed
  • Static analysis0 / 10No static analysis found
  • Token permissions0 / 10CI tokens have broad write rights

Advisories read from GitHub on 12 November 2026. From the OpenSSF Scorecard of 9 November 2026; checks that do not apply to ProjectSend are left out.

ProjectSend license: is it open source?

ProjectSend uses GPL-2.0, an open-source license approved by the OSI. Contributors sign a contributor license agreement, which lets the owner relicense their work later.

  1. March 2014First published on GitHub.
  2. TodayGPL-2.0. A contributor license agreement is required.

ProjectSend for developers

Written in

  • PHP 77%
  • TypeScript 22%
  • Shell <1%
  • Dockerfile <1%
  • CSS <1%
  • Other <1%

Getting involved

Contributing guideYesCONTRIBUTING.mdOpen issues14On GitHub
Authors, 90 days1Of the latest 100 commits

Language shares are GitHub’s count of the code in the repository.

Alternatives to ProjectSend

  • GokapiLightweight selfhosted Firefox Send alternative without public upload. AWS S3 supported. 59 health · AGPL-3.0 · 3k stars
  • OnionShareSecurely and anonymously share files, host websites, and chat with friends using the Tor network 69 health · GPL-3.0 · 7.2k stars
  • ZiplineA ShareX/file upload server that is easy to use, packed with features, and with an easy setup! 78 health · MIT · 3.5k stars
  • DashBeamShare files nearby and beyond. 77 health · AGPL-3.0 · 10.3k stars
  • TransmissionOfficial Transmission BitTorrent client repository 66 health · GPL-3.0 · 15.4k stars

All 14 projects in File sharing

Questions about ProjectSend

Is ProjectSend open source?

Yes. ProjectSend is published under GPL-2.0, an OSI-approved open-source license.

Is ProjectSend still maintained?

Its health score is 73 of 100 (actively developed). It had 702 commits in the last 90 days, the latest on 11 November 2026, and its latest release came out on 9 November 2026.

How do I run ProjectSend?

You can run it with the Docker image projectsend/projectsend and in one click from YunoHost, Unraid and Proxmox VE Helper-Scripts. The README on GitHub has the exact steps.

What is ProjectSend written in?

ProjectSend is written mainly in PHP (77% of the code), with TypeScript (22%), by GitHub’s count of the repository.

What languages is ProjectSend available in?

The repository has interface translations for 14 languages, including German, French, Spanish, Portuguese, Dutch, Polish, Russian and Turkish.

What are the alternatives to ProjectSend?

Close alternatives in the File sharing category include Gokapi, OnionShare, Zipline.