Why I Stopped Using Cloudinary and Built My Own Image API

The author left Cloudinary after bandwidth-based image delivery costs kept rising with steady e-commerce traffic.

He also wanted to avoid juggling separate tools for transformations, color metadata, BlurHash, and background removal.

He built img apis as a single GET-based image service that combines processing and metadata in one endpoint.

The new setup uses cache hits at no charge, handles 404s cleanly, and starts at a lower monthly price on Cloudflare.