Image requirements guide
Pixels vs KB: why image dimensions and file size are different
Upload forms often list both a pixel requirement and a file-size requirement because they measure different properties. Meeting one does not automatically satisfy the other.
One image can have three separate requirements
Consider this illustrative file:
The raster has 200 pixel columns and 230 pixel rows.
The encoded file occupies 47 KB under the tool's 1024-byte unit convention.
The image is stored using JPEG encoding.
Those values can change independently. A 200 × 230 px image might be 47 KB, 80 KB, or another size depending on its content, format and encoding choices.
Why identical pixel dimensions can produce different KB sizes
Pixel dimensions tell you the number of samples in the raster, not how efficiently those samples can be stored. Two images with the same width and height can contain very different detail, noise, gradients and color patterns. They can also use different formats or compression settings.
That is why there is no honest rule such as “200 × 230 pixels always equals 50 KB.” The relationship depends on the actual image and how it is encoded.
Resizing changes dimensions; compression or re-encoding changes storage
For example, turn a larger photo into exactly 200 × 230 px when that is the required output dimension.
For supported formats, encoding choices can change the resulting byte size without pretending that pixels and KB are the same thing.
A form may require both exact dimensions and a maximum or range in KB. In that case the final output has to pass both checks.
Format changes what kinds of tradeoffs are possible
JPEG
JPEG is commonly useful for photographs and can often produce smaller photo files. It does not preserve transparency.
PNG
PNG preserves transparency, but Upload Ready's browser PNG encoding does not provide a meaningful lossy quality control. A PNG therefore may not be able to reach a very small maximum without changing dimensions or choosing a different accepted format.
WebP
WebP can often balance visual quality and size when the destination explicitly accepts WebP. Always follow the format list shown by the actual form.
Upload Ready validates the actual generated bytes
After processing, Upload Ready measures the real generated Blob bytes rather than estimating from a quality slider or the source file size. That matters because the serialized result is what the destination will receive.
1 KB = 1024 bytes. 1 MB = 1024 KB. Some portals may define units differently, so follow the portal's own instructions when they specify a convention.
Some combinations are genuinely impossible
An exact dimension, a required format and a very small size ceiling can conflict. Upload Ready does not append junk bytes, create fake metadata, silently loosen your entered dimensions, or pretend a failing output passed. If a legitimate generated file cannot satisfy every active requirement, the result remains unsuccessful.
The useful response is to re-check the form requirements, choose another format only if the form permits it, or use a different source image—not to manufacture a byte count.