head to head · open source

uppy vs projectsend

uppy has 31,016 GitHub stars, 2,111 forks, 186 open issues and last shipped today. projectsend has 2,027 stars, 360 forks, 9 open issues and last shipped yesterday. uppy leads on adoption by 1,430% (31,016 vs 2,027 stars). uppy is written in TypeScript under MIT; projectsend is written in PHP under GPL-2.0. uppy has attracted 7% as many forks as stars, projectsend 18%. uppy was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (open-source), so they are genuine substitutes rather than adjacent tools.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

uppy ★ 31K projectsend ★ 2.0K category Productivity & Utilities

← all 20902 open source comparisons

Side by side

uppy projectsend
GitHub stars ★ 31K ★ 2.0K
License MIT GPL-2.0
Written in TypeScript PHP
Last push 2026-10-08 2026-10-07
Forks ⑂ 2.1K ⑂ 360
Self-hosting Yes Yes
Data ownership Your server Your server

pick uppy if

  • You weight community size — 31K stars and counting
  • You want the MIT license terms
  • Your stack matches TypeScript
  • You value the larger contributor base for long-term maintenance

full uppy profile →

pick projectsend if

  • You want the projectsend feature set and don't need the biggest community
  • You prefer the GPL-2.0 license terms
  • Your stack matches PHP
  • You evaluated both and projectsend fits your workflow better

full projectsend profile →

About uppy

Uppy is an MIT licensed, TypeScript built, modular JavaScript file uploader for web browsers that drops into any web application, aimed at developers who would rather wire up plugins than build file uploading from scratch.

read the full uppy overview →

About projectsend

ProjectSend is a self hosted, GPLv2 licensed PHP and MySQL application that lets you share files with clients from your own server, with each client signing in to a private page, and it is aimed at freelancers, agencies and teams who would rather not hand client documents to a third party service.

read the full projectsend overview →

More in Productivity & Utilities

n8n ★ 207K Excalidraw ★ 134K RustDesk ★ 125K LocalSend ★ 94K AppFlowy ★ 77K OBS Studio ★ 77K

Related comparisons

localsend vs uppy localsend vs rclone localsend vs copyparty localsend vs files localsend vs yazi localsend vs spacedrive localsend vs nextcloud localsend vs cloudreve openclaw vs khoj open-webui vs open-notebook open-webui vs khoj appflowy vs affine appflowy vs memos appflowy vs plane appflowy vs joplin mem0 vs memos n8n vs langchain n8n vs browser-use firecrawl vs browser-use n8n vs langgraph n8n vs frigate n8n vs lightpanda n8n vs proxmoxve n8n vs activepieces

More File Management & Sync projects

Compare either of these against the rest of the File Management & Sync field.

uppy vs LocalSend uppy vs rclone uppy vs copyparty uppy vs Files uppy vs yazi uppy vs Spacedrive uppy vs Nextcloud uppy vs cloudreve uppy vs superfile uppy vs ranger uppy vs Seafile uppy vs PairDrop

Frequently asked questions

Is uppy or projectsend more popular?

uppy has 31,016 GitHub stars and projectsend has 2,027. uppy has the larger community by that measure.

Are uppy and projectsend free?

Both are open source. uppy is licensed under MIT and projectsend under GPL-2.0. Neither carries a licence fee.

What is the difference between uppy and projectsend?

uppy is written in TypeScript and projectsend in PHP. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, uppy or projectsend?

Choose uppy if you want the larger community (31,016 stars) or its MIT licence terms. Choose projectsend if its feature set, stack or GPL-2.0 licence fits better. Both are self-hostable.