img apis.
Start free
// VERSUS · IMGIX

Same URL DX. A broader bundle, flat billing.

imgix invented the URL-as-image-API model in 2014 — and they are still excellent at it. They are tuned for very high volume where unit cost dominates the bill, and they bundle bandwidth and storage at every tier. img apis is the leaner pick when the wedge is broader: native BlurHash encode and decode, a /info call that returns palette + metadata + BlurHash in one round-trip, first-class /grid composition for 2–5 sources, an account-level default mark that auto-applies across every endpoint on Pro+, background removal at a disclosed credit cost — and idempotent credits that never bill the same URL twice within a month.

You love the imgix URL model. You want intelligence in the box (BlurHash, palette, metadata in one call), composition without a sidecar, brand marks that travel with every asset, and the same URL never billed twice on a cache miss retry.

Start freeSee the table
Pick us when

Pick img apis when the bundle is the wedge.

  • /info returns dimensions, palette (with WCAG-paired contrast) and BlurHash in a single 24h-cached round-trip — three trips collapsed into one.
  • First-class /grid composition for 2–5 sources, plus a /placeholder family that renders BlurHash or color tiles to real PNG.
  • Account-level default mark (Pro+) auto-applies across every image-returning endpoint — set the brand once, every URL ships marked.
  • Idempotent credits, cache hits cost zero, bandwidth bundled flat — no per-GB meter, no cache-read line item.
  • Workspace-native multi-tenancy — unlimited workspaces, users and custom domains without per-seat fees.
Pick them when

Pick imgix when you want the cheapest per-transform at scale.

  • You operate at the scale where unit transform cost dominates the bill.
  • You want bandwidth and storage bundled into the same credit pool.
  • A mature S3-first pipeline and Render API for video are part of the deal.
  • Established procurement, SSO and enterprise compliance are required at sign-off.
  • You already have an imgix Source set up and the team knows the param vocabulary.
// SIDE BY SIDE

img apis vs imgix

Compared on billing shape and feature coverage — line by line, claim by claim.

// comparison matrix2 vendors
// feature
oursimg apis
imgix
Mid-tier billing modelflat plan, bandwidth bundledcredit pool
Transforms at mid-tierflat credit allowancecredits shared with bandwidth + storage
Palette + BlurHash + metadata in one /info call
Color pairs with WCAG contrast
Smart gravity (face + entropy)
Background removal
BlurHash decode endpoint (renders to PNG/JPEG)
1-year immutable transform cache
Edge POPs serving you300+100+
Free trial200 cr / 7d30d capped
Bill is one line (no shared pool with bandwidth & storage)
Same URL never billed twice
Custom domain on cheapest plan

Spotted something off? tell us →

// FORMAT NEGOTIATION

Same negotiation. Same edge.

Both APIs negotiate AVIF, WebP and JPEG per Accept header. imgix uses auto=format; img apis uses format=auto. Same physics, same edge cache — this comparison is about everything else the URL can do.
Coastline hero−79%
jpeg
140KB
webp
53KB
avif
30KB
Pour-over hero−78%
jpeg
124KB
webp
47KB
avif
27KB
Studio hero−78%
jpeg
156KB
webp
61KB
avif
35KB
One URL · format=auto · cached one year, immutable.
// ONE CALL, NOT THREE

BlurHash, palette and metadata — in one round-trip.

imgix returns metadata at ?fm=json. It does not ship BlurHash natively — you encode it client-side from a thumbnail, or pay a separate service to do it for you. img apis collapses palette, BlurHash and metadata into a single /info call with WCAG-paired contrast per palette swatch.
// THREE CALLS VS ONE

Less wiring. Smaller bundle.

On imgix, the BlurHash story is a wire-it-yourself story: transform, then fetch ?fm=json, then encode BlurHash on your side or in a sidecar. On img apis, /info returns it inline — and you can render it back as a real image via /placeholder/blurhash.
bash·imgix · three calls + glue
# 1. transform
curl 'https://images.imgix.net/runner.jpg?w=480&h=360&fit=crop&crop=faces'

# 2. metadata (separate endpoint)
curl 'https://images.imgix.net/runner.jpg?fm=json'

# 3. BlurHash — no native endpoint.
#    You generate it client-side from a thumbnail,
#    or wire up a separate service in front of imgix.
bash·img apis · one /info call
# everything from one call
curl 'https://imgapis.com/info/your-bucket/runner.jpg'

# response (truncated)
{
  "width": 1600, "height": 1067,
  "dominant": "#c97d4a",
  "palette": [ /* 5 swatches with WCAG pairs */ ],
  "blurhash": "LFE.@D9F01_2..."
}
// READY TO COMPARE FOR REAL

Ship faster than imgix.

200 credits free for 7 days. No card, no SDK to pin — paste a URL, watch it work.

Start freeSee pricing