A compressed image can be larger because the tool creates a new encoded file, and that encoding may be less compact than the source. A format change, higher quality choice, larger pixel grid or minimum-size padding can add bytes. The original may already be small enough and efficiently compressed.
Compare the actual files before changing more controls. If the source already meets the destination's requirements, you do not need a larger replacement just because it came from a compressor. The image-size tool is useful when you have a specific change to make, such as a byte cap or smaller dimensions.
File size and pixel dimensions are different
Width and height describe the pixel grid. Bytes describe how much storage the encoded file uses. Two images with the same dimensions can have different byte counts because their content and encoding differ.
As a simple dimension example, 1200×800 contains four times as many pixel positions as 600×400. That does not mean every file at the first size must be exactly four times larger. A flat graphic and a detailed photograph compress differently, and each encoder makes its own choices.
Start by recording the source format, dimensions and bytes. Record the same properties for the download. Otherwise, a comparison may accidentally attribute a crop, resize and format change to the quality slider alone.
A conversion is not a guaranteed saving
JPEG and PNG store image information differently. The PNG specification defines lossless raster storage. Saving the decoded pixels from a JPEG as PNG does not recover detail that the JPEG discarded earlier.
For a photograph, that PNG may use more bytes while retaining the same visible limitations. It can be appropriate when a later workflow requires PNG, but a larger file is not evidence that new detail appeared.
The reverse is not guaranteed either. A small flat diagram or optimized logo PNG may already be compact. Converting it to JPEG can add graphic artifacts without providing a useful saving. Compare the actual outputs rather than choosing from the extension alone.
The source may already be optimized
A photo saved from a chat, downloaded from a website or exported previously may already have reduced dimensions or substantial lossy compression. There may be little useful byte saving left without a further visible compromise.
Increasing a quality slider while re-encoding such a source can produce a larger file. It stores a new approximation of the pixels available now; it does not reopen the camera original or recover earlier discarded texture.
Return to a better master when you need a new crop or larger delivery copy. If you only have the small source, keep its limitations in mind. Repeated conversions cannot turn it into an untouched original.
A higher quality setting can spend more bytes
The HTML canvas specification defines a quality parameter for supported variable-quality exports. It does not promise one universal mapping from the slider to bytes or visible detail across browsers.
Quality 90 in one exporter is not a percentage of retained source information, and it is not guaranteed to match quality 90 elsewhere. A higher setting can be useful for difficult detail, but it can also create a larger delivery copy than you need.
When comparing settings, use the same source and hold crop, dimensions, format and sharpening constant. The JPEG quality guide includes actual downloadable comparisons and explains the limits of that experiment.
Check resizing and sharpening
Custom Exact size can enlarge a smaller source to the requested dimensions. More output pixels do not recreate missing detail, and the new file can use more bytes. Use Keep original pixels when resizing is unnecessary, or Fit within to reduce within maximum bounds.
Sharpening changes local edge contrast. It can also change the image that the encoder must store. Do not assume turning sharpening on is a free improvement with the same byte count.
For a fair size comparison, start with sharpening off. Add a restrained amount only if inspection shows it helps the actual resized image. Check hair, lettering and high-contrast edges for new outlines.
Understand PNG and WebP controls
This tool does not expose a PNG quality slider that trades detail for bytes. Its PNG export stores the rendered result without a new lossy PNG step. Resizing, cropping and sharpening can still change that result before it is encoded.
WebP is another option when the destination accepts it. Google's documentation describes its lossy and lossless capabilities, but those format capabilities do not guarantee a smaller result for every source or exporter. IGCOMPRESSOR's current WebP workflow is an opaque export on white.
If transparency matters, choose PNG here and inspect the background. Do not sacrifice a required transparent edge just to get a smaller number. The background guide explains that decision.
Separate a maximum cap from a minimum size
A byte cap tells the tool to search for a result within a maximum. In general KB and Custom cap workflows, dimensions can also shrink when quality changes alone do not fit. Always inspect the downloaded width and height alongside its bytes.
A JPEG minimum-size option does the opposite when needed: it adds comment data to increase bytes. That padding does not add visual information. Avoid setting a minimum simply because a larger file sounds better.
For an application or exam upload, check your exact current notification and submission instructions. Required format, dimensions, minimum bytes and maximum bytes are separate conditions. The KB guide explains those constraints without promising portal acceptance.
Diagnose one file before processing the batch
- Keep the original and note its format, pixel dimensions and actual file size.
- Identify what the destination really requires, rather than aiming for a saving without a purpose.
- For a controlled comparison, keep dimensions and sharpening unchanged and export in the same format.
- Change one setting at a time, checking detail as well as bytes.
- Use a cap only when you need a maximum, then inspect the resulting dimensions too.
- Keep the source if it already meets the requirements and the new export adds no useful benefit.
IGCOMPRESSOR processes the file on your device. Its result is a new delivery copy, not a guarantee of savings or proof that a receiving service will leave it unchanged.
Limits and checklist
No compressor can promise a smaller file, identical visible detail, unchanged dimensions and every output format for every source. A byte saving is useful only when the output still serves its purpose.
- Compare the actual source and download, not two thumbnails.
- Record format, pixels and bytes separately.
- Keep a suitable original rather than repeatedly re-encoding it.
- Isolate quality from resizing, cropping and sharpening.
- Check transparency before changing formats.
- Use minimum-size padding only for an actual stated requirement.
- Stop when the file meets the task and looks suitable.