Skip to content
BeeTools— Fast. Private. Free.

Image Compressor

Runs in your browser

Compress JPEG, PNG and WebP images on your device. Drop up to 20 files and see exactly how much you saved.

Image Tools

Your data never leaves your device

This tool runs entirely in your browser. Nothing you enter is uploaded, stored or logged by BeeTools.

How to use the image compressor

  1. Add your images

    Drag files onto the drop zone or click to browse. JPEG, PNG, WebP, GIF and BMP are all accepted, up to 20 files of 30 MB each.

  2. Wait a moment — compression starts automatically

    Each file is processed as soon as it lands. There is no upload step, so this is usually near-instant.

  3. Adjust quality if you need to

    Start at the default 75%. Drop toward 50% for images that only need to look right on a screen; raise it toward 90% if you can see artefacts in areas of flat colour or gentle gradient.

  4. Consider converting to WebP

    For anything going on a website, WebP at the same quality is usually noticeably smaller than JPEG.

  5. Download individually or all at once

    Use the arrow on any row for a single file, or Download to save the whole batch.

Features

  • Up to 20 images at once

    Drag a folder of photos in. Each one is compressed and reported separately.

  • Live before-and-after sizes

    Every file shows its original size, new size and the percentage saved.

  • Quality you control

    Adjust the quality setting and the whole queue re-compresses immediately.

  • Convert while compressing

    Output as JPEG, WebP or PNG, or keep each file in its original format.

  • Never freezes the page

    Processing runs in a Web Worker, so the interface stays responsive during a batch.

  • Your photos never leave your device

    No upload, no server-side copy, nothing to delete afterwards.

About this tool

Most image compressors work by uploading your photos to a server. This one does the work on your own device using the Canvas APIs built into your browser, which means two things: your photos are never transmitted anywhere, and compression starts the instant you drop a file rather than after an upload.

Compression here means re-encoding at a lower quality setting. For photographs that is exactly the right trade: at 75% quality most images are visually indistinguishable from the original at a fraction of the file size, because the information being discarded is detail the eye does not attend to. You can adjust the setting and see the resulting size immediately for every file in your queue.

Downscaling — which is often the bigger win — uses stepped halving rather than a single resampling pass. Going straight from 4000 pixels wide to 400 in one step samples too few source pixels and produces visible aliasing; halving repeatedly until close to the target keeps every source pixel contributing. It is a small implementation detail with a large, visible effect on quality.

You can also convert while compressing. WebP is typically 25–35% smaller than JPEG at matching visual quality and is supported by every current browser, so it is usually the best choice for the web.

  • Up to 20 images at once. Drag a folder of photos in. Each one is compressed and reported separately.
  • Live before-and-after sizes. Every file shows its original size, new size and the percentage saved.
  • Quality you control. Adjust the quality setting and the whole queue re-compresses immediately.
  • Convert while compressing. Output as JPEG, WebP or PNG, or keep each file in its original format.
  • Never freezes the page. Processing runs in a Web Worker, so the interface stays responsive during a batch.
  • Your photos never leave your device. No upload, no server-side copy, nothing to delete afterwards.

Frequently asked questions

Are my images uploaded to a server?

No. Compression uses the Canvas API in your own browser, and your files are read directly from disk into the page. Nothing is transmitted, which you can confirm by watching your browser’s network panel while compressing. This is the main practical reason to use this tool over most alternatives.

How much smaller will my images get?

For photographs straight off a phone or camera, savings of 60–80% at 75% quality are typical, because those files are usually saved at a quality setting far higher than any screen needs. Images that have already been compressed once will save much less — sometimes nothing, since re-encoding an already-compressed JPEG can add bytes rather than remove them. The tool tells you honestly when there was no gain.

Will compression visibly damage my images?

At 75% quality, almost never for photographs. Lossy compression discards detail the eye is least sensitive to, so the first 60% of file size usually goes without a visible difference. Where you will notice it is in large areas of flat colour or smooth gradient — skies, studio backgrounds — which can show faint banding. Screenshots, logos and line art are a different case: they compress badly as JPEG and should stay PNG.

Why did my PNG get bigger?

PNG is a lossless format, so the quality slider does nothing for it, and the browser’s PNG encoder is not as sophisticated as a dedicated tool like pngcrush. If the source was already well-optimised, re-encoding can produce a slightly larger file. For photographs, convert to JPEG or WebP instead — that is where the real savings are.

Should I use JPEG or WebP?

WebP for anything going on the web: at equivalent visual quality it is typically 25–35% smaller, and every current browser supports it. Stay with JPEG when the file needs to work in older software, be attached to an email, or be opened by someone whose tools you do not control — JPEG support is genuinely universal in a way WebP is not yet.

Is image metadata preserved?

No. Re-encoding through a canvas discards EXIF data, which includes the camera model, capture time and any GPS coordinates. For publishing photos online this is usually a benefit — it strips location data you probably did not intend to share. If you need the metadata kept, this is not the right tool.

Why is there a 20-file limit?

Because everything is held in your device’s memory. Twenty images is comfortable on a laptop and safe on a phone; going much beyond that risks the browser killing the tab mid-batch, which would be worse than a limit. Files are compressed one after another rather than all at once for the same reason.

Related tools

Tools that pair well with this one.