> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://uploadcare.com/docs/llms.txt.

With Uploadcare, you can easily build custom image transformation workflows and automate most image manipulation and optimization tasks. For example, you can set up a chain of actions for user-generated images that'll unify their look.

Every URL image operation generates a modified image version on the fly, while the original file stays intact. The transformed image version will be cached on CDN nodes to optimize delivery.

### Input image formats

List of supported image formats:

* AVIF
* BMP
* GIF
* HEIC
* JPEG
* PCX
* PNG
* TGA
* TIFF
* WEBP

Some formats have several variations, and we support the most popular ones.
[Contact sales](mailto:sales@uploadcare.com) if you require additional
formats or variations.

Without any image processing operation in the URL, CDN instructs browsers
to show images (`Content-Disposition: inline`) and download other file types
(`Content-Disposition: attachment`). Browsers may not show all image formats,
for example, TIFF and HEIC format. If you need to display an image, add any
image processing operation, `-/preview/` for instance. The `inline` control
allows you to change this behavior.

```
-/inline/yes/
-/inline/no/
```

### Core operations

When processing images, add at least one of the following operations
via their respective URL directives:

* [`resize`](/docs/transformations/image/resize-crop/#operation-resize)
* [`smart_resize`](/docs/transformations/image/resize-crop/#operation-smart-resize)
* [`scale_crop`](/docs/transformations/image/resize-crop/#operation-scale-crop)
* [`preview`](/docs/transformations/image/resize-crop/#operation-preview)

### Output image dimensions

The dimensions you specify for the last operation should not exceed 3000x3000
pixels. You can go up to 5000x5000 pixels by explicitly setting
your [image format](/docs/compression/#operation-format)
to JPEG, `cdn›/format/jpeg/`.

You can extend the output max resolution up to 8192x8192, and up to 16384x16384
for JPEGs in trade-off for increased latency. [Contact sales](mailto:sales@uploadcare.com) to learn more
about this option.

### SVG files

Any image transformation CDN URL is valid with an SVG file. Most operations
don't affect the response SVG body, while geometric operations
(`crop`, `preview`, `resize`, `scale_crop`) change SVG attributes and work as expected.

To apply full range of operations on SVG file, it should be rasterized by
applying `-/rasterize/` operation.

Note: Operation is safe to apply to any image. Not SVG images won't be
affected by this operation.

*SVGs uploaded before May 26, 2021 still have `is_image: false` and adding
processing operations to them will result in error. Contact
[support](mailto:help@uploadcare.com) to batch process previously uploaded files.*

### Image resolution

We don’t provide on-the-fly image processing for images greater than
75 Mpx in resolution: those are tagged as **non-image** files and can only be delivered
via CDN as-is. Adding processing operations to non-image files will result
in an error.

### Simple rotation

When the only image transformation you want is rotating, consider using the
[`preview`](/docs/transformations/image/resize-crop/#operation-preview)
control without any arguments. When you use any of the transformations, we
automatically rotate images according to their EXIF orientation.

### Animated images

Animated images are treated as static by the transformations engine, consider
checking out our [GIF to Video](/docs/transformations/gif-to-video/)
workflow optimized for animated images delivery.

### REST API image processing

Most image processing operations work on-the-fly,
except some that must be called via [REST API](/docs/api/rest/):

* [Background removal](/docs/remove-bg/)
* [Object recognition](/docs/intelligence/object-recognition/)
* [Video](/docs/transformations/video-encoding/) and [document](/docs/transformations/file-conversion/) thumbnail generation