Image optimization using both next.js / vercel, and supabase - am I paying to optimize twice?
I set up images using the next.js loader, as described here in the docs.
Then I uploaded 2k images, and immediately hit the usage caps on both supabase image optimization, and vercel image optimization.
But then I realized. This setup seems pretty stupid? Aren't I just paying suapabse to optimize the image, but then again for vercel to optimize the pre-optimized image? Why do that step twice?
I was using it for the transformation (pre-cropping to a square), but I think I could write that out.
Am I missing something, or is this a dumb approach?
Posted Jan 31, 2025, 11:35 PM UTC
20