Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
DS
Self-host Drawpile Server
updated Nov 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
The dedicated server for Drawpile, a collaborative drawing program where several people paint on one canvas at the same time. The desktop app connects to it over TCP on port 27750, and sessions can be password protected, kept on disk and moderated through a JSON admin API. This entry is the server only: drawing happens in the Drawpile desktop or mobile client, not in a browser page served by it.
Pick Drawpile Server when a group wants to paint, draw or animate on one canvas together and you want to host the sessions yourself. This entry is the dedicated server only: people join from the Drawpile desktop or Android app (the README says it runs on Windows, Linux, macOS and Android) over TCP port 27750, and there is no drawing page served by the server. The server keeps sessions and settings in files and a configuration database, and offers a JSON admin API. It is GPL-3.0 C++ on Qt. Our snippet follows `pkg/docker/README.md` with the image pinned to `drawpile/drawpile-srv:2.3.1` (released 2026-10-21; the README's own examples still show 2.2.0) as a Compose file with file-backed sessions and a configuration database in a named volume, and the web admin API published on 127.0.0.1 only with a login generated into `.env`. Neither the README nor the docs give a RAM figure, so our 128 MB floor is an estimate. In the catalog, draw.io makes diagrams, Excalidraw and WBO are whiteboards used in the browser, and OurBoard is a canvas of notes and images; Drawpile Server is for shared painting with the Drawpile client, and as set up here it fits only if everyone installs that app: Drawpile's hosted browser client (web.drawpile.net) can join a self-hosted server only if you add `--websocket-port` and a TLS reverse proxy, which our snippet does not.
What you need
Any VPS with at least 128 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
Drawpile's Docker README, server API documentation and source flag these before you rely on it:
non-negotiableThe server serves no drawing page. With this snippet every participant needs the installed Drawpile client, because the hosted browser client (web.drawpile.net, the only option on iPad and iPhone) needs --websocket-port and a TLS reverse proxy that we do not configure. Our run only checks that the admin API answers /api/status/ and that port 27750 accepts a TCP connection; we did not join a session or draw.
non-negotiableThe admin API docs say it must not be publicly accessible, and the Docker README publishes it as 127.0.0.1:27780 with --web-admin-access all, the setting it says to use inside the container. Our snippet does the same and reads its user:password from the DRAWPILESRV_WEB_ADMIN_AUTH variable that the source documents as an alternative to --web-admin-auth. Port 27750 is published on all interfaces, and by default (allowGuests and allowGuestHosts are true, 25 sessions of up to 99 MB) anyone who can reach it can host a session; set allowGuestHosts to false through the admin API on a public server.
non-negotiableLogins are guest logins by default. doc/logins.md still describes a userfile backend, but the 2.3.1 server has no such option: registered accounts are managed through the admin API's /api/accounts/, or through --extauth. Our snippet creates no accounts, so people in a session are identified only by the name they choose and any session password they set.
non-negotiableThe server source has --ssl-cert and --ssl-key options for TLS; our snippet passes neither, so we make no claim about encryption on port 27750.
non-negotiableSessions and the settings database live in /home/drawpile (the drawpile-data volume, through --sessions and --database), so back that volume up. Serverwide limits such as the session size limit and the maximum number of sessions are settings in the admin API, not Compose options.
non-negotiableDocker Hub lists amd64 and arm64 builds for this tag. The GitHub releases page also carries a continuous pre-release; we pin the stable 2.3.1 tag instead.
Drawpile Server used 3 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 128 MB.
Is the Drawpile Server install snippet verified?
The Drawpile Server install snippet is marked verified on Ubuntu 26.04 (Nov 2026).