Uppy is a sleek, modular JavaScript file uploader that integrates seamlessly
with any application. It’s fast, has a comprehensible API and lets you worry
about more important problems than building a file uploader.
Fetch files from local disk, remote URLs, Google Drive, Dropbox, Box,
Instagram or snap and record selfies with a camera
Preview and edit metadata with a nice interface
Upload to the final destination, optionally process/encode
Lightweight, modular plugin-based architecture, light on dependencies :zap:
Resumable file uploads via the open tus standard, so large
uploads survive network hiccups
Supports picking files from: Webcam, Dropbox, Box, Google Drive, Instagram,
bypassing the user’s device where possible, syncing between servers directly
via @uppy/companion
Works great with file encoding and processing backends, such as
Transloadit, works great without (all you need is
to roll your own Apache/Nginx/Node/FFmpeg/etc backend)
Sleek user interface :sparkles:
Optional file recovery (after a browser crash) with
Golden Retriever
Speaks several languages (i18n) :earth_africa:
Built with accessibility in mind
Free for the world, forever (as in beer 🍺, pizza 🍕, and liberty 🗽)
Cute as a puppy, also accepts cat pictures :dog:
Installation
1npm install @uppy/core @uppy/dashboard @uppy/tus
Add CSS
uppy.min.css,
either to your HTML page’s <head> or include in JS, if your bundler of choice
supports it.
Alternatively, you can also use a pre-built bundle from Transloadit’s CDN: Smart
CDN. In that case Uppy will attach itself to the global window.Uppy object.
⚠️ The bundle 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 only a few.
React — components to integrate Uppy UI plugins
with React apps
React Native — basic Uppy component for React
Native with Expo
Browser Support
We aim to support recent versions of Chrome, Firefox, and Safari.
FAQ
Why not use <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:
We received complaints about broken uploads and found that resumable uploads
are important, especially for big files and to be inclusive towards people on
poorer connections (we also launched tus.io to attack that
problem). Uppy uploads can survive network outages and browser crashes or
accidental navigate-aways.
Uppy supports editing meta information before uploading.
Uppy allows cropping images before uploading.
There’s the situation where people are using their mobile devices and want to
upload on the go, but they have their picture on Instagram, files in Dropbox
or a plain file URL from anywhere on the open web. Uppy allows to pick files
from those and push it to the destination without downloading it to your
mobile device first.
Accurate upload progress reporting is an issue on many platforms.
Some file validation — size, type, number of files — can be done on the client
with Uppy.
Uppy integrates webcam support, in case your users want to upload a
picture/video/audio that does not exist yet :)
A larger drag and drop surface can be pleasant to work with. Some people also
like that you can control the styling, language, etc.
Uppy is aware of encoding backends. Often after an upload, the server needs to
rotate, detect faces, optimize for iPad, or what have you. Uppy can track
progress of this and report back to the user in different ways.
Sometimes you might want your uploads to happen while you continue to interact
on the same single page.
Not all apps need all these features. An <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.
Why is all this goodness free?
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 only 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 yet. :D
Does Uppy support S3 uploads?
Yes, please check out the docs for more
information.
Can I use Uppy with Rails/Node.js/Go/PHP?
Yes, whatever you want on the backend will work with @uppy/xhr-upload plugin,
since it only does a POST or PUT request. Here’s a
PHP backend example.
And you’ll need @uppy/companion 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).
Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
Info: Found text in security policy: SECURITY.md:1
Reason
no binaries found in the repo
Reason
license file detected
Details
Info: project has a license file: LICENSE:0
Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
packaging workflow detected
Details
Info: Project packages its releases by way of GitHub Actions.: .github/workflows/companion-deploy.yml:41
Reason
Found 6/15 approved changesets -- score normalized to 4
Reason
dependency not pinned by hash detected -- score normalized to 2
Details
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/bundlers.yml:129: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/bundlers.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/bundlers.yml:171: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/bundlers.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/bundlers.yml:201: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/bundlers.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/bundlers.yml:226: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/bundlers.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/bundlers.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/bundlers.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/bundlers.yml:32: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/bundlers.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/bundlers.yml:40: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/bundlers.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/bundlers.yml:77: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/bundlers.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/bundlers.yml:91: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/bundlers.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:40: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:46: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:54: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:73: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:79: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:87: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/ci.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/companion-deploy.yml:23: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/companion-deploy.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/companion-deploy.yml:36: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/companion-deploy.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/companion-deploy.yml:49: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/companion-deploy.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/companion-deploy.yml:59: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/companion-deploy.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/companion-deploy.yml:80: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/companion-deploy.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/companion.yml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/companion.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/companion.yml:35: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/companion.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/companion.yml:43: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/companion.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/e2e.yml:51: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/e2e.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/e2e.yml:73: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/e2e.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/e2e.yml:81: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/e2e.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/e2e.yml:160: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/e2e.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/e2e.yml:225: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/e2e.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/e2e.yml:233: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/e2e.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/e2e.yml:244: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/e2e.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/e2e.yml:249: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/e2e.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/e2e.yml:286: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/e2e.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/linters.yml:28: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/linters.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/linters.yml:31: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/linters.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/linters.yml:50: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/linters.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/linters.yml:52: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/linters.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/lockfile_check.yml:23: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/lockfile_check.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/lockfile_check.yml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/lockfile_check.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/lockfile_check.yml:37: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/lockfile_check.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/manual-cdn.yml:28: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/manual-cdn.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/manual-cdn.yml:34: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/manual-cdn.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/manual-cdn.yml:42: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/manual-cdn.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release-candidate.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/release-candidate.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release-candidate.yml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/release-candidate.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release-candidate.yml:37: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/release-candidate.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/release.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/release.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:38: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/release.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:143: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/release.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/release.yml:155: update your workflow using https://app.stepsecurity.io/secureworkflow/transloadit/uppy/release.yml/main?enable=pin
Warn: containerImage not pinned by hash: Dockerfile:1
Warn: containerImage not pinned by hash: Dockerfile:20: pin your Docker image by updating node:18.17.1-alpine to node:18.17.1-alpine@sha256:3482a20c97e401b56ac50ba8920cc7b5b2022bfc6aa7d4e4c231755770cf892f
Warn: containerImage not pinned by hash: Dockerfile.test:1: pin your Docker image by updating node:18.17.1-alpine to node:18.17.1-alpine@sha256:3482a20c97e401b56ac50ba8920cc7b5b2022bfc6aa7d4e4c231755770cf892f
Warn: npmCommand not pinned by hash: Dockerfile.test:14
Warn: npmCommand not pinned by hash: .github/workflows/bundlers.yml:137
Warn: npmCommand not pinned by hash: .github/workflows/bundlers.yml:188
Warn: npmCommand not pinned by hash: .github/workflows/bundlers.yml:209
Warn: npmCommand not pinned by hash: .github/workflows/bundlers.yml:234
Warn: npmCommand not pinned by hash: .github/workflows/bundlers.yml:99
Warn: downloadThenRun not pinned by hash: .github/workflows/companion-deploy.yml:87
Warn: downloadThenRun not pinned by hash: .github/workflows/e2e.yml:138
Info: 0 out of 47 GitHub-owned GitHubAction dependencies pinned
Info: 10 out of 13 third-party GitHubAction dependencies pinned
Info: 0 out of 3 containerImage dependencies pinned
Info: 0 out of 6 npmCommand dependencies pinned
Info: 0 out of 2 downloadThenRun dependencies pinned
no effort to earn an OpenSSF best practices badge detected
Reason
detected GitHub workflow tokens with excessive permissions
Details
Warn: no topLevel permission defined: .github/workflows/bundlers.yml:1
Warn: no topLevel permission defined: .github/workflows/ci.yml:1
Warn: no topLevel permission defined: .github/workflows/companion-deploy.yml:1
Warn: no topLevel permission defined: .github/workflows/companion.yml:1
Warn: no topLevel permission defined: .github/workflows/linters.yml:1
Warn: no topLevel permission defined: .github/workflows/lockfile_check.yml:1
Warn: no topLevel permission defined: .github/workflows/manual-cdn.yml:1
Warn: no topLevel permission defined: .github/workflows/release-candidate.yml:1
Warn: no topLevel permission defined: .github/workflows/release.yml:1
Info: no jobLevel write permissions found
Reason
project is not fuzzed
Details
Warn: no fuzzer integrations found
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Warn: 0 commits out of 29 are checked with a SAST tool
Reason
68 existing vulnerabilities detected
Details
Warn: Project is vulnerable to: PYSEC-2018-66 / GHSA-562c-5r94-xh97
Warn: Project is vulnerable to: PYSEC-2019-179 / GHSA-5wv5-4vpf-pj6m
Warn: Project is vulnerable to: PYSEC-2023-62 / GHSA-m2qf-hxjv-5gpq
Warn: Project is vulnerable to: GHSA-84pr-m4jr-85g5
Warn: Project is vulnerable to: PYSEC-2024-71 / GHSA-hxwh-jpp2-84pm
Warn: Project is vulnerable to: PYSEC-2020-43 / GHSA-xc3p-ff3m-f46v
Warn: Project is vulnerable to: GHSA-2g68-c3qc-8985
Warn: Project is vulnerable to: PYSEC-2020-157 / GHSA-3p3h-qghp-hvh2
Warn: Project is vulnerable to: GHSA-f9vj-2wh5-fj8j
Warn: Project is vulnerable to: PYSEC-2019-140 / GHSA-gq9m-qvpx-68hc
Warn: Project is vulnerable to: PYSEC-2017-43 / GHSA-h2fp-xgx6-xh6f
Warn: Project is vulnerable to: PYSEC-2023-221 / GHSA-hrfv-mqp8-q5rw
Warn: Project is vulnerable to: GHSA-j544-7q9p-6xp8
Warn: Project is vulnerable to: PYSEC-2023-57 / GHSA-px8h-6qxv-m22q
Warn: Project is vulnerable to: GHSA-q34m-jh98-gwm2
Warn: Project is vulnerable to: PYSEC-2023-58 / GHSA-xg9f-g7g7-2323
Warn: Project is vulnerable to: PYSEC-2022-203
Warn: Project is vulnerable to: GHSA-968p-4wvh-cqc8
Warn: Project is vulnerable to: GHSA-mm7r-265w-jv6f
Warn: Project is vulnerable to: GHSA-9m4x-8w29-r78g
Warn: Project is vulnerable to: GHSA-q24h-5rq3-63j9
Warn: Project is vulnerable to: GHSA-r5fx-8r73-v86c
Warn: Project is vulnerable to: GHSA-28hp-fgcr-2r4h
Warn: Project is vulnerable to: GHSA-89mq-4x47-5v83
Warn: Project is vulnerable to: GHSA-5cp4-xmrw-59wf
Warn: Project is vulnerable to: GHSA-mhp6-pxh8-r675
Warn: Project is vulnerable to: GHSA-2qqx-w9hr-q5gx
Warn: Project is vulnerable to: GHSA-2vrf-hf26-jrp5
Warn: Project is vulnerable to: GHSA-mqm9-c95h-x2p6
Warn: Project is vulnerable to: GHSA-prc3-vjfx-vhm9
Warn: Project is vulnerable to: GHSA-qwqh-hm9m-p5hr
Warn: Project is vulnerable to: GHSA-wf5p-g6vw-rhxx
Warn: Project is vulnerable to: GHSA-jr5f-v2jv-69x6
Warn: Project is vulnerable to: GHSA-qwcr-r2fm-qrc7
Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
Warn: Project is vulnerable to: GHSA-pxg6-pf52-xh8x
Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
Warn: Project is vulnerable to: GHSA-9vvw-cc9w-f27h
Warn: Project is vulnerable to: GHSA-gxpj-cx7g-858c
Warn: Project is vulnerable to: GHSA-wm7h-9275-46v2
Warn: Project is vulnerable to: GHSA-67mh-4wv8-2f99
Warn: Project is vulnerable to: GHSA-qw6h-vgh9-j6wx
Warn: Project is vulnerable to: GHSA-mph8-6787-r8hw
Warn: Project is vulnerable to: GHSA-7mhc-prgv-r3q4
Warn: Project is vulnerable to: GHSA-c7qv-q95q-8v27
Warn: Project is vulnerable to: GHSA-2p57-rm9w-gvfp
Warn: Project is vulnerable to: GHSA-p6mc-m468-83gw
Warn: Project is vulnerable to: GHSA-35jh-r3h4-6jhm
Warn: Project is vulnerable to: GHSA-5v2h-r2cx-5xgj
Warn: Project is vulnerable to: GHSA-rrrm-qjm4-v8hf
Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
Warn: Project is vulnerable to: GHSA-w9mr-4mfr-499f
Warn: Project is vulnerable to: GHSA-mwcw-c2x4-8c55
Warn: Project is vulnerable to: GHSA-r683-j2x4-v87g
Warn: Project is vulnerable to: GHSA-9wv6-86v2-598j
Warn: Project is vulnerable to: GHSA-rhx6-c78j-4q9w
Warn: Project is vulnerable to: GHSA-gcx4-mw62-g8wm
Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
Warn: Project is vulnerable to: GHSA-m6fv-jmcg-4jfg
Warn: Project is vulnerable to: GHSA-cm22-4g7w-348p
Warn: Project is vulnerable to: GHSA-g4rg-993r-mgx7
Warn: Project is vulnerable to: GHSA-3g92-w8c5-73pq
Warn: Project is vulnerable to: GHSA-c76h-2ccp-4975
Warn: Project is vulnerable to: GHSA-x8rq-rc7x-5fg5
Warn: Project is vulnerable to: GHSA-4vvj-4cpr-p986 / GHSA-64vr-g452-qvp3
Warn: Project is vulnerable to: GHSA-9cwx-2883-4wfx
Warn: Project is vulnerable to: GHSA-vg6x-rcgg-rjx6
Warn: Project is vulnerable to: GHSA-776f-qx25-q3cc
Score
4.1
/10
Last Scanned on 2025-03-10
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.