What is the difference between this and the compressor?

The compressor changes quality at the size you give it. This resizes and re-encodes together, which is what a web image usually needs and produces a better result for the same bytes.

For photographs on a website, yes — meaningfully smaller than JPEG at the same quality, and supported everywhere current. Keep JPEG for anything that will be emailed or opened in older desktop software.

How small should a web image be?

Under about 200 KB for a large hero image and well under 100 KB for anything smaller. If a single image is over half a megabyte, resizing it is almost certainly the fix.

Does this change the image dimensions?

Only if you ask it to. Resizing is where most of the saving comes from, so it is offered first, but the original dimensions are kept if you prefer.

Image Optimizer

Resizes and re-encodes an image together, so a photograph destined for a web page comes out at sensible dimensions in an efficient format.

Runs in your browser — nothing is uploaded

Your image

Drop an image here

or choose a file — it never leaves your browser

Re-encoding is generationally lossy for JPEG and WebP — each pass loses a little detail. Always work from the original rather than re-processing a result.

Result

Your processed image appears here.

Need this as an API?

Why use it

Built to be genuinely useful

Both steps, in the right order

Resize then compress. Doing it the other way produces a worse image at the same file size, and it is the more common order.

Picks a format that suits the image

Photographs and flat graphics compress by different mechanisms, and the right format for one is the wrong one for the other.

Nothing is uploaded

The image is decoded and re-encoded by your browser. It never reaches a server, which matters for anything with a face, a document or a location in it.

Free, no watermark

No account, no queue, and nothing stamped across the result.

How it works

Three steps

1
Open the image.
2
Set the display width you need.
3
Download the optimised file.

Why images dominate page weight

On a typical page, images are the majority of the bytes — usually far more than the scripts everyone worries about. A single unoptimised photograph from a phone can outweigh the entire rest of the page several times over.

That shows up directly in the metric Google measures as Largest Contentful Paint, because the largest element on most pages is an image. Optimising the images is generally the single largest improvement available to a slow page, and it requires no code changes.

Format, briefly

For photographs, WebP is roughly 25–35% smaller than JPEG at the same visual quality and is supported by every current browser. AVIF is smaller again, with slower encoding and slightly narrower support.

For flat graphics, logos and screenshots, PNG is lossless and compresses runs of identical colour extremely well — and WebP's lossless mode usually beats it. The one rule worth remembering is that a photograph in PNG and a logo in JPEG are both the wrong way round, and both are common.

FAQ

Questions people ask

API access

Need Image Optimisation in Your App?

Add image optimisation to your own website, app, SaaS product or workflow through API access.

Tell us what you are building, how you plan to use it and the volume you expect. We will come back to you with availability, integration details and a quote for your usage.

Related tools

More image tools

Available tools are linked; the rest are in development.

Image Compressor Image Resizer Image Cropper Image DPI Converter AI Writer AI Summarizer AI Paraphraser AI Humanizer AI Grammar Checker AI Rewriter AI Translator AI PDF Summarizer

All Image Tools

Need a tool like this for your business?

We build internal tools, dashboards and automation that fit how your team works.

See Our Services