tus/tusd

Reference server implementation in Go of tus: the open protocol for resumable file uploads

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 30 minutes ago
Added to GitGenius on September 17th, 2026
Created on March 16th, 2013
Open Issues & Pull Requests: 83 (+0)
GitHub issues: Enabled
Number of forks: 555
Total Stargazers: 3,876 (+0)
Total Subscribers: 64 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 16.1 hours
Mean response time: 32.7 days
90th percentile: 12.6 days
Tracked items: 111

Most active contributors

Sign in to see contributor activity.

How this project is maintained

67% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "question" is answered fastest, typically in about 4 hours, while "bug" waits about 24 hours. Three people close 85% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 39
New in 7 days: 2
Closed in 7 days: 5
Avg open age: 726 days
Stale 30+ days: 34
Stale 90+ days: 33

Recent activity

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

Top labels

  • question (44)
  • bug (40)
  • enhancement (24)
  • breaking change (3)

Detailed Description

tusd is a reference server implementation in Go of the tus protocol for resumable file uploads.

The tool addresses the problem of interrupted file uploads by implementing the tus protocol, which allows uploads to be paused and resumed without re-uploading previously transmitted data. This is particularly valuable when network interruptions, user pauses, or server outages occur. The protocol uses HTTP as its transport mechanism and specifies a flexible method for handling uploads of arbitrary size.

The server supports multiple storage backends including local disk, Google Cloud Storage, and AWS S3 or any S3-compatible storage system. Its modular and extensible architecture means that support for additional cloud providers can be added without major restructuring. This flexibility makes it suitable for projects that need resumable uploads across different infrastructure choices, from simple single-server deployments to cloud-native applications.

The project maintains active development with regular commits addressing bug fixes, feature enhancements, and protocol compliance. Pull requests receive timely review and feedback from maintainers. The codebase shows consistent attention to code quality and testing practices. Documentation is comprehensive and kept current alongside code changes.