ImageKit Free Plan Limits: What You Actually Get

Short answer: ImageKit's free plan is good for small sites, tests, portfolios, and early projects. It is not something I would use blindly for a production site that can get traffic spikes, because the free bandwidth limit is a hard stop.

You get 20 GB of monthly bandwidth, 3 GB of DAM storage, 2 users, 500 purge requests, 500 video units, and 650 extension units. Image transformations and optimization are included, which is the useful part.

The two limits that matter most are bandwidth and storage.

Bandwidth resets every month. Storage does not.

ImageKit Free Plan Limits

Here is the current free-plan limit table for ImageKit's complete media processing and DAM product.

Source: ImageKit's public pricing page.

The headline numbers are simple. The behavior behind them is what decides whether the plan fits your site.

If you only need URL-based image resizing, format conversion, compression, and delivery for a small site, the free plan is strong. If you need a custom domain, predictable uptime during spikes, more storage, or team access, you will probably outgrow it.

The 20 GB Bandwidth Limit

The 20 GB bandwidth limit is monthly.

It is also a hard limit on the free plan. ImageKit says media delivery stops when you hit it, and the counter resets at the beginning of the next calendar month.

That means the real question is not "is 20 GB enough?"

The real question is "can this site survive broken images for the rest of the month?"

For a small blog, probably yes.

For a product page, local service site, SaaS landing page, marketplace, paid ads page, or ecommerce site, no.

Rough bandwidth math

Use this as a rough planning model, not a promise.

ImageKit's pricing page describes 20 GB as enough for roughly 20,000 page views per month. That assumes about 1 MB of delivered media per pageview.

Your site may be much better or much worse.

A tight blog post with one hero image and WebP delivery might use far less. A product category page with many thumbnails can use more. A portfolio with full-width photography can burn through 20 GB quickly even at modest traffic.

The way to measure it is simple:

1. Open a real page in Chrome DevTools.
2. Disable cache.
3. Reload.
4. Filter the Network tab by images.
5. Add up transferred image bytes.
6. Multiply by expected pageviews.

Do this on your heaviest real template, not only the homepage.

The 3 GB DAM Storage Limit

The 3 GB storage limit is fixed.

It does not reset every month.

It applies to files stored inside ImageKit's DAM or Media Library. Once you hit it, new uploads stop until you delete files or upgrade.

This is why the storage limit feels smaller than it looks.

3 GB is enough for a small collection of optimized assets. It is not a lot if you use ImageKit as your main media library and keep uploading original camera images, product photos, screenshots, PDFs, or video thumbnails.

Storage is different from bandwidth

Bandwidth is usage.

Storage is inventory.

If you upload a 2 MB image to the Media Library, that 2 MB keeps counting until you remove it. If you upload 1,000 images over a year, those files still sit inside the storage cap even if some of them are no longer used on active pages.

This matters most for:

• WordPress media libraries
• ecommerce catalogs
• portfolios
• agency sites with many client examples
• blogs that upload screenshots often
• apps that let users upload media

If your upload workflow is messy, 3 GB disappears faster than expected.

Origin Pull vs Media Library

This is the part many people miss.

ImageKit can work in two different ways.

You can upload files into ImageKit's Media Library. Those files count against the 3 GB DAM storage limit.

Or you can configure ImageKit to pull images from an external origin, like your website, S3 bucket, storage provider, or another asset host. In that setup, your original files remain outside ImageKit's DAM storage.

The difference is important:

Origin pull is usually the better setup if you are using ImageKit mainly as an image CDN.

It lets you keep storage where it already lives, then use ImageKit for resizing, compression, format conversion, and CDN delivery. The 20 GB bandwidth limit still applies, but the 3 GB DAM storage limit becomes much less important.

Use the Media Library when you actually want ImageKit to be your asset manager.

Use origin pull when you want ImageKit to sit in front of an existing image source.

WordPress Can Fill Storage Quickly

WordPress makes storage math worse because one upload often becomes many files.

A single image upload can create:

• the original file
• a large thumbnail
• a medium thumbnail
• a small thumbnail
• theme-specific sizes
• plugin-specific sizes
• retina or cropped variants

If those generated files are uploaded or synced into ImageKit's Media Library, one "image" is no longer one file.

The exact number depends on your theme, plugins, media settings, and image sizes. But the principle is simple: WordPress can multiply storage usage behind the scenes.

If you use WordPress with ImageKit, check which mode your integration uses.

If ImageKit is only rewriting image URLs and pulling from your WordPress uploads folder, the 3 GB DAM limit is not your main issue.

If your WordPress images are being uploaded into ImageKit's Media Library, storage is a real limit. In that case, disable unnecessary thumbnail sizes, compress originals before upload, and clean unused media regularly.

Custom Domain Limit

The free plan includes 0 custom domains.

Your image URLs use ImageKit's default domain pattern instead of something like:

https://cdn.example.com/path/image.jpg

This is not always a technical blocker. Images can still load, be cached, transformed, and served over HTTPS.

But it does matter in a few cases.

Use a custom domain if you care about keeping image URLs under your own brand, avoiding provider-looking URLs in source code, making migrations cleaner later, or consolidating image search and asset paths around your domain.

ImageKit's pricing table currently shows custom domains only starting on Pro for the complete media processing plan. Lite still shows 0 included custom domains.

So do not upgrade from Free to Lite only for a custom domain unless you have confirmed your account's current options in the ImageKit dashboard.

Lite and Pro Limits

ImageKit's paid tiers remove the most painful free-plan behavior: hard stops for bandwidth and storage.

Lite is the practical upgrade when your site is small but should not break during a traffic spike.

You get 40 GB included bandwidth and overage billing instead of a free-tier stop. That is the main reason to pay for it.

Pro is a different category. It makes sense when you need the larger DAM storage, much higher traffic allocation, more video processing, extension units, advanced DAM features, and a custom domain.

For normal websites, Pro is usually not the first paid step.

When ImageKit Free Is Enough

ImageKit free is a good fit when:

• the site is small
• the image load is predictable
• broken images during a spike would be annoying but not expensive
• you are testing image optimization
• you use origin pull instead of storing everything in the DAM
• you do not need a custom CDN domain
• one or two people manage the project

It is especially useful for learning how image CDNs work.

You can test URL transformations, responsive image sizes, WebP delivery, AVIF behavior where supported, cache behavior, and origin pull without paying upfront.

That is a good free tier.

Just do not confuse "good free tier" with "safe production infrastructure."

When You Should Upgrade or Leave

Upgrade or move away from the free plan when any of these are true:

• monthly bandwidth crosses 12-15 GB consistently
• one campaign or viral post could push you past 20 GB
• missing images would hurt revenue or leads
• DAM storage crosses 2 GB and keeps growing
• you need more than 2 users
• you need more purge requests
• you need reliable video processing or AI extensions
• you need a custom image domain
• you are building for a client

If you like ImageKit's APIs, dashboard, SDKs, and DAM workflow, Lite is the cleanest next step.

If you mainly need cheap image delivery and optimization, compare it with BunnyCDN, Cloudflare Images, and the broader free vs paid image CDN decision guide.

BunnyCDN can be cheaper for plain image delivery. ImageKit can be better when you want a full image API and asset workflow.

Pick based on the workflow, not only the first free number.

ImageKit Free vs Other Free Image CDNs

ImageKit's free plan is generous in one specific way: it gives you real image transformation and optimization without making you pay immediately.

But every free image CDN has a tradeoff.

For a wider list, use the free image CDNs guide.

If you are comparing free plans because you have no traffic yet, ImageKit is fine.

If you are comparing free plans for a live business site, focus less on the free allowance and more on the failure behavior.

The failure behavior is what users see.

Summing Up!

ImageKit's free plan is useful, but it is not unlimited infrastructure.

Use it for small sites, testing, portfolios, low-risk blogs, and origin-pull image optimization. Watch the 20 GB bandwidth counter and the 3 GB DAM storage cap.

If the site needs reliable image delivery, upgrade before the cap becomes an incident. The important difference between free and paid is not only more bandwidth. It is that paid plans can keep serving media after the included allowance is used.