HTTP-based
Built as a layer on top of the popular HTTP protocol, tus can easily be integrated into applications using existing libraries, proxies and firewalls, and can be used directly from any website.
People are sharing more and more photos and videos every day, but mobile networks remain fragile. Platform APIs are often a mess and every project builds its own file uploader. There are a thousand one-week projects that barely work, when all we need is one real project. One project done right.
We are going to do this right. Our aim is to make file uploads reliable once and for all. tus is a new, open protocol for resumable uploads built on HTTP. It offers simple, cheap and reusable stacks for clients and servers. It supports any language, any platform and any network.
It may seem to be an impossible dream. Perhaps that is because no one has solved it yet. Still, we are confident and we are going to give it our best shot. Join us on GitHub and help us make the world a better place. Say "No!" to lost cat videos! Say "Yes!" to tus!
HTTP-based
Built as a layer on top of the popular HTTP protocol, tus can easily be integrated into applications using existing libraries, proxies and firewalls, and can be used directly from any website.
Production-ready
tus is ready for use in production. It has undergone numerous rounds of improvements and received valuable feedback from people working at Vimeo, Google and multiple other well-known companies.
Open source
tus is brought to you by the people behind Transloadit but the source code to all of our implementations, this website and even the protocol itself is accessible to everyone under MIT license, directly from our GitHub organization.
Minimalistic design…
The specification only requires a very small set of features to be implemented by clients and servers. tus embraces simplicity, fast development and iteration speed for everyone.
…yet still extensible
tus nevertheless features a sizable list of extensions that introduce additional functionality, such as parallel uploading or checksums and expiration. All of these may be implemented according to your preferences.
Community-owned
We believe in an open and accessible evolution of this protocol. At any stage since the beginning of tus, feedback has been appreciated and integrated. We look forward to your contributions as well.
Additionally, there are many other projects built and maintained by our community.
jukuisma commented on Add support for client certificates in tus/tus-py-client
github-actions pushed 1 commit to tus/draft-digest-fields-problem-types
mackinleysmith commented on s3store: Pass Content-Type from `filetype` metadata field to S3 in tus/tusd
Acconut closed pull request s3store: Pass Content-Type from `filetype` metadata field to S3 for tus/tusd
Acconut approved pull request s3store: Pass Content-Type from `filetype` metadata field to S3 in tus/tusd
Acconut pushed 1 commit to tus/tus-android-client
Acconut closed pull request Bump org.robolectric:robolectric from 4.14 to 4.14.1 for tus/tus-android-client
dependabot opened pull request Bump org.robolectric:robolectric from 4.14 to 4.14.1 for tus/tus-android-client
dependabot created a new branch in tus/tus-android-client: dependabot/gradle/org.robolectric-robolectric-4.14.1
clarifysky is now watching tus/tus-js-client
github-actions pushed 1 commit to tus/draft-digest-fields-problem-types
siffogh is now watching tus/tus-js-client
mackinleysmith commented on feat(s3store): pass the contentType or filetype metadata field to S3 if supplied in tus/tusd
aisensiy forked tus/tus-java-client
elishowk is now watching tus/tus-node-server
perslev is now watching tus/tus-js-client
blacktear23 forked tus/tusd
Acconut commented on feat(s3store): pass the contentType or filetype metadata field to S3 if supplied in tus/tusd
mackinleysmith commented on feat(s3store): pass the contentType metadata field to S3 if supplied in tus/tusd