Clients keep uploading enormous phone photos to a small site. I can resize the display in CSS, but that obviously doesn't stop the browser from downloading a multi-megabyte original. I want a workflow that makes sensible responsive sizes and a modern format automatically, with the original available if needed. The sites aren't large enough to justify a complicated image service. Are you handling this at upload time, in the build step, or through an image proxy?
Handling image sizes without turning every upload into manual work
- webdev
- handling
- image
- sizes
27
4 replies
If the site is small, I’d handle it at upload time or build time, not with a fancy proxy. Generate a few sensible sizes, make WebP or AVIF i...
If the site is small, I’d handle it at upload time or build time, not with a fancy proxy. Generate a few sensible sizes, make WebP or AVIF if you can, and keep the original tucked away somewhere safe.
That’s how we do it on a tiny client site. The browser only gets what it needs, and nobody has to think about the giant original every time.
I’d still leave the original available, but I wouldn’t serve it by default. People upload huge phone shots and then wonder why the page crawls.
Build step is my preference if the uploads are controlled. If clients are dropping files straight into the site, upload-time processing is l...