Our take
Activeregular commits and releases- Activity
- 66
- Community
- 37
- Issues
- 57
- Pull requests
- 34
+51 stars in the last 30 days
- Slower to merge pull requests than 86% of the projects we track
Zipline is a feature-rich choice for self-hosted uploads, with a strong recent release pace but notable reliance on one contributor.
Good fit if
- You want a ShareX-compatible upload destination with a web interface and file organization.
- You can operate Docker Compose and PostgreSQL, or meet the documented Node.js requirements for a manual install.
- You value recent maintenance and releases, and are comfortable with the project's concentrated contributor base.
Look elsewhere if
- Your host lacks an AVX-capable CPU, which Zipline's provided images require.
- You need a lightweight upload service without a PostgreSQL database or account-management features.
- You require a project whose maintenance is distributed across contributors, since most measured contributions come from one person.
All health signals
| Last commit | 2026-10-04 (6 days ago) |
|---|---|
| Commits, last 90 days | 59 |
| Releases, last 12 months | 16 (latest v4.8.0, 2026-09-27) |
| Contributors | 31 (top contributor: 95% of commits) |
| Issues closed, last 90 days | 11 (typically closed in 6 days) |
| Pull requests merged, last 90 days | 8 (typically merged in 4 days) |
| Project age | 6 years |
Checked on 2026-10-11 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
3,503Forks
259Change since Nov 14, 2026: 0 stars·-2 forks
Overview
Zipline is a self-hosted upload and file-sharing server designed to work with ShareX and other upload clients. It gives users a place to send files, images, and videos, then manage and share them through a web interface rather than relying on a third-party hosting service.
It is aimed at people who want more than a basic upload endpoint: Zipline combines file organization, sharing controls, authentication, and integrations in one service. The project is actively maintained, though its measured contributor activity is highly concentrated in one person.
Key Features
- Accept uploads from ShareX and other clients through its API.
- Organize files with folders and tags, and create shortened URLs.
- Share content using embeds, password protection, and Discord or HTTP webhooks.
- Protect accounts with OAuth2, two-factor authentication, and passkeys.
- Compress images and generate video thumbnails.
- Store uploads locally or use an S3-compatible datasource.
- Run as a progressive web app, with quotas, invites, and custom themes.
Use Cases
- ShareX users can upload screenshots and other files to a server they control.
- A small team can keep shared uploads organized with folders, tags, and quotas.
- Community administrators can publish images or clips with password protection and Discord notifications.
- Developers can integrate uploads into scripts or services through the API and webhooks.
What you need
Detected in the repository
- Node.js >=22 (from package.json)
- A Dockerfile, so it can run in a container; a Compose file sets up the related services
- A test suite and automated checks on GitHub Actions
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
The recommended setup uses Docker Compose. Save the Compose configuration and environment variables from the README or the Docker setup guide, then start the services:
docker compose up -d
Set the required CORE_SECRET and PostgreSQL password before starting. See the documentation for configuration and storage options.
Alternatives
- chibisafe: Chibisafe is a file vault for uploads and link sharing, while Zipline also focuses on ShareX integrations and managing files, folders, tags, and links.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| zipline | TypeScript | MIT | 3.5k | Active |
| chibisafe | TypeScript | MIT | 2.8k | Quiet |
Considerations
- Docker deployments need PostgreSQL, persistent storage for uploads, and an AVX-capable CPU. The README warns that provided images do not support non-AVX CPUs.
- Manual installation requires Node.js 22 or newer and a PostgreSQL server.
- Zipline v4 was a complete rewrite, so migrating from v3 requires exporting data and using v4's importer rather than performing an in-place upgrade.
- The project has recent commits and releases and handles issues and pull requests in a relatively short time, but measured contributions are heavily concentrated in one person. That creates a maintenance continuity risk even while the project is active.
Found this useful?
Share it with someone who would like zipline.