1

at the moment I'm designing a new gallery and I have quite a lot of different image sizes for different ways pf presentation in the frontend. And now I'm wondering if I should create every size on the server or just create a few and then use browser resizing and HTLM/CSS "croping".

So it's many images on the server, a lot of space on the disk and also a lot of requests from the client against fewer requests, fewer space and resizing/cropping with the browser.

I tend to think the second solution is more advanced and modern, but also more complicated?

Thanks for any advice!

Community
  • 1
  • 1
Jona
  • 2,087
  • 15
  • 24

2 Answers2

0

It's really a trade-off as you've said yourself. Performance is increasingly important though, and even affects page ranking, which is a good reason to keep various sizes on the server, i.e. only send thumbnails when that's all the user needs to see.

If you wanted to go to the programming effort, you could use a library like ImageMagick to generate smaller images from large ones. This way, you only need to store the large images on the server. The downside being programming effort and extra server load; since space is cheap, probably not worth it unless you need to serve many different variants.

mahemoff
  • 44,526
  • 36
  • 160
  • 222
0

You could create a handler to serve up your images. When a request is made for an image in a size you don't yet have stored in the file system on your server, you could do the resize, save the file and send it to the client.

That way you only have the files that are needed on the server.

Antony Scott
  • 21,690
  • 12
  • 62
  • 94