Zipline is a self-hosted file upload and sharing server — the “next generation ShareX server”. You run it on your own machine behind Docker with PostgreSQL, point ShareX, its web uploader or the HTTP API at it, and every screenshot, screen recording or file you share lands on your own domain with a short link you control instead of on somebody else’s host.
The documented setup is a Compose stack of ghcr.io/diced/zipline plus postgres:16, with three bind mounts for uploads, public assets and themes, and two secrets you must generate yourself: CORE_SECRET (32 characters) and the database password used in DATABASE_URL. It listens on port 3000 by default and the port and hostname are both configurable. Two things are worth knowing before you start: the published images need a CPU with AVX support, and Zipline v4 was a complete rewrite with no in-place upgrade from v3 — migrating means exporting your v3 data and importing it with the built-in importer.
Anyone who shares screenshots and clips all day and wants a permanent URL for them on their own infrastructure, rather than links that expire with a third-party service. If you want a send-once transfer service instead of a growing library, Transfer.zip covers that habit.