What should I change to make an image smaller?

A file-size limit and a pixel-dimension limit are different requirements. Check the upload rules first, then decide whether to resize the image or re-encode it at the same dimensions.

Published and maintained by Utilook

Is the limit in bytes or in pixels?

Resizing 4000 × 2000px to 1000 × 500px leaves one-sixteenth as many pixels. That does not mean the file will contain exactly one-sixteenth as many bytes. In this Compressor, re-encoding changes format and quality while keeping pixel dimensions.

Is the limit in bytes or in pixels?
Your situationWhat to choose or check
The destination specifies width and height in pixelsSet the requested dimensions in Resizer. Decide whether you need to preserve the aspect ratio first.Image Resizer
Keep dimensions but try to reduce KB or MBCompare actual output sizes with different formats and quality settings. An exact byte-size target is not guaranteed.Image Compressor
A transparent logo needs a smaller fileTry WebP in Compressor and check the transparent areas. JPEG replaces them with white.Image Compressor

Compression means re-encoding the original

For web pages or email attachments, a smaller file can reduce transfer size. Re-encoding can also change how the image looks, so inspect the preview alongside the actual output size.

A source that is already efficiently compressed can become larger if you save it at high quality or use a different codec. Compression does not guarantee a smaller result. Check Utilook's size comparison and the downloaded file before deciding which version to use.

When to choose JPEG or WebP

JPEG is worth trying first for photographs and other images with gradual color changes. It cannot preserve transparency. For JPEG output, Utilook fills transparent areas with white before encoding.

Try WebP when a logo or graphic needs a transparent background. WebP can preserve transparency, but it is not always smaller than JPEG: the image and the browser encoder both affect the result. This tool accepts PNG input but does not offer PNG output.

Quality 80 does not mean 80% of the original quality

The quality value is a hint passed to the browser's Canvas encoder. Utilook offers 10–100 and starts at 80. It is not an exact visual-quality percentage or a target file size.

For a web preview or thumbnail, lower the value in small steps and inspect text, edges, and color artifacts. Keep the original if you may edit the image later or need an archival copy.

A reproducible sample: transparent shapes at quality 80

On 2026-10-25, we created a 320 × 180px PNG containing a gradient and simple shapes with transparent outer edges. The source is 45,826 bytes. In Chrome 154.0.8037.93, Image Compressor at quality 80 produced a 3,801-byte JPEG and a 2,060-byte WebP from that same source.

Download the source, choose JPEG or WebP with quality 80, and compare the output. JPEG fills the transparent edges with white; WebP keeps transparency. These sizes describe this sample and browser, not a promised reduction or a measured visual-quality score. Other browser encoders can produce different sizes.

What Utilook processes

Image Compressor accepts PNG, JPEG, and WebP and uses Canvas to output JPEG or WebP. Input files must be no larger than 10MB, with each side at most 10,000px and no more than 25MP in total.

Encoding and preview happen in your browser; the image file is not uploaded to the server. After a successful result, only a tool-use count request is sent, without image content.

Measured quality comparisons for continuous tones and small text

The existing transparent-shapes sample, 2026-10-25 measurements and files are preserved. These additional owned 480 × 270px samples were measured with the actual Image Compressor in Chrome 157 on 2026-11-12. The landscape is a procedural continuous-tone/textured illustration, not a photograph. The small-text screen is also a synthetic public demonstration without personal data.

The original was selected in the tool and encoded separately as JPEG/WebP at quality 60, 80 and 95. Every output was decoded to check dimensions. Transparent corners in the small-text sample became white/opaque in JPEG and remained transparent in WebP. Quality is an encoder hint, not a percentage of original quality.

Inspect readability as well as size

Input
Original PNGs below → JPEG/WebP at 60, 80 and 95
Conditions
Local Chrome 157 Canvas encoder; no resizing. Original landscape 248,917 bytes / small text 14,772 bytes.
Observed result
Small-text PNG 14,772 bytes → JPEG quality 95: 15,096 bytes
JPEG quality 60: 7,630 bytes / WebP quality 60: 5,012 bytes
Interpretation
An already-small PNG became larger as a high-quality JPEG. At equal display scale, inspect halos around small strokes, text edges, landscape texture and gradients. Greater byte savings do not establish better visual quality.
Limits and failure conditions
These observations apply to these files, browser and settings—not guaranteed savings, perceptual-quality scores or identical bytes in another browser. One synthetic landscape does not represent every photograph.
Next action
Keep the original and compare previews at the same scale alongside actual bytes. For text/transparency, consider WebP or retaining the original PNG.
Measured quality comparisons for continuous tones and small text
SampleFormat / qualitySource bytesOutput bytesDimensionsTransparency
Synthetic landscapeJPEG 6024891710450480 × 270Opaque source
Synthetic landscapeJPEG 8024891721003480 × 270Opaque source
Synthetic landscapeJPEG 9524891755958480 × 270Opaque source
Synthetic landscapeWebP 6024891711086480 × 270Opaque source
Synthetic landscapeWebP 8024891721380480 × 270Opaque source
Synthetic landscapeWebP 9524891751018480 × 270Opaque source
Small textJPEG 60147727630480 × 270White background
Small textJPEG 80147729841480 × 270White background
Small textJPEG 951477215096480 × 270White background
Small textWebP 60147725012480 × 270Transparent edge
Small textWebP 80147725966480 × 270Transparent edge
Small textWebP 95147729110480 × 270Transparent edge
Original small-text PNG: transparent corners
Original small-text PNG: transparent corners
JPEG quality 60: compare small strokes at equal scale
JPEG quality 60: compare small strokes at equal scale

Put it into practice

References

Verification scope and change record

Published and maintained by Utilook · Example checked:

The added samples were encoded with the actual tool, saved and decoded to verify bytes, dimensions and corner transparency. Identical cross-browser output and objective visual-quality scores were not measured.

  • This revision preserves the shapes example and adds owned continuous-tone/small-text sources with outputs for 12 settings.
Report an error or unclear explanation