Skip to content
FlipConverto home

Image Compressor

An image compressor to compress images — JPG, PNG or WebP — and reduce file size with a quality slider and a live before/after comparison, all in your browser.

Loading Image Compressor…

Runs entirely in your browser. Files stay on your device — nothing is uploaded. Verify it yourself

What quality setting should I use for web images?

75 to 85 for photographs — usually indistinguishable from the original at normal viewing size, at a fraction of the file size. Below about 60, compression artefacts become visible around sharp edges and in flat areas of colour.

Cost
Free, no limits
Upload
None — runs on your device
Sign-up
Not required
Works offline
Yes, once loaded

How to reduce image size

  1. Choose an image

    Select a JPG, PNG, WebP, GIF or BMP file, or drag it onto the drop area. It is read directly from your device and never uploaded.

  2. Pick an output format

    JPEG for photographs, PNG for screenshots and anything needing transparency, WebP for the web generally — it is 25–35% smaller than JPEG at the same quality.

  3. Adjust the quality

    Drag the slider and watch the size comparison update. 75–85 is usually indistinguishable from the original.

  4. Compare and download

    Check the before and after previews side by side, then download. If the file got larger, the original was already well optimised — keep it.

Examples

  • A 4 MB phone photo at quality 80Typically a few hundred kilobytes

    Usually indistinguishable at normal viewing size.

  • A screenshot saved as PNGLittle or no saving

    PNG is lossless — the quality slider does nothing for it.

Key features of the Image Compressor

  • Quality slider with a live before-and-after comparison
  • Outputs JPEG, PNG or WebP
  • Reports the actual size saved, including when there is none
  • Processes on your device — images are never uploaded

Supported formats

Input

  • JPG
  • PNG
  • WebP
  • GIF
  • BMP
  • AVIF

Output

  • JPEG
  • PNG
  • WebP

When should you use this?

  • Getting a photo under an upload size limit.
  • Reducing page weight before publishing images to a website.
  • Shrinking a batch of photos for email.
  • Converting to WebP to save bandwidth.

Limitations

  • Compression is not reversible. Detail discarded at this step cannot be recovered, so always compress from the original rather than from a previously compressed copy.
  • Re-encoding an already well-optimised JPEG at high quality can produce a larger file than the original. The tool reports this honestly instead of claiming a saving it did not achieve.
  • JPEG has no transparency. Transparent areas are composited onto white rather than kept.
  • The quality slider has no effect on PNG output, because PNG is lossless by definition.
  • Very large images are limited by the memory your browser will give the page — phones are stricter about this than desktops.

Troubleshooting

The file got bigger

It was already well compressed, and the encoder is spending bits preserving detail the previous pass softened. Lower the quality, or keep the original.

The transparent background turned white

You output JPEG, which cannot store transparency. Choose PNG or WebP instead.

The tab froze on a very large image

The work happens on your device. Close other tabs, or resize the image before compressing.

Common mistakes to avoid

  • Compressing a file that has already been compressed several times. Each pass degrades the previous result.
  • Using PNG for photographs. It produces files several times larger than JPEG for no visible benefit.
  • Pushing quality very low to hit a size target when resizing would achieve it with far less visible damage.

Pro tips

Tips for better results

  • Quality

    Start at 75–85 for photographs

    Quality 75–85 is the usual sweet spot for photographs. Below about 60 the artefacts become visible around edges and in flat colour.

  • Web performance

    WebP is the sensible default for the web

    WebP is typically 25–35% smaller than JPEG at equivalent quality and supports transparency. It is the sensible default for the web.

  • Order of work

    Resize first: it saves more than any quality setting

    Resize before compressing. An image displayed at 800px wide gains nothing from being 4000px, and downsizing saves far more than any quality setting.

Concepts behind image files

The terms that decide what changes when an image is compressed, resized or converted.

Resolution
The pixel dimensions of the image or frame, such as 1920×1080. It sets the amount of real detail present. Enlarging afterwards interpolates between existing pixels and produces a softer picture — no amount of upscaling recovers detail that was never captured. Reference: CSS Values and Units Module Level 4, W3C
Colour depth
How many bits describe each pixel's colour. Most formats use 8 bits per channel, giving about 16.7 million colours. Indexed formats such as GIF store a palette of at most 256 instead, which is why photographs converted to them show visible banding. Reference: GIF89a Specification, CompuServe, hosted by W3C
Metadata
Information stored alongside the content itself — camera settings, GPS coordinates, artist and album tags, author names. Conversion frequently drops it, which is usually a privacy benefit and occasionally a loss if you relied on it.
Colour space
The rule that maps the numbers in a file to visible colours. sRGB is what browsers assume, Display P3 and Adobe RGB describe wider ranges used in photography, and CMYK describes ink rather than light. A file converted without its profile keeps its numbers and changes its colours. Reference: sRGB, the default colour space, ICC
DPI and PPI
Dots or pixels per inch: a number describing how large the picture is meant to print, stored as a tag beside the pixels. It changes nothing on a screen, which draws by pixel count alone, and nothing about the detail present — only the size a printer lays the same pixels down at. Reference: CSS Values and Units Module Level 4, W3C
EXIF data
The block cameras and phones write into a photograph: exposure, lens, orientation, the date, and on a phone usually the coordinates it was taken at. Converting writes a fresh file without it, which loses the shooting data and removes the location along with it. Reference: CIPA DC-008: Exchangeable image file format (Exif), CIPA
Pixel
One addressable square of a raster image, holding a single colour. A 1920×1080 picture is 1920 across and 1080 down, about 2.07 million in all, and that count is fixed when the file is written — which is why enlarging one later invents the pixels it does not have. Reference: PNG Specification, Third Edition, W3C

Standards and terms behind the Image Compressor

The named things this tool works with, and the documents that define them.

Canvas APISpecification
The HTML drawing surface that lets a browser decode, resize and re-encode an image without a server. Reference: Canvas API
JPEG quality factorHow it works
The 1-100 encoder setting that scales the quantisation tables, trading visible detail against file size.
Lossy compressionHow it works
Permanently discarding detail the eye or ear is unlikely to miss, in exchange for far smaller files.
Web performanceWhere it is used
Page weight and loading speed, the usual reason to trade an image format for a smaller one.
Email attachment limitsWhere it is used
The practical ceiling on what mail will carry — commonly 20-25 MB per message.

Also searched as: make a photo smaller in mb, compress a picture for email, reduce image file size without losing quality.

How lossy compression works

JPEG and WebP discard information the eye is least sensitive to. They work in a frequency domain, keeping the broad structure of an image and throwing away fine high-frequency detail — which is why compression artefacts appear first around sharp edges and text, and are almost invisible in smooth gradients or foliage.

The quality slider controls how aggressively that detail is discarded. Between 75 and 85 the loss is usually imperceptible at normal viewing size while the file is a fraction of the original. Below about 60, artefacts become visible: blockiness, colour banding and haloing around edges.

Compression is not reversible

Once detail is discarded it is gone. Re-saving a JPEG repeatedly degrades it further each time, even at high quality, because each pass compresses the already-compressed result. Always compress from the original, never from a previously compressed copy.

When the file gets bigger

Re-encoding an already well-optimised JPEG at high quality can produce a larger file than the original — the encoder is being asked to preserve detail that the previous compression already softened, and spends bits doing it. The tool reports this honestly rather than claiming a saving it did not achieve. If you see it, either lower the quality or keep the original.

Choosing a format

JPEG for photographs. It has no transparency, so transparent areas are composited onto white here rather than rendered black.

PNG is lossless — the quality slider does nothing. Right for screenshots, diagrams, line art and anything needing transparency. Wrong for photographs, where it produces files several times larger than JPEG for no visible benefit.

WebP is typically 25–35% smaller than JPEG at equivalent quality and supports transparency. Supported by every current browser, so it is the sensible default for the web unless you need to support something very old.

Privacy and file handling

The Image Compressor runs entirely in your browser. Your file is read by the page, processed on your own device, and the result is handed straight back to you — no copy is sent anywhere, because none needs to be.

You can confirm this rather than take our word for it: open your browser’s developer tools, watch the Network tab, and use the tool. No request carries your file or your input. It also keeps working with the connection off.

Details are in the privacy policy.

What next?

Reducing dimensions usually saves more than compression alone.

Resize it as well

Image Compressor — questions

Can I compress a photo on my iPhone or Android phone?

Yes, in the phone’s browser: there is nothing to install, and the photo is not uploaded. On an iPhone or iPad the output choices are JPEG and PNG, because Safari cannot write WebP.

How do I compress a PNG or a JPG?

To compress a JPG, keep JPEG as the output and lower the quality. To compress a PNG, choose WebP or JPEG instead: PNG is lossless, so the quality slider has nothing to trade away in a PNG. WebP keeps its transparency.

Are my images uploaded?

No. Compression happens on a canvas in your browser using its native image encoders. You can open DevTools and confirm in the Network tab that your image is never sent while you compress.

What quality setting should I use?

75–85 for photographs on the web — usually indistinguishable from the original at a fraction of the size. Below 60, compression artefacts become visible around edges and in flat colour areas.

Why did my file get bigger?

Because it was already well compressed. Re-encoding at high quality asks the encoder to preserve detail the previous pass already removed, and it spends bits doing so. Lower the quality, or keep the original.

Should I use JPEG, PNG or WebP?

JPEG for photographs, PNG for screenshots and anything needing transparency, WebP for the web generally — it is 25–35% smaller than JPEG at the same quality and supports transparency. Every current browser handles WebP.

Does compressing repeatedly make it worse?

Yes. Lossy compression is not reversible, and each pass compresses the already-degraded result. Always work from the original file.

Part of Image Tools · Browse every tool