Predictable image costsfor Next.js

A drop-in for next/image. Flat monthly pricing, unlimited transforms, and a CDN you can actually budget for.

10 of 10 pilot spots still open - claim yours before they fill up.

Starts at: $5.00/mo
Transforms: Unlimited
Global POPs: 119+

Who it's for

Built for builders. Not billing teams.

The solo founder & AI builder.

You ship a landing page on a Saturday, or push a fresh batch of demos, screenshots, and OG images every release. By Monday each one is a transformation, a cache read, and a line item you didn't budget for.

The small team.

You launched. Traffic spiked. Now you're googling "how to disable Vercel image optimization" at 11pm.

Teams of any size.

More environments, more releases, more traffic - and an image bill that compounds with every one. Nobody owns the line item, so it just keeps growing.

Drop-in

Two lines of config. Zero rewrites.

One npm install. One wrapper in next.config. Every <Image /> in your codebase keeps working - untouched.

Diff summary

+ 1 dep: @imgnave/next
+ 2 lines: next.config.ts
± 0 LOC: your components

Remote Images through remotePatterns is not available yet. Will be available in future.

01~/your-app

$ npm install @imgnave/next

1 dependency · zero client-side runtime added

02next.config.tsDiff

import { withImgnave } from "@imgnave/next";

export default nextConfig;

export default withImgnave(nextConfig);

03app/page.tsxNo diff

<Image

src="/hero.png"

width={1200}

height={800}

alt="Hero"

0 lines changed · existing components untouched

The problem

Image optimization gets expensive when your product is working.

The pain isn't the price. It's not knowing what the next deploy, launch, or tweet will do to your bill.

Per-transform billing

Every responsive width, quality level, and AVIF/WebP variant becomes another transformation line item.

Stacked meters

Cache reads, cache writes, fast data transfer, and edge requests each meter independently.

Unpredictable spikes

A launch tweet or demo day spike turns into a bill you only see after it has happened.

Receipts · r/nextjs

This isn't a manufactured pain. Verified, upvoted, ongoing.

Three numbers. One bill.

Transforms

∞

Unlimited.

Every resize, quality, AVIF, and WebP variant your next/image renders - included. No per-transform meter, ever.

Counters Per-transform billing

Bandwidth

$0.07/GB

One meter only.

Beyond the included allowance, CDN bandwidth is one flat rate. No cache-write, edge-request, or fast-data-transfer surcharges.

Counters Stacked meters

Surprises

Zero hidden charges.

Your bill has exactly two line items: a fixed base, and CDN bandwidth. A traffic spike can't add a new column.

Counters Unpredictable spikes

The lifecycle

How a public image actually travels.

01Build-time

$next build

Public images sync.

Changed files in your /public folder upload to ImgNave storage and a manifest is written for the loader - once per deploy, not per request.

02Render

‹›<Image src="/hero.png" />

Loader hands out URLs.

Your existing <Image /> components ask the ImgNave loader for an optimized URL with the right width, quality, and format. No rewrites in your app.

03Edge delivery

↘GET pz001.imgnave.com/…avif

Variants stream from POP.

Bunny streams the variant from the nearest of 119+ POPs. Format negotiated (AVIF/WebP), compressed, cached - ready before the next byte hits the screen.

Pricing

Pricing that fits on a sticky note.

Plan · Starter

ImgNave Starter

Replace per-transform image bills with a single, fixed monthly price. For solo founders and small teams shipping on Next.js.

Base: $5.00/mo; Same number, every month.
Bandwidth: $0.07/GB; After 10 GB included.

Dodo checkout activates the project.

Invoice previewMay 2026

Your monthly bandwidth25 GB

1050100200 GB

ImgNave Starter · monthly base$5.00

CDN bandwidth · 15 GB over 10$1.05

Total$6.05

We never charge for

Per-transform fees · cache-read · cache-write · edge-request meters · fast-data-transfer surcharges.

Infrastructure

Built on Bunny's global edge.

Production-grade delivery, not a side project. The same network shipping billions of requests across 6 continents and 119+ points of presence.

Edge infrastructure · stackView region map

Delivery: BunnyCDN · 6 continents · 119+ points of presence
Origin: Bunny Storage Zones · global replication
Optimizer: Resize, quality, AVIF & WebP - negotiated at the edge
Caching: HTTP-compliant TTL · purge API · build-time invalidation

FAQ

Questions founders ask before switching.

Q01IntegrationCan I keep using next/image?
Yes. ImgNave is a drop-in image layer for Next.js. You keep using next/image and add the ImgNave wrapper to your next.config - no component changes anywhere in your app.
Q02IntegrationDo I need to leave Vercel?
No. ImgNave works wherever you deploy your Next.js app - Vercel, Netlify, your own infra. The SDK syncs public assets during builds and the loader returns ImgNave CDN URLs at runtime.
Q03IntegrationHow do public assets get uploaded?
During build, the SDK uploads changed public images and writes a manifest. At runtime, next/image requests optimized variants from your ImgNave URLs - no extra build complexity to learn.
Q04BillingAre transformations really unlimited?
Yes. ImgNave never meters image transformations. Your bill is the monthly base price plus CDN bandwidth over the included allowance. That's the whole pricing model.
Q05BillingWhat exactly am I paying for?
A flat monthly base price plus $0.07/GB CDN bandwidth overage after the included allowance. No per-transform fees, no cache-write charges, no edge-request meters.
Q06OperationsCan I use a custom domain later?
Yes. Start on the default ImgNave URL and swap in your own hostname from the dashboard whenever you're ready. No code changes required.

10 of 10 pilot slots open

The only thing left is the install command.

Two lines of config. One deploy. Keep the wrapper, you're in. Remove it, you're back. Risk-free by design.

~/your-app

$ npm install @imgnave/next

Dodo checkout · Reversible by design