Getting started

Integration & migration

Image & video API

DAM user guide

API overview


Migration from Akamai to

Learn how to migrate from Akamai Image Manager to ImageKit without changing existing URLs.

Akamai Image Manager has limited image optimization and transformation support compared to Migrating to can help you leverage advanced image optimization and transformation capabilities, leading to faster loading times and improved user experience. This guide outlines the steps for migrating your media assets delivery and optimization from Akamai Image Manager to

Step 1: Configure your origin in supports all external storage that Akamai Image Manager supports. That means you can easily configure existing storage in ImageKit. Refer to configure external storage and follow the integration steps based on your storage.

If you use Akamai NetStorage, expose it on a public endpoint and configure it as web folder in ImageKit.

Alternatively, you can migrate your assets to your own S3 or ImageKit storage using Rclone. Refer to and for more information.

Step 2: Enable Akamai URL rewriter

Open URL endpoints in the dashboard, and enable URL rewriter in the desired URL endpoint under the "Advanced settings" tab. This will rewrite the incoming URL to the format that ImageKit understands. This allows you to keep the existing Akamai transformations in your application and still use ImageKit for media optimization, transformation, and delivery.

Step 3: Test and make the switch

Now, you should be able to access existing assets through ImageKit. At the same time, existing Akamai transformations should work without any changes.

Test the migration thoroughly before making the switch. You can use a local host entry to test the migration without changing the DNS settings.

Create a local host entry

You should create a separate property in Akamai to test the migration. This will help you test the migration without changing the DNS settings.

However, if you want to test on existing domain names, you can create a local host entry in your system to point the domain to ImageKit. This will help you test the migration without changing the DNS settings.

Use the dig command to find the IP address and add the following entry to your host file.

For Windows

  1. Open your text editor in Administrator mode.
  2. In the text editor, open C:\Windows\System32\drivers\etc\hosts.
  3. Add the IP Address and hostname.
  4. Save the changes.

For Linux

  1. Open terminal.
  2. Use the nano command line text editor or a different one you have available to open the host file. The command with nano is as follows (the command will require your Linux user password)
  3. sudo nano /etc/hosts
  4. Add the appropriate changes in the host file.
  5. Use the Control and 'X' key combination to save the changes.

Let's fetch an image without any transformation. The same would work for other file types as well.

Let's see if transformations work as expected. The same would work for videos as well.

For a list of supported transformations and how they are translated, refer to the Akamai URL Rewriter specification.

Once you are confident that ImageKit is serving your assets correctly, you should update your DNS settings to point to ImageKit. This will ensure that all your assets are served through ImageKit.

Akamai URL rewriter specification

Akamai transformation Example translation Remarks