Getting started

Integration & migration

Image & video API

DAM user guide

API overview


Integrate Azure Blob Storage with

Connect Azure Blob Storage as an external storage with ImageKit to get real-time image and video optimization and transformation capabilities in minutes.

You can add your existing Azure blob storage as an origin in This allows you to use's real-time optimization, transformation, and streaming features on all existing images and videos in your storage. You will also be able to deliver non-media files like JS, CSS, and more with this integration.

Before continuing, understand how external storage integration works, what is URL endpoint, and how to troubleshoot 404 errors.

If you have granted anonymous public access to your Azure container, you can choose to configure your container as a Web Server. Provide your container URL as the web server URL in the web server configuration steps. See how to configure a web server origin. However, note that it is advisable to configure your origin using secure integration, as explained below.

Step 1: Generate a Shared Access Signature (SAS) Token

The following instructions are for generating a Shared Access Signature (SAS) token for your Azure storage account. This token will allow ImageKit to access the files in your Azure storage container. This allows you to restrict ImageKit to only reading objects from your container. i.e. ImageKit will not be able to create/delete/update objects in your container.

If something doesn't work as expected, you can refer to Azure's official, albeit more verbose, instructions on this page.

  1. Sign in to your Azure Account through the Azure portal.
  2. Select Storage Accounts.
  3. Select the corresponding storage account.
  4. Search for the Shared Access Signature setting in the settings pane on the left.
  5. Now, select the options as shown in the following image. This ensures that ImageKit is allowed to only read files from your Azure container.
  6. Enter an End expiry time that is practically infinite. Preferably, enter a time 10 years from the start time (which should be right now)
  7. Click on 'Generate SAS and connection string'
  8. Note down the SAS token generated. It should be of the format ?sv=2019-12-12&ss=bfqt.........

This method generates an account-level Shared Access Signature. To generate a service SAS or a user-delegated SAS, visit the official Azure documentation pages here.

Step 2: Configure your Azure storage container with your ImageKit account

We have now created a SAS token for ImageKit and granted it the Read permission for your container, which means that ImageKit can do nothing more than just read objects in your container. At this point, you should have the following values with you:

  • Azure storage account name: The name of your storage account.
  • Azure storage container name: Name of the container that you want to integrate.
  • SAS Token: As generated in step 1. Do note that the SAS token should begin with a ? when adding it to the origin in ImageKit. For example - ?sv=2019-12-12&ss=bfqt.........

Now, go to the External Storage section in the dashboard. Click on the "Add new" button, select "Azure Storage" in the Origin Type dropdown, enter the corresponding values, and click Save.

Step 3: Access the file through URL endpoint

When you add your first external source (origin) in the dashboard, the origin is, by default, made accessible through the default URL endpoint of your account. For subsequent origins, you can either create a separate URL endpoint or edit the existing URL endpoint (including default) and make this newly added origin accessible by editing the origin preference list.

When you request, internally accesses the object at path rest-of-the-path.jpg in your Azure container.

            URL endpoint                transformation      file path 

Let's look at a few examples to fetch an image file. The same would work for other file types as well.

If you get a "Not found" error while accessing the file, check out this troubleshooting guide.

You can also use a custom domain like

Step 4: Integrate and Go live

Start using URLs in your application to deliver perfect images and videos.