Uppy is a sleek, modular JavaScript file uploader that integrates seamlessly with any application. It’s fast, easy to use and lets you worry about more important problems than building a file uploader.
Uppy is being developed by the folks at Transloadit, a versatile file encoding service.
Code used in the above example:
const Uppy = require('uppy/lib/core')
const Dashboard = require('uppy/lib/plugins/Dashboard')
const GoogleDrive = require('uppy/lib/plugins/GoogleDrive')
const Instagram = require('uppy/lib/plugins/Instagram')
const Webcam = require('uppy/lib/plugins/Webcam')
const Tus = require('uppy/lib/plugins/Tus')
const uppy = Uppy({ autoProceed: false })
.use(Dashboard, { trigger: '#select-files' })
.use(GoogleDrive, { target: Dashboard, host: 'https://server.uppy.io' })
.use(Instagram, { target: Dashboard, host: 'https://server.uppy.io' })
.use(Webcam, { target: Dashboard })
.use(Tus, { endpoint: 'https://master.tus.io/files/' })
.on('complete', (result) => {
console.log('Upload result:', result)
})
Try it online or read the docs for more details on how to use Uppy and its plugins.
$ npm install uppy --save
We recommend installing from npm and then using a module bundler such as Webpack, Browserify or Rollup.js.
Add CSS uppy.min.css, either to <head>
of your HTML page or include in JS, if your bundler of choice supports it — transforms and plugins are available for Browserify and Webpack.
Alternatively, you can also use a pre-built bundle from Transloadit's CDN: Edgly. In that case Uppy
will attach itself to the global window.Uppy
object.
⚠️ The bundle currently consists of most Uppy plugins, so this method is not recommended for production, as your users will have to download all plugins when you are likely using just a few.
1. Add a script to the bottom of <body>
:
<script src="https://transloadit.edgly.net/releases/uppy/v0.24.4/dist/uppy.min.js"></script>
2. Add CSS to <head>
:
<link href="https://transloadit.edgly.net/releases/uppy/v0.24.4/dist/uppy.min.css" rel="stylesheet">
3. Initialize:
<div class="UppyDragDrop"></div>
<script>
var uppy = Uppy.Core()
uppy.use(Uppy.DragDrop, { target: '.UppyDragDrop' })
uppy.use(Uppy.Tus, { endpoint: '//master.tus.io/files/' })
</script>
Tus
— resumable uploads via the open tus standardXHRUpload
— regular uploads for any backend out there (like Apache, Nginx)Transloadit
— support for Transloadit’s robust file uploading and encoding backendAwsS3
— upload to AWS S3 (also works for Google Cloud)Dashboard
— universal UI with previews, progress bars, metadata editor and all the cool stuffDragDrop
— plain and simple drag and drop areaFileInput
— even plainer “select files” buttonProgressBar
— minimal progress bar that fills itself when upload progressesStatusBar
— more detailed progress, pause/resume/cancel buttons, percentage, speed, uploaded/total sizes (included by default with Dashboard
)Informer
— send notifications like “smile” before taking a selfie or “upload failed” when all is lost (also included by default with Dashboard
)GoldenRetriever
— restores files after a browser crash, like it’s nothingThumbnailGenerator
— generates image previews (included by default with Dashboard
)Form
— collects metadata from <form>
right before an Uppy upload, then optionally appends results back to the formReduxDevTools
— for your emerging time traveling needsGoogleDrive
, Dropbox
, Instagram
, Url
— select files from Google Drive, Dropbox, Instagram and direct urls from anywhere on the web. Note thatuppy-server
is needed for these.Webcam
— snap and record those selfies 📷We aim to support IE10+ and recent versions of Safari, Edge, Chrome, Firefox, and Opera.
<input type="file">
?Having no JavaScript beats having a lot of it, so that’s a fair question! Running an uploading & encoding business for ten years though we found that in cases, the file input leaves some to be desired:
Not all apps need all of these features. A <input type="file">
is fine in many situations. But these were a few things that our customers hit / asked about enough to spark us to develop Uppy.
Transloadit’s team is small and we have a shared ambition to make a living from open source. By giving away projects like tus.io and Uppy,we’re hoping to advance the state of the art, make life a tiny little bit better for everyone, and in doing so have rewarding jobs and get some eyes on our commercial service: a content ingestion & processing platform.
Our thinking is that if just a fraction of our open source userbase can see the appeal of hosted versions straight from the source, that could already be enough to sustain our work. So far this is working out! We’re able to dedicate 80% of our time to open source and haven’t gone bankrupt just yet :D
Yep, we have Uppy React components, please see Uppy React docs.
Yes, there is an S3 plugin, please check out the docs for more.
Yes, whatever you want on the backend will work with XHRUpload
plugin, since it just does a POST
or PUT
request. Here’s a PHP backend example.
If you want resumability with the Tus plugin, use one of the tus server implementations 👌🏼
And you’ll need uppy-server
if you’d like your users to be able to pick files from Instagram, Google Drive, Dropbox or via direct urls (with more services coming).
website/src/docs/contributing.md
CHANGELOG.md
arturi | goto-bus-stop | kvz | hedgerh | ifedapoolarewaju | sadovnychyi |
richardwillars | AJvanLoon | wilkoklak | oliverpool | nqst | janko-m |
gavboulton | bertho-zero | johnunclesam | ogtfaber | sunil-shrestha | tim-kos |
phitranphitranphitran | btrice | Martin005 | martiuslim | richmeij | Burkes |
ThomasG77 | zhuangya | fortrieb | muhammadInam | rosenfeld | ajschmidt8 |
rhymes | functino | radarhere | azeemba | bducharme | chao |
csprance | danmichaelo | mrboomer | lowsprofile | gjungb | Cloud887 |
jagoPG | jcjmcclean | jessica-coursera | lucaperret | mperrando | mnafees |
pauln | phillipalexander | luarmr | sergei-zelinsky | tomsaleeba | eltercero |
xhocquet | avalla | c0b41 | franckl | kiloreux | raineluntta |
amitport |