Just a few observations.. The "powers of 2 thing": It's true. It's got nothing to do with Poser really, it's got everything to do with the the underlying operating system (certainly Windows, and IIRC, Unix). Their system calls to manipulate bitmaps (which, incidently, are probably the fastest available 'cos they're written at the lowest level to take advantage of the PC's machine language), work best with bitmaps which are in powers of 2, especially in the X dimension, and probably in the Y dimension too - I'm a little rusty on that aspect. Bmp/jpeg/tiff/png size: Whatever they are on disc, once they get into Poser they'll be decompressed (if necessary) into memory to fit the "powers of 2" thing. It's quicker that way (until, of course, you start running out of real memory and disk-swapping starts up..) DPI/PPI (Dots Per Inch/Pixels Per Inch) etc. If you're only going to render for screen, then ignore it entirely. If you're going to render for printing things get a lot more complex, and I'm not going there now (too tired). The rest of this (if there is much more, I'm thinking(?) as I type) is directed at screen pics only... Consider a bitmap, 1024x1024. For a head, say. How big will that head texture be in the final render? If it's a close-up portrait then (on a 1280x1024 image) you'll probably need all of it. Don't forget, the texture wraps around the head, so approx. 1/2 of it won't be seen. But if it's for the head on a full-figure shot (with the figure taking up most of the screen), then the head will be approx 1/6th of that size. So the rendering software will have to scrunch the texture down, anti-alias it etc. to 1/6th of its size. And lose a lot of detail in the process. Now, most 2D applications can do a better job of re-sizing down than renderers can ('cos 2d aps are designed to be able to do these things, whilst renderers have other things on their minds). So in that case, squish the bitmap in a 2D app 1st (by about a sixth). Then apply the squished bitmap in Poser. If any of the above didn't make sense, I apologise - it's just my way of looking at things and probably explained badly. But it seems to work for me.. Things are different if you're going to render for printing, but that's a whole new can of worms, for another night.. I really do hope that helps.. It's about as clear as I can make it without going into minute mathematical/programming/scientific detail (much of which I don't have anyway) as I can. If I confuse or (more likely, have got something wrong), I apologise. Cheers, Diolma (drat, took so long typing that many others answered befoe I could post. Oh, well, feel free to ignore..)