Image Tools

Image Compressor & Converter

Compress images in bulk and convert between JPG, PNG, WebP and AVIF. Tune quality and dimensions, then drag a slider to compare quality—all processed locally.

Local, zero upload Batch + folders MozJPEG / OxiPNG / libavif Free, no limits

Drop images here, or click to choose

Add multiple images at once, choose an entire folder, or just Ctrl+V to paste from your clipboard. Processing starts automatically with the current settings. Every operation runs in your browser.

JPG PNG WebP AVIF Batch processing
/ Before After Saving %

FEATURES

Compress, convert, resize and compare — all in one place

Focused on the last step before delivery: processed locally, batched efficiently, results you can verify.

01

Pro compression engines

JPEG, PNG, WebP and AVIF are encoded with MozJPEG, OxiPNG, libwebp and libavif — the same WASM engines Squoosh uses, running entirely in your browser.

02

True batch processing

Multi-select files, add whole folders or just drag them in — one consistent pipeline, and you can keep adding while it runs.

03

Format conversion

Convert freely between the four formats; transparency is preserved when exporting to WebP or AVIF.

04

Smart resizing

Scale by percentage or cap the maximum width/height with automatic aspect-ratio fit — one setting applies to every image.

05

Before/after comparison

A near-fullscreen dialog with a draggable divider lets you inspect detail and balance size against quality before downloading.

06

Background workers

Encoding runs in a Web Worker, so the page stays responsive even while large images are being processed.

Who is this for?

A quick self-check — if any of these sound like you, this tool fits:

Creators & bloggers

Batch-resize cover images and screenshots before publishing, without a design tool.

E-commerce sellers

Compress hundreds of product photos to AVIF/WebP at once — faster listing pages, less storage.

Web developers

Convert an entire assets folder to WebP/AVIF in one drop to cut page weight and improve Core Web Vitals.

Email & attachments

Shrink photos under a size limit before sending, without leaving your inbox tab.

Sensitive documents

IDs, contracts, medical scans — compressed locally, never uploaded anywhere.

Running out of storage

Batch-shrink a phone's camera roll export before backing it up or sharing it.

How to compress and convert images in bulk

1

Add images

Choose multiple images or a folder, or drag the files directly into the workspace.

2

Choose output rules

Each image keeps its original format by default. Select JPG, PNG, WebP or AVIF only when converting the whole batch, then set quality or dimensions.

3

Preview and save

Download files one by one or save every result in one ZIP, with automatic before/after size totals.

Image compression basics

A bit of background helps you pick the right format and dial in the settings.

Why only JPEG, PNG, WebP and AVIF?

These four cover the vast majority of bitmap images on the modern web: JPEG is the de-facto standard for photos, PNG handles lossless and transparency, WebP is the efficient modern format supported by every current browser, and AVIF is the next generation (typically 20-50% smaller than WebP). BMP and TIFF are uncompressed and not suited for the web; HEIC is Apple-specific with limited browser support; GIF's animation is outside the scope of "static compression". Focusing on these four covers 95%+ of everyday use cases.

Why are PNG files so large, and why do they compress so poorly?

PNG is lossless — it cannot throw away any pixel data, only reorganize it using ZIP-like algorithms. For photos (where neighbouring pixels are noisy and different), lossless algorithms have almost nothing to work with, which is why savings are often just 5-15%. To shrink a photo meaningfully you have two options: accept lossy encoding and switch to JPEG or WebP, or, if you truly need lossless, switch to lossless WebP or AVIF, which are usually 30-50% smaller than PNG.

Why can't the compression ratio go up forever?

Every image contains "information entropy" — essentially the colour data of its pixels. Lossy encoders (JPEG / WebP / AVIF) break through that limit by discarding details the human eye is less sensitive to: the lower the quality setting, the more is thrown away and the smaller the file, but the worse it looks. Lossless encoders can't drop any detail and can only find redundancy in existing data, so they hit a wall quickly. In other words: the compression ceiling is set by image quality, not by the tool.

When should I pick WebP and when AVIF?

WebP has the best compatibility (every browser since 2014) and encodes fast — a safe default. AVIF typically saves another 20-40% but is much slower to encode (a 4000×3000 photo can take 10-30 seconds) and very old browsers don't support it. For mainstream websites and CMS bulk processing, WebP is the safer pick; for static sites, technical blogs or situations where file size really matters (e.g. an e-commerce catalogue with hundreds of product shots), AVIF is worth the wait.

Does compression lose image information?

Two different things can be lost. Lossy formats (JPEG, lossy WebP, lossy AVIF) drop pixel data — how much is controlled by the quality setting; 75-90 is the usual "you can't really tell" range. Lossless formats (PNG, lossless WebP, lossless AVIF) keep every pixel but strip all metadata (EXIF, camera model, GPS location, capture time). That's actually a privacy bonus: cleaning that information before sharing is safer.

Why are some images slow to process?

It mostly comes down to three things: output format, image size and the queue. AVIF is the slowest to encode — a 4000×3000 photo can take 10-30 seconds, in exchange for a much smaller file; more pixels mean more time, so a 6000×4000 photo takes far longer than a screenshot; and images are processed one after another in the background, so each task waits for the previous one to finish. For faster results, switch to JPEG or WebP output, or cap the maximum width/height first.

Why does compression sometimes make the file bigger?

Three common causes: the source was already efficiently compressed (e.g. it was already WebP or AVIF), so re-encoding it in the same format just compresses an already-compressed result and often grows it; the image is very small (a few dozen KB — icons, thumbnails), where the encoder's header overhead can outweigh the pixel savings; or you converted lossless PNG to lossy JPEG at too high a quality setting, which preserves more detail. This tool detects that case automatically, keeps the original file and shows "Original kept" in the result row.

Best practices by scenario

Skip the parameter research — pick your scenario and copy the settings.

Scenario Format Quality / size Why
Blog / website illustrations WebP Quality 80–85, max width 1920 Best compatibility and 25-35% smaller than JPEG — the default choice in 2026
E-commerce product photos (bulk) AVIF Quality 75–80, max width 1600 Another 20-40% smaller than WebP; across hundreds of images the bandwidth savings add up
Social media sharing JPEG Quality 85, max width 2048 Universal compatibility; platforms recompress anyway, no point using newer formats
Logos / icons with transparency PNG or WebP Keep original size JPEG has no transparency; WebP is smaller but some older tools reject it
Email attachments JPEG Quality 75, max width 1200 Email often caps attachments at 5-10MB; small dimensions + moderate quality is safest
Photos before printing Original or JPEG quality 95 No resizing Printing needs ~300 DPI; over-compressing produces visible color banding
Sensitive images (IDs, contracts) WebP Quality 85 Processed locally with zero upload; compression also strips EXIF / GPS metadata

The four formats at a glance

Where each format came from, what it's good at and where it falls short.

JPEG

aka JPG · jpeg · jpe
1992

Joint Photographic Experts Group · JPEG committee

Lossy No transparency Universal support
Best for
Photos and realistic imagery
Avoid for
Screenshots, text, logos (produces artifacts)
Support
Every browser and device

PNG

1996

Portable Network Graphics · W3C / PNG Development Group

Lossless Transparency Larger files
Best for
Screenshots, logos, icons, transparent assets
Avoid for
Photos (5-10x bigger than JPEG)
Support
Every browser and device

WebP

2010

Web Picture format · Google

Lossy + lossless Transparency Animation
Best for
The modern default for web images
Avoid for
Very old device compatibility
Support
All major browsers since 2014

AVIF

2019

AV1 Image File Format · AOMedia (Google / Mozilla / Netflix et al)

Highest compression Slower encoding HDR support
Best for
Large product catalogs, size-sensitive static sites
Avoid for
When speed matters or old browsers must be supported
Support
Chrome 85+ / Firefox 93+ / Safari 16.1+

How it compares to other compressors

TinyPNG, Squoosh, Compressor.io and similar tools each have their focus. This one is positioned as "local batch + privacy first + zero upload".

Tool Uploads images? Batch support Formats Free quota Privacy
This tool No (runs in browser) Yes, whole folders JPEG/PNG/WebP/AVIF Unlimited ★★★★★
TinyPNG Yes, to server Up to 20/batch PNG/JPEG/WebP 500/month ★★★
Squoosh No (runs in browser) One at a time Many formats Unlimited ★★★★★
Compressor.io Yes, to server Up to 10/batch JPEG/PNG/WebP/SVG Free tier ★★

Based on each tool's public version as of 2026. If you need "upload and get it back from the cloud", TinyPNG and friends still have the edge; if you care about privacy or process lots of local files, running in the browser is a better fit.

Frequently asked questions

Are my images uploaded to a server?

No. Images are decoded, resized and re-encoded in your browser with the Canvas API. The file contents never leave your device.

Which input and output formats are supported?

Any common browser-decodable image works as input. JPEG, PNG, WebP and AVIF output is produced by the bundled WASM encoders instead of the browser itself, so WebP and AVIF export work in every modern browser.

Can a file end up larger than the original?

Not in the output. When the format stays the same and dimensions are unchanged, the original file is kept automatically if re-encoding does not make it smaller, marked as “Kept original”. Explicit format conversion and resizing always honor your chosen output (e.g. PNG to JPEG for compatibility may change the size either way).

Does compression preserve EXIF metadata?

No. Canvas re-encoding removes EXIF and other metadata, while applying the image orientation correctly. This also reduces file size and avoids exposing location or device details. Animated GIF files are processed as a static first frame.

Why did converting to PNG make the file larger?

PNG is lossless and is not ideal for compressing photos. For photos, screenshots and illustrations, JPEG or WebP usually produce smaller files. Use PNG when you need transparency or lossless pixels.

Can compression make an image sharper?

No. Compression reduces file size while preserving acceptable quality; it cannot restore lost detail. Keep the original and export a compressed copy for the web, social media or sharing.

Why offer both individual downloads and a ZIP?

Saving many files individually can trigger the browser’s multiple-download confirmation. A ZIP downloads one file and is more convenient for large batches.

Where do I download the processed images?

Once a file finishes, a download button appears on the right side of its result row — click it to save that one. You can also use the toolbar’s "Save individually" or "Download ZIP" for bulk downloads. If your browser asks whether to allow multiple file downloads, choose Allow; ZIP mode avoids that prompt entirely.

Related tools

You may also need these before or after compressing:

Free Image Editor

Crop, brighten, add watermarks first, then compress. Built on the open-source miniPaint — edit images online without sign-up.

Image format conversion

Current tool

Built into this tool: convert to WebP or AVIF while compressing for even smaller files.