I really depends on your read/write ratio and how often a given picture is going to be displayed. If you have a very large number of images where each image viewed only rarely, even in its thumbnail form, then it might make sense to do it on the fly. Resizing on the fly every time is something you could test the performance of pretty easily; just throw together a quick page and test it with some images from your class path. Note that you're going to have to use s:transformImageSize to actually transform server side. If you just set the width and height on the s:graphicImage (i assume it passes these through the same way that h:graphicImage does) then the browser will resize the image and it won't look as nice (esp in IE6). If the "big" images are a large size, say.. > 5MB you almost certainly don't want to pull in 20 or 50 of those into memory just to resize them and ship them out as thumbnails. The application i'm working with is a consumer site where we generate the images once and then use them many times... generally about 25-40 per page. Each image is in 2-3 sizes (all of them relatively small... ~20K - 50K . We pregenerate the images we need use and just use normal h:graphicImage tags which point to a filesystem where the pics are then served by apache. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042710#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...