ImageKit Alternative

ImageKit is an image CDN with real-time, URL-based transformations: append parameters like tr:w-400,h-300 to a URL and it resizes, crops, reformats to WebP/AVIF, and caches the result at the edge. The free tier is generous — 20 GB bandwidth and a few GB of storage with unlimited transformations — and paid plans run Lite at $9, Essential at $49 (100 GB bandwidth, 50 GB storage, custom domain), and Pro at $89 (225 GB bandwidth/storage), with bandwidth overages around $0.45–$0.50/GB.

The meter that matters is delivered bandwidth, and the headline feature is the transformation layer. If your app's value is dynamic image variants generated on demand, ImageKit is purpose-built and hard to beat. files.link solves a deliberately smaller problem: durable storage plus fast delivery of the file exactly as uploaded. It does not transform images — no resizing, cropping, format conversion, or tr: parameters.

State that plainly, because it is the dividing line. Plenty of teams, though, generate their derivatives once at upload time (Sharp, ImageMagick, a Lambda) and then just need each rendition stored and served from a CDN — and there, paying for an on-the-fly transform engine you trigger once is overkill. The files.link flow is three HTTP calls with your raw API key in the Authorization header: POST /v1/files/{folderId} returns a presigned URL, PUT the bytes, POST /v1/files/confirm-upload returns a permanent CDN URL.

Pre-generate width variants client- or server-side, upload each, and store the URLs — for example, loop your sizes [400, 800, 1600], run sharp(input).resize(w).webp().toBuffer() for each, push it through the three-call upload, and save the returned CDN URL per width. Public images come back as permanent edge-served URLs; private assets use signed URLs with a 10-minute expiry.

Where ImageKit keeps the edge: anything requiring on-demand transforms, automatic format negotiation, DPR-aware srcset, or its media library with focus-point cropping. Where files.link wins back: you store originals and pre-baked renditions without a transform meter, you serve them over a global CDN, and you pay prepaid credits covering storage and delivery together instead of watching a bandwidth tier. For teams that transformed once and just need hosting, it is the leaner bill.