Accounts created before Nov. 1st, 2021
Accounts created before November 1, 2021 have to include /v7/ in the path, like shown below.
//token.cloudimg.io/v7/original_image_url?operations&filters
Accounts created on or after November 1, 2021 do not require /v7/ and documentation have been updated accordingly.
To verify the type of configuration on your Cloudimage account, log in to your Cloudimage admin panel and look at the syntax provided on the Welcome page.
[NOTE] If you are an existing Cloudimage customer and wish to be able to remove the v7 from your URL syntax, please contact our support.
Introduction
Cloudimage will solve your challenges with image resizing, transformation, and acceleration in the Cloud.
Images slow down your website and mobile apps? Don't want to spend hours Photoshopping images for the web? Don't want to write complex image resizing automation scripts? Looking for Responsive Images As A Service? You've come to the right place.
We have documented the most common resizing functions here. Cloudimage supports many more, but we want to focus on what is really necessary for you to get started. If you have any requests for undocumented features, contact us and we will help you out!
The basics
Everything starts with the basic URL format of a Cloudimage URL
//token.cloudimg.io/original_image_url?operations&filters
| token | Your Cloudimage customer token. Subscribe here to get one. You can also ask us for a custom token. |
| original_image_url | That's an easy one :) |
| operations | Image manipulation operations like width, height, crop, fit, rotate, trim. For a full list, see Image resizing. |
| filters | Use filters like contrast, pixellate, blur, greyscale and sharpen to apply different effects on your image. For a full list, see Image filters. |
If your Cloudimage account has been created brefore 20.10.2021, you might need to add v7/ to your Cloudimage url before the origin image. Example: //token.cloudimg.io/v7/original_image_url?operations&filters.
Cloudimage's resizing servers, located in three data centres worldwide (Canada, France, and Singapore) will download your original image from origin_image_url, transform it based on the operation and filter parameters, and finally, display it on your website or mobile app through a rocket fast CDN.
An example with an original image hosted on your web server, Amazon S3 bucket, or any other storage accessible over HTTP.
If you host your images on a Web Server, Image Repository, or Storage Bucket sitting behind a Firewall, make sure your images are accessible over HTTP or HTTPS. Otherwise, Cloudimage servers will not be able to download the originals.
Please refer to the full list of options here: resizing operations, image filters, watermarking.
CDN acceleration
All resized and filtered images are delivered by default to your end users over multiple (Content Delivery Networks) through 1400+ PoPs (Points of Presence). This enables fast delivery and absorbs load during high traffic peaks.
We work with multiple CDN providers and can help with selecting the best one for your use case. Contact us for discussing your needs.
Static content delivery
You can also use our CDN to deliver static content like JS or CSS files with the func=proxy option. For more details, you can refer to the Content / Acceleration section.
Direct download
If you would like to download the resulting image instead of displaying it in the browser, you could use the force_download=NAME option where NAME is the desired filename after download.
//doc.cloudimg.io/sample.li/paris.jpg?width=400&grey=1&force_download=paris_bw.jpg