How Uploadcare works

Uploadcare is a complete platform helping you build file handling on the web. Save resources spent building the file infrastructure, optimize your content, conversions, load times, traffic, and UX.

The four major components of Uploadcare are the upload interface, storage, media processing, and CDN. When integrating Uploadcare, you get all of these components seamlessly working together.


There are many ways in which your files can get to Uploadcare. There is a dialog called Uploadcare Widget, REST and JavaScript APIs, libs, and mobile components. All of those together are our “upload interface.” We allow for uploading multiple files at once, getting files from social media, in-browser image editing, and more.

You don’t even have to sign up to check out how uploads work. There are things like Quick Start and playing with our demo account keys.

Each time a file gets uploaded, your app receives a CDN link with its unique file identifier, UUID. UUIDs are then used by our APIs to handle files: copy, store, and request detailed info, all that kind of stuff.


Alright, after uploading, you’ll get a CDN link with file UUID. Two things happen to make this a reality. First, your file is uploaded to our storage. Second, it gets cached on our CDN. Long story short, when you address a file using its UUID, that file is delivered by CDN. Regarding storage, there are two workflows,

Media processing

Uploadcare allows you to process media files by using our DSL. This implies the processing operations are applied by including their respective URL directives. You can use those to process images, GIFs, videos, and detect objects.

For instance, with images, you can do things like crop, resize, scale_crop, blur, and more. You can also pipe operations:

CDN delivery

Uploadcare uses Akamai as the default content delivery solution. It allows us to get your media to more than 200,000 servers in over 130 countries. Here is how the CDN link looks like:[:operations/][:filename]

Where identifies that you are addressing our CDN, :UUID points at a specific file, :operations tell us what to do with it, and :filename can be set to any RFC3986 compliant string. The last two are optional: your file might be better off with its original filename and no manipulations.

Here’s how you can easily show an image using its :UUID, no :operations or :filename are used in the case,

<img src="" />

And that’s how you let users download the file,

<a href="">

Time to practice

To practice, you might want first to sign up. After the signup, you’ll start with our Free plan. It’s there forever and is packed with oodles of features ready to play with.

For example, say you want to try our Quick Start and interactive widget configurator to grasp how the Uploadcare workflow feels like. If you want to use Uploadcare with a specific language or platform, check out the libraries and integrations.

We’re striving to make Uploadcare as useful and simple as possible. Make sure not to miss other links in our sidebar. There’s so much more in there.

We’re always happy to hear from our users and other super cool folks. Check out our community area or hit us up at

Uploadcare Team