FAQ's
Why does the 24 KB target matter when my image is only slightly above it?
Why can a tiny change in the original image affect the final compressed size?
Why does the original file extension not tell me how large the compressed file will be?
Why does a 24 KB target produce different results for different original file sizes?
Can I compress the same image to 24 KB more than once?
Why does a 24 KB file sometimes have a larger file-size reduction than expected?
What happens when the original image contains a lot of unnecessary image data?
What does “24 KB or lower” actually mean?
Why can an image with the same width and height become much smaller after compression?
Why does adding a small amount of detail sometimes increase the file size considerably?
Can a file be too small to contain enough information even though it meets the 24 KB limit?
Why is 24 KB very different from a “small” image?
A “small” has no precise file-size meaning, while 24 KB establishes a measurable limit. This makes it useful when a system has a specific maximum rather than a general preference for smaller files. The compressor can therefore work toward a clearly defined target.
Why shouldn't I judge compression by the percentage reduction alone?
A 90% reduction can mean very different things depending on the starting file size. Reducing 50 KB by 90% produces a very different result from reducing 5 MB by 90%. For a 24 KB target, the more useful measures are the final file size and whether the resulting image remains suitable for its intended purpose.