Unable to Set My Website as Primary Origin in ImageKit – Need Detailed Help

General
1

Hi everyone,

I’ve integrated ImageKit into my website to optimize image delivery and performance. The basic integration seems to be working fine. However, I’m facing an issue when trying to set my website’s origin as the primary origin in the ImageKit dashboard.

Issue:

I want to use my own website as the default origin for serving images via ImageKit CDN. But currently, I’m unable to set it as the primary origin. The option appears disabled or not functioning correctly, especially while on the free plan.

My Setup:

Integration Status: Image URLs are transforming correctly using the default origin.
Custom Origin Configuration: I’ve added my domain as a custom origin in the ImageKit dashboard under “External origin”.

What I’ve Tried:

  1. Added a new external origin pointing to my domain.
  2. Tried to change the default origin, but the option is either locked or greyed out.
  3. Checked documentation, which mentions that some features may be restricted on the free plan.

Questions:

  1. Is it mandatory to be on a paid plan to make my custom origin the primary/default?
  2. If yes, which ImageKit plan enables this feature?
  3. Is there a workaround or fallback method to prioritize my origin without making it primary?
  4. Does ImageKit always fallback to the default origin even if the custom one is working?

Objective:

My goal is to serve all images from my website’s directory through ImageKit’s CDN using optimization and transformation features, without relying on their default origin.

Any help, guidance, or workaround would be really appreciated!

2

Media Library will always be the first origin.
It is also used for internal cache lookups (though you don’t see these files in the Media library dashboard). If the file is not in the Media Library, it fails quickly to go to your origin.