Skip to content
user@convertitive:~$convertitive

Image Compress

Drop a file, slide the quality, watch the bytes drop. Stays in your browser.

The compressor below uses two levers: scale (the percentage of original pixel dimensions) and quality(how aggressively the encoder discards fine detail). Both run on the browser’s Canvas2D + native image encoders — no upload, no server. The live before/after size readout shows the trade-off as you move the sliders. For most web use cases, WebP at 80% quality and 100% scale cuts file size 40-70% with no visible difference.

Drop an image here, or

PNG, JPG, WebP up to 32 MB. Stays in your browser.

How to use

  1. Drop your file

    PNG, JPG, or WebP up to 32 MB. The original dimensions and size appear.

  2. Slide the scale

    100% keeps pixel dimensions. 50% halves both width and height (and quarters total pixels). For thumbnails, 25-50% is normal; for hero images, leave at 100%.

  3. Slide the quality

    WebP at 80% is the modern web default. JPEG can go as low as 60% on photos before showing artifacts. PNG is lossless — the slider has no effect.

  4. Download the result

    The output filename ends in -compressed. Side-by-side dimension + byte readout confirms the savings.

Quality vs file-size guide

Use caseFormatQualityTypical savings
Hero image (above-the-fold)WebP85%40-60% vs JPEG
Article inline photoWebP75%60-80% vs PNG
Thumbnail / list imageWebP / JPEG65%80%+ vs PNG
Email attachmentJPEG80%50%+ vs PNG
Print archivePNG / OriginalN/AKeep lossless

Frequently asked questions

Does the image upload anywhere?
No. The compressor runs entirely in your browser using createImageBitmap + Canvas2D + the browser's built-in JPEG/WebP/PNG encoders. Convertitive has no way to see your file.
Why is my PNG output sometimes larger than the original?
PNG is lossless and re-encoding doesn't recompute the compression — and the browser's PNG encoder is less sophisticated than dedicated tools like pngquant or oxipng. For PNG-to-PNG savings, use a dedicated PNG optimizer offline. To shrink PNGs significantly, convert to WebP instead.
What quality should I pick?
WebP and JPEG: 80% is a safe default. 75% is fine for most content. 60% starts showing artifacts on photographs but is fine for cartoon-like or flat-color content. Below 50% is rarely the right answer.
Why doesn't the quality slider work on PNG?
PNG is lossless — every byte of the original image is preserved. There's nothing to discard. To shrink a PNG, you can either reduce its dimensions (scale slider works) or convert it to WebP/JPEG.
Does compressing twice degrade quality further?
Yes — each lossy round drops more information. Always compress from the original source, never from a previously-compressed copy. If you need to make small adjustments, archive the source PNG and re-compress fresh each time.
Can I batch-compress multiple files?
Not yet. The widget processes one file at a time. For large batches, a desktop tool like ImageOptim (Mac) or oxipng (CLI) handles bulk operations.

About

Why WebP usually wins

WebP uses the same lossy-coding techniques as JPEG plus an extra prediction step that JPEG lacks. The result: 25-35% smaller files at the same visual quality for photographic content, and 50%+ smaller for graphic content (illustrations, screenshots). Browser support has been ~97% since 2020 — Safari shipped it in version 14.

When PNG is the right answer

PNG is lossless, supports transparency (alpha channel), and handles flat-color content efficiently. Use it for logos, icons, screenshots with sharp text, or any image where pixel-exact fidelity matters. PNG is the wrong tool for photographs — file sizes are 5-10× JPEG at no visible benefit.