Re-encode JPEG, PNG, WebP, or AVIF in the browser, or hunt a file-size cap with a quality search. Nothing is uploaded.
Runs in your browser · Nothing uploaded
Compression here means re-encoding pixels, not magically deleting bytes from the original bitstream. A JPEG compressor writes a new JPEG. A PNG compressor writes a new PNG. If you need a different container, that's Convert. If you need “under 200 KB for this form,” that's Compress to target size.
Quality sliders are honest: lower means more of the picture is thrown away. I won't label 40% “high definition.” Photographic JPEGs usually have room. Screenshots and type usually don't, those belong on the PNG tool or they will look chewed.
All of this runs in the tab. A passport scan, a medical still, a screenshot of a bank page, none of that needs to visit a compression site that also sells VPNs.
JPG compressor re-encodes a JPEG (or a decoded PNG) at a quality you set. Dimensions stay the same. It is the right first move for a photo that's a few megabytes too large for email. It is the wrong move for a screenshot of a spreadsheet.
PNG compressor writes a tighter lossless PNG. Pixels stay identical; the saving comes from working harder on the same data. Photos rarely shrink much this way. UI, diagrams, and screenshots often do.
WebP compressor encodes to lossy WebP from whatever you dropped. Transparency survives. If you already have a JPEG, this is often smaller at a similar look. If you already have a tiny PNG icon, leave it.
AVIF compressor is the slower, usually smaller cousin of WebP. Encoding in a browser tab takes longer than JPEG. Worth it for a hero image you will ship many times; annoying for a one-off attachment.
Compress to target size binary-searches JPEG quality until the file lands under the number you typed. Forms that say “max 500 KB” are the whole point. If quality alone can't get there, it also steps the pixel dimensions down and tries again. It won't invent detail to hit a size, and a tiny cap on a huge photo will look like a tiny cap.
Auto-optimize encodes JPEG, WebP, and AVIF at the same quality and keeps the smallest file. It is a size contest, not a promise that the picture is untouched. Transparency won't survive if JPEG wins.
Compress image to 20KB is for the harshest portal limits (tiny avatars, exam photo slots); expect the tool to shrink dimensions as well as quality.
Compress image to 50KB aims at the cap government and university forms love, and a cropped portrait usually fits where an untouched holiday photo won't.
Compress image to 100KB targets the common email and CMS soft limit, with enough room for a usable photo after one sensible re-encode.
Compress image to 200KB is the "attach it to the ticket" budget; most phone photos fit through the quality search alone.
Compress image to 500KB leaves room for a decent photograph, so the quality search is usually enough and dimensions stay put.
Compress image to 1MB is the generous form limit: you get the highest JPEG quality that still clears it, not a crushed thumbnail.
Compress JPEG to 50KB takes a file that's already a .jpg and re-encodes it under 50KB, with one more generation of JPEG loss as the price.
Compress JPEG to 100KB is the same JPEG-only page for a 100KB ceiling, aimed at camera and download files that are already JPEGs.
Compress JPEG to 200KB brings a heavy JPEG under 200KB; a phone original usually needs quality to drop and sometimes dimensions too.
Compress signature to 20KB is for scanned signature uploads: crop tight first, because blank paper around the ink costs bytes you don't have.
Convert changes the container and codec (PNG to JPEG, JPEG to WebP). Compress stays in one family and turns the quality or effort knob. Target size is still JPEG under the hood, it just picks the quality for you.
Sometimes a little, usually not enough to bother, and you pay with another generation of artefacts. If the file is already a mid-quality JPEG, resize it first or accept the size. If it's a 95-quality export from a camera, yes, there's fat to cut.
JPEG, WebP, and AVIF at the quality you set. The smallest blob wins. It doesn't measure SSIM. If JPEG wins, transparency is gone. Check the printed line before you ship the file.
There is no server to upload to. Each page is a static file, and the work happens in your browser. Your file is read from disk into memory, processed, and handed back as a download. Once the page has loaded you can disconnect from the network and it keeps working. The longer explanation
