By migrating to Cloudimage, your images will need to be downloaded from their origin and cached by Cloudimage. Make sure your origin is able to process the initial load or contact us to perform a warm-up.
Case 1: not using a custom CNAME
Example 1:
If your image is currently delivered via:
<img src="https://yourdomain.provider.com/{image_url_or_path}?operations&filters" />Then you need to replace the FQDN from yourdomain.provider.com to token.cloudimg.io/v7/ for the <img src> to become:
<img src="https://token.cloudimg.io/v7/{image_url_or_path}?operations&filters" />Example 2 :
If your image is currently available at http://token.provider/operations/sample.li/flat.jpg and referenced in your code as:
<src="http://img.provider.com/{token}/{operations}|{filters}/{path_fo_folder}/flat.jpg" />Then you need to adapt it to be:
<src="https://token.cloudimg.io/{operations}|{filters}/{path_fo_folder}/flat.jpg" />Where:
- token: your Cloudimage token you obtain after registering for a Cloudimage account
- operations: the resizing operation(s) as listed under Operations
- filters: the filter transformation(s) as listed under Filters
Case 2: using a custom CNAME
Example 1:
If your image is currently delivered via:
<img src="https://img.domain.com/{image_url_or_path}?operations&filters" />Example 2 :
If your image is currently delivered via:
<src="http://img.domain.com/{token}/{operations}|{filters}/{path_fo_folder}/flat.jpg" />In both scenarios, migrating to Cloudimage only requires the change of your CNAME record for img.domain.com on your DNS provider.
Where:
- token: your Cloudimage token you obtain after registering for a Cloudimage account
- operations: the resizing operation(s) as listed under Operations
- filters: the filter transformation(s) as listed under Filters
Cloudimage supports multiple image transformations format, contact us to discuss your migration project.