Home/ Questions/Q 6470951
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T06:10:09+00:00

Let me start off by stating that I realize the arguments against doing CSS

  • 0

Let me start off by stating that I realize the arguments against doing CSS Sprites for large images. I even asked a question about why that could be considered a bad idea (and added an answer of my own). Now that we’ve had that talk…

I’m going to be making a large CSS Sprite-map. For the process of making this sprite-map, it behooves me to know what (if any) limit exists for the height and/or width of a sprite image in order for browsers to properly process it.

The ultimate reason behind this question is a debate over whether to lay out the sprite images in a grid or in a single row/column. For example: is it necessary or beneficial to do 4000 x 3000 instead of 400 x 30000?

Edit: The sticking point here isn’t about what size images can be, but rather what size browsers can process for sprites. Given the lack of detail thus far, I’m moving forward with generating the single-large-column sprite. I’ll post details of my experiences as an answer once that is complete.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Sometimes it’s more of a matter of download time. Since browsers can use multiple connections to download files, a huge image can take longer to download than a few smaller ones.

    If your image is so big that it’s slowing down page load maybe it’s time to consider several smaller sprite images.

    Direct-X 9 has a size limit if 4096 pixels, so any Internet Explorer filters applied to these elements will crop them at 4096 pixels.

    See: IE display transparency bug on height > 4096px?

    • 0