While building out this site I looked at switching the post images over to Hugo’s built-in image processing pipeline. Here’s what that means, what the trade-offs are, and why we kept things simple.

What Is the Image Pipeline?

Hugo has an extended build mode that can process images at build time. Instead of serving images as dumb static files, Hugo can:

• Resize them to specific dimensions
• Compress them at a given quality level
• Convert them to modern formats like WebP
• Generate multiple sizes for responsive srcset attributes

The result is that a 6MB iPhone photo becomes a 150KB WebP for mobile and a 300KB JPEG fallback for older browsers — automatically, every build.