Hello!
I'm just curious to know why people use image slicing. Wouldn't it look the same, if it were all put together? I'm pretty sure PSP7 has an image slicer? Though I don't know how to use it.

Thanx for the help!

slicing helps large images load faster.

People think it helps images load faster, but really it doesnt...if anything it would make them load slower (only marginally though)...it just makes it look like its loading faster.

Ohh I see. I thought it would do more then that.. Lol. Thanx for the help :D

It does load faster, and it does allow for other things, but I am way to tired to explain it this late, lol.

doesn't really load faster...just loads smaller images but all in all, the same about of data has to be transfered so it doesn't make a differnece, just looks like it does.

and mostly image slicing is used to put them as backgrounds in tables.
its easyer to add the content in small cells with small background then to do it with one big image

it doesn't load faster but you will see it earlyer
like if you have one big file you will have to wait till the hole file is loaded
when you slice you will see everytime one little file loaded so it looks like its faster

Look, I am tired of people with no understanding trying to act like they know everything. I respect the fact that most people here are just learning, so I am patient, but I see so many half-truths around here it isn't funny.

When you slice an image it will load faster. Why? Imagine you have a 200 pixel by 200 pixel image that's 200k in size. You can optimize this image, say, to under 50k. But if you sliced this image into four separate images, each of which is 50 pixels by 50 pixels in size, and then optimize each image, the combined size of all four images might be as low as 10k.

Like I said, I could explain in detail why and how this happens, but it would be a really long post.

Slicing also reduces file sizes espcially if you're repeating something... such as the headers of navigation bars.

And also, if you're using GIF with one large imgae with different areas having their own large number of colors, splitting them would allow each image to cover a wider area of the palette pertaining to just that image, instead of having being limited to 256 (?) colors for the whole image.

Look, I am tired of people with no understanding trying to act like they know everything. I respect the fact that most people here are just learning, so I am patient, but I see so many half-truths around here it isn't funny.

When you slice an image it will load faster. Why? Imagine you have a 200 pixel by 200 pixel image that's 200k in size. You can optimize this image, say, to under 50k. But if you sliced this image into four separate images, each of which is 50 pixels by 50 pixels in size, and then optimize each image, the combined size of all four images might be as low as 10k.

Like I said, I could explain in detail why and how this happens, but it would be a really long post.


Slicing and optimising obviously ruduces the size and makes it load faster...but most people dont realise that, they think they can just slice it and thats it. So you are right yeah, if you slice and optimise it will load faster, but the two things arent synonymous and that wasn't the question

Any image you use on a webpage should be optimized, that is a given, therefore slicing it will make it load faster if you know you are supposed to optimize it anyway.

There are certain webhosts that only allow a certain amount of image size. Making one image multiple images allows the user to use the ability to use them to make one large image without exceeding the size limit. Wow, I got all technical....

still ONLY slicing images will not make the image load faster.

If you slice a wooden block from 5kg into two pieces you still have 5kg together. The only thing is that you now have 2 pieces and not one big block.

It's that simple :rolleyes:

digital images are not wooden blocks, and web browsers handle smaller images better than one large one. Nothing is "as simple as that", as you say.:rolleyes: :rolleyes:

Web browsers load sliced images faster than unsliced images since it is possible to open many simultaneous HTTP connections to download the image slices. This works because you don't usually get the maximum throughput for any one connection and smaller packets of data download proportionally faster than larger packets.

Imagine having one arm to carry a 50lb block up the stairs. Now imagine having 50 arms to carry 50 1lb blocks up the stairs. Which do you think would be easier on your arm?

Once you slice you can cutout the useless parts. Besides that you can use for example background images of 1 pix width, to fill a whole titleblock or something, you can save every images the right way (jpg, gif) so it's compressed logically and blah blah lots of other stuff ofcoarse. Besides that if you slice, the files are loaded seperatly using more ports to connect, usually means faster loading. I usually have a 500KB image of a website i design once i save it as *.jpg 70% compression. If i slice & code i eventually have about 50KB of images and a 10KB html file. so that's a 10th of an already compressed image AND it looks better cause you compressed every single part the right way.

Photoshop has a nice slicer, but it does create a horrible html page (optional). I suggest you throw that html page away and build the sliced file up from scratch. Ofcoarse you need to have a little html knowledge though, and the way html is used best.

Exactly. I don't think most people here are ready to hear about making whole websites in photoshop, though. You should see the response from the dreamweaver thread, LOL.

Hello!
I'm just curious to know why people use image slicing. Wouldn't it look the same, if it were all put together? I'm pretty sure PSP7 has an image slicer? Though I don't know how to use it.

Thanx for the help!

I think they use it because it makes images load faster. People say it doesn't but it must do. I did tests....lol. It looks the same because each bit of image is put into a table margin or summat so basically it's the same image fitting together but in bits

If you optimize it, it does load faster. I know so because I normally have an 800k image, optimized as a single .png it would be about 400k. But if I slice it and optimize it, then I end up with about 20 little images that all fit together, each of them about 4k. That's how it works with optimizing.