Blog

Uppy 6.0 is here, freshly groomed and ready to play. Rather than teaching it new tricks, we spent this release mostly cleaning up after our faithful file-uploading companion. Every pup needs a bath eventually.

We rewrote @uppy/aws-s3 from scratch, folded four packages into @uppy/core, and dropped a fifth entirely.

If you have ever debugged a duplicate-version bug in your lockfile or given up halfway through configuring an S3 upload, this release is for you.

@uppy/aws-s3 has been Uppy’s most-used uploader plugin, but also the one with the most bug reports. Over the years, it accumulated nearly 2,000 lines of tightly coupled code, 11 user-facing callback options, and 8 Companion endpoints. Every bug fix risked breaking something else and nobody wanted to touch it.

So we rewrote it.

The new plugin closes 13 open issues and replaces 11 overlapping callbacks (which conflated signing with S3 protocol details) with 3 mutually exclusive signing modes, plus a few orthogonal config options. Companion is now optional: you can talk directly to any S3-compatible service from the browser.

The dog didn’t eat our homework, so we’re here to show you what we’ve been up to over the past year. We are proud to announce Uppy 5.0! Our faithful file-uploading companion has been attending all the training courses and is now equipped with the most requested feature of all time: truly composable, headless UI components. For years, developers have found themselves stuck between Dashboard’s kitchen-sink approach and the bare-bones drag-drop plugin, with little room to build something that fits just right.

This major release brings headless components and hooks to address those needs. Everything has been backported to 4.0 as well, so you can get going without the need to upgrade.

With Uppy 5.0 , you can finally build the exact upload experience your users deserve – modular, accessible, and tailored to your needs. Whether you need a simple file picker or a complex multi-source interface, Uppy’s got the building blocks to make it happen.

Hold on to your leashes, folks! Uppy 4.0 is here, and it’s more exciting than a tennis ball at the dog park! Our beloved Uppy mascot, the adorable coding canine, has been hard at work fetching all the latest updates for you.

From a full TypeScript makeover to shiny new React hooks, and even Google Photos integration – this release is so packed with treats that we’re almost wagging our tails in excitement. Without further a-dog, let’s dig into what makes Uppy 4.0 the goodest of good boys in file uploading!

It’s this time of the year again! Make yourself cozy by the fire, and let us help you unwrap the gifts Uppy has prepared for you.

We proud of all the improvements and amazing new features and bug fixes we were able to introduce this year. The highlights being: conditional S3 multipart and signing S3 uploads on the client, speedy handling of 10-50k file uploads, refresh tokens (useful when the token expires mid-upload for a large amount of files / slow connections), server-sent events and new assemblyOptions for the Transloadit plugin, Dashboard Single File mode (singleFileFullScreen), improved ETA in the Status Bar, a bunch of new languages, including Hindi, Mexican Spanish and Catalan.

This one, however, is a recent Uppy updates post, covering releases from 3.13.0 to 3.21.0: announcing the switch to Typescript, Dashboard can now auto-install plugins, support for Catalan language, a heap of bug fixes for Tus, Companion, AWS S3, and more.

We recently released an “image scaling on rotation” feature for Uppy’s Image Editor, an often-requested feature that we’re super proud to be able to announce.

In this blog post, we’ll be taking a peek behind the curtain, as we take a detailed look into the development of this feature, and our thought-process approaching it.

Before we start though, take a look below at a comparison between how Uppy’s Image Editor used to handle image rotations, and how it handles them now.

Without further ado, let’s dive into some of the finer technical details, so you can follow along and implement this feature into your own image editor.

This is a big Uppy update post, covering releases from 3.3.0 to 3.13.0!

In this issue: the long-awaited unified S3 plugin which can switch between regular and multipart uploads, improved performance when adding and validating 10k+ files, and stability improvements and bug fixes. The Transloadit plugin is now also easier to configure and leaner in bundle size, since we removed socket.io-client in favor of Server-Sent Events.

Please make a cup of something tasty ☕️ (in a non-spillable container), as this will be quite a ride.

We are excited to announce that our new website, documentation and blog are now live out of beta, ready for you to enjoy on Uppy.io! Let us know what you think on twitter.

🎅🐶 Ho-ho-ho, we are about to wrap up another year for Uppy! Three minor releases ago we’ve introduced Uppy 3.0. It’s time to give you an update on what’s been cooking in the Uppy-Transloadit headquarters (besides cranberry sauce) for the past couple of months.

In short: AWS S3 Multipart stability improvements, Single File Mode for the Dashboard, more tests and bugfixes, new locales.

For those new to Uppy, coming from Reddit, Hacker News and Product Hunt today: Uppy is a popular open source file uploader for the browser. Pick files from local disk or camera, remote sources like Instagram, Unsplash, Dropbox etc, record audio and screencasts. Crop and tweak images with the image editor plugin. Supports resumable uploads to a tus.io server, AWS S3 (and many others with similar API like DigitalOcean), multipart. Try it!

Uppy is turning three! When you’re counting in dog years – which we most certainly are – that’s 29 already. An age like that signifies proper adulthood. For Uppy, this means it’s ready to stay loyal, but without the silly mistakes (read: bugs). Uppy also underwent (ESM) surgery to keep it strolling by your side in the current ecosystem, and received other behavioral improvements 🐶