That’s what I’m experimenting with at img.pro.
How it works: + Upload an original (JPEG, PNG, WebP, HEIC, AVIF, PSD, etc.) + The API generates optimized variants automatically (S/M/L sizes by default) + Originals are stored in R2 → cheap, no hidden bandwidth costs + Optimized images are delivered through Cloudflare’s edge (300+ PoPs) + Output formats are predictable (JPEG for opaque, WebP for transparency, GIF/SVG preserved)
The idea is: if R2 really makes egress “free,” can an image API scale without the usual CDN/storage tradeoffs?
Right now I’m focused on making the pipeline as simple as possible (no knobs, just sane defaults). Pricing is mostly placeholder ($10 = 1k images, $50 = 10k, etc.), but I’m more interested in whether the developer experience feels right.
To get real feedback, I’m offering free access forever to the Launch plan (1,000 uploads/month) with the code: LAUNCHN
I’d love to hear: + Does the R2-backed model make sense to you? + What’s missing for you to trust this in production? + Are the defaults (sizes/formats) useful, or would you expect more control up front?
Live at https://img.pro.
No comments yet.