Comment on page


After migrating to from another service, can translate your pre-existing transformation URLs written in the syntax of your previous service provider to ImageKit's syntax. This allows you to continue using your already written URLs with minimal changes. For example, if you are migrating from Cloudinary, ImageKit can translate the following URL written in Cloudinary's syntax to ImageKit's syntax:<cloudinary_cloud_name>/image/upload/h_300,w_300,c_crop,g_north/folder/image.jpg
Cloudinary URL
Translated ImageKit URL
static part transformations file path
static part transformations file path
  • The static part -<cloudinary_cloud_name>/image/upload must be manually replaced by you with<your_imagekit_id>
  • The transformations part - h_300,w_300,c_crop,g_north will be translated by ImageKit to produce tr:h-300,w-300,cm-extract,fo-top
  • The file path - folder/image.jpg will stay as it is unless your file structure has changed during migration

Supported services currently supports rewriting URLs for the following services:

How to use a URL-rewriter

A URL-rewriter can be attached to a URL-endpoint in your account. For instance, If you attach the Cloudinary URL-rewriter to the endpoint with the cl_rewrite identifier, ImageKit will accept transformations written in Cloudinary's syntax for all URLs on this endpoint.
An example URL that performs two chained transformations might look like this:<your_imagekit_id>/cl_rewrite/h_300,w_300,c_crop,g_north/a_50/folder/image.jpg
To attach a rewriter to one of your endpoints, please contact us at [email protected].