What ProjectSend 2 Needs to Run
ProjectSend 2 runs on Docker or on a Linux server with PHP 8.4+, MySQL 8.0+, and nginx. Shared hosting without shell access does not meet the requirements.
· By ProjectSend Team

ProjectSend 2 has two supported install paths: Docker and the release zip. With Docker, you need Docker Engine and Compose — the production compose file handles everything else. From the zip, you need PHP 8.4 or newer, MySQL 8.0 or newer, a web server with PHP-FPM, shell access, a background worker, and scheduled tasks. Shared hosting without shell access is not supported.
This note is based on ProjectSend 2.8.1 (November 2026).
With Docker
Docker is the setup we recommend. All you need is Docker Engine and Compose — PHP, MySQL, nginx, the background worker, and the scheduled tasks are wired into the production compose file. The official image (projectsend/projectsend on Docker Hub, available for amd64 and arm64) has been part of every release since 2.1.0.
The quickstart downloads the compose file, sets your APP_URL and the passwords, and starts the stack:
curl -O https://raw.githubusercontent.com/projectsend/projectsend/main/docker/production/compose.example.yaml
# edit APP_URL and the passwords in it, then:
docker compose -f compose.example.yaml up -d
# → open APP_URL — the setup screen creates your admin accountThe Docker guide covers where your database and uploads live, how to survive reboots, and how to run updates. The section on volumes is the part to read before your first install — it is what keeps your data safe across image upgrades.
From the release zip
You can download the release zip and install it on any server with shell access. It takes about ten minutes. It is not an install you can do over FTP alone. You will need:
- PHP 8.4 or newer (both the CLI and PHP-FPM), with extensions: bcmath, ctype, curl, dom, fileinfo, filter, gd, iconv, intl, json, ldap, mbstring, openssl, pcntl, pdo_mysql, session, simplexml, tokenizer, zip. Note: ldap is required even if you do not use LDAP — a library ProjectSend depends on declares it.
- MySQL 8.0 or newer. We test on MySQL 8.4 LTS.
- A web server with PHP-FPM. nginx is strongly recommended. ProjectSend runs on Apache and LiteSpeed too, but on nginx file downloads are handed directly to the web server instead of holding a PHP worker open for the duration — a meaningful capacity difference on a busy install.
- Shell access to the server — for migrations, managing file permissions, and running updates.
- A background worker that runs as a persistent service, handling email sending and building zip archives of multiple files. Without it, no email is ever sent and zip downloads never finish. The background worker section of the install guide has the systemd configuration. Two things worth noting:
Restart=alwaysmatters (the worker restarts when you save email settings), and the queue name--queue=default,zipsmatters (a worker withoutzipswill send email but never finish a zip download). - Scheduled tasks — one cron entry every minute, which gives ProjectSend its heartbeat for housekeeping: expired files, abandoned uploads, and version checks.
Redis is optional — the default configuration uses MySQL for sessions, cache, and queues. The install guide covers each requirement in detail, including the web server configuration blocks and the cron entry.
Docker or the zip?
Both paths install the same software. The difference is in what you manage. With Docker, the background worker and scheduled tasks are part of the compose file — nothing to set up separately. Updates are pulling a new image and restarting the stack. With the zip, you set up the worker as a systemd service and add one cron entry; updates run update.sh. Redis is included in Docker and optional from the zip. Shell access is needed for both.
If you can run Docker, that is the simpler path to maintain. The note Running ProjectSend with Docker covers the Docker path in full, including the compose file, volumes, and backups.
What about shared hosting?
The 2.x does not run on typical PHP-only hosting — the kind managed through a control panel without shell access. Three things are needed that most shared hosting plans do not provide: shell access (for migrations, permissions, and updates), a persistent background process (the queue worker), and scheduled tasks.
GitHub issues #1663 and #1803, opened in 2026, document what people run into when they try: open_basedir restrictions block core functions, and there is no supported way to keep the queue worker running. Installing from the zip on shared hosting also breaks at the update step — update.sh requires shell access. If Docker is not an option, a VPS with shell access is the alternative path.
Questions
If something in this note does not match what you are seeing, ask in the Discord community or open an issue on GitHub. The installation docs live in the app repository — corrections are welcome as pull requests. You can browse all notes on setting up ProjectSend in the Installation category.
Frequently asked questions
- Can I install ProjectSend 2 on shared hosting?
- No. The 2.x requires shell access, a background worker that runs as a persistent process, and scheduled tasks. Most shared hosting plans do not provide these.
- What PHP version does ProjectSend 2 require?
- PHP 8.4 or newer, both the CLI and PHP-FPM. The ldap extension is required even if you do not use LDAP — it is declared by a library ProjectSend depends on.
- Do I need Redis?
- Redis is optional. ProjectSend installs fine using MySQL for sessions, cache, and queues. The Docker setup includes Redis; from the zip, you can add it later.
- Which web server should I use?
- nginx is recommended. ProjectSend runs on Apache and LiteSpeed too, but on nginx file downloads are handed directly to the web server rather than holding a PHP worker open — a meaningful capacity difference. The install guide at /docs/install covers configuration for each.
- What is the background worker?
- A system service (systemd on Linux) that processes ProjectSend's queue — sending email and building zip archives of multiple files. Without it, no email is sent and zip downloads never complete.
ProjectSend Team. Written by the people who build and maintain ProjectSend, the open-source client portal developed in the open since 2011.
Keep reading
- Common ProjectSend Install ErrorsFour common zip install errors -- Apache AllowOverride, MariaDB compatibility, PHP-FPM permissions, and reverse proxy headers -- and how to fix each.
- Email via OAuth with Microsoft 365 or GmailHow to configure ProjectSend to send email through Microsoft 365 or Gmail using OAuth rather than SMTP passwords, with app registration steps and common fixes.
- Running ProjectSend behind a reverse proxyMost reverse proxy problems with ProjectSend come down to two settings: TRUSTED_PROXIES for 419 errors, and buffer sizes for 502 on some pages.
ProjectSend is free and open source
It's GPL v2 and built in the open. If something here didn't work for you, or you know a better way to do it, let us know: that's how the docs and the software get better.
Prefer not to run a server? ProjectSend Cloud is the hosted version, run by the same people.