I’ve been thinking about building responsive web sites lately. This has lead me down the path towards fluid image scaling and on to the problem of serving appropriately sized images for the client platform. In other words, how can we serve up small scale images for mobiles and tablets and larger images for desktops?
Fluid image scaling alone is not sufficient, mobile clients can’t be expected to download a 1000px wide image then scale it down to 200px wide. This is both slower and more tariff hungry than necessary.
The immediate solution is to use media queries to swap out different scaled images for different display sizes. But this is cumbersome to manage on a large scale and offers no robust solution when using the
SRC attribute of the
I’m not the only one to recognise this as an issue for responsive we design. In the course of my research I came a cross this article by the Filament Group, proposing another solution to the problem. The Filament Group method uses .htaccess files and some JS to serve up different sized images based on the screen width.
Within the PHP script is a nested array that lists images files and their relative percentage scales. The array is structured such that each image is assigned a URL safe id (‘puppy’ in the example). For each image file the nested array describes the file’s scale. The largest image has a scale of 100 down to the smallest at 0. The 0 scale image is initially loaded by the browser, so in the example this is a 1x1 pixel transparent PNG.
$images['puppy'] = 'puppy_1280x960.jpg'; $images['puppy'] = 'puppy_960x720.jpg'; $images['puppy'] = 'puppy_640x480.jpg'; $images['puppy'] = 'puppy_320x240.jpg'; $images['puppy'] = 'puppy_128x96.jpg'; $images['puppy'] = 'clear_pixel.png';
The PHP script serves up an images file based upon two GET parameters, id and scale. The script returns the first file that is greater than the requested scale. So a URL like …/getimage.php?id=puppy&scale=47 will return the image at scale 50. If no scale is specified the 0 scale image is returned. This is important, I’ll explain why in a bit.
In the HTML file the image
SRC attribute as the scale parameter.
Taking this information, the server returns the appropriately scaled image for the width of the image element. So mobile browsers will download smaller image files than desktops. The only overhead is the initial request for the 0 scale image, which is why I’ve set it to a clear pixel.
It goes without saying that the image data need not be stored in an array, a data base would probably be better and certainly easier to integrate with a CMS.
Also, while I’ve use a relative scaling measure (0-100) the same affect would be achieved when using absolute width measurements. There’s pros and cons to each approach, I’ll leave you to judge.
demo page is set up here and the source is up on GitHub. This is far from polished, so any comments, criticisms or suggestions are more than welcome. EDIT: Since swapping hosts, the demo no longer works - sorry.