Compress JPEG
Shrink JPG and JPEG photos with a quality slider or an exact target size in kilobytes.
Compress JPEGCompress image
Works on JPG, PNG and WebP. Keep the format you started with, or convert on the way out.
- Free forever
- No signup
- Files never uploaded
- No watermark
- Unlimited files
Image compressor
JPG, PNG and WebP files are accepted, mixed together if you like. Paste from clipboard with Ctrl+V (Cmd+V on a Mac).
Keep the original format, or convert on the way out to compare which one is smallest.
Removes camera model, timestamps and GPS coordinates from the output.
Compress without changing the pixel size of the image. Turn this off in target-size mode to let the tool shrink the image when quality alone cannot meet your limit.
Ready. Add a file to begin.
Results
Quality mode · same as input output · 0 files
No files yet. Results will appear in this table as soon as you add one.
Your files are processed by your own browser. Nothing is uploaded to a server, so nothing can be stored, read or shared.
More tools
Other tools on this site
Each one runs in the browser the same way, with no upload and no account.
Compress PNG
Reduce PNG screenshots and graphics while keeping transparency and hard edges intact.
Compress PNGCompress WebP
Re-encode WebP images at a lower quality, or convert JPEG and PNG into WebP.
Compress WebPResize Image
Change pixel dimensions by width, height or percentage, with the aspect ratio locked.
Resize an imageJPG to PDF
Combine several photos into one PDF, reorder the pages and choose paper size and margin.
Build a PDFDocument Editor
Write a formatted document in the browser and export it to PDF, DOCX or HTML.
Open the editor
Specification
Technical specification
Every capability written out as text, including the ones where the answer is no. A specification that only listed the wins would not be worth reading.
| Attribute | This tool |
|---|---|
| Supported input formats | JPG and JPEG |
| Output formats | JPEG, PNG, WebP |
| Compression type | LossyJPEG discards detail permanently by design. PNG output is lossless but far larger for photographs. |
| Quality control | Adjustable, 10 to 100Maps directly to the encoder's quality setting. Moving it genuinely changes the output. |
| Exact output file size | Yes — target in KBThe encoder searches for the highest quality that fits under your limit, then reports the size it actually reached. |
| Resize / image dimensions | Yes — max width and heightAspect ratio preserved. The resizer page adds exact pixel and percentage modes. |
| Batch / bulk processing | UnlimitedFiles are encoded in parallel across a Web Worker pool and can be downloaded as one ZIP. |
| Maximum file size | No limit set by this siteBounded in practice by your device's memory, since each image is held uncompressed while it is processed. |
| EXIF and metadata | Stripped by defaultCamera model, timestamps and GPS coordinates are removed. You can switch it off. |
| Transparency / alpha channel | Not applicable to JPEGJPEG has no alpha channel. Choose PNG or WebP output if you need transparency. |
| Chroma subsampling control | Not availableThe browser's encoder chooses it and exposes no setting. We will not add a control that cannot affect the output. |
| Progressive JPEG control | Not availablecanvas.toBlob gives no control over progressive encoding. Use MozJPEG or ImageMagick if you need it. |
| Color profile handling | Converted to sRGBA browser canvas works in sRGB, so wide-gamut images are converted. Correct for the web, wrong for print masters. |
| Bit depth | 8 bits per channelThe maximum a browser canvas provides. HDR and 10-bit output need AVIF, which browsers cannot write. |
| Animation support | Not supportedA canvas decodes only the first frame of an animated file, so animation is out of scope rather than half-supported. |
| Where processing happens | In your browserNo upload endpoint exists in the compression path. Disconnect from the network after the page loads and it still works. |
| File retention | None — nothing is receivedThere is no copy to retain or delete, because no file is ever transmitted. |
| Watermark | NeverThe output contains your image and nothing else. |
| Account, quota or cost | NoneNo sign-up, no daily cap, no paid tier withholding a feature. |
| Browser support | Chrome, Edge, Firefox, SafariDesktop and mobile. Requires Canvas and Web Workers, which every current browser provides. |
How it works
How to compress image
Step 1: Add your images
Drag files onto the drop zone, click it to browse, or paste an image straight from the clipboard. Batches of any size are fine.
Step 2: Choose your settings
Pick a quality level, an exact target size in kilobytes, or a maximum width and height. Defaults are tuned for the web if you would rather not change anything.
Step 3: Download the compressed files
Every file is listed with its old size, new size and percentage saved. Save them one at a time or grab the whole batch as a ZIP archive.
Features
What this tool does
Batch processing
Queue as many image files as you like. A Web Worker pool runs them in parallel, so a large batch never freezes the page.
Real quality control
The slider maps straight to the encoder setting. Move it and the output genuinely changes — nothing here is cosmetic.
Exact target size
Ask for 200 KB and the encoder finds the highest quality that fits, then reports the size it achieved.
EXIF and metadata stripping
Camera model, timestamps and GPS coordinates are removed on the way out — worth doing before publishing a phone photo.
Format conversion
Write the result as JPEG, PNG or WebP whatever you put in, so you can test which is smallest.
Nothing is uploaded
The whole pipeline runs in your browser through the Canvas API. Disconnect your network after the page loads and it still works.
No watermark, no sign-up
The output is your image and nothing else. There is no account, no daily quota and no paid tier holding back a feature.
Works on mobile
The layout, the drop zone and the results table are all usable on a phone, and mobile browsers run the same encoder as the desktop ones.
In depth
Compressing any format
One tool, three formats, different behavior for each
This page accepts a mixed batch and treats each file according to what it is. Leave the output on "same as input" and a PNG stays a lossless PNG while a JPEG is re-encoded at your chosen quality — because applying one lossy setting to both would quietly ruin the screenshots.
If you would rather force everything into one format, set the output explicitly. Converting a mixed batch to WebP is usually the single best thing you can do for a website's image weight.
Which format should the output be?
- Photographs
- JPEG, or WebP if the images are going on a web page.
- Screenshots, logos, diagrams, text
- PNG, or lossless WebP. Never JPEG — lossy encoding puts haloes around every hard edge.
- Anything with transparency
- PNG or WebP. JPEG has no alpha channel and will fill transparent pixels.
- Mixed batch for the web
- WebP handles all of the above and is smaller than whatever it replaces.
Lossy and lossless compression are not the same thing
Lossless compression rewrites the file so every pixel survives exactly — decode it and you get the original back, byte for byte. PNG, GIF, lossless WebP and ZIP all work this way.
Lossy compression discards detail on purpose. JPEG converts the image to a frequency representation and throws away the high-frequency detail your eye is least likely to miss. That is irreversible, and it is how lossy reaches sizes lossless cannot: a photograph saved as PNG is routinely five to ten times larger than the same photograph as JPEG.
Neither is better. Photographs suit lossy encoding; screenshots, logos and line art suit lossless, because lossy encoders leave haloes around hard edges.
How quality maps to file size
The quality number is not a percentage. It is an index into quantization tables that control how aggressively detail is discarded, and its relationship to file size is steep and non-linear.
- 95–100 — near-original, often only 20–35% smaller. Rarely worth it.
- 80–90 — photography you care about. 50–70% smaller, no artifact at normal viewing distance.
- 70–80 — ordinary web images. Usually 70–85% smaller.
- 50–70 — visible softening in smooth areas; thumbnails survive it.
- Below 50 — blocking, ringing and color banding. Placeholders only.
Returns diminish fast at the top: 100 to 90 usually halves the file for no perceptible change, 90 to 80 saves far less. If you remember one number, use 80.
Why re-compressing a JPEG keeps degrading it
Every time a JPEG is decoded, edited and saved, the encoder re-runs quantization on data already quantized. Errors from the previous pass are treated as real detail and collect new errors on top. This is generation loss, and it only accumulates.
Re-saving at quality 90 restores nothing; it spends more bytes preserving the earlier pass's artifacts. Compress from the highest-quality original you have, and settle on one output size in a single pass rather than nudging quality down and re-saving.
Questions
Frequently asked questions
Every answer below is present in the page source, expanded, so it can be read without opening anything.
What is the difference between this page and the JPEG compressor?
This one accepts JPG, PNG and WebP together and adapts to each. The JPEG page is tuned specifically for photographs — JPEG-only input, JPEG-focused defaults and JPEG-specific guidance. Use this page for a mixed folder, and that one when everything you have is a photograph.
Can I mix formats in one batch?
Yes. Each file is handled according to its own type, and each row in the results table shows what it started as and what it became.
Do I have to pick a quality?
No. If you know the size you need, switch to target-size mode and give it a number in kilobytes — the encoder works backwards to reach it. There are also purpose-built pages for the common limits, from 20KB up to 1MB.
Will my PNGs lose quality?
Not if the output stays PNG — that path is lossless and the quality slider has no effect on it. It only becomes lossy if you convert the output to JPEG or WebP, and the tool labels that honestly rather than implying otherwise.
Is there a limit on how many files I can add?
None imposed by this site. The practical ceiling is your device's memory, since each image is held uncompressed while it is processed. For very large sets, the bulk compressor page is the same engine with copy written for that job.
Are my images uploaded?
No. Decoding and encoding both happen in this browser tab through the Canvas API. Load the page, disconnect from the network, and it still works.
Related topics
Explore the topic
Related concepts, formats and guides across the site. Every link goes to a page that covers the term properly.
Compression concepts
Exact size targets
Common problems
From the blog
Related reading
Longer explanations from the blog.
Practical Guides How to Compress Images for a Website Without Wrecking Them
Resize before you compress. Measured on one photograph: half the width at quality 80 produced a 16.4 KB file, while full width at quality 40 produced 20.6 KB and looked far worse. The order of operations matters more than the settings.
8 min read
Image Compression JPEG Quality Settings Explained: What the Number Actually Means
Quality 80 is not 80% of anything. It is an index into a quantisation table. Measured on one photograph: dropping from 100 to 90 removes 77% of the file and 4.2 dB of fidelity; dropping from 40 to 30 removes 17% and costs almost as much.
8 min read
Image Formats PNG vs JPEG: When to Use Each, With the File Sizes to Prove It
PNG stored the same photograph in 1274.1 KB where JPEG needed 67.5 KB — nineteen times larger. On a flat graphic PNG won. On a smooth gradient PNG lost to JPEG by a factor of two, which surprises most people.
9 min read