> For the complete documentation index, see [llms.txt](https://docs.cloudimage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudimage.io/implementation/migrating-from-another-image-cdn.md).

# Migrating from another image CDN

If your are transferring your image optimisation and CDN service from another provider, Cloudimage provides an easy way to migrate your images without code changes.

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](https://www.cloudimage.io/en/contact-us) to perform a warm-up.

<figure><img src="/files/BDwSZRIpQmqkoPCjF65L" alt=""><figcaption></figcaption></figure>

## Case 1: not using a custom CNAME <a href="#od_7ae4151e" id="od_7ae4151e"></a>

### **Example 1**

If your image is currently delivered via:

```js
<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/` for the `<img src>` to become:

```js
<img src="https://token.cloudimg.io/{image_url_or_path}?operations&filters" />
```

### **Example 2**

If your image is currently available at [http://token.provider/operations/sample.li/flat.jpg](http://sample.li/flat.jpg) and referenced in your code as:

```js
<src="http://img.provider.com/{token}/{operations}|{filters}/{path_fo_folder}/flat.jpg" />
```

Then you need to adapt it to be:

```js
<src="https://token.cloudimg.io/v7m/{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 [Image operations](/transformations/image-operations.md)
* **filters**: the filter transformation(s) as listed under [Image filters](/transformations/image-filters.md)

## Case 2: using a custom CNAME <a href="#od_944d4986" id="od_944d4986"></a>

### **Example 1**

If your image is currently delivered via:

```js
<img src="https://img.domain.com/{image_url_or_path}?operations&filters" />
```

### **Example 2**

If your image is currently delivered via:

```js
<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 [Image operations](/transformations/image-operations.md)
* **filters**: the filter transformation(s) as listed under [Image filters](/transformations/image-filters.md)

Cloudimage supports multiple image transformations format, [contact us](https://www.cloudimage.io/en/contact-us) to discuss your migration project.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cloudimage.io/implementation/migrating-from-another-image-cdn.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.