Saving Image Bandwidth
It is common that you don’t want hi-res original images uploaded to your Uploadcare account. Doing so is inefficient on both ends:
- Sending large images over mobile networks can be expensive for your users.
- Large images take up your account storage limit and delivering those increase your traffic.
The option is passed into your widget as a string holding your preferred resolution and, optionally, a JPEG quality of the resulting image. The preferred resolution you provide does not affect original image aspect ratio. You will not have control over the image format: Image Shrink outputs to JPEG: your layers and alpha channel data will be lost.
Here are some examples of strings you can specify to control the option behavior,
800x600, shrinks images to 0.48 megapixels with the default JPEG quality of 80%.
1600x1600 95%, shrinks images to 2.5 megapixels with the JPEG quality set to 95%.
The resolution you set for optimized images should not exceed 5 megapixels. All EXIF info from your original images will be copied to the resized ones. The copied EXIF info includes image orientation, camera model, geolocation, and settings.
Images will not be optimized in the following cases,
- When a client browser does not support all the required APIs.
- When images are uploaded from social media or URLs.
- If the
original resolution / target resolutionratio falls behind
2.0. For example, you can not shrink a 2560x1560px (4 MP) image to 1600x1600px (2.5 MP) while this works with a 2448x3264px (8 MP) original. The reason we implemented this limit is to preserve an optimal balance between a decline in quality and drop in file size.
Resize to 1024x1024px on a client
<input type="hidden" role="uploadcare-uploader" name="my_file"
Resize multiple files to 640x640px on a client
<input type="hidden" role="uploadcare-uploader" name="my_files"