imgproxy resizes and optimizes images on demand. Keep the original in object storage and request the size your page needs through a URL.
We started using it because our own blog thumbnails were slow. The page displayed a small image, but the browser still downloaded the full original. One of those images was about 1.8 MB. Changing its size with CSS didn’t make the download any smaller.
That’s a lot to download for a thumbnail.
We now serve that image as WebP: about 9 KB at 320 pixels wide or 20 KB at 640 pixels wide. The original is still available when someone wants to enlarge it.
I’ve paid for image resizing services before. If you mainly use a service like Imgix, Cloudinary, or ImageKit to resize and optimize images, you can self-host imgproxy on Blossom and save yourself a separate bill.
Deploy with a Prompt
We deployed imgproxy on Blossom and moved our images to Cloudflare R2.
Deploy imgproxy on Blossom with R2. Help me connect it to my blog.
The App Guide covers deployment. Here’s how we’re using it:
- R2 keeps the originals. We keep one original and let imgproxy handle the different sizes.
- imgproxy serves the sizes we need. A thumbnail gets a small image. An article gets a larger one.
- Cloudflare caches the results. Repeated requests can use the cached image instead of resizing it again.
imgproxy is written in Go and is very lightweight. Cloudflare also caches the images after they’re generated. That keeps resource usage extremely low. We easily get away with two containers at 0.5 vCPU and 512 MB of RAM each. If it fits within existing Blossom capacity, it’s free. That’s the nice thing about Blossom.
Here’s one of our blog cards using a smaller image:

Let the Browser Pick the Size
Make the blog thumbnails load faster. Let readers click to see the original.
We updated the homepage, category pages, search results, and related articles. The image markup gives the browser a few sizes to choose from. We don’t have to generate and manage a separate folder of thumbnails.
Keep the Images, Replace the Containers
imgproxy doesn’t need a database or an attached Volume for this setup. The originals are in R2, so we can replace or add Containers without moving the images.
We checked this by redeploying imgproxy and requesting the images again. The same URLs still worked.
That’s the part I like about this setup. We get faster images without managing a bunch of thumbnails, and another app running on Blossom that we actually use.
Want to try it? Start with the imgproxy App Guide.