diced/zipline

A ShareX/file upload server that is easy to use, packed with features, and with an easy setup!

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 20 minutes ago
Added to GitGenius on September 20th, 2026
Created on April 22nd, 2020
Open Issues & Pull Requests: 6 (+0)
GitHub issues: Enabled
Number of forks: 256
Total Stargazers: 3,422 (+0)
Total Subscribers: 13 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 21.3 hours
Mean response time: 4.3 days
90th percentile: 9.2 days
Tracked items: 279

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Practically every issue opened in the past year has drawn a reply. 96% of issues opened in the past year have since been closed. Three people close 87% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 1
Closed in 7 days: 2
Avg open age: 128 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 1
Closed in 7 days: 2
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (267)
  • v4 (16)
  • v3 (5)

Detailed Description

Zipline is a ShareX-compatible file upload server that lets users quickly set up self-hosted file sharing with a web interface.

The tool solves the problem of needing a private, self-controlled alternative to cloud file-sharing services. It works by providing a server that accepts file uploads via ShareX integration or direct web upload, stores them locally or on S3-compatible storage, and serves them back through a web gallery. Users can configure authentication, set quotas, tag files, shorten URLs, and receive notifications through Discord or HTTP webhooks. The server includes a progressive web app interface built with React and Mantine, allowing browsing and management of uploaded files through a modern UI.

Zipline suits developers and teams who want to host their own file-sharing infrastructure without relying on third-party services. It works well for screenshot sharing, file distribution, and building custom upload workflows. The Docker setup is the recommended deployment path, though manual installation from source is also supported. The tool requires a CPU with AVX support and can be configured to use either local filesystem storage or S3 backends. Custom themes can be applied to match organizational branding.

The project maintains active development with regular commits to the main branch and a functioning CI/CD pipeline. The maintainers provide comprehensive documentation covering Docker deployment, configuration options, and API usage. Community engagement is supported through a Discord server for users to ask questions and share feedback.